Cookie and storage policy

Cookies and browser storage in eeteel

eeteel uses storage for security, session continuity, and interface usability. Storage controls affect off-chain app behavior, not on-chain share or claim finality.

Effective date: 2026-03-11Version: 2.0Privacy policy Terms

Protocol boundary

Off-chain storage vs on-chain records

Browser storage and blockchain records are different layers with different properties.

Cookies and local storage are off-chain browser artifacts.
On-chain share ownership, stake state, and claim history are separate public blockchain records.
Clearing browser storage does not remove, change, or hide finalized on-chain data.

Storage classes

What we store and why

Storage is categorized by purpose, location, and retention behavior.

Strictly necessary

Maintain secure sessions, protect wallet-connected flows, and preserve safe app operation.

Where stored: Secure cookies and browser storage

Retention: Session-scoped or rotated by security controls

Required for sign-in, session continuity, and abuse prevention where applicable.
May support app-level routing, protected views, and secure interface behavior.
Blocking these items may disable important dashboard or support workflows.

Functional preferences

Remember UI choices and non-sensitive workflow preferences.

Where stored: Browser local storage

Retention: Until the user clears data or the app resets preferences

Examples include selected tabs, display preferences, and non-sensitive dashboard state.
Removing these items resets local preferences but does not affect on-chain records.

Performance and diagnostics

Support reliability, error detection, and service troubleshooting.

Where stored: Operational telemetry and diagnostics systems

Retention: Limited operational retention windows

Used for stability, debugging, and security response rather than ad-tech profiling.
Collected data is limited to operational and product reliability needs.

We do not use

Tracking boundaries

eeteel avoids ad-tech cookie behavior that does not fit a protocol and infrastructure product.

No third-party ad-tech cookies for behavioral advertising.
No cross-site tracking cookies for marketing profiling.
No cookie-based replacement for wallet custody or private key control.

User controls

Managing cookies and storage

Browser controls and app settings provide direct control over local artifacts.

Use browser controls to inspect, block, or clear site storage.
Clearing essential storage may sign you out or reset secure app sessions.
Clearing preference storage resets non-critical UI behavior such as selected views or local interface preferences.
App settings may support preference changes without clearing all local storage.

Operational noteClearing essential storage usually requires signing in again or reconnecting to protected app surfaces.

Security context

Session and storage security

Security controls are designed to reduce unauthorized access and preserve service integrity.

Session and storage controls are designed to reduce unauthorized access risk.
Transport and operational controls are used to protect off-chain service data.
Security events are handled according to incident response and applicable legal obligations.

Security overview Risk disclosure

Questions and requests

Need help with storage behavior?

Review docs first, then contact support for account-specific clarification.

FAQ How it works Support page contactus@currinfo.com