01
What we store, and why
Scriptopus uses your browser's storage for two purposes: making the product work, and counting visits so we can see which screens people use and fix what is confusing. The first is keeping you signed in, keeping your writing safe on your own device, and remembering preferences like your theme. Everything in the inventory below is strictly necessary for a feature you are actively using.
The second is analytics. It is not necessary; we run it because we would rather fix a confusing screen than guess about it. Section 03 says exactly what it records, what it is prevented from recording, and how to switch it off.
02
The full inventory
Cookies
| Name | Set by | Purpose | Lifetime |
|---|---|---|---|
sb_auth |
app.scriptopus.com, for all scriptopus.com sites | A 0/1 flag meaning "a writer is signed in", so the marketing site can show "Continue writing" instead of "Log in". It carries no identity, no token, and nothing readable about you. | 30 days, refreshed while you use the app; cleared on sign-out |
_ga, _ga_…app_ga, app_ga_… |
Google Analytics: the first pair on this site, the second in the app | A random id and the time of your last visit, so a returning visitor is not counted as a new one. It is not linked to your account, your name or your email. See section 03. | 12 months; in the app, removed when you switch analytics off |
Browser local storage (app.scriptopus.com only)
| What | Purpose |
|---|---|
| Session tokens | Keeping you signed in between visits, so the app can talk to your account securely. |
| Your projects (local-first copy) | The working copy of your scripts on your own device, so writing works offline and instantly. |
| Preferences | Theme, page setup, panel layout, dismissed tours and hints: the app remembering how you like it. |
Third parties: the site loads its fonts from Google Fonts, which serves font files without setting cookies. If you use "Sign in with Google", Google's own sign-in page operates under Google's privacy policy on Google's domain, not ours. Analytics is Google Analytics, which loads from Google's servers and reports to them directly.
03
Analytics, and what we still do not use
We use Google Analytics to count visits: how many people come, roughly where from (country and city), on what kind of device, and which pages and screens they open. That is the whole ambition: finding the screen where people give up. Its advertising features and Google signals are switched off, so none of it feeds Google's ads.
Three limits are built in
- Your screen is never recorded. Nothing we run plays your visit back like a video, in the app or on this site. There is no recording of your editor to leak, lose or subpoena.
- Your writing is never sent. Google Analytics counts visits and page views. It never reads what you type or what an editor holds, so not a line of your screenplay reaches it. In the app it does not even see the address in your browser bar: it is told the name of the screen instead, such as "project / script", so no project id, share link or invitation link reaches Google.
- It is not tied to your account. We do not connect analytics to your name, your email or your projects.
Switching it off
We honour your browser's Do Not Track setting on both the app and this site: turn it on and nothing is collected. Inside the app you can also choose Local only or Offline storage. Both switch analytics off completely. Error reports are a separate matter: the web app sends them to FaultFixer, our error-tracking service, in every storage mode, as the Privacy Policy describes.
The app's daily activity tally is a different thing. It sets no cookie and is kept with your account, and the Privacy Policy explains what it counts and who it leaves out.
What we still do not use
- No advertising or retargeting cookies.
- No social-media pixels.
- No cross-site tracking of any kind, ours or anyone else's.
- We do not sell anything to anyone, ever.
If that ever changes, this page and the Privacy Policy will change first.
04
Your control
You can clear cookies and site data for scriptopus.com at any time from your browser's settings. The effect is that you will be signed out, the app will re-sync your projects from the cloud on your next sign-in, and the analytics ids are forgotten. Blocking storage outright also works; it just prevents the app from keeping you signed in on that device.
To stop analytics without losing the rest, use the two switches in section 03: Do Not Track in your browser, or Local only / Offline storage inside the app.
Questions: hello@scriptopus.com.