How storage is used
Overview
This notice covers cookies, local storage, session storage and similar technologies on the RAMSCloud website and application. They support sign-in, requested editing and preferences, and service measurement. A technology can process device information even when it does not use cookies.
Strictly necessary storage
Sign-in and security storage supports authenticated access. Editor recovery and interface preferences support requested functions. Each technology must meet the conditions of the relevant legal exception or use consent where required; useful storage is not automatically strictly necessary.
Local document drafts
Your browser may retain document drafts, file references and interface preferences. Local storage can remain after closing the browser until cleared or replaced. Session storage normally ends with the tab, subject to browser restoration. There is no universal automatic expiry for editor drafts. Cloud deletion does not clear copies on every device. Clear site storage before sharing a device, but save needed work first: clearing it can remove unsaved drafts.
Analytics and optional storage
Vercel Web Analytics measures page use and limited product events, and Speed Insights measures performance. Our event payloads exclude document content, raw search queries and direct account identifiers; telemetry URLs are filtered to remove query strings and UUID path segments. Vercel also processes request/device information and temporary hashed visitor identifiers. These tools are not used by this integration for advertising. Cookie-free does not mean that no device information or personal data is processed.
Technology list
| Name | Type | Provider | Purpose | Duration | Status |
|---|---|---|---|---|---|
| Supabase sign-in | Cookies | RAMSCloud / Supabase | Maintain authentication and session refresh, including temporary sign-in state | Persistent authentication cookies use an expiry of up to 400 days when set or renewed; sign-out and browser controls can clear them, and actual session validity is separate | Used for requested sign-in; blocking can prevent authenticated access |
| RAMS editor recovery | Local storage | RAMSCloud | Recover document editing state and supporting-file references on this device | Until cleared, replaced or removed by the editor; no universal automatic time expiry | Supports editing; clearing site storage can remove unsaved work |
| Theme and interface preferences | Local storage | RAMSCloud | Remember theme, library views, management pins and document-output preferences where used | Until cleared or replaced | Changed through relevant interface settings or browser storage controls |
| Announcement draft | Session storage | RAMSCloud | Recover an unsent management announcement | Normally the tab session, subject to browser restoration; removed after successful save | Used in the management announcement editor |
| Vercel Web Analytics | Browser network requests; no analytics cookies or local storage | Vercel | Measure page use and bounded product events using request/device information and temporary hashed visitor identification | Vercel describes the visitor identifier as lasting up to 24 hours; this is not the reporting-data retention period, which depends on the provider plan | No self-service analytics choice switch; signed-in account exclusions are managed by the platform Owner |
| Vercel Speed Insights | Browser network requests; no analytics cookies or local storage | Vercel | Measure page performance using browser performance APIs and request/device information | Measurements are sent during page visits; reporting availability and provider retention depend on the provider plan | Uses the same account-exclusion check; no self-service analytics choice switch |
Choices and changes
Consent controls
The current service does not display an analytics cookie banner or provide a self-service analytics consent or objection switch. Vercel Web Analytics and Speed Insights use network requests rather than analytics cookies or local storage. Cookie-free measurement can still involve device information and is not, by itself, a reason that consent or objection requirements do not apply. The platform Owner can exclude a signed-in account from the integrated analytics and performance measurement. Contact support@ramscloud.co.uk to request an account-based exclusion or raise a measurement objection. The app checks that exclusion before loading or sending integrated browser telemetry and keeps that telemetry off if the policy check fails. This account-based control does not provide a choice for anonymous visits. You can change interface preferences in the app and inspect, block or clear cookies and browser storage through your browser. Blocking sign-in cookies may prevent access, and clearing recovery storage may delete unsaved work. Clearing cookies or storage does not by itself stop cookie-free measurement requests.
Browser controls
Browser settings can remove or block stored information. Blocking essential authentication storage may prevent sign-in and some preferences from working.
Questions contact
Effective date
25 October 2026