01The short version
Nara is built so we don't need much about you. Agents and runners sign in with keys, not names or emails. A recipient's details are encrypted for one runner before they reach us. We don't run identity checks, show ads or use third-party analytics, and we never sell data. This is everything we store:
| What | Why | Kept for |
|---|---|---|
| Job records | To run and settle each payout: the agent's address and public key, the rail, the amount, the kind of recipient detail (an email, a phone, an IBAN…), the deadline, the fee cap, an optional label, the runner's per-job key, payout address and fee, statuses, times and transaction hashes. | Kept for: 180 days after the job ends (§10) |
| Sealed recipient details | Ciphertext encrypted to the assigned runner. If the agent disputes, a sealed copy of its key for the arbiter. We can't read either. | Kept for: 30 days after the job ends |
| Payment proofs | Ciphertext from the runner, encrypted to the agent and sealed to the arbiter, for disputes. | Kept for: 30 days after the job ends |
| Runner profiles | A runner's account address and public key, alias, rails, limits, fee, online status, first and last seen, job counts and reputation. Agents see the alias and the reputation. | Kept for: 365 days after the runner's last activity |
| Caps and relay budgets | Each agent's dollar total for the day, and how many signatures the relayer submitted. | Kept for: 2 days |
| Used signatures | A record of each signed request, so nobody can replay it. | Kept for: 10 minutes |
| Email address | Updates list: news about the launch and your spot. | Kept for: Until you ask, or the list closes |
| Referral code and count | Your place on the list and your points, plus a one-way hash of your inbox so a referral counts once. Not who referred whom. | Kept for: Same as your email |
| @handle and meta-addressPublic | So people can pay your private account by handle. Includes the wallet that claimed it. | Kept for: Until you ask us to remove it |
| Payment announcementsPublic | Copies of public notes attached to private-account payments, so apps find them fast. | Kept for: Kept (public anyway) |
| Scanned address and report | A cache, so repeat scans don't hit the network again. | Kept for: Up to 24 hours |
| Share card | A random ID with a coarse score and labels. Never the address. | Kept for: 30 days |
| Console requests | Turned into a plan on our server, then dropped. Never logged. | Kept for: Not stored |
| Rate-limit counters | Counting requests per IP address to stop abuse. | Kept for: A day at most |
| Request logs | Kept by our hosting provider for security and debugging. | Kept for: Set by the host |
02Who we are
This policy covers the Nara website, APIs, SDK, MCP server and apps (the “Service”), run by the operator of Nara (“we”, “us”). Our legal entity details will be published here once confirmed. Until then, reach us through the contact in section 16.
03What we never collect
- An agent's private key. The SDK and the MCP server sign on your machine and send signatures only.
- Your Nara keys, and the runner keys derived from them. They come from a signature inside your browser, stay in memory, and are never sent to us or saved.
- Who owns an agent, or who a runner is. We never ask for a name, an email or an ID to pay or to run.
- Readable recipient details. They're encrypted before they leave the agent's machine.
- Advertising or tracking cookies, or third-party analytics.
04Payouts: what we store
Jobs
When an agent posts a payout, we keep a job record (see the table) so we can show it to runners, match it, track it through the escrow and enforce the caps. The public job board shows only the rail, the amount and payout currency, the kind of recipient detail, the fee cap and the deadline: never the agent, the label or the details themselves.
Recipient details
The agent's SDK encrypts the recipient's details to the assigned runner's key (ECDH on secp256k1, HKDF-SHA256, AES-256-GCM) and sends us the ciphertext, which we store and hand to that runner once the escrow is funded. We can't read it. If the agent disputes, its SDK also seals the key of that ciphertext to the arbiter, so the arbiter can check what the runner was asked to pay.
Notes and labels
The note a runner writes on the payment (the SDK's memo) is encrypted with the recipient's details. The API also accepts an optional job label that is not encrypted: we store it and show it to the assigned runner only. Don't put anything private in it.
Proofs
A runner's proof of payment (a reference or a screenshot) is encrypted to the agent and sealed to the arbiter before it reaches us. The arbiter uses it to decide disputes.
Runners
A runner's profile holds a key-derived account address, an alias, the rails, limits and fee they chose, whether they're online, and counts of their jobs, from which we compute a reputation agents can see. Each job uses a fresh key on-chain; our server knows which runner account took which job, because it handled the signed request.
The arbiter
The arbiter is run by us for now. It can open proofs, and the recipient details of a disputed job, and uses them only to decide disputes.
05Everything else we store
Updates list
Your email address, a referral code, your place on the list and how many people joined with your code, plus a one-way hash of your inbox (your address without +tags or dots) so each inbox earns a referral only once. We don't record who referred whom. We use your email to tell you about the launch and your spot. Nothing else.
@handles
Your handle, the public meta-address it points to, the wallet address that signed the claim, and when. The handle and meta-address are public by design: that's how people pay you. We never publish the claiming wallet, and there is no way to look up a handle from a wallet address.
Payment announcements
After a payment to a private account, the paying app sends us a copy of the public note attached to it. It's already on the blockchain. Your app checks notes in your browser, so we never learn which ones are yours.
Exposure scanner
The address you scan and its report, cached for up to 24 hours. A share card holds a random ID, a coarse score and up to four finding labels for 30 days: never the address, balances or counterparties.
Console requests
When you ask the agent console for something, our server turns your words into a plan and sends it back. We don't store or log the text. If our built-in rules can't read a request, it may be sent to our AI model provider to draft the plan.
Abuse protection and logs
We count requests per IP address in short windows to stop abuse; the counters delete themselves within a day at most. Our hosting provider records standard request logs (IP address, time, page requested, browser type) for security and debugging, and deletes them on its own schedule.
06What stays in your browser
We don't use cookies. Your browser's storage keeps only small conveniences, on your device, and never sends them to us on its own: your updates-list code, which wallet app you connected, a short fingerprint of your Nara keys (derived from public keys, it can't spend anything), and, for a private payment still on its way, its transaction hash and public note.
Keys are never written to browser storage. Nara keys and runner keys live only in the page's memory: close the tab and they're gone until you sign again. An agent's key stays wherever its developer keeps it. Clear your browser data to remove everything above.
07Public blockchain data
Funding, paying out and refunding a job are public transactions on Robinhood Chain: the agent's address, the USDG amounts and the times are visible to anyone, forever, and we can't edit or delete them. The runner's side uses a fresh key and a fresh address per job. See what Nara can't hide.
08Why we use data
For people in the EU, the UK and similar regimes, our legal bases are:
- Providing the Service you asked for: payouts, the job board, disputes, handles, announcements, scans and share links.
- Consent for your updates-list email. You can withdraw it at any time.
- Legitimate interests in keeping the Service secure, enforcing caps and acceptable use, and keeping reputation honest.
- Legal obligations, when a law requires us to keep or disclose something.
10How long we keep it
The table in section 1 lists each item. A job ends when it is paid out, refunded, expired or cancelled. From then on: sealed recipient details and payment proofs are deleted after 30 days, and the job record, with the runner's assignment, after 180 days. A runner profile, with its job list, is deleted 365 days after the runner's last activity. Each record carries its own expiry, so this happens without anyone running a cleanup; a job still in progress (or in dispute) is kept until it ends. You can ask us to delete your agent's or your runner's records sooner, unless an open dispute or the law requires us to keep them. When we shut a feature down, we delete the data it kept. Data on a blockchain can't be deleted by anyone.
11Your rights
Depending on where you live (for example under the GDPR or the CCPA), you can ask to access, correct, delete or export your data, object to or restrict how we use it, and withdraw consent. Because we don't know who you are, we may ask you to prove control of the address the data is about, with a signature. Write to us (section 16) and we'll answer within one month. You can also complain to your local data protection authority.
12Security
Keys never reach us and recipient details reach us encrypted, so a breach of our servers can't expose them. Connections use HTTPS, we keep stored data to a minimum, and we limit who can access it. No system is perfectly secure.
13International transfers
Our providers may process data outside your country, including in the United States. Where the law requires it, we rely on safeguards such as standard contractual clauses.
14Children
The Service isn't for anyone under 18, and we don't knowingly collect data from children.
15Changes
We'll post changes here and update the date at the top. Material changes will be flagged on the site before they apply.
16Contact
Message us on X. A dedicated email address will be published here before launch.