Cookies

Cookie note

Updated 1 October 2026

Folio uses a short list of storage, split the way European rules expect: what is required to run the service, and what is optional measurement.

Essential — always on

  • Session cookie from sign-in, so the server knows the request is yours. Duration follows the session.
  • folio-guest, httpOnly: remembers a guest desk so a refresh cannot mint a second welcome balance. About six months.
  • folio-theme in local storage: light or dark. Preference only.
  • folio-consent in local storage: the choice you made on the banner, so we do not ask every visit.

These are strictly necessary for a service you asked to sign in to, or for storing a preference you set.

Analytics — off until you allow it

If you opt in, Folio records a page-view event (path and time) against your account. No advertising cookies, no third-party ad networks, no sale of the record. Refuse and the studio still works. You can change your mind by clearing site data and answering the banner again, or by erasing your account.

What is not a cookie

Credit ledger entries, payment claims, and document-open events are account records kept to perform the contract, not tracking cookies. They are described in the privacy policy. The PDF itself is not stored.