Security and Data Handling

Access and confidentiality

• Named individual accounts are used for service access.
• Access is limited according to role and engagement need.
• Shared administrative credentials are avoided.
• Strong authentication and multifactor authentication are used where supported and required by the customer or system.
• Access is removed when no longer required.
• Personnel with access to customer data are subject to confidentiality obligations.

Data handling and minimisation

Auditbahn requests access only to systems and records needed for the agreed scope. Customer data is handled in customer-controlled systems where practical, and local exports are avoided unless needed for an agreed task.

Sensitive personal data should not be provided unless the engagement expressly requires and documents it.

Transmission, storage, and integrity

Web connections use encrypted transport where supported by the relevant service. Auditbahn-controlled systems are hosted in Hetzner’s Falkenstein, Germany location by default. A customer may request another available location, including a location outside the EEA, subject to documented instructions and applicable transfer safeguards.

Customer-selected platforms retain their own storage and encryption responsibilities. Any Auditbahn-controlled storage containing customer data must be identified in the service-provider schedule before use.

Material changes to compliance records are performed through authorised accounts. Available platform audit logs and approval records are preserved according to customer settings and instructions.

Availability and recovery

Availability, backup, and recovery for customer-selected systems are controlled by the customer and the relevant provider. Recovery arrangements for any Auditbahn-controlled system used for customer data are documented before use.

No recovery time, recovery point, uptime, or restoration commitment applies unless expressly approved in the agreement.

Incident response and provider governance

Suspected incidents are escalated to the incident owner. Access may be revoked, affected credentials rotated, and relevant evidence preserved during containment. Customer notifications are handled under the DPA, and findings and corrective actions are documented.

Auditbahn subprocessors are identified in the engagement-specific service-provider schedule. Customer-selected providers are recorded separately, and applicable international transfer mechanisms are documented in the Data Transfer Addendum.

Planned architecture

Bring-your-own AI is part of the Auditbahn vision. Under that model, a customer selects and contracts with its AI provider and configures its own account or endpoint. It is not represented as an implemented measure until provider routing, credential isolation, and data flows have been implemented and verified.