Privacy notice

Omnious, Address supplied in the beta invitation, operates this beta. Contact privacy@omnious.xyz for privacy requests or questions.

• Account and access: wallet address, Privy account identifiers, invite status, and security/session records.
• Payments and market records: signed USDC authorisations, request identifiers, token counts, prices, provider, settlement references, and immutable receipt/epoch evidence. We do not receive your wallet private key.
• Prompts and replies: routed to the winning inference provider. Raw completion calls and ordinary quick chat are transient. Chat Build mode and explicit agent runs create a capability-protected durable task containing the submitted goal, execution events, checkpoints, and effect/verification evidence. Patient orders retain a prompt until close; explicit public shares retain the selected transcript until revoked or expiry.
• Location: when you ask a relative question such as “near me”, your browser asks before sharing its current coordinates. If approved, they are sent to the winning inference provider and map-data service for that request, and are not added to the saved visible conversation.
• Optional connectors: provider account labels and encrypted OAuth access/refresh tokens. Connected services process the exact reads and approved actions you request.
• Device data: settings, local conversations, drafts, burner-wallet material, recovery markers, and revocation capabilities may remain in your browser storage.
• Operations and support: bounded IP/security logs, error diagnostics, feedback, and correspondence.

We process data to perform the beta service and payments; secure, prevent abuse, reconcile, and improve it; meet legal obligations; and pursue legitimate interests in reliable operations and fraud prevention. Optional feedback/identity sharing is based on your consent, which you can withdraw below.

Data may reach the winning model provider; Privy; HyperEVM infrastructure; connected OAuth providers; hosting, database, logging, support, and privacy-configured product analytics vendors; and advisers or authorities where required. PostHog receives anonymous US-region product analytics and interaction replay. Input values are masked; message content, attachments, conversation titles, request bodies, request headers, console logs, and sensitive application network requests are excluded. Some recipients may process outside the UK. We use the transfer mechanism and safeguards applicable to each vendor; request current vendor details or safeguards at the address above.

• Ordinary prompt/reply buffers: memory only and swept within minutes; not written to the router database.
• Durable tasks: seven days by default, caller-selectable from one hour to 30 days, or until earlier deletion with the task capability. Expiry/deletion removes the task, events, checkpoints, effects, and approvals.
• Public conversation shares: available for 30 days or until earlier revocation using the management capability stored in the publishing browser. Expired rows are denied immediately and swept from storage by the hourly cleanup.
• OAuth tokens: until disconnect, revocation, expiry, or account deletion; transient OAuth proof rows expire within minutes and sessions within their configured lifetime.
• Payment, receipt, anti-fraud, action-receipt, and accounting records: retained for the beta and afterwards as reasonably needed for reconciliation, claims, security, and legal obligations. Before external launch, the operator must publish the exact statutory/accounting schedule.
• Local browser data: until you delete it, clear site storage, or use the relevant in-product control.

Depending on applicable law and the processing basis, you may request access, correction, deletion, restriction, portability, or object to processing. You may withdraw consent at any time and complain to the UK Information Commissioner’s Office or your local supervisory authority. Some payment/receipt evidence cannot be erased where retention or immutable-chain records are legally or technically required.

You may object at any time to processing based on legitimate interests by emailing the privacy address above.

Omnious uses first-party cookies and browser storage needed for network selection, authentication, invite access, security, recovery, preferences, local product state, and anonymous product analytics and session continuity. PostHog is not given a wallet, email, or other identified person profile, and message recording is blocked. The optional UserJot feedback SDK is not loaded until you actively agree when opening feedback. Omnious does not use advertising cookies in this beta.

The beta is for people aged 18 or over. We will show material privacy changes before they take effect and review this notice as the product, processors, and law change.