Authentication
Session and security cookies keep users signed in, protect requests, and support account-security workflows.
Cookies
Sklash Cookie and Local Storage Notice
A practical explanation of the cookies and browser storage used to sign users in, protect sessions, remember preferences, and operate Sklash.
Overview
What this means in practice
Explore the systems, responsibilities, and workflows behind this part of Sklash.
Preferences
Browser storage may remember interface choices, navigation state, dismissed notices, or public Site preferences.
Public Sites
Creators may enable their own cookie notice for public Sites when their configuration or integrations require one.
Control
You can clear browser cookies and local storage, but doing so may sign you out or reset saved interface preferences.
Current beta use
Sklash uses essential storage to operate accounts and security.
- Session authentication and remember-me state.
- Cross-site request forgery protection and security challenges.
- Passkey, two-factor, password confirmation, and Google authentication state.
- Interface preferences and dismissed notices stored in the browser where appropriate.
Third parties
Connected providers may set or receive browser information during their workflows.
Google authentication, payment providers, media services, monitoring, or future analytics may operate under their own notices when enabled.
Sklash will update this notice and request renewed acceptance when optional tracking or materially different browser storage is introduced.
Continue
Read the Privacy Notice
Cookies are one part of Sklash data handling.
The Privacy Notice describes account, project, operational, provider, and beta-reset data practices.