Privacy Policy
No surprises. This explains what Unplain collects, why, and the control you have over your data.
Last updated: November 17, 2026
Unplain turns docs and AI drafts into publish-ready PDFs. To do that, we handle some of your information. We keep what we collect to the minimum the service needs, we don't sell it, and we don't claim ownership of anything you upload or create.
Information we collect
We collect the following so the service can work:
- Account information: your name (if you provide one) and the details needed to create and secure your account.
- Email address: used to sign you in, send important service messages, and respond to support requests. We send email through Lettr, our email delivery provider.
- Documents: the files you upload, the text you paste, or the content an AI assistant sends on your behalf through the Unplain MCP, in order to make a PDF.
- Saved projects: the documents, covers, images, layouts, Brand Themes and exports you save to your account.
- Organizations: an organization's name, who its members are and their role, and the email address an invitation is made for, which is used only to check that the person who opens the invitation link is that person. We also record who made and who last saved each document in an organization. Members of an organization can see each other's name and email address.
- Leads: if you publish guides on a Library, the details your readers give to read them and how they read them. See Lead magnets and Libraries.
- Payment information: handled by Stripe. We receive limited billing details (such as your plan and payment status); we never see or store your full card number.
- Analytics and usage data: basic information about how the service is used (for example, pages visited and features used, including which Unplain tools a connected AI assistant used and whether they worked, never the content), which helps us find problems and improve Unplain. See Cookies for the tools we use.
How we use information
We use the information above to:
- Provide the service and generate your ebooks and PDFs.
- Save your projects and make them available from your dashboard.
- Process payments and manage your plan, and any Creator Pack balance you already have.
- Improve Unplain, fix bugs, and understand which features help.
- Communicate important updates, such as security or billing notices.
We do not sell your personal information, and we don't use the contents of your uploaded documents to train AI models.
Using Unplain without an account
You can create and export a PDF without signing up. While you are signed out, your document is kept in your browser's storage on your device, not in an account on our servers. To produce the PDF, the document is sent to our export service, which uses it only to render that file.
If you upload a file from unplain.io, it is held for at most 30 minutes so the editor can open it, then deleted once it has been opened. We keep a one-way hash of the uploading IP address with it, to limit abuse. If you later create an account, you can save the document to it.
AI features
Unplain does not write or rewrite your text. It can generate images with AI if you ask it to, for covers and for images inside a document. To do this, your prompt and the context needed for the image are processed by our AI image provider, currently OpenAI, on our behalf. We share only what's needed to generate your image.
You keep ownership of your content. Unplain does not claim ownership of the documents you bring or of the projects, covers and images you generate.
AI assistants (MCP)
You can connect an AI assistant to your account through the Unplain MCP in two ways: by signing in to Unplain from the assistant (for example Claude, ChatGPT, Cursor or VS Code), or with an API key you create (for example for Claude Code or Codex). Either way, the assistant works only in the one workspace you chose, with the permissions you approved, and your plan's limits apply exactly as they do in the editor.
Content your assistant sends to Unplain is handled like a document you upload, and the documents it creates are saved to your account. Unplain receives only what the assistant sends to create, read or change your documents and Brand Themes; we do not receive your conversation with the assistant.
When you connect by signing in, Unplain shows you which app is asking, the address it will send you back to and what it will be able to do, and nothing is shared until you choose Allow access. We then keep a record of the connection: the app's name and addresses, the workspace, the permissions you approved, when you connected and when the app last used it. The app receives access tokens that expire after an hour and refresh tokens that renew them. We store tokens and API keys only as one-way hashes, so we cannot read them back.
You can disconnect an app at any time on Connect to AI in your account (app.unplain.io/connect), and revoke an API key in your account settings. Either stops working on its very next request. What your assistant's provider does with your conversation is covered by that provider's own privacy policy.
File uploads
Files you upload (or text you paste) are used to generate ebooks and provide the service to you: for example, to build the layout, table of contents, and export. They are stored as part of your projects so you can come back to them from your dashboard.
You can delete projects from your account, and you can ask us to delete your account and associated data at any time (see Your rights).
Lead magnets and Libraries
Unplain customers, usually agencies, can publish guides (PDFs) on a
public Library at an address like name.unplain.page.
To read and download a guide, a visitor fills in a short form: an
email address, a name if the agency asks for one, and a consent
sentence the agency writes. Below, we call these visitors readers,
and what they submit a lead.
Who is responsible
For readers' data, the agency that published the guide is the controller: it decides why the data is collected and what is done with it. Unplain is the processor: we store and handle that data for the agency, on its instructions. Unplain is the controller for abuse reports (see Reporting a page) and for Unplain account data, as described in the rest of this policy.
What we store for each lead
- The email address, and the name if the form asks for one.
- The exact consent sentence the reader agreed to, and when.
- Whether the reader allowed reading insights (see below), and when they chose.
-
The UTM parameters of the link the reader came from (for example
utm_source). - Which form was used: the guide's own page, or a form the agency embedded on its own site.
- The address of the page the reader came from (the referrer).
- A salted one-way hash of the reader's IP address, used only to limit abuse. We never store the IP address itself.
Counting visits
We count visits to a guide's page and the start of its form, with the UTM parameters of the link and the host name of the website the visitor came from. To count each visitor once a day, we combine the date, the Library, the visitor's IP address and browser type into a one-way hash that changes every day. We store only that hash, never the IP address, and nothing is stored on the visitor's device for it. Opens of a share link are counted the same way.
Reading insights, only if the reader allows them
The form has an optional box, unticked by default, that lets the agency see how the reader reads the guide. Only when it is ticked do we record, tied to the lead:
- Opening the guide, which pages were viewed, and the time spent on each page.
- Clicks on links inside the guide, recorded as the address the link points to.
- Whether the email with the reader's copy was opened, and clicks on the links in that email. The open is measured with our own 1x1 image in the email, which is left out when the box is not ticked.
We store the reader's choice and when it was made. The reader can turn reading insights off at any time from the guide itself, or by filling in the form again without the box. Downloads, and share links the reader creates, are counted either way. Our email provider's own open and click tracking is switched off for these emails.
Cookies on Library pages
-
ul_leads: a signed list of the guides this browser has already unlocked, so a returning reader is not asked to fill in the form again. It lasts one year and is HttpOnly, so scripts on the page cannot read it.
That is the only cookie. Library pages set no analytics cookies,
and Unplain's own analytics do not load on them. Unplain account
cookies are never set or read on Library addresses. An older
visitor cookie, ul_v, is no longer used and is
removed when a browser that still has it visits.
The agency's own privacy policy
The agency can link its own privacy policy under the form. That policy, not this one, explains what the agency does with the leads it collects.
Other services on Library pages
- Supabase, our database and file storage provider, stores the leads, their activity and the guides.
- Cloudflare Turnstile checks that the form is filled in by a person. For that, Cloudflare processes the reader's IP address and signals from their browser.
- Lettr, our email delivery provider, sends the reader their copy of the guide link (unless the agency turns that email off for the guide) and sends the agency a note about each new lead. Library emails come from Unplain's sending address, with the agency's address as the reply-to, so a reader's reply goes to the agency.
The fonts on Library pages come from Unplain's own servers, so the reader's browser does not contact Google for them.
What the agency does with leads
The agency sees its leads and their reading activity in Unplain, and can export them. It can also have each new lead sent to a webhook on its own server. What happens to the data there is the agency's responsibility.
Each plan includes a monthly allowance of new leads. A reader who signs up after the agency's account has gone over it is treated the same as any other: their lead is stored with the same details, and they get the guide. But the lead is locked. The agency is told that a lead came in, without the reader's name or email address, and a locked lead is not shown in Unplain, not included in exports, not available to the agency's connected assistant and not sent to its webhook. It stays locked, including after the month ends, until the agency moves to a plan that unlocks it. Then the agency can see it and export it, and it is sent to the webhook with the time the reader originally signed up. Locked leads are kept and deleted on the same rules as other leads (below).
How long leads are kept
Leads and their reading activity are kept for as long as the agency
keeps the guide and its account. When the agency deletes a lead, we
erase that person's data for good, and it cannot be undone: the
email address, name, consent sentence and time, referrer, IP hash,
the free-text UTM fields (utm_term and
utm_content) and any other UTM value holding an email
address. The random ID that tied their activity to their browser is
replaced with a new one. Their reader, download and share links stop
working.
What stays is an anonymous record, so the agency's totals and the monthly lead count stay correct: the guide, the date, which form was used, the link's source, medium and campaign, the website they came from (only its host name), and the activity listed above (such as pages viewed, downloads and link clicks) without anything that says whose it was. We cannot tie it back to the person. If they fill in the form again, that is a new lead.
Copies outside Unplain are not touched: emails already sent, and what the agency exported or received by webhook. Those are the agency's to delete. When the agency deletes the guide, or its workspace, the guide's leads and their activity are deleted for good.
If you filled in a form on a Library
To get a copy of what you gave, or to have it deleted, ask the agency that published the guide. Its name and contact are on the Library, and it can erase your lead in Unplain. You can also write to us at info@unplain.io: we will pass your request to the agency and help it.
Reporting a page
Every Library page has a Report abuse link to a form. A report stores the page, the reason, the details you write, your email address if you choose to give it, and a salted one-way hash of your IP address. Unplain staff are emailed about each report.
Payments
Payments and subscriptions are processed by Stripe, a third-party payment provider. When you subscribe to Growth, your card details are entered with and handled by Stripe. The same was true of Creator Pack and Export Pack purchases, which are no longer sold.
Unplain does not store your full card information. We receive only the limited billing data we need to manage your plan and any Pack balance, such as what you bought and whether a payment succeeded.
Data security
We use reasonable technical and organizational measures to protect your information against loss, misuse, and unauthorized access. No online service can be completely secure, but we work to keep your data safe and to respond quickly if something goes wrong.
Your rights
You can access and update much of your information directly in the app. You can also contact us to request a copy of your data, to correct it, or to delete your account and the data associated with it.
To make a request, email us at info@unplain.io. We'll respond within a reasonable time. Depending on where you live, you may have additional rights under local data-protection law.
If you gave your details to read a guide on a Library, the agency that published it decides what happens to them, so ask it first; you can also write to us and we will pass your request on and help it. See Lead magnets and Libraries.
Data retention
We keep your information for as long as your account is active or as needed to provide the service. When you delete your account, we remove or anonymize your personal data, except where we need to keep certain records to meet legal, accounting, or security obligations.
Sign-in codes and tokens for connected AI assistants are deleted automatically once they expire. The record of a connection, including one you disconnected, is kept until you delete your account.
Leads and their reading activity are kept while the agency keeps the guide and its account. When the agency deletes a lead, the person's data is erased for good and only an anonymous record stays, so its totals and the monthly lead count stay correct; deleting the guide or the workspace deletes its leads and their activity for good. Abuse reports are kept; there is no automatic deletion of them yet. See Lead magnets and Libraries.
An invitation link works once and for seven days, and unused invitations are removed afterwards. When someone leaves an organization or is removed, we delete their membership; the documents they made in it stay with the organization, no longer marked as theirs. When an organization is deleted, everything in it is deleted.
Changes to this policy
We may update this Privacy Policy from time to time as the service evolves. When we make material changes, we'll update the date at the top of this page and, where appropriate, let you know.
Contact
Questions about privacy or your data? Email us at info@unplain.io. We're happy to help.
Looking for our terms instead? Read the Terms of Service →