Smithy
Privacy policy
Smithy is a wallet you hold the keys to, with an AI agent that works inside limits you set. This page says what data Smithy holds, who else sees it, how long it's kept and what you can delete. We wrote it in plain words. Where a claim has limits, we say them next to it.
Each claim carries a note on how it's backed:
- Our code, checked by tests Smithy's server does it, and our automated tests check it. It's our promise; we could change the code, and this page would change with it.
- Enforced by the FLOP chain The public chain enforces it, and Smithy can't override it.
- Their terms Another company's stated policy, which we can't check.
At a glance
- Your wallet key and 12-word recovery phrase stay on your phone. Backups that leave it are encrypted with your password or passkey, and we can't open them.
- No email, name or phone number. You sign in with your wallet account address and your device's keys.
- Each reply says who answered, and its label explains who saw your message. You pick who answers each chat: FLOP, Claude (Anthropic) or Open (an open model through OpenRouter and one of our vetted hosts).
- Your chats and memories are stored encrypted on our server, with a key per user and a key per memory. Our server holds those keys and reads your messages while it answers. This is not end-to-end encryption.
- Smithy staff see counts, costs and times, never what you wrote. Your Usage screen shows the same numbers we see.
- Logs hold codes, not content. No message, memory, search, page text or web address you asked about.
- No ads, no analytics, no tracking. Notifications are opt-in and never show what was said.
- You can see and forget every memory. Forgetting destroys that memory's key.
- The FLOP chain is public. Balances, transfers, device keys, limits and payments for FLOP replies are on it, readable by anyone, and neither we nor you can delete them.
- Smithy is for people 18 and over.
Who we are
Smithy is made by Victory Applications LLC, a New York limited liability company. In this policy "Smithy", "we" and "us" mean that company. Contact details are at the end.
This policy covers the Smithy apps for iPhone and Android, the Smithy web wallet, and Smithy's agent service (agent.asksmithy.com). Smithy is in a private beta on FLOP devnet, a test network where FLOP has no value. Data on devnet and on the beta server may be reset.
What stays on your phone
- Your wallet key and recovery phrase. They never leave the phone. The key opens with Face ID or your fingerprint.
- Backups that leave the phone are encrypted, and we can't open them. A backup file, a passkey, iCloud Keychain (iPhone) or your Google account (Android) hold the same password-encrypted key file, never the recovery phrase or an unencrypted key. The password never leaves the phone and isn't stored, so Smithy can't recover it. Limits: anyone who gets a backup can try to guess the password offline, so use a long one (we require at least 8 characters) and a password manager. Apple encrypts iCloud Keychain end to end. Google encrypts Block Store backups end to end only when the phone has a screen lock; without one, Google encrypts them but can read them. Apple and Google can see that a Smithy backup exists and when it changed.
- The camera scans QR codes on the phone and keeps no images.
What Smithy's server holds, and why
| What | Why | Notes |
|---|---|---|
| Your wallet account address and device public keys | To sign you in and to bind sign-ins to your devices | No email, name or phone number |
| Your invite code | The agent is invite-only during the beta | Staff can see which code an account used |
| Chats: your messages, replies, sources, approvals | To run the agent and show you your history | Encrypted at rest per user (see How your data is stored) |
| Memories | So Smithy can remember what you asked it to | Each has its own key; see Memory |
| Research questions and reports, schedules and their results | To run the tasks you started or confirmed | Stored with the chat, encrypted |
| Receipts | A record of each action Smithy took for you | No message, memory or page text; see Receipts |
| Your payment key (only if you let Smithy pay for FLOP replies from your account) | To pay FLOP miners within the caps you set on chain | Encrypted under its own key; deleting it destroys it |
| Push token (only if you turn notifications on) | To deliver notifications to that one device | Deleted when you sign out or remove the device |
| Usage records | Plan limits and your Usage screen | Counts, costs and times, never text; see Usage records |
| Limits you set and your memory setting | To apply them, and to show when and from which device each was changed | Kept as a history that can't be edited |
We use this data only to provide Smithy to you. We don't use it for ads, we don't share it with data brokers, and the apps contain no advertising or tracking code. We don't sell your personal data.
Who answers, and who sees your message
You choose who answers each chat. The reply's label names who answered; tap it to see who saw your message. Whichever you pick, Smithy's server reads your message while it answers, and your kept memories are sent along with your messages to whoever answers. What a provider keeps of what it was sent is under its own terms; forgetting a memory later can't recall a copy a provider already received.
If you switch an existing chat to a different provider, that chat's earlier messages go to the new provider with your next message. Smithy never quietly switches providers for you: a failed reply stays failed and isn't sent elsewhere. Our code, checked by tests
FLOP
- Who sees your message: FLOP's gateway and the FLOP miner that answers see it in plain text, and checker miners re-run about 1 in 40 replies to check them, so they can see it too. When Smithy pays the miner from your own payment key, the reply skips FLOP's gateway, but the miner and Smithy's server (which relays it) still see it.
- FLOP replies are verifiable, not private. Anyone can check on the public chain which model answered, which miner, and what was paid. "Verifiable" means that, and nothing about whether the answer is correct. Enforced by the FLOP chain No FLOP reply today is private: that would need every party that sees the text to run in sealed, checked hardware, and that isn't available yet.
- What's public: a FLOP reply's payment, model and miner are public chain data, and payments made with your payment key are linked to your account on chain.
- Proof-of-answer certificates are public pages anyone with the link can open. They never hold your question or answer, only a salted fingerprint of each, so nobody can find a short question by guessing. The check code that unlocks the fingerprint is stored only in your own encrypted chat and goes into a shared link only if you turn on "Include the check code". Limits: whoever has a link with the code can test guesses of a short question or answer. Certificates made before the salted version (1.0) have no code, and their pages say so.
- What FLOP's gateway and miners keep is under FLOP's rules, not ours. Their terms
- "Search the web first" (off unless you turn it on for a FLOP chat): before FLOP answers, Claude searches the web through Anthropic using your last message only (no earlier messages, no memories), and FLOP answers with Claude's notes. A reply your spending rules stop never reaches Anthropic.
Claude (Anthropic)
- Who sees your message: Anthropic, which runs Claude. Anthropic keeps what it's sent under its own terms; we have no zero-retention agreement with Anthropic today. Their terms
- Web search: Claude searches the web through Anthropic. Anthropic and the search service it uses see the searches, which Claude writes from your message. Anthropic doesn't name that search service per request.
- Reading web pages (where available): see When Smithy reads the web for you.
- Cards Claude makes can only show information and open web pages; they can't ask for approvals or payments.
Open (OpenRouter and a vetted host)
- Who sees your message: OpenRouter and the company that runs the open model for that reply. We allow only our vetted hosts (DeepInfra, Fireworks, Together, Nebius), with no fallback to other hosts, and the reply's explanation names the host. Our code, checked by tests
- What they keep: every request asks OpenRouter and the host for zero data retention and no data collection. We can't check that they do. Their terms
- An Open chat never reaches Anthropic, including its searches and pages. Our code, checked by tests
- Web search (where available) goes through Brave Search. Brave receives only the search queries the model wrote, sent from Smithy's server with Smithy's key: never your conversation, your memories or your IP address. The model is told not to put personal details in a query, and our tests check it, but we can't guarantee it never happens. What Brave keeps of queries is under Brave's terms. Search results aren't stored; only the cited title, address and site are kept as the reply's sources. Their terms for Brave; Our code, checked by tests for the rest.
When Smithy reads the web for you
Where available, Smithy's server opens web pages itself, for page reading, research and scheduled checks.
- Sites see Smithy's server, not you. The request comes from our server's address with the name "SmithyFetch", not from your phone or your IP address, and no third-party reader sees the address. Limits: the site can log Smithy's request (our server's address, the page and the time).
- Only addresses you wrote, or that search results or earlier pages returned, can be opened; never one the model made up. Private, local and cloud-internal addresses are refused. Research doesn't follow links on pages.
- Page text goes to the model that answers (Anthropic for Claude; OpenRouter and the host for Open) so it can read it. For Claude, page text is kept encrypted in memory for 15 minutes, then dropped. Our logs keep only the site's name.
- What you read on the web never becomes a memory without asking you.
Research (where available) runs only after you tap Start on a plan; neither the model nor a web page can start it. Research steps get only your question and the page text: no memories, chat history or tools that change anything. Claude research searches through Anthropic; Open research searches through Brave and never reaches Anthropic. Step notes are deleted when the task ends; the report stays in your chat. Logs hold no question, query, address or page text.
Scheduled tasks (where available) are created only by you, from your own message, and nothing runs until you confirm. Runs are read-only: they search and read pages, and can't book, buy or send. Each run uses the chat's own provider. Logs hold no request, time zone, query, address or result.
Our code, checked by tests The vendor terms above apply to what research and schedules send.
Memory
- You can see, undo and forget every memory in the Memory screen. Forgetting destroys that memory's own key. Limits: copies in our backups and old disk blocks remain until those backups expire (within 7 days); we don't say "instantly" or "forever".
- Automatic saving. Smithy saves a memory on its own only when Claude judges it not sensitive (health, money, other people, beliefs, sexual orientation, exact location, identity or account numbers are sensitive). Sensitive ones wait for you to tap Keep and approve on your phone. Each automatic save shows under the reply with Undo. You can turn automatic saving off. Passwords, keys and recovery phrases are never suggested. Limits: the sensitive check is a model's judgement and can miss; an automatic memory may be more personal than you meant until you undo or forget it.
- Memories go with your messages to whoever answers (see above). When Claude suggests a memory, it also sees your kept memories.
Receipts
Every action Smithy takes for you leaves a receipt: a reply you approved, a memory you kept, research you started, a schedule you confirmed and each of its runs.
- A receipt holds no message, memory or page text, no searches and no secrets. It holds codes, counts, ids, fingerprints, model and site names, and the source links you were shown. Limits: site names and source links show where Smithy looked, and a short memory could be guessed from its fingerprint by whoever has the receipt file.
- Receipts are encrypted with your key, and can't be changed or deleted through the app. A correction is a new receipt naming the old one. Receipts stay when you delete a chat, because they hold no text. Limits: Smithy's server holds the keys, as it does for chats, and database administrators could override the no-edit rule.
- Only you can see your receipts; there's no public link. If you export one and send it to someone, they see everything in it.
Notifications
- Opt-in. The app asks only when you turn notifications on, never at launch.
- Notifications never show what was said. Our server sends only a kind of event and ids; your phone fills in fixed text. Our code, checked by tests Limits: Apple and Google deliver notifications, so they learn that Smithy notified your phone, when and how often.
- The push token (a Firebase Cloud Messaging token) is tied to one device and deleted when you sign out or remove the device. Apple or Google may keep their own copy for a while.
- No analytics. The apps include no analytics, advertising ID or crash-reporting library. Google's messaging library may send its own technical diagnostics to Google.
Usage records
To apply plan limits and show your Usage screen, Smithy keeps per-account records of each reply: provider, model, outcome, tokens, cost, searches and error codes, and for FLOP replies paid from your own key, the public payment channel and transaction. Never the text. Our code, checked by tests
- Your Usage screen shows the same numbers Smithy's staff see about your account. Staff also see a list of accounts with plan, invite code, number of devices and last seen. Limits: conversation ids and reply times are visible, so staff can see when and how often you use Smithy.
- Every staff change to an account (plans granted or removed, invite codes) is recorded in a record that can't be edited, and plan changes need a reason.
- Limits you set can only be lower than your plan's, and every change is kept with when and which device made it.
- Payments. During the beta there are no purchases in the apps, and Smithy holds no card or bank details. Wallet balances and transfers are public chain data you read and write yourself.
Logs
Smithy's server logs hold codes, not content: no message or memory text, no search queries, no web addresses you asked about, no page text. They record things like who answered, the cost, error codes and, for page reading, only the site's name. Our code, checked by tests Limits: the logs of Anthropic, OpenRouter and its hosts, FLOP's gateway and Brave are outside our control. Google Cloud, which hosts Smithy, also logs each request to our server with your IP address and app or browser name; we keep those request logs, like our own logs, for 30 days.
How your data is stored
- Where: Google Cloud, in the us-east1 region (South Carolina, United States). If you use Smithy from outside the United States, your data is sent to and stored in the United States.
- Encrypted in transit: HTTPS to Smithy's server, encrypted connections to FLOP and to Firebase.
- Encrypted at rest with per-user keys, and a key per memory. Chats, approvals, memories, receipts and your payment key are sealed before they're written to the database.
What that protects against: someone who gets a copy of the database or its disks without the keys can't read your chats or memories. Destroying one memory's key (when you forget it) leaves its stored copy unreadable.
What it doesn't protect against: Smithy's server holds the keys and reads your messages while answering, so this is not end-to-end encryption, and someone with control of the running server could read them. The length of a message is visible, and records like conversation ids, times and usage counts aren't sealed. Copies sent to the provider that answers are under that provider's terms.
How long we keep it
| Data | Kept until |
|---|---|
| Chats, research reports, schedule results | You delete the chat, or all your Smithy data |
| Memories | You forget them |
| Receipts | Kept when you delete a chat; deleted when you delete all your Smithy data |
| Page text read for Claude | 15 minutes, in memory only |
| Research step notes | The end of the task |
| Push token | You sign out or remove the device |
| Payment key | You revoke it on chain; then it's deleted, and what's left of its fee money goes back to your account |
| Usage records (which model or tool, cost, time) | While your account exists; then 90 days without your address (below) |
| Limits history and staff change record | For as long as Smithy runs, as a security record; your address is replaced when you delete your Smithy data |
| Server logs and request logs (including IP addresses) | 30 days |
| Usage counts after you delete your Smithy data | 90 days, without your account address |
| Database backups | 7 days: one backup a day, the last 7 kept, plus 7 days of change logs for point-in-time recovery (deleted data stays in them until they expire) |
| Copies sent to Anthropic, OpenRouter and its hosts, FLOP's gateway and miners, Brave | Their terms |
| FLOP chain data | Permanently, on a public network we don't control |
During the beta, data on the beta server and on devnet may be reset.
Deleting your data
In the app you can:
- forget any memory, or undo an automatic one;
- delete a chat (its receipts stay; they hold no text);
- turn off automatic memory saving;
- sign out, which deletes that device's push token;
- remove a linked device, and revoke your payment key, which stops every payment at once and deletes the key;
- remove the account from your phone (this doesn't delete what's on Smithy's server);
- delete all your Smithy data: Settings → Delete my Smithy data.
Delete my Smithy data erases everything Smithy's server keeps for your account, right away: chats, memories (and earlier versions kept for Undo), approvals and rules, research and scheduled tasks, receipts, proof-of-answer links, your sign-ins and notification tokens on every device, the payment key (any fee money left on it goes back to your account first), your plan, your own limits and your place on the invite list. Smithy also destroys the encryption keys your data was sealed with, so any copy left behind can't be read. Your wallet key confirms the request (Face ID, Touch ID, fingerprint or your password), so a stolen session can't do it. It can't be undone; to use Smithy's agent again you'll need a new invite code.
What stays: usage counts with no content (which model or tool, cost, time) for 90 days without your account address, for billing and abuse checks; a record that a deletion happened, with counts but no address or content; database backups until they expire (7 days); copies model providers already received (their terms); and everything on the FLOP chain (below).
No longer have the app? Restore your account in the web wallet and use Settings there, or ask by email (Contact, below); we'll check the request comes from the account's owner. Step by step: asksmithy.com/delete-data
The chain is public, and not ours to delete
Smithy is a wallet for the FLOP network. Your account address, balances, transfers, device keys, spending limits and the payments for FLOP replies are public chain data. Anyone can read them, and they can be linked to your account. Smithy doesn't run the chain and can't change or delete anything on it, and neither can you. Using the chain is your own use of a public network, not data Smithy collects.
Children
Smithy is for people 18 and over. We don't knowingly hold data about anyone younger. If you think a child is using Smithy, contact us: when we learn that someone under 18 is using it, we delete the data Smithy's server holds for their account.
Your rights
You can ask us for a copy of the data Smithy's server holds about you, to correct it or to delete it, using the contact below. We reply within 30 days. Receipts can already be exported from the app. If the privacy law where you live gives you further rights, ask us and we'll honour them.
Changes to this policy
When this policy changes, we'll post the new version here with a new date.
Contact
Victory Applications LLC (New York)
Privacy questions and requests: info+smithy@victoryapplications.com
Never send us your 12 words, a key or a backup password. Nobody at Smithy will ever ask for them.
This policy is governed by the laws of the State of New York.