Confidentiality by design
Your data stays yours.
Certification bodies work under confidentiality obligations to their clients and accountability to accreditation bodies. Crosscheck is built to operate inside both.
Three security boundaries
A clear chain of custody for every record.
01 / Ownership boundary
Ownership stays with the provider.
Every company retains ownership of the data it provides to Crosscheck. Uploading or creating records in the service does not transfer those rights.
- Evidence, records, templates, findings, reports and procedures remain the property of the company that provides them.
- Crosscheck acts only as the AI service provider. It processes the data on the certification body's documented instructions and acquires no ownership rights.
- Nothing is shared with scheme owners, accreditation bodies, other certification bodies or another party without written authorization.
02 / Processing boundary
Choose where processing happens.
Run Crosscheck in an isolated enterprise cloud environment or, where confidentiality or accreditation requirements demand it, inside infrastructure controlled by your certification body.
- Hosted files are stored on Google Cloud Platform and platform metadata on Neon, with customer environments logically isolated.
- Data is encrypted at rest using AES-256 and protected in transit.
- Enterprise AI agreements exclude training on customer data and limit retention to the processing itself.
03 / Decision boundary
People remain accountable.
Crosscheck prepares and records the work. Authorized auditors and technical reviewers retain professional judgment and every final decision.
- AI assistance cannot approve findings, close non-conformities or make certification decisions.
- Report templates, checklists, scheme interpretations and reviewer conventions are configured per certification body.
- Every AI-assisted step is logged and reviewable, with documentation available to support ISO/IEC 17065 and ISO/IEC 17021 accreditation assessments.
- Operator preparation and certification-body services run as separate instances with separate data.
Deployment comparison
Cloud or on-premise. The boundary stays visible.
Choose a managed cloud environment or a dedicated deployment for confidentiality clauses and accreditation requirements that demand customer-controlled infrastructure.
Swipe to compare both deployment models
| Control | Enterprise cloud | Dedicated / on-premise |
|---|---|---|
| Data location | US customers use US servers. European customers use EU servers. Files are held on Google Cloud Platform and metadata on Neon. | Runs inside customer-controlled infrastructure in the location selected by the certification body. |
| AI processing | Enterprise AI services operate under terms that exclude training on customer data and limit retention. | Private models run under customer control. No third-party AI provider is involved. |
| Isolation | Each customer is logically isolated. Data is encrypted at rest with AES-256 and protected in transit. | No data leaves the dedicated environment. Isolation follows the customer's own network and access controls. |
| Operational access | Administrative access is protected by multi-factor authentication and least-privilege controls. | Access policies, credentials and operational permissions remain under customer control. |
| Availability | Managed as the standard Crosscheck service. | Available on request where contractual or accreditation requirements demand it. |
| Compliance baseline | GDPR, ISO 27001 and SOC 2 compliant. | |
Security and procurement review
Bring your confidentiality requirements.
We can walk your security, accreditation and procurement teams through the processing boundary and the deployment model that fits your obligations.