Privacy
In effect from 1 October 2026.
Building an e-bulletin tells us nothing about you. There is no account to make and no sign-up. Your e-bulletins are files on your computer.
If you sign in, we know your email address. For an organisation we also keep its name, its contact details if you add them, its members' addresses, the themes its members save, what it publishes, and its subscription status. That is the whole list.
No analytics, no advertising, no tracking of any kind.
Using the app
Foldsheet runs inside your browser. Nothing you build or type is sent to us until you publish it. The app keeps a working draft of each open document in your browser's own storage on your computer, so a closed tab doesn't lose your work; that storage never leaves your machine, and the Remove button in Recent clears it. Themes you save without an organisation stay there too.
A few preferences (dismissed tips, the checklist, phone or computer width, who is signed in) are kept in your browser the same way.
The site is served by Cloudflare, and the app's font (Manrope) comes from Google Fonts. Like any website, that means those servers see the ordinary request for the page: your IP address and browser type. We don't collect or keep that ourselves.
Signing in
To sign in you prove the email address is yours: we email you a six-digit code, or you use Google's sign-in button.
- The code email is sent through Resend, which sees your address and the message. The code itself is kept for ten minutes, in scrambled form, and then deleted.
- The Google button loads only when you open a sign-in box. If you use it, Google tells us the email address of the account you picked and nothing else. Google's own privacy policy applies to the sign-in itself.
- Once signed in, your browser holds one cookie,
fs_unlock. It contains your email address and a signature so it can't be forged, it lasts a year, and scripts can't read it. Sign out deletes it. - To slow down abuse, our server counts code requests per connection and per address for up to an hour. Those counters expire on their own.
Organisations
Whoever creates an organisation gives it a name and adds members by email address. We keep the organisation's name, when its trial began, each member's address and role, when each one first signed in, and what Polar tells us about its subscription: whether it is running, the billing period, and Polar's ids for the customer and the subscription. Each address that is added gets one email from us saying who added it and how to sign in; we don't email members otherwise.
The person running it may add the organisation's address, phone, email and website; new e-bulletins start with them filled in. Themes members save for the organisation are kept with its name and who saved it, and every member sees them.
The person running the organisation sees its members' addresses. Members see the organisation's name and whether its plan is running, not each other's addresses. Whether an organisation's plan is running is checked from our own records each time the app loads.
Removing an address deletes it from the organisation. To delete a whole organisation, email [email protected] from the address that runs it.
Paying
Subscriptions are paid through Polar, which is the seller of record. Polar collects what a payment needs: your name, email address, card details and country (for sales tax). We never see your card. Polar's privacy policy covers that part.
E-bulletins
When an organisation publishes an e-bulletin, the rendered page and the .foldsheet file it came from are stored on Cloudflare, and the page is shown at an unguessable address. Taking an issue down, or its link expiring, stops it showing at once; the files stay in the organisation's archive, where its members can still download the source. To have them deleted, email [email protected]. Readers are not asked to sign in and no cookie is set on those pages.
To show the organisation how many people read an issue, the page sends one short signal after it has been open for three seconds. We store a hash of the day, the reader's connection and browser, so that one person counts once a day and nothing readable is kept; the count itself is what the organisation sees. The page footer has a link to report it to us.
Problem reports
The Report a problem button sends us what you type, your email address if you choose to give one, the address you are signed in with (if you are), the app version, your browser and operating system, and a few facts about the open document (how many blocks it has, whether it is saved to a file). It never sends the document itself. Reports go to [email protected] and a copy is kept, with the connection's IP address, for 90 days.
If you write to [email protected], we keep the conversation the way anyone keeps email, and use it only to answer you.
What we don't do
- No analytics or usage statistics.
- No advertising, no ad networks, no "pixels".
- No selling, renting or sharing of your address with anyone. The three companies above (Polar, Resend, Google) each handle their own step and nothing more.
- No newsletters unless you ask for one.
Seeing or deleting what we hold
Email [email protected] from the address in question and we'll tell you what we have (your email address and any organisation you belong to) or delete it.
Children
Foldsheet is made for offices, not for children, and we don't knowingly collect anything from anyone under 16.
Changes
If this page changes, the date at the top changes with it. Anything that would let us see more than your email address would be a big change, and we'd say so on the front page.
Who to write to
Foldsheet is a small independent product. Questions about this page: [email protected].