Legal
Privacy Policy
Last updated: 22 November 2026
Foliohelps product teams spot users who are slipping and win them back. To do that, we store the product events your app sends us. We don't sell data to anyone, and we don't use your data to train AI models.
This page covers two kinds of data. Your account data is about you and your team, the people who sign in to Folio. For this data we are the controller. End-user data is about the people who use your product, which you send us. For that data you are the controller and we are your processor. Our Data Processing Agreement sets out how we handle it.
What we collect
- Account data: your email address, name and profile picture link from Google when you sign in, plus what you enter in settings: workspace name, website, logo and brand color.
- Billing data: your plan, subscription status and Stripe customer ID. Card details go straight to Stripe. We never see or store them.
- Workspace content: your projects, goals, cohorts, draft and approved messages, funnels, and any brand voice text we pull from a web page you point us at.
- End-user events: the events you send through our SDK, our REST API, the PostHog webhook or the PostHog import. Each event has a name, the properties you attach, the ID you give the user, and a timestamp. Our browser script also records the page URL, a session ID, and on page views the page title and referrer. You decide what to send, so please keep personal data out of event properties unless you have a lawful basis for it.
- End-user traits: whatever you pass to
identify(), often an email and plan. We keep the latest value of each trait per user. - Decision records: which message we served to which user, and whether it was shown, clicked, dismissed or followed by your goal event.
We don't store IP addresses in our database. Our hosting providers see them when they deliver requests and may keep them in their own logs.
What we do with it
We use end-user events to find groups of users at risk of missing your goals, draft messages for them, serve the messages you approve, and measure the result. All of this happens inside your workspace. Nothing is shared with or reused for other customers.
When the AI engine is on, we send Anthropic's Claude API a summary of your project so it can draft groups and message copy. That summary contains: your project name, how many users you track, the names of your traits (not their values), the names of your most common events with their 30-day counts, your goal's name, type, description, target event and time window, your brand voice text if you set one, and the group rules it is writing copy for. It does not contain user IDs, trait values, event properties or any individual events.
Who we share it with
These subprocessors help us run the service:
- Vercel: hosts the app and runs its server functions, in the United States.
- Render: runs our Postgres database and the database API in front of it, in its US East (Virginia) region. All stored data, including uploaded logos, lives here.
- Anthropic: the Claude API drafts groups and copy from the project summary described above.
- Stripe: checkout, subscriptions and the billing portal. Stripe receives your email and handles your payment details.
- Google: sign-in. Google confirms who you are and shares your email, name and profile picture with us.
Each is bound by its own privacy and data handling commitments. If you use the PostHog import, we fetch your events from your PostHog account at your request. PostHog acts for you, not for us, and we don't store the PostHog key you give us. We don't share data with marketing partners, and we don't sell data.
Where it lives
In the United States. The database and file storage are on Render in US East (Virginia), and the app runs on Vercel in the United States. We don't offer other regions or a self-hosted version today.
Your workspace logo is stored in our database and served publicly at a /api/storage/brand-assets/…link, so it can appear in your app and on reports you share. Don't upload a logo you want to keep private.
How long we keep it
- End-user eventsare deleted automatically once they are older than your plan's window: 30 days on the trial, 90 days on Growth and 180 days on Scale. A job runs every day to do this. If your trial ends or your subscription lapses, the 30-day window applies.
- Everything else (account data, workspace content, end-user traits and decision records) stays while your account is open. When you close your account, we delete it within 30 days.
- Billing records that Stripe holds are kept by Stripe under its own rules.
Your rights and deleting data
To access, export or delete your data, or to close your account, email privacy@[domain pending] from the address you sign in with. There is no self-serve delete button yet, so we do it for you. We answer within 30 days. EU and UK residents have the rights described in the GDPR, and California residents have the rights in the CCPA.
If you are one of our customers' end users, please contact the company whose product you use. They control your data, and they can ask us to delete it. Customers can ask us to delete a specific end user by emailing privacy@[domain pending]with the user's ID and project.
Cookies and browser storage
folio_session: one cookie that keeps you signed in. It is httpOnly (page scripts can't read it), signed by our server, and lasts 30 days. It renews itself while you keep using Folio, and signing out removes it.- The sign-in and sign-up pages load Google's sign-in script. Google may set its own cookies under Google's privacy policy.
- We don't use analytics or advertising cookies.
- On your customers' devices, our browser script keeps a
folio_diduser ID in localStorage and afolio_sidsession ID in sessionStorage. It sets no cookies.
Security
All traffic uses HTTPS. Each workspace can only read its own data. Server API keys are stored as hashes, never in plain text. The DPA lists the measures in more detail.
Children
Folioisn't directed at people under 16, and we don't knowingly collect their data.
Changes
We'll email you about material changes 14 days before they take effect.
Contact
privacy@[domain pending]