Privacy Policy
Policy version 1 — 27 August 2026. Applies to Fanfold version 0.54.2 and later until this document is superseded. A change to this policy is an update with a new version and date at the top, never a silent rewrite.
The short version
The Fanfold extension collects nothing and sends nothing. Everything it does happens inside your browser, on your computer. This website is separate, and the one place you can send us anything is by email — only when you write to us.
Part one — the extension
It does not transmit anything. This version of Fanfold makes no network requests of any kind — no analytics, no telemetry, no crash reporting, no remote configuration, no license check. This is not a policy promise alone: the extension's source is checked on every change by an automated check that fails the build if any outbound-network call appears in the shipped code, and a second check refuses to let this claim be made in the product unless that gate is wired into the test suite.
What stays on your computer. To capture a page, Fanfold reads that page's content and takes screenshots of it while scrolling. Both are held in memory for the length of the capture and are written only into the file you save.
There are two kinds of output and they are saved by different parts of Chrome. A PDF is handed to Chrome's own print preview, and Chrome writes the file. Images are PNGs, written to your downloads folder by Chrome's download facility. Neither is uploaded anywhere; there is nowhere for them to be uploaded to.
What is stored locally. Fanfold keeps a history of your captures — except those made in a private window, which are never recorded at all. Each entry holds the page's title and address, the time, how many screenfuls were taken, the one-sentence outcome you were shown, whether the capture was degraded or failed, and — if it failed — a single word naming the kind of failure. It stores no images and no page text, and no error message: those can carry page content, so only the closed list of failure words is kept.
The history lives in Chrome's local extension storage on your machine, is never transmitted, and can be cleared from within the extension, entry by entry or all at once. A private window shows you the same history your ordinary windows have; it simply does not add to it. By default, entries older than 30 days are removed — the next time Fanfold reads or writes the history after they pass that age, not on a timer while your browser is closed. You can turn the default expiry off and keep entries until you delete them yourself. At most 500 entries are kept, oldest first out.
One other thing is kept. Fanfold keeps a record of how a capture went — timed stage names, numbers, and a word for a failure, and no page content. For the last few captures this lives only in your browser's session and is gone when you close Chrome. A capture that did not go cleanly also keeps that record with its history entry, so a problem you write to us about the next day can still be answered. It is kept for at most the 25 most recent such captures, it expires with the history entry it belongs to, and deleting that entry deletes it.
No accounts. There is nothing to sign up for and no identifier is assigned to you.
Permissions, and why each exists
- activeTab — read the page you are on, only when you start a capture from the toolbar button or the keyboard shortcut. It gives no access to any other tab and none at all until you ask.
- scripting — run Fanfold's measuring and scrolling code inside that page.
- downloads — write image captures to your computer. PDFs do not go through it: they are handed to Chrome's print preview, which saves them itself.
- storage — keep the local capture history and your history settings.
Fanfold declares no host permissions at install, so it has no standing access to any site. Some pages keep their content inside a frame belonging to another site; capturing one of those needs your permission for that site specifically, and Fanfold asks at the moment it is needed, in Chrome's own dialog. You can withdraw it at any time from Chrome's extension settings. Granting it changes what Fanfold can read; it changes nothing about what Fanfold transmits, which is still nothing.
Children
Fanfold is not directed at children and collects no information from anyone, of any age.
Part two — this website
The extension and this website are separate things. Everything above describes the extension. This part describes the site you are reading.
The site is static pages served at getfanfold.com. There is no form on it, no account, and nothing to sign up for. The company that serves the pages receives the ordinary request information any web server receives — your IP address, the page you asked for, your browser's user-agent — and handles it under its own privacy statement. The site requires no cookies and sets none. We may come to measure how many people visit and which pages they read; if we do, it will be by a method that sets no cookies, builds no profile of you, and is never connected to anything you have emailed us. This policy will say so before it happens.
If you write to us
Support is an email address: support@getfanfold.com. There is no form, and nothing on this site sends us anything.
If you email us, we have your message and your address, the way anyone does who receives an email. We use it to answer you and to fix what you reported, and for nothing else. We do not add you to a mailing list, and we never sell or share it.
We keep support correspondence while it is useful and delete it when it is not.
If you send a diagnostic report, you can read it first — the extension puts it on your clipboard, so you paste it, and you see every line before it goes anywhere. It is a list of timed stages with numbers and true/false values beside them: how far each of the last few captures got, whether the record was truncated, and, if one failed, a word naming the kind of failure together with the name of the underlying error type — TypeError, for instance, never its message. There is no page content, no screenshots and no addresses in it. The stage names and the failure words are both fixed lists, so nothing from the page can travel in them.
If you attach a file, look at it first. A PDF or a screenshot may contain whatever you were looking at, and only you can tell.
Your rights
The extension collects nothing, so there is nothing to exercise a right against there. What we hold is whatever you have emailed us.
Write to support@getfanfold.com and you can ask for a copy of what we hold about you, correction of anything wrong, or deletion of it. We will answer within a month. There is no account to log into and nothing to prove: the address you write from is the address we hold.
If you are in the EU or the UK and think we have handled your correspondence badly, you can complain to your national data protection authority — in the UK, the Information Commissioner's Office.
Nothing here is decided by a machine. A person reads your email.
What could change, and how you will know
Fanfold is free to use today. Paid options may be offered in the future. If a future version of Fanfold ever transmits data — for example to verify a licence — that version will say so in this policy, the policy version and date at the top will change, and the Chrome Web Store listing's privacy disclosures will be updated before that version is published. A new policy applies to the version of Fanfold released with it and is not applied retroactively to what an older version already did.
Contact
Questions about this policy: support@getfanfold.com.