Traceability Protocols
We strictly control local storage states and user traceability. Here lies the explicit documentation on how we manage your session footprints.
Local State & Cookies
Cookies are localized state-files written to your node when opening sockets to our frontends. They manage telemetry, preserve authenticated sessions, and measure infrastructure latency.
01 Usage Mechanics
Melon Data Services uses session states for the following operational vectors:
- REQEssential States: Hard requirements for sysadmin logins and socket connections.
- LOGPerformance Tracking: Analytics allowing us to measure rendering and ping speeds.
- OPTFunctional Caching: Saving queries and system configurations between sessions.
02 State Types
Strictly Necessary
Un-toggleable files required to boot. E.g. JWT tokens, CSRF protection variables.
Telemetry
Aggregated logs (Google Analytics) that show us system stress points and UX blockers.
03 External Handshakes
Some files are pushed by external content delivery networks (CDNs) or support interfaces:
Google Analytics
Measures network traffic loads.
CDN Nodes
Caches static assets at grid edges.
05 Retention Arrays
| Array Buffer | TTL (Time to Live) |
|---|---|
| Session_Token | Terminated on Browser Close |
| Persistent_Config | 30 - 365 Days |
| Analytics_UUID | 13 - 26 Months |
Manage States
Most terminal interfaces (browsers) allow you to natively block write-access. For internal questions, ping us: