Last updated: October 13, 2026
Policy version: 2026-10-13
What starts, and when
Ashore creates no dashboard cookie or local-storage item before you accept the current Terms of service and Acceptable-use policy during sign-in or registration. Existing cookies or browser storage from another site are not read, changed, or deleted by Ashore. A declined acceptance leaves no new Ashore browser storage from that request, although the browser, reverse proxy, network, or provider may retain connection metadata outside this notice.
Dashboard technologies
| Category | Ashore technology and purpose | Control |
|---|---|---|
| Essential authentication | paas_session is a first-party, host-only authentication cookie. It contains a 64-character hexadecimal encoding of 32 random bytes; the server stores only its SHA-256 hash. It is HttpOnly, SameSite=Strict, Path=/, and Secure on HTTPS. | Required for sign-in. Block or delete it in your browser. |
| Analytics | Ashore does not install analytics cookies, pixels, web beacons, SDKs, or session replay. | Nothing to configure. |
| Advertising and social | Ashore does not install advertising, targeted-advertising, social, cross-site, or fingerprinting technologies. | Nothing to configure. |
| Other dashboard storage | The dashboard does not use Ashore local storage or optional application-controlled browser storage. | Nothing to configure. |
Lifetime, renewal, and logout
The authentication cookie has a fixed maximum age of 24 hours. It is not renewed by activity, and it normally remains in the browser after the browser closes until it expires or is deleted. The server session expires at the same maximum age; periodic worker cleanup removes expired session rows separately. Logout clears the cookie and invalidates the corresponding server session.
If updated terms are declined
If an existing account session encounters a new terms version and you decline it, Ashore does not extend or refresh that session and will reject authenticated requests until the current terms are accepted. The already-issued cookie may remain in the browser and the already-created server session may remain until logout or its fixed expiry; clear the cookie or use logout to remove it sooner. No new cookie or local-storage item is created by declining.
Third-party technologies
Stripe Checkout and the customer portal load on separate Stripe pages after billing authorization. Stripe may use its own cookies and storage under Stripe’s cookie policy. Hosted applications and external services may also use their own technologies. This dashboard notice does not make claims about those separate surfaces.
Controls and changes
Blocking the authentication cookie prevents sign-in but does not delete server records, hosted data, or account information. Deleting it has the same effect. We will update this notice when dashboard technologies or purposes change; the effective date and policy version appear above. Contact the operator below with questions.
Structure adapted from the General Legal cookie-notice template, released under CC0. This Ashore notice is service-specific and is not legal advice.