Ansvar AIService Portability Register
Last reviewed: 30 August 2026
This page is the online register referenced by Section 16 of the Terms of Service. It describes the current switching and portability surface for the Ansvar Service under Chapter VI of Regulation (EU) 2023/2854. Contact legal@ansvar.eu to start a switch, request an export bundle, nominate a destination provider, move to Customer-controlled infrastructure, or request erasure.
1. Switching procedure
- The Customer sends a written instruction that selects another provider, Customer-controlled infrastructure, erasure, or parallel use and identifies any authorised destination or additional provider.
- Ansvar confirms the Customer's authority, the requested scope, the available self-service exports, and any security steps for a destination provider.
- For a terminating switch or erasure request, the 30-day notice period under Section 5 of the Terms runs. For parallel use, no termination notice or transitional period applies; Ansvar confirms the requested scope and export channel.
- Ansvar supplies the exportable data and digital assets. During a terminating switch or parallel-use transfer, Ansvar continues all contracted functions and services and maintains a high level of security.
- For a terminating switch, the Customer or destination provider confirms retrieval and Ansvar reports successful switching and termination; Ansvar erases the data after the retrieval period. For erasure without a switch, Ansvar fully erases the exportable data and digital assets when the notice period ends and reports erasure and termination then. Parallel use leaves the Agreement in force.
Ansvar will provide the information needed to plan the exit before the Customer gives notice. A Customer may test the documented export interfaces during the Term without starting a switch. The Customer may also request repeat exports for parallel use without terminating the Agreement.
2. Data structures, formats, and interfaces
| Data or digital asset | Current interface or method | Export format |
|---|---|---|
| Organisation, seats, roles, entitlements, subscription, billing, and usage | Account area plus a provider-assisted switching bundle delivered through an authenticated, time-limited HTTPS download | JSON; CSV for tabular records; PDF for issued invoices |
| Uploaded documents and document metadata | Document-library list; provider-assisted original-file and segment export in the switching bundle | Original file format; JSON metadata; UTF-8 text and JSON for extracted segments |
| Workflow state, inputs, responses, findings, and evidence bindings | MCP workflow tools and provider-assisted switching bundle over HTTPS | JSON |
| Generated workflow reports | generate_report through the MCP interface | JSON; HTML, PDF, and DOCX where the Customer's Tier includes rendered reports |
| Audit-ledger receipts, anchors, signatures, timestamps, and retained interaction content | list_receipts and export_audit_package through MCP, or account-area export; available where the Customer's Tier includes the audit ledger | JSON, with encrypted receipt envelopes by default and optional authorised plaintext |
| Tenant settings, access assignments, and Customer-created connector or source configuration | Provider-assisted switching bundle over HTTPS | JSON; secrets and private cryptographic keys are omitted and must be replaced at the destination |
Provider-assisted records are delivered as a ZIP bundle containing export.json and the binary files named by its manifest. The complete field-level JSON Schema is published as switch-export-v1.schema.json. The schema covers the organisation, users, seats, entitlements, subscriptions, billing and usage records, documents and segments, workflows, reports, audit records, tenant settings, access assignments, connectors, sources, and the file manifest. A conforming non-production specimen is published as switch-export-v1.example.json. Fields absent from a Customer's Tier or history are represented by empty arrays or null values, not undocumented structures.
The Customer-facing machine interface uses the Model Context Protocol over HTTPS with OAuth 2.1 or a managed service credential. Tool inputs and outputs use JSON-compatible structures. Ansvar makes the same export interfaces and documentation available to the Customer and its authorised destination or additional provider on equal terms. The switching-bundle interface uses standard HTTPS GET with a time-limited bearer URL after Customer and destination-provider identity checks; it requires no proprietary client. During switching or parallel use, Ansvar reissues the bundle after Customer-authenticated requests without charge. The connection guide and the tool schemas exposed by the MCP endpoint describe the current interface. Ansvar does not charge the Customer or its authorised destination or additional provider to use these interfaces for switching or parallel use.
The relevant open interface specifications for the current Service are the Model Context Protocol specification, OAuth 2.1, HTTPS, and JSON. Ansvar will add an applicable harmonised standard or open interoperability specification published under the Data Act to this register and implement the required compatibility within the period set by law.
3. Restrictions and limits
- The Customer or destination provider must authenticate, protect export links and credentials, and provide a destination that can receive the selected formats.
- Short-lived document and report download links expire and can be reissued during the retrieval period.
- Ansvar exports data that it holds through completion of the switch, including input, output, and metadata generated during the notice and transitional periods. The Gateway does not retain ordinary query results unless a workflow, document record, or the Customer's audit-ledger Tier stores them.
- Ansvar does not promise functional equivalence between the Service and a destination service. The export omits the provider-internal categories listed in Section 16 of the Terms.
- Mandatory switching assistance is free. A separate written agreement may cover Customer-requested transformation or professional services outside that assistance.
Ansvar has identified no switching process for the current Service that is highly complex or costly. Ansvar charges no switching or data-egress fee and has no standard early-termination penalty. Standard service fees appear on the pricing page; an order identifies any fixed-term commitment before signature.
4. Infrastructure jurisdictions
| Function | Jurisdiction or routing posture |
|---|---|
| Primary Gateway, account, workflow, document, and audit-ledger processing | Finland, in Hetzner's Helsinki region |
| Off-site object storage and backups | Germany (Hetzner Falkenstein), France (Scaleway fr-par), and Ireland (Microsoft Azure North Europe); limited Microsoft support or telemetry access may occur from the United States |
| Edge TLS and traffic protection | Cloudflare EU edge with routing or processing that may occur in the United States |
5. Safeguards against conflicting third-country governmental access
Ansvar applies the following measures to non-personal data held in the Union:
- EEA primary hosting, encryption in transit and at rest, tenant isolation, least-privilege access, and access logging
- contracts and transfer terms with infrastructure providers, a reviewed sub-processor register, and data minimisation across providers
- legal review of each third-country request for authority, specificity, proportionality, and conflict with Union or applicable Member State law
- recognition or enforcement of a third-country court or authority decision only where an applicable international agreement provides the basis
- where no such agreement exists, separate review under Article 32(3) of Regulation (EU) 2023/2854: the third-country system must require stated reasons, proportionality, and a specific request; Ansvar must be able to raise a reasoned objection that a competent court or tribunal can review; and that court or tribunal must be empowered to consider the interests of the data provider protected by Union or applicable Member State law
- consultation with the competent national body where required, a reasoned objection or challenge where grounds exist, and disclosure limited to the minimum data permitted, and
- notice to the Customer before access or transfer unless law bars notice for the time needed to protect a law-enforcement activity
Ansvar reviews this page when an interface, format, fee, infrastructure jurisdiction, or relevant legal measure changes. Send corrections or portability questions to legal@ansvar.eu.