Cookies and Browser Storage
Version 1.0, effective
One cookie, no tracking, and why there is no consent banner.
#
One cookie: nayto_operator_session. It holds a reference to your signed-in session in the console. It is HttpOnly, so no script on the page can read it; SameSite=Lax, so it is not sent with another site's request; and Secure, so it only travels over an encrypted connection.
It is set when you sign in and cleared when you sign out, and it lasts no longer than the session it refers to - at most 30 days. Nothing else is in it: it carries a reference, not your identity, your organization or your permissions, all of which are looked up on our servers for each request.
#
Nothing in sessionStorage. No analytics, no tag manager, no advertising pixel and no session recording, on the website or in the console.
One thing is kept in localStorage, and only if you ask for it: choosing a light or dark theme in the console writes that single word under the key nayto.theme, so the console does not flash the wrong colours the next time you open it. Leaving the theme to follow your system writes nothing, which is the default, and clearing the choice removes the key.
This is checked, not intended: our browser tests record every write to browser storage while signing in and using the console, and fail if anything else appears.
#
When you create an account, or sign in after many wrong passwords, the page runs Cloudflare Turnstile, which reads signals from your browser to tell a person from an automated script. It is used for that check alone, not to track you. See the subprocessors page.
When you pay for a plan or manage billing, the console sends you to Stripe's own checkout and billing pages. Stripe sets the cookies it needs there, for payment and fraud prevention, under Stripe's privacy policy.
#
Laws such as the EU's ePrivacy rules require consent before a site stores or reads information on your device, except where it is strictly necessary for a service you asked for. A single sign-in cookie, set only after you choose to sign in and used only to keep you signed in, is the plainest example of that exception; so is remembering a theme you chose.
A banner would ask permission for the one thing that does not need it, while suggesting there is something else. We would rather publish the list.
If we ever add analytics or anything else that needs consent, this page changes first and a consent banner arrives with it.
#
The player app on a screen keeps its screen credential and its last published content on the device itself, so the screen keeps playing when the network does not. That is storage on hardware you control, used only to run the screen, and nobody browses on it.
#
Write to privacy@nayto.io.
#
Every version of this document has a number and the date it applies from, both printed under the title. A change is published as a new version rather than an edit to this one, so what the document said on any day can be checked.
When a change matters to what you have agreed or to how we use your data, we tell you before it takes effect. Earlier versions are available from legal@nayto.io.