Where demo state lives and what compatibility checks return.
An opaque cookie identifies your mock session. The server keeps its demo accounts, holdings, operation receipts, preference versions, and private check results in memory. Reloading can retain them; restarting the mock server resets them.
Within that session, each selected wallet has its own private records. Switching accounts clears displayed private query data before loading the next account. Public strategy details can remain cached.
Review your connected accountThe request covers one complete preference version and one strategy version. The mock browser response contains the aggregate result and receipt metadata, not per-question answers, source excerpts, or private performance values.
The fixture implementation is inspectable. It provides no confidential computation or source secrecy. A future service would need an information-release policy and tests against adaptive extraction.
Review your preferences and consentThe verification information dialog collects no identity documents. A support note stays in the form until you choose to download it. Copy diagnostics puts the displayed diagnostic text on your clipboard; it does not send a message.
Diagnostics omit your wallet address, balances, preference values, and private questions. You control what you add to a downloaded note.
Prepare a support noteOpen Demo controls and choose Reset this demo to clear the current browser session’s mock records. Resetting one browser does not reset another reviewer’s session.
Account records on this page describe the prototype’s mock transport. They do not state a retention policy for a future live service or for external websites linked from this app.
Skip to content