Overview
This policy applies to orreryagent.com and the Orrery API. Orrery identifies people by wallet address. Each record the service holds is described below, with the reason it is held.
Orrery never asks for your name, email, phone number or a password, and the website carries no advertising or analytics trackers.
Data read from the chain
The service reads events emitted by the Orrery contracts and the ORRY pools on Robinhood Chain: addresses, amounts, transaction hashes and timestamps. From them it builds running totals for each address, for example stakes, Earn shares, and amounts claimed and earned.
Those totals feed your account views and the leaderboard. All of them derive from records anyone can already read on Robinhood Chain.
Credits and API keys
If an address signs in for an API key, purchases check credits or purchases the platform plan, the service records:
- the wallet address, with its credit balance;
- the end date of its platform plan, if it holds one;
- each payment: its amount, its status and its transaction hash;
- for an ORRY payment, the signed price quote, meaning the buyer address, the pack count or agent id, and the ORRY amount;
- how many checks the address runs in each month, and how many of those fell within the included allowance, so the included checks and the price tier can be applied.
A daily count of checks across every address is kept as well, with no address attached to it. A price quote that goes unused is deleted one day after its expiry.
An API key is held only as a SHA-256 hash tied to your address, and you see the full key a single time, when it is issued. Signing in for a key, or rotating one, relies on a one-time message valid for five minutes.
When you read a paying address, nothing about that address is stored. The only records that change are your credit balance and your check count for the month.
Agent verification
For an agent registered under ERC-8004, the service fetches its public registration file, the HTTPS endpoints it lists and its domain. It stores the outcome: whether the endpoints responded, whether the registration is valid, whether the domain is verified, a hash of the registration, and when the probe ran.
Probe outcomes are also written to Robinhood Chain, where they are public to read.
The website
Cookies hold your wallet connection, so it survives a page reload. They serve no other purpose.
A hosting provider serves the website, and your browser reaches Robinhood Chain through a public RPC endpoint. Each of them receives ordinary request data, your IP address among it, under its own privacy policy. Your keys and signatures are handled by your wallet app, under that app's policy.
Request limits and logs
To enforce request rate limits, the Orrery API holds your IP address in memory only and never writes it to its database. The servers keep operational logs, for example indexer progress.
Why the data is held
Every record above exists to operate the service: issuing keys, granting credits and plans, applying the included checks and price tiers, answering readings, showing balances and earnings, maintaining the leaderboard and keeping the API reachable. Data is shared with the providers that run the service, such as hosting and Robinhood Chain access, and wherever the law requires it.
Security
API keys are held as hashes. Key sign in and key rotation each rely on a one-time message your wallet signs. Your private keys and seed phrase never leave your wallet, and the service never needs them.
Your choices
You decide which wallet to connect and which messages and transactions to sign, and you can disconnect the wallet from the website whenever you like.
Records written to Robinhood Chain are public and remain on chain. To ask about anything the service holds for your address, use the contact details in the last section.
Revisions
Whenever the service changes what it holds, this policy is revised. Each revision appears on this page with a fresh date at the top.
Contact
Write to the team on X at @Orreryagent. The rules for using the service sit in the Terms of Use.
