DeTrust PayIncentive-EnforcedSecure payments powered by DeTrustPay Protocol.
Cookie and storage policy

Cookies and browser storage in DeTrustPay

DeTrustPay uses storage for security, session continuity, and usability. Storage controls affect off-chain app behavior, not on-chain protocol finality.

Effective date: 2026-02-08Version: 2.0Privacy policyTerms
DeFi 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 DeTrustPay Protocol (eDDE) records are public and immutable.
  • Clearing browser storage does not remove, change, or hide finalized blockchain data.
Storage classes

What we store and why

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

Strictly necessary

Authenticate users, protect sessions, and preserve secure app operation.

Where stored: Secure cookies and browser storage
Retention: Session-scoped or rotated by security controls
  • Required for sign-in, account continuity, and abuse prevention.
  • Local snapshot for on-chain data.
  • Blocking these items may disable protected DeTrustPay workflows.
Functional preferences

Remember UI and workflow preferences for a stable user experience.

Where stored: Browser local storage
Retention: Until user clears data or app resets preferences
  • Examples include display preferences and non-sensitive UI state.
  • Removing these items resets personalization but does not alter on-chain records.
Performance and diagnostics

Maintain reliability, detect failures, and investigate service incidents.

Where stored: Operational telemetry and app diagnostics
Retention: Limited operational retention windows
  • Used for service stability and security response, not advertising profiles.
  • Collected data is scoped to operational needs.
We do not use

Tracking boundaries

DeTrustPay avoids ad-tech cookie behavior that conflicts with a mechanism-first product.

  • No third-party ad-tech cookies for behavioral advertising.
  • No cross-site tracking cookies for marketing profiling.
  • No cookie-based replacement for wallet 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 and require re-authentication.
  • Clearing preference storage resets non-critical UI behavior.
  • In-app settings can be used to adjust supported preferences without clearing all site data.
Operational noteClearing essential storage usually requires signing in again.
Security context

Session and storage security

Security controls are designed to limit unauthorized access and maintain service integrity.

  • Session security controls are designed to reduce unauthorized access risk.
  • Transport and operational controls are applied to protect off-chain service data.
  • Security events are handled according to applicable law and incident response procedures.
Security overviewRisk disclosure
Questions and requests

Need help with storage behavior?

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

FAQHow it worksSupport page