Cookies and browser storage
Short, because there is not much to say: one cookie signs you in, three keys remember how you like the site, and nothing here follows you anywhere else.
What is set, and why
The table is generated from the same module the application itself reads, so it cannot drift from what your browser actually receives. Open your developer tools, look at storage for this origin, and you should see exactly this and nothing else.
| Name | Category | What it holds | How long |
|---|---|---|---|
shaidle.session | Essential | the sign-in session, set when you sign in | cleared when you sign out |
shaidle.consent | Essential | this very answer, so the bar does not ask again | kept until you change it |
shaidle-theme | Preference | dark or light | Until you clear it or choose “Essential only” |
shaidle-role | Preference | whether you are looking at Buy or Sell | Until you clear it or choose “Essential only” |
shaidle.film.seen | Preference | whether the launch film has already played | Until you clear it or choose “Essential only” |
Changing your mind
Choosing Essential only does not merely stop future writes — the preference keys already in your browser are deleted at that moment. Your theme and your Buy/Sell view keep working for the rest of the visit; they simply stop surviving a reload.
The film on the front page is part of the same bargain. It introduces itself once and then never again, and it can only make that promise if it is allowed to remember that it already played — so if you decline, it does not open by itself at all. The “Watch the film” button on the landing page is always there, and the player carries its own Don’t open this on its own again checkbox.
This browser is not letting us store anything at all — private mode, or storage turned off. Nothing on the table above is being written, so there is nothing to decide and the bar does not appear.
The rest of it
What we collect on the server side — account data, ledger movements, per-job usage metadata — is a different question, and it is answered on the privacy policy. Payment goes through an external checkout that sets its own cookies on its own domain under its own policy; we do not set anything there and cannot read it. For anything else, the contact page.