Snapshot 262094

Document
Security page
URL
https://www.mindee.com/platform/security
Fetched
HTTP status
200
Content type
text/html; charset=utf-8
Fetch mode
static
Size
130563 bytes
SHA-256 (raw)
15ac6502c5e2183278e607fdf1c53d46fcdce500c05d6f191f7eca274573c1e4
SHA-256 (normalized text)
7ebedd918202c9334c0b5c1ee5a1059f79122bba72ae3e8c585d519aff4e251d

Normalized text

Scripts and page chrome removed; this is what change detection compares.

Your privacy is our main priority
Mindee never sells or shares your data without your agreement. We are independently certified to the world's top security standards: SOC 2 Type II, GDPR and CCPA.
View compliance report
Read our DPA
invoice_0423.pdfprivacy mode · on
Processing zoneEU
Storage duration6 hours
Used to train AINever
Document received
Sent to the API by your application
09:41:02.118
Processed in your zone
Stays in the region you selected
09:41:02.904
Extracted data fetched
"total_amount": 1284.50, "currency": "EUR"
09:41:03.511
Extracted data deleted
Removed from Mindee as soon as it was fetched
09:41:03.512
Not used for AI trainingInputs, outputs and metadata
SOC 2
SOC 2 Type II
Certified
GDPR
GDPR
Compliant, DPA for EU customers
CCPA
CCPA
Compliant
LIVE
Monitored by Delve
Continuous compliance
Your documents, under your rules
Where your data is hosted, where it is processed, how long it stays and what it is never used for. Every one of these is a setting or a commitment, not a promise in small print.
Hosted on AWS high-security facilities
Enterprise-grade security
All data resides in AWS' high-security facilities, featuring continuous on-site security, surveillance systems and comprehensive monitoring.
Your files are not used for AI
We never use your inputs, outputs or metadata to train, fine-tune or improve any AI model without your agreement.
View our DPA
Processing zone
Documents are processed in Europe.
Location storage control
The processing zone setting determines the geographic region where your document data is processed.
Storage duration6hours
Extracted data is deleted 6 hours after processing.
Duration storage control
The storage policy setting defines how long extracted data is retained in Mindee's systems before being deleted.
Available for all users
Privacy mode in a single click
With privacy mode, you can process an auto-deletion after your data has been successfully fetched. Nothing extracted stays on Mindee once your application has it.
Delete data as soon as it is fetched
To enable it
Select a model
General Settings
Storage Policy
Delete extracted data
Toggle on
Storage PolicyGeneral Settings
Storage duration (hours)
6hours
Number of hours Mindee will store extracted data before deleting it.
Delete extracted data when fetched
When enabled, extracted data is automatically deleted after it has been fetched.
09:41:02POST/extraction202 queued
09:41:03GET /inference200 fetched
09:41:03DEL extracted datadeleted on fetch
Independent auditing is mandatory, certifying all the efforts made to secure customer data
Monitored by Delve
GDPR compliant
Our operations fully align with GDPR data retention protocols, and we maintain data processing agreements (DPA) for all EU-based customers.
EU customers
DPA available
SOC 2 Type II
Our SOC 2 Type II certification validates our adherence to critical criteria including System Security, Availability, Processing Integrity, Confidentiality and Privacy.
Security
Availability
Processing integrity
Confidentiality
Privacy
CCPA compliant
Our entire operational framework, including policies and procedures, maintains strict compliance with CCPA requirements.
Policies
Procedures
Need the details for your security review? Our compliance report covers every control above.
View compliance report
Team members
Member	Role	Status
CL
Camille Laurentcamille@acme.com
Active
SO
Sam Okaforsam@acme.com
Active
JL
Jordan Leejordan@acme.com
Active
IM
Inès Moreauines@acme.com
Invited
Available for Pro plans and above
Role-based access control
Manage team permissions with precision. Define exactly who can view, edit or manage your API resources to ensure total environment security.
Share your workspace with granular security options
To set it up
Workspace Settings
Organization
Members
Assign role
FAQ about security
Can't find what you're looking for? Our team answers within one business day.
Talk to an expert
About Mindee
How can I secure and limit access to the API for different members of my team ?
Our platform provides Role-Based Access Control (RBAC) to give granular security. You can assign specific roles—such as Owner, Admin, or Member to different users. This functionality ensures that a team member can view models or analytics without having the permission to delete the entire organization.
‍
Specifically about medical sector, do you have HIPAA certification ?
We focus our efforts on SOC 2 Type II and GDPR/CCPA considerations.
If you need an official HIPAA/BAA position, you’ll need to contact our support team.
Depending on your needs, we can provide customized compliance support.
What security certifications do you have ?
We maintain a robust security and privacy framework, anchored by our SOC 2 Type II certification, which validates the long-term effectiveness of our internal controls.
We are also fully compliant with global privacy regulations, including GDPR and CCPA, ensuring the highest standards of data protection.
Additionally, our infrastructure is HIPAA-eligible, and we can support healthcare-specific requirements and Business Associate Agreements (BAAs) upon request.
How long are my data stored ?
Your extracted data is stored 12 hours by default (configurable 1–24 hours).
In your model’s storage policy, storage duration sets the exact number of hours Mindee keeps the extracted results before automatic deletion. After that, any GET request using the inference ID returns 404. You can also enable the “Privacy Mode” (delete extracted data when fetched) to delete results immediately after you retrieve them (via a GET request) or after they’re delivered to you through a webhook.
This policy applies when sending documents via API calls.
Where are my data stored and how are they protected ?
Your data is processed/stored in the region you choose per model, and access is time-limited.
In model settings, you can set a processing zone: No preference (by default), Europe, or United States.
This controls where your document data is processed and is meant to support data residency needs.
For protection, we explicitly state ni our documentation that RAG resources are encrypted in transit and are isolated within your model (not shared across customers). Integrations, webhooks and source URLs must be HTTPS/TLS.
Do you store the data from the documents you process ?
Yes by default, Mindee stores the extracted results for a limited time.
Mindee’s storage policy controls how long extracted data (the processing output) is retained when you send documents via API calls. The default retention is 12 hours, configurable from 1 to 24 hours, and data is deleted once that duration expires.
You can also enable “Privacy Mode” in your model settings, to permanently delete the extracted data immediately after you retrieve it (GET request) or after it’s delivered via webhook.
Is my data secured and protected during the conversion process?
Yes, your data is highly secured and protected during the entire conversion process. As an enterprise-grade OCR solution, Mindee takes data privacy very seriously. Here are the key security measures in place:
Certified compliance: Mindee's infrastructure is SOC 2 Type II certified and fully GDPR compliant, ensuring strict industry standards for data protection.
Encryption: All documents and extracted data are fully encrypted both in transit (during the API call) and at rest.
Data localization: You have control over where your data is processed, with the option to host and process your data on either EU or US servers.
Strict privacy: Mindee respects data confidentiality. Your processed documents are not shared with third parties, and your private data is not used to train global AI models.
In short, your sensitive documents are processed in a secure, isolated environment and remain completely under your control.
How is data security ensured during transfer between the API and an ERP/CRM?
Every interaction between your ERP/CRM and the Mindee API is protected by industry-standard TLS (Transport Layer Security) encryption. This means that data is encrypted before it leaves your server and can only be decrypted by Mindee. It prevents "Man-in-the-Middle" attacks, ensuring that even if data were intercepted,they would be unreadable.
‍
In addition, our legal team aligns our security protocols with global standards to ensure your integration meets strict regulatory requirements:
GDPR Compliant: Fully aligned with European data protection regulations, ensuring the highest level of privacy for PII (Personally Identifiable Information).
SOC2 & ISO Ready: Our infrastructure is hosted on Tier-1 providers (AWS) that maintain the highest physical and logical security certifications.
Authentication: Access is strictly controlled via secure API Keys and environment-specific credentials, allowing your IT team to revoke access instantly if a breach is suspected on your side.
Process sensitive documents with confidence
Start extracting data with SOC 2 Type II security, privacy mode and full control over where and how long your data lives.
Try Mindee for free
Read our DPA
14-day free trial
No credit card required