Revo Core Technologies: Official Document
Privacy Policy
What the Revo Treasury platform collects, why it collects it, and the boundaries we hold: no accounts, no trackers, no data sold. Your wallet is your identity.
Document
RVO-LGL-01
Version
V 1.0
Effective
2026-08-24
Status
IN FORCE
Scope of this policy
This Privacy Policy describes how Revo Core Technologies ("Revo", "we", "us") collects, uses, and protects information when you use the Revo Treasury platform, the public website, the operator console, and the underlying API (together, the "Service"), operating on Arc mainnet.
Revo is designed around a simple principle: your wallet is your identity. We do not run accounts, mailing lists, or advertising systems, and we collect only what the Service needs to function.
Information we collect
When you use the Service, we process the following categories of data:
- ›Wallet address. The public address you connect and sign in with. It identifies your operator session and your treasury.
- ›Authentication signatures. The one-time nonce we issue and the signed message you return to prove wallet ownership. Signatures authorize nothing beyond sign-in.
- ›Session data. A single session cookie that keeps you signed in, with its creation and expiry timestamps.
- ›Treasury records. Proposals, policies, activity history, security settings, alerts, and audit events generated by your use of the console.
- ›Agent conversations. Messages you exchange with Arcus, the treasury agent, and the responses it produces.
- ›On-chain transfer records. Transaction hashes, amounts, and wallet addresses for deposits, withdrawals, and swaps you initiate.
- ›Technical logs. Standard request logs (timestamps, request paths, status codes) used for reliability and abuse prevention.
What we do not collect
- ›No names, email addresses, phone numbers, or postal addresses.
- ›No government identification or KYC documentation.
- ›No private keys or seed phrases; signing always happens inside your own wallet.
- ›No third-party advertising trackers, analytics pixels, or fingerprinting scripts.
Design principle
How we use information
We use the data described above exclusively to:
- ›Authenticate operators and maintain signed-in sessions.
- ›Operate your treasury: generate, validate, execute, and record proposals.
- ›Verify deposits and process withdrawal requests on-chain.
- ›Enforce security controls: withdrawal caps, emergency pause, and role permissions.
- ›Maintain a tamper-evident audit trail of privileged actions.
- ›Detect abuse, debug failures, and keep the Service reliable.
We do not sell, rent, or trade any data, and we do not use your data for advertising or profiling.
AI processing
Arcus, the treasury agent, is powered by a third-party large-language-model provider. When you send a command or question, the text of your message, together with non-personal treasury context such as balances, modes, and policy state, is transmitted to that provider to generate a response.
Agent conversations are subject to rate limits and content bounds to prevent abuse. Do not include personal, sensitive, or confidential information in messages to Arcus; the agent needs none of it to manage your treasury.
On-chain data is public
Deposits, withdrawals, and Uniswap v4 trades settle on Arc mainnet, a public blockchain. Transaction hashes, wallet addresses, amounts, and timestamps are permanently visible to anyone through a block explorer. This is a property of public blockchains, not something Revo controls, and it cannot be deleted by us or by you.
How we protect data
- ›Tenant isolation. Every treasury is private to the wallet that owns it. All reads and writes are scoped server-side to your authenticated session; no client-supplied identifier can reach another treasury.
- ›Encrypted custody keys. Private keys for platform-managed treasury wallets are sealed with authenticated encryption at rest and are never exposed through the API.
- ›Tamper-evident auditing. Privileged actions are recorded in a hash-chained audit log, so retroactive modification is detectable.
- ›Signature-bound withdrawals. Funds only leave a treasury toward a wallet that has cryptographically proven ownership, within enforced limits.
Data retention
Treasury records, audit events, and transfer history are retained for as long as the Service operates, because they form the operational and security record of your treasury. Expired sessions are invalidated and unusable. On-chain records remain public according to Arc's operation and cannot be deleted by Revo.
Your controls
- ›Sign out at any time: this invalidates your session immediately.
- ›Stop using the Service: no background collection occurs when you are not signed in.
- ›Withdraw your funds: deposited USDC can be withdrawn back to the depositing wallet, subject to security limits.
Changes to this policy
We may update this policy as the Service evolves. Material changes will be reflected in the version number and effective date at the top of this document. Continued use of the Service after a change takes effect constitutes acceptance of the revised policy.
Contact
Questions about this policy can be raised through the operator console. This document should be read together with the Terms of Service and the Risk Disclaimer.
Issued by Revo Core Technologies · Arc mainnet · Chain 5042
RVO-LGL-01 · 2026-08-24
