Data Processing Policies

Mindee provides flexible options to help you manage how and where your document data is processed, stored, and deleted.

The following features help ensure compliance with your regional regulations and allow control over data retention and privacy.

Processing Zone

This feature is not available on all plans.

The Processing Zone setting determines the geographic region where your document will be processed. This option can impact compliance with data residency requirements (e.g., GDPR, CCPA).

The processing zone can be set for all models in the organization settings page.

If you need to set the processing zone for a specific model, it can be accessed on the model's "General Settings" page.

Available options:

No Preference (Default) Mindee will automatically route your documents to the closest or most available processing region. This is the recommended default for optimal performance and availability, but your data may be processed in Europe and in the United States.
Europe Forces all data processing to occur exclusively within data centers located in Europe (EU). Recommended for organizations subject to GDPR or EU data residency policies.
United States Forces all data processing to occur exclusively within data centers located in the United States. Recommended for organizations subject to U.S. data governance or compliance policies.

This is only a zone for processing, not extraction or analysis support.

You can send documents from any country to the Mindee API!

Storage Policy

This feature is available on all plans.

This section applies when sending documents via API call.

The Storage Policy defines how long extracted data (i.e., the results of document processing) is retained in Mindee’s systems before being permanently deleted. The original uploaded file is never stored to disk.

Storage Duration

Defines the exact number of hours that extracted data is stored.
Default: 12 hours
Minimum: 1 hour
Maximum: 24 hours

Data is automatically deleted as soon as the storage duration expires.

During this time, you may make GET requests to retrieve the payload using its inference ID. After this period, any calls to the inference ID or job ID will result in a 404 error.

This setting helps balance between accessibility of results for your workflow and minimizing retention for privacy and compliance.

Delete Extracted Data When Fetched

When disabled, data will be retained until the configured Storage Duration elapses. (Default)

When enabled, extracted data is automatically and permanently deleted immediately after:

the inference is accessed using a GET request (usually when polling)
the inference is successfully sent to your server via a webhook

The data will be deleted regardless of the Storage Period setting.

Once the Storage Period is passed, the data will be deleted regardless of whether this option is enabled. Once the data are deleted, any calls to the inference ID will result in a 404 error.

This option is recommended for workflows where:

you only need to access the data once
you are storing the data from each API call in your system
there are operational requirements that specify a Zero Data Retention policy

Best Practices

For testing and setup: Use a longer Storage Duration (up to 24 hours) to allow time to check and validate processed results. This is particularly useful when setting up a webhook workflow.
For general production use: Set a relatively short Storage Duration (3-5 hours).
For privacy or Zero Data Retention: Always enable Delete When Fetched. Best to also set a short Storage Duration (1 hour) in case of failed calls (i.e. network failure on GET).
For compliance: Select the Processing Zone that matches your legal and regulatory requirements.

Example Configuration

Processing Zone: Europe
Storage Duration: 4 hours
Delete When Fetched: Enabled

With this setup, all documents are processed in EU data centers, results are stored for a maximum of 4 hours, and deleted automatically once you first download them.

Configure the Data Processing Policy

This feature is not available on all plans.

Frequently Asked Questions

Does Mindee use my documents for training?

No, all documents are the property of their organization and are not used for training Mindee models.

We can only use your documents internally with your explicit knowledge and prior consent. This is limited to using your documents to help resolve a ticket you opened with our support team.

Files sent by API are not saved to disk.

Are my documents or their data shared or sold to 3rd parties?

No, never.

Documents and their data are only accessible to the users of the organization that the model belongs to.

Mindee never sells documents or their data to 3rd parties.

Files sent by API are not saved to disk.

Can I request data deletion at any time?

Yes. You can request full or partial data deletion at any time by using the deletion features available in your model settings, organization settings, or account settings.

Mindee ensures that your data is securely and permanently removed upon request.

You can also contact our support team if you are unsure.

Can you sign a BAA for HIPAA compliance?

We can, however these agreements are limited to enterprise users.

If you have an enterprise plan, contact your dedicated account manager for more information.

Where can I find the Data Processing Agreement and Terms of Use?

These are available on our website: