Privacy Policy: What Tension Free Zone Stores and What It Never Sees
Tension Free Zone is built on a privacy-first architecture. Your data never leaves your device, and we have no servers, accounts, or tracking systems. This page explains exactly what is stored locally, what minimal information is transmitted, and how you maintain full control.
The short version
- There are no accounts. Nothing asks for your name, email address or phone number, and nothing can, because there is no sign-in.
- Your documents and figures are never uploaded. The tools read what you type and compute in the tab you have open.
- What you save is kept in your own browser's storage. You can export all of it to a file, and you can erase all of it with one button.
- Three things leave your device: the request for the page itself, requests to Google for web fonts, and, only if a measurement tag is configured, anonymous counts of which pages and tools were used.
- No advertising network is loaded on this site today. No advertising cookie is set, and no profile of your browsing is built here.
What is stored, and where
Everything the tools remember lives in your browser, on your machine, under storage keys that all begin with the prefix `tidy-`. That prefix is not decoration: it is how the app finds its own data, how the backup knows what to include, and how "clear workspace" knows what to remove.
The kinds of content saved there: text you clean up or keep in the scratchpad, saved scratchpad drafts, citation entries and batches, semester grades, the attendance grid and holiday dates, deadline entries, resume drafts and their design settings, invoice drafts and their saved business and client profiles, budget figures, loan and EMI inputs, compound-interest inputs, link-shortener entries and their click counts, and your two preferences, the theme and the interface language you chose.
Two further things are stored in IndexedDB rather than localStorage, because a folder handle cannot be written to localStorage: the handle to the folder you connected for downloads, and the index of files the app recently wrote to it. The handle is a permission token, not a copy of the folder: it lets the app write a file you asked it to write, and nothing more.
What leaves your device
Assuming the site is served normally and no measurement tag is configured, the only outbound requests are for the site's own files and for its web fonts.
- The page request itself. Whoever hosts the site sees the request, which includes your IP address, the path you asked for, and your browser's user-agent string. That is true of every website; it is listed here because it is one of the few things this site cannot avoid.
- Google Fonts. The typefaces are loaded from fonts.googleapis.com and fonts.gstatic.com, which means Google receives a request from your IP address when a page loads. When a resume export embeds a chosen typeface into the PDF, the stylesheet and the font file are fetched again for that family. If that request matters to you, a font-blocking extension prevents it and the site falls back to typefaces already on your system.
- Measurement, if configured. The app contains a measurement bridge, code that hands a page view and a download event to Google Analytics 4 or a Google Tag Manager data layer, and that bridge only does anything when such a tag is present on the page. Where it is present, a page view carries the route path and the tool id, and a download carries the file's type (pdf, png, docx). File names are deliberately stripped before measurement and never leave the device.
What is never sent, under any configuration
The contents of anything you type or open. Text you clean, PDFs you merge, images you compress, grades you enter, attendance records, citation entries, resume content, invoice contents and client details, budget and loan figures, and saved profile data are all handled inside your tab and are never part of any request.
Your typed personal details are also never used to identify you. There is no user id to attach them to, because there is no account to attach one to.
The folder you connect
If you use the optional download-folder feature, the browser asks your permission through the File System Access API and gives the app a handle to the folder you chose. From then on, files the tools produce can be written straight into that folder, organized into sub-folders by category, and the app can list what it recently wrote there.
Two limits are worth stating exactly, because "the app can read your folder" would be the wrong reading. It is granted access to the folder you picked, it writes only files it is producing, and it reads back only the files it wrote, the recent-files list is the app's own index, not a scan of your disk. You can revoke the permission from the browser's site settings at any time, and "clear workspace" forgets the handle along with everything else.
Cookies
Tension Free Zone does not set cookies. All data storage uses browser-native mechanisms (localStorage and IndexedDB) that are not attached to HTTP requests and cannot be read by third parties.
We may introduce analytics or advertising in the future. If we do, any third-party cookies will be disclosed here with a policy update date before they are enabled. Your privacy guarantees regarding local data storage will remain unchanged.
Backups you make yourself
The workspace backup writes a single JSON file containing your saved data: the `tidy-` keys and their values, plus your theme and language. It is written to your own disk or to the folder you connected, and it is never sent anywhere.
Two things to know about that file. It is plain text: anyone who opens it can read your notes, grades, invoice profiles and resume content, so store it the way you would store any other document with your details in it. And it is honest about what it holds, it excludes the key that records which page you were last on, because a backup should restore your work rather than teleport you to a route you happened to be viewing.
Reading, exporting and erasing everything
Your data is yours to inspect and remove, and there are three ways to do it.
- Back up first. "Backup workspace" writes the file described above. Do this before you clear anything: it is the only copy that will exist.
- Clear workspace removes the saved data and forgets the connected folder. It deliberately keeps your theme and language, because losing those is an annoyance rather than a reset. The action takes two clicks, and it reloads the page when done.
- Your browser's own controls do the rest. Clearing site data for this domain removes everything at once, including anything the app forgot about. A private window keeps nothing after it closes, which makes it a good way to use the tools on a shared computer.
If you clear your browser data
The consequence is worth stating without softening it: there is no server copy, so there is nothing to recover from. If your browser data is gone and you have no backup file, your saved work is gone, and no one, including whoever builds this site, can bring it back.
A backup taken before the clear restores everything, including your saved profiles and preferences. A backup taken afterwards carries almost nothing, which is why the habit worth forming is to export before you tidy up, not after.
Children, shared computers and other people
There is no account and no age check, so a child can use the tools without giving anything up. On a shared computer, though, browser storage is per-browser rather than per-person: notes saved by one user are visible to the next. A private window is the cleaner option there, and it leaves nothing behind.
If you are entering another person's details, a client's tax number on an invoice, a classmate's name in a group project, remember that you are the one storing them, on your machine.
Changes to this page
The date under the title changes whenever the behaviour changes, and the wording changes in the same edit. Additions that matter, a new third-party service, advertising, anything at all that starts leaving your device, will be described here rather than added quietly to a section nobody re-reads.
Questions about any of this
If something here does not match what you can observe in your browser, that is worth reporting as a defect rather than a question, and it will be treated as one. The contact page says how.