Legal

Privacy Policy

What data the Robot Money website collects, and what it does not

1. Overview

Robot Money is a permissionless, non-custodial interface to a public blockchain protocol. We intentionally minimize the personal data this Site collects: we do not require an account, an email address, or KYC information to browse the Site or view the analytics dashboard.

2. Onchain Data Is Public

Wallet addresses, transaction history, token balances, and other data displayed by the analytics dashboard are read from public blockchains and public third-party APIs (block explorers, market-data providers). This data is public by the nature of the blockchain itself — Robot Money does not create, sell, or exclusively control it, and displaying it on the Site does not make it any more or less public than it already is onchain.

3. Information We Collect

Usage data. Our servers record technical request logs. When public-site analytics is enabled, we load Cloudflare Zaraz and send page visits to Google Analytics only after you accept analytics. This can include browser type, approximate location and a cookie-based visitor identifier. Privileged pages are excluded; page URLs sent to Google omit query parameters and fragments.

Local storage. The Site uses your browser's session and local storage to remember UI state — for example, table sort order, column widths, and dashboard access tokens — entirely on your device. This data is never transmitted to us as "personal data" beyond what your browser sends with any ordinary web request.

Voluntary submissions. If you use a form on the Site (for example, to submit an agent, coin, vault, or wallet for tracking, or to apply to a program), we collect exactly the information you choose to enter into that form.

Early access requests. The early access form collects a Telegram or X handle, what best describes you (for example a DAO or an individual), the range you would deposit and the share of your treasury you would hold outside stablecoins. An email address and an EVM wallet address are optional. A referral code, typed into the form or carried by the referral link you arrived through, is stored with your request. A handle and a wallet address together connect you to everything that wallet holds and does on chain, so this list is kept private, in a spreadsheet in our Google Workspace: it is used only to contact you about access to the vault and to credit the referral, and it is never published or sold.

4. What We Do Not Collect

We do not require wallet-signature-based login, do not ask for private keys or seed phrases (never enter these anywhere), and do not link your onchain activity to an offchain identity unless you voluntarily provide that link through a submission form.

5. Cookies and Similar Technologies

The Site uses essential browser storage for access and UI state. We save your analytics choice locally. Optional Google Analytics cookies are used only after acceptance. Use Analytics preferences to reject or change your choice; rejection stops new collection and reloads a document that has already loaded analytics. No advertising tracking or session replay is enabled.

6. Third-Party Services

The Site fetches data from third-party providers server-side (for example, block explorers and market-data APIs) to render dashboard pages. Your browser's requests to the Site do not go directly to those third parties for this data; where a page links out to a third party (for example, an explorer or a project's own site), that third party's own privacy policy governs your interaction with it.

7. Data Retention

Voluntary submissions and any associated moderation records are retained for as long as needed to operate the Site's review and tracking pipeline. Early access requests are kept while they are needed to give access and to credit referrals, and yours is removed if you ask. Usage/analytics data is retained only as long as needed for aggregate traffic analysis and is not sold to third parties.

8. Changes to This Policy

This Privacy Policy may be updated from time to time. Material changes will be reflected by an updated "Last Updated" date below. Continued use of the Site after a change constitutes acceptance of the revised policy.

9. Contact

Questions about this policy can be raised through any of the community channels linked from the Site's home page.

Last Updated: October 2026