Cookies and Local Storage Policy
How Tolstoy Compose uses essential cookies and browser storage, including local document storage for a local-first writing app.
Last updated: 18 June 2026
The short version
Tolstoy Compose uses cookies and browser storage to make the website and app work.
Because Compose is local-first, browser storage may hold your document content. This can include drafts, notes, sources, review comments, versions, recovery data and document settings.
We do not use advertising cookies. We do not use session replay. We do not use behavioural advertising pixels. We do not use in-app product analytics at launch.
Cloudflare may provide default network, security and traffic information as part of hosting, security and delivery of the website and app.
If we introduce optional analytics, advertising cookies or other non-essential tracking later, we will update this policy and ask for consent where required.
What this policy covers
This policy covers cookies and similar technologies used by the Tolstoy Compose website and app.
“Cookies and local storage” includes:
- cookies;
- localStorage;
- sessionStorage;
- IndexedDB;
- service worker cache;
- browser cache;
- authentication/session storage;
- similar technologies that store or access information on your device.
Some of these technologies are essential for a local-first writing app. Others would need consent if we add them later for optional analytics, advertising or similar purposes.
Why Compose uses browser storage
Compose uses browser storage so the app can save and restore work locally.
This may include:
- your current draft;
- Shelf notes;
- sources and citation information;
- review comments and suggestions;
- version history;
- recovery entries;
- document settings;
- appearance and language preferences;
- recent workspace state;
- installed-app files and service worker cache.
This storage helps Compose work as a local-first app. It is also why clearing site data can delete local-only work.
Essential technologies
We use essential cookies and local storage where needed to provide the service you ask for.
Scroll horizontally to see the full table.
| Technology type | Why it is used |
|---|---|
| Authentication/session storage | Keeps you signed in and connects your account to the correct plan |
| Billing and checkout storage | Supports checkout, billing portal and subscription status flows |
| Local document storage | Saves drafts, notes, sources, versions and recovery data locally |
| Service worker and cache storage | Helps the app load and support installed-app behaviour |
| Security and technical logs | Helps protect the service and troubleshoot problems |
| Preferences | Remembers settings such as appearance, language and editor choices |
These technologies are used to provide the website, app, account, billing, Teams and local writing experience.
Local document storage
Local document storage is central to how Compose works.
It may contain personal data or confidential material if you put that information in your documents, notes, sources, comments or files.
We do not automatically upload that document content to us just because it is stored locally in your browser.
You are responsible for saving, exporting and backing up important work. Browser storage can be cleared by you, your browser, your device, private browsing settings, storage limits, security tools or other software.
Before clearing site data, changing browsers, resetting a device or uninstalling the app, save or export anything important.
Account and billing technologies
If you create an account, sign in, buy a plan or use Teams, our providers may use cookies or similar technologies to support:
- secure sign-in;
- account sessions;
- checkout;
- payment confirmation;
- billing portal access;
- Team access;
- tax calculation where configured;
- fraud prevention;
- service security.
Stripe, Supabase, Cloudflare and Resend may process information for the parts of the service they provide.
Analytics and advertising
At launch:
- we do not use advertising cookies;
- we do not use session replay;
- we do not use behavioural advertising pixels;
- we do not use in-app product analytics;
- we do not sell personal data;
- Cloudflare may provide default network, security and traffic information as part of hosting, security and delivery of the service.
If we introduce optional analytics, advertising cookies, affiliate tracking or similar technologies, we will update this policy and ask for consent where required.
How to control cookies and storage
You can control cookies and site data through your browser settings.
Most browsers let you block cookies, clear site data, delete local storage, remove cached files, control private browsing, and manage storage permissions.
Be careful: if you clear Tolstoy Compose site data, you may delete local-only drafts, notes, sources, review comments, versions, recovery data, settings and installed-app files.
If you want to keep your work, save or export it first.
What happens if you block storage
Some parts of Compose may not work properly if cookies or browser storage are blocked.
You may lose the ability to:
- stay signed in;
- use paid features;
- complete checkout or billing portal flows;
- save and restore local work;
- recover unsaved changes;
- keep versions;
- use the installed app smoothly;
- keep appearance and language preferences.
Changes to this policy
We may update this policy as the product, providers or law changes. If we add non-essential cookies or similar technologies, we will update this policy and ask for consent where required.
Contact
For questions about cookies and local storage, contact:
Bhavesh Prabhakar trading as Tolstoy Compose
Email: hello@createdbybhavesh.com