anonimize.

Taking your data with you

Export register

Version of 19 October 2026

1. Purpose of this register

This register describes which data you can export from Anonimize, in which formats and data structures, and how to do it. It belongs to Article 21 of the terms and conditions and to the European Data Act. We update it as soon as the export options change.

Provider: Digital Change Management Services BV (Anonimize), Galgestraat 109, 3300 Tienen, Belgium, enterprise number 0798.754.517, info@anonimize.eu.

2. Exporting yourself in the app

Processed documents

  • Result of a single document: TXT (UTF-8), PDF or DOCX.
  • All results of a processing run: a ZIP archive with one file per document in TXT, PDF or DOCX, optionally with the reversal key as a JSON file.
  • Restored text: TXT, PDF or DOCX.

Reversal keys

  • Reversal key of a processing run: a JSON object with the fields format (always anonymize-key), version, created_at, project_id, job_id and entries.
  • Each element of entries contains pseudonym (the replacement code in the result), original (the original text) and kind (the type of data).
  • Reversal keys and libraries of projects: JSON with the same structure.

Review and audit

  • Review evidence of a processing run: JSON, TXT or PDF.
  • The review evidence contains the hash of the content (SHA-256), the approval and the complete audit log with its hash chain.

Through the API

With an API key that has the export permission, the REST API returns the results of a processing run as a ZIP archive and the reversal key as JSON. With the read permission, you read results and their metadata as JSON. You can download the complete description of routes and data structures in the app on the API page as an OpenAPI 3.1 document (JSON).

Browser encryption

With browser encryption (BYOK), your browser decrypts and exports the results and reversal keys. The server cannot export that content in readable form.

3. Data on request

Data you cannot export yourself, such as the settings of your organisation and workspaces, users and roles, project settings, processing metadata, credit usage and project audit logs, we provide on request as JSON (UTF-8). Request an export via info@anonimize.eu. We deliver within thirty days.

4. Switching

If you want to switch to another provider or to your own environment, we cooperate in accordance with Article 21 of the terms and conditions. Exporting in the app costs no credits.

5. Limitations

  • Original files are not stored. The results, the reversal keys and the other data in this register can be exported.
  • Irreversible anonymisation has no reversal key.
  • Data deleted under the configured retention periods can no longer be exported.
  • A PDF or DOCX contains the text of the result, not the layout of the original document.

6. Formats and standards

  • JSON: RFC 8259, character encoding UTF-8.
  • TXT: plain text in UTF-8.
  • PDF: ISO 32000.
  • DOCX: Office Open XML, ISO/IEC 29500.
  • ZIP: the ZIP file format according to the PKWARE specification (APPNOTE).
  • API: REST over HTTPS, described with OpenAPI 3.1.