[i] CLIENT STORAGE TRANSPARENCY
This Cookies Policy explains how Vellum Cash ("Vellum," "we," "us," or "our") uses cookies, browser local storage, and similar client technologies when you access our website (https://vellum.cash) or interact with the Sovereign Bridge Terminal.
By continuing to interact with our interface, you consent to our use of strictly necessary and functional client storage as articulated in this Codex. This document should be read alongside our Privacy Policy and Terms of Service.
§ 1. What Are Cookies & Web Storage?
[DEFINITIONS]Cookies are small text strings placed on your device (computer, smartphone, or hardware interface) when visiting a website. They enable web applications to maintain session state, secure against automated bot abuse, and remember user preferences.
SESSION COOKIESTemporary cookies that exist exclusively while your browser tab is open and are deleted upon closing the browser.
PERSISTENT COOKIESCookies that remain stored on your device until a set expiration epoch or until explicitly cleared by the user.
§ 2. Similar Client Technologies We Use
[STORAGE VECTORS]Beyond traditional HTTP cookies, Vellum utilizes modern HTML5 client storage APIs that store state directly inside your browser without sending data over network requests:
- Browser LocalStorage (localStorage): Stores client UI configurations (such as dark theme settings, selected source/destination EVM chains, and gas priority toggles). LocalStorage persists across sessions until manually cleared.
- Session Storage (sessionStorage): Manages temporary ephemeral conduit generation parameters and countdown timers during an active bridging session. Data is purged immediately when you close the browser tab.
- Web Workers & IndexedDB: Used strictly to cache compiled Circom WebAssembly artifacts (.wasm) and proving keys (.zkey) locally, accelerating client-side ZK proof computation without re-downloading large cryptographic proving matrices.
§ 3. Categorization of Cookies & Client Data
[TAXONOMY]3.1 Essential & Strictly Necessary Storage[MANDATORY]
These client markers are strictly necessary for the technical operation and security of Vellum. They cannot be disabled without breaking core routing.
• Edge DDoS Defense & Rate Limit Tokens (Edge Security)
• Cross-Site Request Forgery (CSRF) Prevention
• Ephemeral Conduit Route Verification State
3.2 Preference & Functionality Storage[FUNCTIONAL]
Enables the terminal interface to recall your preferred settings between visits, improving operational efficiency.
• Selected Source Chain (e.g. Ethereum Mainnet, Arbitrum, Base)
• Bridge Preset Amount Badges (e.g. 0.5 ETH, 1.0 ETH, 5.0 ETH)
• Terminal Slippage Tolerance & Poisson Delay Buffer Presets
• Documentation Expansion & Codex Sidebar State
3.3 API Request & Developer Storage[DEVELOPER]
Used when accessing developer console endpoints, generating API credentials, or reviewing real-time relayer node telemetry.
§ 4. Third-Party Services & Web3 RPCs
[ECOSYSTEM INTEGRATIONS]When interacting with public blockchains, your browser connects directly to decentralized Web3 Remote Procedure Call (RPC) nodes to read on-chain balances and broadcast raw zero-knowledge transaction envelopes.
We utilize privacy-respecting, anonymized telemetry (such as Vercel Edge Analytics) to detect broken build links and network outages without recording IP addresses or building profiling graphs. We do not integrate tracking pixels or surveillance SDKs.
§ 5. Managing & Deleting Client Storage
[USER CONTROLS]You possess full autonomy over the storage mechanisms enabled on your hardware. Most modern browsers allow you to inspect, restrict, or purge stored cookies and local storage:
Brave / Chrome / Chromium: Settings → Privacy and Security → Clear Browsing Data → Cookies and other site data.
Mozilla Firefox: Settings → Privacy & Security → Cookies and Site Data → Clear Data.
Apple Safari: Settings → Privacy → Manage Website Data → Remove All.
Notice on Clearing LocalStorage: If you clear local browser storage while an active ephemeral conduit is awaiting deposit, your local visual countdown timer and cached conduit address will be removed from your screen (though the on-chain smart contract conduit remains active until expired).
§ 6. Client Data Protection & Security
[SECURITY POSTURE]All cookies deployed by Vellum enforce the Secure attribute (ensuring transmission occurs strictly over encrypted HTTPS) and the SameSite=Strict attribute (mitigating cross-site request forgery risks).
§ 7. Updates to This Policy
[REVISION PROTOCOL]As Vellum integrates additional zero-knowledge proving backends or client optimizations, we may update this Cookies Policy. Changes take effect upon publication of the amended text.
§ 8. Contact Information
[COMMUNICATIONS]For technical inquiries regarding client storage or to request clarifications regarding web worker memory handling, contact our technical maintainers:
STORAGE INQUIRIES: support@vellum.cash[CODEX RATIFIED MMXXVI]