Skip to main content
Dynamic Document API
Product
HTML to PDF API PDF Generation API Image Generation API PDF Template API URL to PDF API Markdown to PDF API Enterprise All features
Use cases
Invoice PDF API E-invoicing API Receipt Generation API Report Generation API Certificate Generation API Document Generation API All use cases
Tools Developers Pricing
EnglishEN DeutschDE
Sign in Start free

Product

HTML to PDF API PDF Generation API Image Generation API PDF Template API URL to PDF API Markdown to PDF API Enterprise

Use cases

Invoice PDF API E-invoicing API Receipt Generation API Report Generation API Certificate Generation API Document Generation API
Tools Developers Pricing
EN DE
Sign in Start free

Legal

Privacy Policy

Version 1.9 · Last updated 17 November 2026

This policy explains what we do with personal data when you visit this website, write to us, create an account or use the API. A short version: we collect what we need to run the Service and bill for it, we keep customer documents only as long as you set, we do not sell data, and we do not train models on your content.

On this page

  1. Who is responsible
  2. Two different roles
  3. What we process, why, and on what basis
  4. Where data is processed
  5. Who receives data
  6. International transfers
  7. How long we keep things
  8. Your rights
  9. Cookies and storage on your device
  10. Security
  11. Children
  12. United States: state privacy rights
  13. Changes

1. Who is responsible

Controller within the meaning of the GDPR: N.M.M. Noble Minds Media Ltd, Grigori Afxentiou 7, 6023 Larnaca, Cyprus, registration number HE 453611. Full provider details are in the legal notice.

For any question about data protection, and to exercise your rights, write to privacy@dynamicdocumentapi.com.

You can complain to a supervisory authority. Ours is the Office of the Commissioner for Personal Data Protection of the Republic of Cyprus; you may also complain to the authority where you live or work.

2. Two different roles

Keeping these apart matters, because different rules apply.

  • We are the controller for data about you as a visitor, account holder or contact: registration and login, billing contact data, emails and support conversations, usage of the Service, security logs and marketing you asked for. That is what this policy covers.
  • We are a processor for whatever is inside the documents you generate — the payload you send to the API, the templates you build, the files we return. We process that only on your instructions, under the Data Processing Agreement. If you are an employee, customer or recipient of one of our customers and have a question about such data, please contact that customer; they decide what happens to it.

3. What we process, why, and on what basis

DataPurposeLegal basis
Name, email, password hash, language, time zone, marketing preference; second-factor credentials where you set them up; tokens of integrations you connect Creating and running your account Art. 6(1)(b) — performance of a contract
Name, email and account ID from Google, GitHub or Microsoft Signing you in with that account, if you choose to Art. 6(1)(b)
IP address and browser signals during sign-up and login Telling people from bots (Cloudflare Turnstile) Art. 6(1)(f) — legitimate interest in protecting accounts from automated abuse
Billing contact, billing address, tax ID, subscription status Charging for paid plans and keeping tax records. The seller of paid plans is Link (see section 5); we never see card data Art. 6(1)(b) and (c) — contract and legal obligation
API key metadata; for each request and render: time, endpoint, template, pages, size, status, duration, IP address Delivering renders, counting usage for your plan, diagnosing errors, protecting against abuse Art. 6(1)(b) and (f) — contract and our legitimate interest in a working, secure service
Request logs in your workspace: method, path, headers with secrets removed, IP address, status; request bodies only if you switch them on Letting you trace and debug your own requests Art. 6(1)(b)
Request payloads and generated files Producing the document you asked for Processed for you as processor — see the DPA
Error reports: stack trace and technical context of the failed request Finding and fixing bugs Art. 6(1)(f) — legitimate interest in a working service
Emails you send us, with attachments Answering you and keeping a record of what was agreed Art. 6(1)(b) and (f)
Security and audit logs: actions in your account, IP address, browser, country Detecting attacks, investigating incidents, showing you who did what Art. 6(1)(f) and (c)
Email address for product and marketing mail Service notices; newsletters only if you asked for them Art. 6(1)(b) for service mail, Art. 6(1)(a) — consent — for marketing, withdrawable at any time
Connection data when you visit this website: IP address, browser, page, time Delivering the page and defending against attacks. Cloudflare does this for us; we keep no server logs of the website Art. 6(1)(f)
Only if you agree in the cookie banner: pages viewed, time, referrer, device and browser, approximate location (Google Analytics), on this website and in the dashboard. In the dashboard also the events sign-up (with the method, e.g. email or Google), start of checkout (plan, billing interval, price) and purchase (plan, amount, currency, invoice number) Understanding how the website and the dashboard are used and which channels lead to sign-ups and purchases, so we can improve them Art. 6(1)(a) — consent, which you can withdraw at any time; for the cookies Art. 5(3) of the ePrivacy Directive (in Germany § 25(1) TDDDG)
Only if you agree in the cookie banner, in the dashboard: a recording of how you use it (session replay with PostHog): clicks, mouse movements, scrolling, page changes and the layout of the pages with the dashboard’s own text (menus, buttons, notices, error messages), numbers, amounts and dates, and the plans with their prices, with all other text and every input made unreadable and images, editors and document previews left out; your user ID; browser, device and screen size; the plan of the workspace you are viewing; the events sign-up (with the method, e.g. email or Google), checkout started (plan or render pack, billing period, list price) and return from checkout (completed or cancelled) Finding where the dashboard is hard to use and why a sign-up or purchase fails, and fixing it Art. 6(1)(a) — consent, which you can withdraw at any time; for storing its IDs in your browser Art. 5(3) of the ePrivacy Directive (in Germany § 25(1) TDDDG)
How you found us, handed to the sign-up: the page you came from, our page you landed on, campaign parameters in the address, the date. Only if you agree in the cookie banner is the first visit remembered in your browser; otherwise the sign-up link carries only what the page you click on knows Knowing which channels bring customers Art. 6(1)(f) — legitimate interest; for remembering it in your browser Art. 6(1)(a) and Art. 5(3) of the ePrivacy Directive
Only if you click play on a video: IP address, browser and device details, the page you are on, and what YouTube stores in your browser Showing our videos, for example in the tutorials, on the page (YouTube, section 5) Art. 6(1)(a) — consent, which you give by clicking play; for cookies and similar technologies Art. 5(3) of the ePrivacy Directive (in Germany § 25(1) TDDDG)

Where we rely on legitimate interests, we have weighed them against your interests; you can object under section 8.

The PDF tools stay in your browser. Files you open in the free PDF tools on this website are processed on your device and are not uploaded to us or anyone else.

No training on your content. We do not use customer documents, templates or payloads to train machine-learning models, neither our own nor anyone else’s.

No sale of data. We do not sell personal data and we do not share it for cross-context behavioural advertising.

4. Where data is processed

We run the Service in the European Union. Servers and file storage are in data centres in Germany; application logs and encrypted backups stay in the EU. Your account, request payloads, templates and generated files are stored and rendered in Germany. There is no other region yet; if we add one, you will choose it per workspace, and we will update this policy before it opens.

Some service providers process data outside the EU, for example for payments or email. Section 5 and the sub-processor list say who and where; section 6 explains the safeguards.

5. Who receives data

Inside our company, only people who need access for their work get it, under confidentiality obligations. Beyond that, data goes to service providers who process it on our behalf: hosting, delivery and protection of the website and the Service, email, and error monitoring. The current list, with purpose and location, is on the sub-processors page; we announce new sub-processors for customer data there at least 30 days in advance.

Some recipients act on their own responsibility:

  • Payments. Paid plans are sold through Stripe Managed Payments; the seller (merchant of record) is Sold through Link, LLC, a Stripe company (“Link”). Link collects your payment details at checkout and processes them under its own privacy policy. We receive your billing contact, billing address, tax ID and subscription status.
  • Sign-in with Google, GitHub or Microsoft. If you choose it, that provider confirms your identity to us under its own privacy policy.
  • Stock photos. If you use the image search in the template editor, your browser loads the preview images directly from Unsplash or Pexels, which therefore see your IP address.

Google Analytics. Only if you agree in the cookie banner, Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland, processes usage data of this website and of the dashboard for us as our processor; Google LLC in the United States may receive it (section 6). Google Analytics 4 does not store IP addresses. Google signals and all advertising features are switched off. So that a purchase can be counted even though it is confirmed by the payment provider and not in your browser, we keep the pseudonymous Google Analytics ID of your browser and your choice in the banner with your account, and our server reports the purchase to Google under that ID (Measurement Protocol). We send Google no name, email address or other account data, and nothing at all once you have withdrawn consent.

Session replay with PostHog. Only if you agree in the cookie banner, PostHog Inc., 2261 Market St., #4008, San Francisco, CA 94114, USA, records how you use the dashboard and processes the recordings for us as our processor. The data is stored in the EU (Frankfurt, Germany); PostHog does not store IP addresses. Only the dashboard’s own text stays readable (menus, headings, buttons, notices and error messages), along with numbers, amounts and dates and the plans with their prices. All other text, such as the names of templates and files, people’s names, email addresses and keys, and every input is made unreadable in your browser, and images, videos, the template editors and document previews are left out, so the content of your templates, requests and generated files never reaches PostHog. Page addresses are sent without their query string, page titles not at all. PostHog knows you only by your user ID; we send it no name or email address. So that we can see why a sign-up or purchase fails, PostHog also receives the plan of the workspace you are viewing and three events: sign-up (with the method, e.g. email or Google), checkout started (plan or render pack, billing period, list price) and return from checkout (completed or cancelled). PostHog receives no payment details. We never record pages you open from an access link, such as invitations, password resets and email confirmations, nor our staff’s own pages, sessions in which our staff act in your account, or anything in a workspace set to keep no data (zero retention). This website itself does not use PostHog.

Videos from YouTube. Some pages, such as the tutorials in the documentation, contain a video from our YouTube channel. Until you click play, the page shows only a preview image from our own domain, and nothing is loaded from YouTube. When you click play, your browser loads the video from YouTube, a service of Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. YouTube then receives your IP address, details of your browser and device and the address of the page, and it can store cookies or similar identifiers in your browser. If you are signed in to a Google account, Google can link the video to that account. What Google does with the data is governed by its own privacy policy (policies.google.com/privacy); Google LLC in the United States may receive it (section 6). Your click applies to that one video only and is not remembered. If you prefer, open the video on YouTube directly through the link below the player.

Emails to our addresses are forwarded through Cloudflare to our mailboxes with email providers in Switzerland and the United States. These providers hold our own correspondence and are therefore not on the sub-processor list, which covers the data we process for customers.

We also disclose data where we must: to public authorities on a valid legal basis, and to advisers, auditors or an acquirer in the context of a corporate transaction, in each case under confidentiality. We will tell you about an authority request unless we are legally barred from doing so.

6. International transfers

Where a provider processes personal data outside the EEA, the transfer rests on an adequacy decision of the European Commission — for example for Switzerland, or for US companies certified under the EU–US Data Privacy Framework — or otherwise on the Commission’s Standard Contractual Clauses (Decision 2021/914), together with an assessment of the legal situation in the destination country and additional safeguards where needed — in particular encryption in transit and a policy of challenging unlawful access requests. For the United Kingdom we add the IDTA addendum, for Switzerland the Swiss amendments. Copies are available on request. Google LLC, which may receive Google Analytics data and data from YouTube videos you play, is certified under the EU–US Data Privacy Framework. PostHog Inc. is a company in the United States: the session replay data is stored in the EU, but access from the United States cannot be ruled out, so we have agreed the Standard Contractual Clauses with PostHog.

7. How long we keep things

Generated files7 days by default (files from test keys: 1 day). You can change this per workspace, template or request up to your plan’s maximum (Free 7 days, Starter 90 days, Growth 365 days, Pro and above unlimited), or not store files at all
Request logsPaid plans: 7 days by default, adjustable up to the plan’s maximum (Starter and Growth 7 days, Pro 30, Scale 90, Enterprise 365). The Free plan keeps no request logs
Render and usage records13 months after the generated file is gone; daily usage totals per workspace are kept with the billing records
Webhook and email delivery logs30 days
Access logs of the application14 days
Audit log1 year; visible in the dashboard for 30, 90 or 365 days depending on plan
Security logs1 year
API keysTime and IP address of last use, until the key is deleted
Account after deletion7 days recoverable, then deleted; audit entries remain without IP address and browser details, billing records as below. Backups roll off within 35 days after that
Billing records6 years, as Cypriot tax law requires
Emails and support conversations3 years
This websiteWe keep no server logs
Google Analytics (only with consent)Cookies _ga and _ga_02N4SWXM24: 2 years; usage data at Google: at most 14 months. Withdrawing consent deletes the cookies. The Google Analytics ID and your choice stored with your account: as long as the account exists
PostHog (only with consent)Recordings at PostHog: deleted after 30 days. Page views and events with your user ID: deleted after one year. PostHog’s IDs in your browser’s local storage: until you withdraw consent, which deletes them
YouTube (only when you play a video)Google decides how long it keeps the data and its cookies (see Google’s privacy policy); we see only YouTube’s aggregated statistics for our channel

8. Your rights

You can ask us to give you a copy of your data, correct it, delete it, restrict its processing, or hand it to another provider in a portable format. You can object to processing we base on legitimate interests, including profiling; we then stop unless we have compelling grounds. You can withdraw consent at any time, with effect for the future. Marketing email can be stopped with the unsubscribe link in every message.

Write to privacy@dynamicdocumentapi.com. We answer within one month and may ask for information to confirm who you are. Much of it is also self-service in the workspace: change your account details, download your templates and files, or delete your workspace or account.

9. Cookies and storage on your device

This website sets cookies only if you agree. On your first visit a banner asks: “Accept” switches on Google Analytics, remembers how you found us and, in the dashboard, switches on session replay with PostHog; “Necessary only” leaves all of it off, and “Customize” lets you choose. Until you accept, nothing loads from Google and no cookie is set: fonts, styles, scripts and images come from our own domain. The exception is a video you start yourself: clicking play loads it from YouTube, which can then set its own cookies (section 5); you can delete them in your browser’s settings. If your browser sends Global Privacy Control, we treat that as “Necessary only”.

NamePurposeLifetime
dda_consentRemembers your choice in the banner, for this website and the dashboard at app.dynamicdocumentapi.com alike, so you are asked only once; strictly necessary1 year
dda-attribution (local storage, only with consent)Remembers how you found us (referring site, landing page, campaign parameters, date) until you sign upUntil you withdraw consent or clear your browser data
_ga (only with consent)Google Analytics: recognises your browser across visits2 years
_ga_02N4SWXM24 (only with consent)Google Analytics: keeps the state of your current visit2 years
ph_… (local storage, dashboard only, only with consent)PostHog: the IDs that hold a session replay together (your user ID, the current session)Until you withdraw consent, which deletes them

Your choice applies to this website and to the dashboard at app.dynamicdocumentapi.com; neither asks a second time, and Google Analytics treats a visit to both as one. You can change or withdraw your choice at any time under “Cookie settings” in the footer of every page and in the dashboard; withdrawing deletes the Google Analytics cookies, stops reports from our server, ends session replay and deletes PostHog’s IDs from your browser. If you switch between light and dark mode in the documentation, your browser also remembers that in its local storage.

The web application uses two cookies. Both are strictly necessary and therefore do not require consent under Article 5(3) of the ePrivacy Directive.

CookiePurposeLifetime
dda_sessionKeeps you logged in14 days after your last activity
dda_csrftokenProtects forms against cross-site request forgery1 year

The application also keeps settings such as the editor layout and the colour theme in your browser’s local storage, and unsaved template drafts in its database (IndexedDB) until you save them. Fonts, including the Google Fonts families in the template editors, come from our own domain; your browser loads no fonts from Google. The bot check at sign-up and login is loaded from Cloudflare (see section 3).

10. Security

We protect data with encryption in transit, encrypted database volumes and backups, strict separation between workspaces, least-privilege access with multi-factor authentication for staff, sandboxed rendering, logging and monitoring, and tested backups. Passwords are hashed and checked against the Have I Been Pwned breach list, which receives only the first five characters of a hash. The security page describes the measures; Annex 2 of the DPA is the binding version for customer data. If a breach affects your personal data and is likely to result in a high risk to you, we tell you without undue delay.

11. Children

The Service is not directed at children. We do not knowingly process the data of anyone under 18. If you believe a child has given us data, write to us and we will delete it.

12. United States: state privacy rights

Several US states give their residents privacy rights, among them California, Colorado, Connecticut, Texas and Virginia. We extend the following to everyone, regardless of whether a particular state law applies to us:

  • Your rights. You can ask what personal information we hold about you, get a copy, have it corrected or deleted, and appeal a refusal by writing to us again. Send requests to privacy@dynamicdocumentapi.com; we answer as described in section 8.
  • No sale, no sharing, no profiling. We do not sell personal information, we do not share it for cross-context behavioural advertising, and we do not use it for profiling with legal or similarly significant effects.
  • Do Not Track and Global Privacy Control. We do not track visitors across websites. If your browser sends Global Privacy Control, Google Analytics and session replay stay off unless you switch them on under “Cookie settings” (section 9). We also treat both signals as a valid request to opt out of sale and sharing.
  • No discrimination. Using these rights never affects the price or quality of the Service you get.

Where we process personal information on behalf of a business customer, we act as its service provider or processor: we use that information only to provide the Service and for no other purpose. Section 15 of the DPA contains the service-provider terms.

13. Changes

We update this policy when the Service or the law changes. The version and date are at the top, and the change history below records what moved. If a change materially affects how we handle your data, we tell you by email before it takes effect.

Change history

VersionDateChange
1.917 November 2026Session replay with PostHog: the dashboard’s own text, numbers, amounts, dates and plans stay readable; all other text and every input are still made unreadable: sections 3 and 5
1.817 November 2026PostHog also receives the workspace’s plan and the events sign-up, checkout started and return from checkout: sections 3, 5 and 7
1.717 November 2026Session replay with PostHog in the dashboard, only with consent: sections 3, 5, 6, 7, 9 and 12
1.610 November 2026Videos from YouTube in the documentation, loaded only when you click play: sections 3, 5, 6, 7 and 9
1.59 October 2026Google Analytics in the dashboard with the same consent: sign-up, checkout and purchase, the purchase reported by our server: sections 3, 5, 7 and 9
1.49 October 2026The banner choice is kept in the cookie dda_consent and applies to the dashboard as well
1.39 October 2026Google Analytics on this website, only with consent, and how a sign-up found us: sections 3, 5, 6, 7, 9 and 12
1.27 October 2026The template editors’ fonts come from our own domain instead of Google Fonts (sections 5 and 9)
1.15 October 2026Version in force at launch
Dynamic Document API

API infrastructure for automated document and image generation.

Product

HTML to PDF API PDF Generation API Image Generation API URL to PDF API PDF Template API Markdown to PDF API Enterprise Pricing

Use cases

Invoice PDF API E-invoicing API Receipt Generation API Report Generation API Certificate Generation API Document Generation API

PDF tools

Compress PDF Merge PDF Split PDF PDF to image PNG to PDF HTML to PDF Markdown to PDF All free tools

Developers

Documentation API reference SDKs Webhooks Template gallery Security Render-time benchmark wkhtmltopdf alternative

Company

About Contact

Legal

Terms Privacy DPA Acceptable use SLA Sub-processors Withdrawal Report content Legal notice Cookie settings

© 2026 Dynamic Document API. All rights reserved.

  • Deutsch
  • Legal notice
  • Privacy
  • Terms