Cookie Policy

Last updated: 25 August 2026 · consent version 2

In short. One cookie keeps you signed in. Your screenplays and breakdowns stay in your own browser or in your account — never sold, never shared for advertising. There is no analytics, no advertising, no profiling, and no other company involved: every library this app needs is served from here. The one thing we ask permission for is whether that sign-in cookie may outlive your browser session.

Cookies we set

NameWhat it doesHow longType
spoglio_sessione Keeps you signed in. It holds a signed identifier and nothing else — no name, no email, no behaviour. It is HttpOnly, so page scripts cannot read it, and Secure on the live site. Until you close your browser Strictly necessary
spoglio_sessione
(kept)
The same cookie, but allowed to survive closing your browser so you return straight to your work. Signing you in during a visit is necessary and needs no permission; recognising you a week later is a convenience, so we ask first. If you say no, or say nothing, the cookie is erased when you close the browser. 30 days Your choice

That is the entire list. We set no other cookie, first-party or third-party.

What the app keeps inside your browser

These are not cookies — nothing here is sent to us automatically — but the law treats storing them on your device the same way, so here they are in full.

WhereWhatType
IndexedDB Your projects and drafts, so your work survives a reload and so the app can run without an account at all. Strictly necessary
sessionStorage The passcode for AI analysis, for as long as the tab is open. It is gone when you close it. Strictly necessary
localStorage — b27.consenso Your answer to the choice below, with the date you gave it and the version of this policy it refers to. Without it we would have to ask you on every page. Strictly necessary

Other companies your browser talks to

Loading a file from another company means your IP address reaches that company, even when no cookie is involved. So we removed them. The PDF reader and the spreadsheet writer used to come from public CDNs; both are now served from this site, with their versions and checksums recorded in the source. Opening your screenplay and exporting your breakdown involve nobody but us.

WhoWhyType
Stripe Payment, and only if you subscribe. Card details are handled on Stripe's own pages, under Stripe's own policy — we never see or store them, and Stripe sets no cookie on this site. Strictly necessary to pay

Our hosting provider and our database provider process data on our behalf under contract; they are listed in the Privacy Policy.

Your choice

The first time you arrive we ask, before anything optional happens. Accepting and refusing are the same single click — refusing is not buried in a second screen, and choosing nothing counts as a refusal. We record what you chose and when, together with the version of this policy, because a consent nobody can date is a consent nobody can prove. We ask again after six months, and again whenever this list changes. Change your mind while signed in and the cookie is reissued immediately — a withdrawn consent that stayed on your device for another month would not be a withdrawal at all.

Turning everything off

Your browser settings can block cookies entirely. If you block the session cookie you cannot stay signed in — the app still works without an account, keeping your projects on your own machine. Clearing your browser data clears everything on this page, including the record of your choice, and we will ask again.