Legal
Data Processing Agreement
Last updated: 22 November 2026
This agreement covers the personal data about your end users that you send to Folio. It forms part of our Terms of Service. If the two disagree about end-user data, this agreement wins. It is written as a plain-English template. To get a signed copy, email privacy@[domain pending].
1. Who does what
- You (the customer) are the controller. You decide which end-user data to send us and why.
- Folio is your processor. We handle that data only to run the service for you.
2. The data this covers
"End-user data" means data about the people who use your product that reaches us through the browser script, the SDK, the REST API, the PostHog webhook or the PostHog import. That is:
- the user IDs you assign, and the session IDs our browser script creates;
- events: their names, the properties you attach, timestamps, and, from the browser script, the page URL, title and referrer;
- traits you send with
identify(), such as an email address or plan; - which groups each user falls into;
- records of the messages we served to each user and whether they were shown, clicked, dismissed or followed by your goal event.
Please don't send special category data (such as health data) or data about children.
3. How we use it
We process end-user data only on your instructions. Your instructions are these terms and the way you set up Folio: your projects, goals, approved messages and settings. We use it to group users, serve the messages you approve, and measure the results inside your workspace. We don't sell it, share it with other customers, or use it to train AI models. If we think an instruction breaks data protection law, we will tell you.
Everyone at Folio who can access end-user data is bound to keep it confidential.
4. Subprocessors
You agree that we may use these subprocessors:
- Render: runs our Postgres database and the database API in front of it, in its US East (Virginia) region. All end-user data is stored here.
- Vercel: hosts the app and runs the server functions that receive events and serve decisions, in the United States.
- Anthropic: the Claude API drafts groups and message copy. It receives a project summary only: event names with their 30-day counts, trait names (not values), how many users you track, your goal text and target event, the group rules, your project name and any brand voice text you set. It never receives user IDs, trait values, event properties or individual events.
We also use Stripe for billing and Googlefor sign-in. They handle your team's account data, not end-user data.
Before we add or replace a subprocessor that handles end-user data, we will update this page and email your account address 14 days ahead. If you object on reasonable data protection grounds, tell us and we will work with you on it. If we can't resolve it, you may cancel. We hold each subprocessor to data protection terms that protect end-user data at least as well as this agreement.
5. Where the data is
End-user data is stored and processed in the United States. If your use of Folio needs a transfer mechanism, such as the EU Standard Contractual Clauses or the UK Addendum, email us before you send data and we will work through it with you.
6. Security
These are the measures in place today:
- Encryption in transit: every connection to Folio and from our servers to the database API uses TLS (HTTPS).
- Workspace isolation: the database enforces row-level security, so a signed-in user can only read and change rows that belong to their own workspace. Server jobs that work across workspaces check ownership before returning anything.
- Locked-down database API: the database API refuses any request without a token our server signs, and each token expires after 5 minutes. Browsers never hold one.
- Restricted database access: direct connections to the database are only accepted from an allow list of IP addresses.
- Hashed API keys: server API keys are stored only as SHA-256 hashes. We show the full key once, when you create it, and you can revoke it at any time.
- Secrets out of the code: database, signing, payment and AI keys are kept in our hosting providers' encrypted environment settings, not in our source code.
- Sessions: sign-in is through Google only, with no passwords stored by us. The session cookie is signed, httpOnly and expires after 30 days.
- Ingestion limits: each project's public key can only send events, traits and feedback, and fetch decisions. You can restrict it to your site's origin, and requests are rate limited per project.
7. Breaches
If we become aware of a breach affecting your end-user data, we will tell you without undue delay by emailing your account address. We will explain what happened, what data is involved, what we are doing about it, and how to reach us. We will keep you updated as we learn more and help you meet any duty you have to notify regulators or users.
8. Helping you with requests
If an end user asks you to access or delete their data, we will help. Email privacy@[domain pending]with the project and the user's ID, and we will send you their data or delete their events, traits and decision records within 30 days. If an end user contacts us directly, we will pass the request to you and not answer it ourselves.
9. Retention and deletion
Events are deleted automatically once they pass your plan's window (30 days on the trial, 90 on Growth, 180 on Scale). Other end-user data stays while your account is open.
When your account ends, we delete all end-user data within 30 days. Before that, you can ask us for an export. Any copies in our database provider's backups expire on that provider's schedule.
10. Audits
On request, we will answer reasonable written questions about how we protect end-user data, such as a security questionnaire, and give you the information you need to show that this agreement is being followed. Email privacy@[domain pending]. If a regulator asks you for something, we will help with that too.
11. Term
This agreement lasts as long as we process end-user data for you. The sections on confidentiality, deletion and breaches continue until the data is deleted.
Contact
privacy@[domain pending]. See also our Privacy Policy.