Data Privacy
Docamint is designed with strict data-handling boundaries. Your templates and payloads are processed securely and never used for training, analytics, or secondary purposes.
Data
Your data stays your data
Templates, JSON, and XML payloads are used only for document generation. They are not inspected,
analyzed, or used to train any models. No customer data is shared with third parties.
Security
Encryption
All traffic is encrypted in transit (HTTPS/TLS). Templates and any data you choose to store in Docamint Cloud
are encrypted at rest in tenant-specific storage.
Isolation
Environment isolation
Customer environments are isolated. Self-hosted deployments ensure that all data remains entirely within
your own infrastructure and network boundaries.
Retention
Data retention
Docamint does not need to retain your payloads: you can send the template and data with each request and keep
nothing in Docamint. If you store templates in Docamint Cloud, you control how long they are kept. In
self-hosted deployments you control all retention.
Access
Access control
User authentication and access roles are handled by your calling application. Docamint authenticates each API
request with your API key, and processes only the data that request supplies.
Compliance
Compliance posture
Docamint follows strong security and privacy practices. While Docamint does not claim formal certifications
such as SOC 2 or PCI, it is designed with enterprise-grade controls and can be deployed in environments
that meet your compliance requirements.
Summary
Privacy Summary
Docamint’s privacy model is simple:
- No training on customer data
- No analytics on payloads
- No sharing with third parties
- Encrypted in transit and at rest
- Tenant-specific storage isolation
- You control what is stored and for how long
Whether hosted or self-hosted, Docamint ensures that your data remains protected and under your control.