Privacy Policy
Last updated: 2026-09-10
1. Who we are
FRONTPLUG LLC, a limited liability company organized under the laws of the State of Delaware, United States of America, operates BrewMyPDF at brewmypdf.com. For questions about this policy or to exercise your rights, contact support@brewmypdf.com.
2. Our role ★
There are two different kinds of data here, and we have a different role for each.
| Data | Our role | Governed by |
|---|---|---|
| Your account data — your email, billing, usage | Controller | This policy |
| Data you send us to render — which may contain personal data of your own users | Processor, acting on your instructions | DPA |
3. What we collect and why
| Data | Purpose | Legal basis (EEA/UK) |
|---|---|---|
| Email address, password (hashed) | Create and secure your account | Performance of a contract |
| API keys (hashed) | Authenticate API requests | Performance of a contract |
| IP address, User-Agent | Security, abuse prevention, audit records | Legitimate interests |
| Usage records (counts, sizes, timestamps) | Enforce plan limits and bill correctly | Performance of a contract |
| Billing details | Take payment (held by Stripe, not by us) | Performance of a contract |
| Support messages — the reply address, subject and body you write, plus your account and plan if you were signed in | Answer your question | Legitimate interests |
We never store passwords or API keys in plain text — only a hash. We do not store full payment card numbers; our payment provider does.
We do not sell or share personal information, and we do not use it for cross-context behavioural advertising.
When you write to support, the address you give is used only to reply — we do not add it to any list and we send nothing else to it. We check the IP address at the moment of submission to prevent abuse and do not store it with the message.
4. Cookies and consent ★
Strictly necessary cookies — signing in, your language, and your cookie choice itself — are set without asking, because the service cannot work without them. Analytics and marketing cookies are off until you allow them. We ask once, refusing takes a single click, and you can change your answer at any time from the Cookie preferences link on any legal page.
If you allow analytics or marketing, we use Google Analytics 4, which sets cookies and processes your IP address, device and browser information, and the pages you view, plus some usage context (your plan, language, approximate ranges of your template and render counts, whether you use an API key, and how long since signup — all as ranges). If you refuse, the Google tag is not loaded at all.
One exception: when you complete a purchase, we send a server-side record of that purchase (plan and amount) to Google Analytics 4 to measure conversions, and this happens even if you decline cookies — it is sent from our server, not your browser, stores nothing on your device, and carries no individual identifiers. Its basis is our legitimate interest in measuring conversions, separate from the consent-based cookie analytics, and you may object. The full list of cookies, their lifetimes and how to withdraw is in the Cookie notice.
Legal basis. Strictly necessary cookies rest on our legitimate interest in operating the service you asked for. Analytics and marketing rest on your consent (GDPR Art. 6(1)(a)), which you may withdraw at any time; doing so does not affect processing carried out before the withdrawal. We record the time and the version of the notice you agreed to. The server-side purchase conversion transmission described above rests not on consent but on our legitimate interest in measuring conversions (GDPR Art. 6(1)(f)), which you may object to.
We do not sell or share personal information for cross-context behavioural advertising.
5. How long we keep data ★
| Data | Retention |
|---|---|
| Generated output (PDF, images) | The download link expires in 10 minutes by default (24 hours at most). The stored file is deleted on a 7-day schedule |
| Request payloads (the JSON you send) — successful renders | Not stored — deleted as soon as rendering finishes |
| Request payloads — renders that finally failed | 24 hours, so that you can re-run them, then deleted |
| Templates and account data | For as long as your account exists |
| Audit logs | 30 days in the console. After that a record moves to our internal archive, where it is kept for at most 730 days and then deleted. IP address and User-Agent are removed at the moment of the move, whether or not the account still exists. Deleting your account removes them from the recent records too. What remains is pseudonymized — a random account identifier stays, because billing records we must keep for tax law refer to it |
| Google Analytics event and user data (with consent) | 14 months each, then deleted |
| Billing records | As required by tax and accounting law |
| Support messages | 180 days, then deleted automatically. Deleting your account also deletes the messages you sent while signed in |
Expiry and deletion are irreversible. We keep no backups for your benefit and cannot restore expired or deleted data — see Terms §10.
6. Who we share data with
Only the service providers we need to run the Service. They are listed, with their role and what they process, on our Subprocessors page. We also disclose data where the law requires it.
If — and only if — you allow analytics or marketing cookies, Google receives the data described in section 4 as an additional recipient.
7. Where data is processed
The Service runs on Cloudflare's global network, and we and our providers are located in the United States and elsewhere, so your data may be processed outside your country. For transfers of personal data out of the EEA, the UK, or Switzerland, we rely on the European Commission's Standard Contractual Clauses and, for the UK, the ICO Addendum, as set out in the DPA.
Where you have consented to analytics or marketing, Google may transfer that data to the United States. We rely on your consent for the processing and on Google's Standard Contractual Clauses and Data Privacy Framework certification for the transfer.
8. Your rights
Depending on where you live, you may have the right to access, correct, delete, restrict, or object to the processing of your personal data, and to receive it in a portable format.
- Access — view your data in the console
- Portability — export templates and settings as JSON from Settings
- Erasure — delete your account from Settings; this removes your data from our database and object storage, and we confirm when it is done. Audit logs are kept for the legally required period. Your IP address and User-Agent are removed from them; a random account identifier remains, because billing records we are required to keep refer to it
- Restriction or objection — write to us
Contact support@brewmypdf.com. We respond to legitimate requests within one month. We do not charge for this, and exercising your rights will not cause us to treat you differently. If you are in the EEA or the UK you may also complain to your local supervisory authority.
9. California residents
If you are a California resident, you have the rights to know, delete, and correct personal information, and to opt out of sale or sharing. We do not sell or share personal information, so there is nothing to opt out of. Use the same contact address above; you may use an authorized agent.
10. Children
The Service is not directed to children. We do not knowingly collect personal information from anyone under 13. If you believe a child has given us personal information, contact us and we will delete it.
11. Security
We use TLS in transit, hash passwords and API keys, isolate every account at the database query level, block network access inside the rendering environment, and keep access audit records. No system is perfectly secure; we describe our measures in the DPA.
12. AI features ★
We do not use customer data to train models. If you use an AI feature, the prompt is sent to our AI provider listed on the Subprocessors page solely to produce your result.
13. Changes
We will post any update here with a new "last updated" date, and give notice of material changes by email or in the console.
14. Language
This policy is published in English and Korean. The English version is the authoritative version; the Korean version is a convenience translation.