Trust
Security
Documents carry the things companies care about most: invoices, contracts, customer data. This page describes how we protect them, what we do not offer, and how to report a problem. For customer data, the binding version of these measures is Annex 2 of the Data Processing Agreement.
1. How your data is handled
- Traffic between you and the Service is encrypted with TLS 1.2 or higher, with HSTS. Database volumes are encrypted with AES-256, and backups are encrypted before they leave the server.
- Generated files are delivered through signed URLs that expire after 1 hour by default; you can choose up to 7 days. Anyone holding the link can open the file until it expires — treat links as secrets.
- Files are deleted automatically when their retention window ends: 7 days by default, adjustable up to your plan’s maximum, or no storage at all. The windows are listed in section 11 of the Terms of Service.
- Request logs are kept for 7 days by default on paid plans; the free plan keeps none.
- Every query is scoped to its workspace, backed by row-level security in the database and by automated tests that check the separation holds.
- We do not use your content to train machine-learning models.
- Customer Content is stored and rendered in the European Union, on servers in Germany.
2. Isolation of the renderer
Rendering executes input we cannot vouch for — your HTML, your CSS, and, in the URL endpoints, a third party’s web page. Renderers therefore run without root rights on a read-only file system, with a seccomp profile and the browser’s own sandbox, and keep no browser profile from one render to the next. They never see the credentials of storage you connect yourself. Outbound requests go through an egress proxy that blocks private, loopback, link-local and other internal addresses, which is also why the Acceptable Use Policy forbids trying to reach them.
3. Access and keys
- Staff use individual accounts with multi-factor authentication and get access only as far as their task requires. Administrative access is logged. To resolve a support request, staff can view your workspace read-only for a limited time, with a stated reason; each such session is recorded in the audit log.
- API keys are stored only as hashes; we cannot show you a key again after creation. Keys can be limited by scope, template and IP address, can expire, and can be rotated with a grace period in which the old key still works.
- Passwords are hashed with Argon2 and checked against the Have I Been Pwned breach list, which receives only the first five characters of a hash. Accounts support multi-factor authentication.
- Workspaces on Growth and above have an audit log of administrative actions.
4. Availability and backups
Databases are archived continuously with about one minute’s delay and backed up in full every night. Backups are encrypted and kept for 35 days, and restoring them is tested at least quarterly. Availability commitments for Pro, Scale and Enterprise are in the SLA. Current availability and incidents are on our status page, status.dynamicdocumentapi.com; planned maintenance is announced by email at least 7 days in advance.
5. Development and change management
Changes go through code review and automated tests before release. Continuous integration checks dependencies for known vulnerabilities and the code for leaked secrets. Development and staging are separated from production, and production data is not used for development.
6. Incidents
Security incidents are assessed, contained and documented. If a breach affects personal data we process for you, we notify you within 48 hours of becoming aware, as set out in section 10 of the DPA. If a breach affects your own account data and is likely to result in a high risk to you, we tell you without undue delay.
7. What we can give your procurement team
- Annex 2 of the Data Processing Agreement — the measures on this page as a binding contractual commitment.
- Written answers to your security questionnaire, once a year and free of charge.
- A signed copy of the DPA, including the Standard Contractual Clauses, and of the SLA: sign them in the dashboard under Settings → Agreements and download the PDF.
We hold no external certifications such as SOC 2 or ISO 27001, and we cannot provide third-party audit or penetration test reports.
8. Reporting a vulnerability
If you find a security problem, tell us at security@dynamicdocumentapi.com. Include steps to reproduce and what you think the impact is. We confirm receipt within 2 business days, keep you posted, and will credit you when the issue is fixed if you want that.
Please test only against your own workspace, do not access other people’s data, do not run denial-of-service or spam tests, and give us reasonable time to fix things before publishing. We will not take legal action against researchers who follow these rules. There is no bug bounty: we do not pay for reports.
Change history
| Version | Date | Change |
|---|---|---|
| 1.2 | 8 October 2026 | Section 4: the public status page |
| 1.1 | 5 October 2026 | Version in force at launch |