What we use
This Interface uses cookies and local storage only to make ProveXAgent work in your browser. Settlement itself — escrow, ZK proof, release — does not depend on a marketing cookie.
Strictly necessary
- Session and security: CSRF-style barriers, rate-limit coherence, circuit-breaker display.
- Local protocol state: demo agents, simulated settlements, and console history in localStorage (provexagent-v2) so a refresh does not wipe a rehearsal.
- Preference crumbs such as a dismissed sheet or last-open tab, if present.
What we do not use as part of ProveX
- Cross-site advertising cookies.
- Sale of cookie-derived profiles.
- Third-party trackers injected into the proving flow.
How to control them
You can block or delete cookies and site data in your browser. If you do, the demo state and some Interface features will reset. Clearing storage does not unwind a ProveX escrow that already exists on PulseChain.
See also the Privacy Policy.
