BY NUMBER7 AIOpen AIdaptIQ ↗Book a demo →Security & trust
Review access, data handling, model providers, retention and accounting-system permissions before representative documents are transferred.
Review the facts for the proposed deployment.
Security review follows the evidence through intake, processing, storage, authorized access, integration and retention or deletion. The proposal must identify which controls and responsibilities apply to the selected deployment.
Review facts and supporting documents
Scroll across to compare the columns
| Area | Published status | What to confirm for the deployment |
|---|---|---|
| SOC 2 / ISO 27001 | Not stated on this website | Current certification status and available evidence. |
| Authorized access | Reviewed for the operating model | Authentication, roles, administrators and permitted actions. |
| Data separation | Reviewed for the operating model | Tenant, client and legal-entity separation, including integration context. |
| Storage and encryption | Deployment-specific | Storage location, processing path, encryption and backup access. |
| Retention and deletion | Deployment-specific | Retention period, deletion trigger, backup handling and deletion evidence. |
| Models and subprocessors | Confirmed during review | Providers, processing locations and terms governing training use. |
| System-of-record access | Integration-specific | Credentials, access scopes, permitted writes and returned outcomes. |
| Payment execution | AIdaptIQ does not execute payments | Payment recording and returned payment state are distinct from moving money. |
The website does not establish a universal certification, storage location or subprocessor list. Request the evidence that applies to your proposed deployment.
Follow the evidence
Authorized sources and client resolution.
Locations, isolation, access, model terms and retention.
Credential scopes, permitted action and acceptance.
Authority and integration
Scroll across to compare the columns
| Boundary | Required decision |
|---|---|
| Reviewer access | Who can see the client evidence, change a value or resolve an exception? |
| Approval authority | Who can approve the configured accounting action, and what records the decision? |
| System integration | Which credentials and scopes are needed, and what is returned after the action? |
| Failure recovery | Who handles retries, duplicate protection, rejected outcomes and reconciliation? |
| Administration | Who can change policy, access or integration settings, and how is that change recorded? |
Request the review package
Share your deployment requirements and the security documents your team needs. The review should cover data flow, access, encryption, model processing, subprocessors, retention, deletion and integration permissions.
General website enquiries collect contact and workflow context. Financial documents follow the agreed customer data-processing and transfer path.
Security and data handling
| Area | Evidence / scope | Review question |
|---|---|---|
| Hosting and regions | Deployment-dependent | Confirm the hosted or customer-hosted model, locations and responsibilities in the review. |
| Encryption | Request verification | Confirm transport protection, encryption at rest and key ownership for the selected environment. |
| Isolation and access | Request verification | Request the tenant/entity boundaries and who can view, change or approve evidence. |
| Authentication and roles | Deployment-dependent | Confirm roles and authentication. SSO availability is not established by these public materials. |
| Model training use | Contract review | Confirm provider terms and customer-data use in the applicable data-processing agreement. |
| Subprocessors | Request disclosure | Request the providers that process the agreed workflow and any region restrictions. |
| Retention, deletion and export | Deployment-dependent | Agree duration, deletion procedure, access and export before sample transfer. |
| Audit logs and incidents | Request verification | Request log scope, customer access and incident responsibilities. |
| Customer-hosted responsibility | Scope agreement | Agree infrastructure, patching, credentials, backups and support ownership. |
| DPA, NDA and certifications | Security review | Request legal documents and current certification evidence. These materials do not establish SOC 2, ISO 27001 or HIPAA compliance. |
The website enquiry sends contact and workflow details through the configured intake service. It has no document upload field. Product security controls require the deployment’s evidence and agreed terms.
Request a security reviewScope and action
Request the verified integration contract and hosting scope. Public guidance is not a validated machine-readable specification or a promise of SDK availability.
Action: Scope agreement required.
Read the workflow scopeThe recorded product-owner confirmation applies to the named capabilities. Deployment scope, integration permissions and approval requirements are agreed separately.