Privacy
Privacy policy
Notol has no accounts, no email sign-up and no analytics. Your wallet is your identity, and most of what a transfer involves is on a public blockchain anyway. This page says what we keep, what we never see, and who else is involved.
Last updated 12 November 2026.
What this covers
The website www.notol.app, the app app.notol.app, the api api.notol.app, the co-signer cosigner.notol.app, the npm packages @notol/agent and @notol/mcp, and the Notol plugins listed in plugin directories, which run @notol/mcp. All of it runs on Arc mainnet.
Public on chain
A Notol transfer is a transaction on Arc. Sender and recipient addresses, amounts, the payee name you confirm, transaction hashes and times are public on chain and visible in any block explorer. We cannot hide or delete them. Our api keeps a copy of this public data to answer status and payee checks quickly.
What we store
- Transfers and payees. The public on-chain data above: addresses, amounts, statuses, names and transaction hashes.
- Names (handles) and custom domains. If you register a name, we store the name, your address and your signatures. Names are public by design. A deleted name is marked deleted rather than erased, so nobody can take it over or register a lookalike of it.
- API keys (developers). The owning wallet address, the key name you chose, a hash of the key (never the key itself), its plan and limits, and for keys made in the developer portal a keyed hash of the requesting IP address, used only to cap new keys per network. A revoked key is marked revoked.
- Webhooks (developers). The URL you register, the events and address filters you pick, and a delivery log. Delivery records are removed after 7 days, as are endpoints that stay disabled for 7 days.
- Usage counts. Per API key, which transfers its requests touched and a daily count of its payee checks, for plans and billing. Across everyone, a daily count of payee checks per client type (
mcp,sdk,weborother): numbers only, no address, key or IP. - PIN checks (co-signer). When a transfer uses a PIN, the co-signer stores a keyed hash of it (with a secret only the co-signer holds), tied to that transfer, plus the number of attempts. The PIN itself is never stored and never reaches the api.
The home page shows recent activity and totals. They come from the same data, rounded, delayed by up to 15 minutes, and without any address, name or transaction id.
What we never see or keep
- Claim and confirm links. The secret part of a Notol link sits after the
#, which browsers never send to a server. We never receive it. - Private keys. Your wallet signs on your device. A passkey wallet's key stays in your device's authenticator. An agent wallet made with
notol-mcp initis a file on your own computer that we never see. - Email, phone and chat accounts. We do not collect them. Payees get their links from you, not from us.
- IP addresses. Our services use your IP address in memory to rate-limit requests and do not store it, except the keyed hash for portal keys described above.
- Analytics and ad trackers. None, on the website or in the app.
Logs and error reports
Our code does not log requests, request bodies or IP addresses. It logs errors with the route pattern only, plus background job results that can include a shortened transfer id. Our host, Railway, keeps its own request logs, which can include the requested URL (for example the addresses in a payee check), for its retention period.
The api and co-signer send unexpected errors to GlitchTip, an error tracker. A report holds the error type, a scrubbed message and the code location. It never holds request bodies, headers, IP addresses or keys; emails and URLs are cut out of messages. The app in your browser sends no error reports.
In your browser
One cookie, notol-theme, remembers light or dark mode for a year. It is shared by the website and the app and holds nothing else.
The app keeps a few things in your browser's local storage, on your device only: links you chose to keep for a transfer you sent (until they expire), your passkey wallet's public details, your last display name, your name and whether you dismissed the name prompt, a pending custom-domain payment, the wallet app you picked, and your wallet connection. Clearing site data removes them.
Third parties
- Railway hosts the website, app, api, co-signer and their databases (Southeast Asia region). Porkbun runs our DNS.
- Google Cloud KMS holds the co-signer and name-signing keys and signs with them on our services' request.
- GlitchTip receives the scrubbed error reports described above.
- Arc RPC (
rpc.mainnet.arc.io): your browser reads the chain directly, and our api reads it through Alchemy. - WalletConnect relays messages between the app and a phone wallet, only if you connect one that way. Its telemetry is off and its analytics endpoint is blocked.
- Circle provides the passkey wallet's account services, only if you use a passkey wallet.
- Cloudflare and Google public DNS answer the TXT lookup for a custom domain you are setting up. They see the domain name only.
- npm serves
@notol/agentand@notol/mcpwhen you install or start them. - Your wallet app and the webhook URLs you register receive what you send them.
We do not sell or share data for advertising.
SDK, MCP server and plugins
A payee check sends the sender and recipient addresses and the client type to api.notol.app. A status check sends a transfer id. With a key or agent wallet configured, sends and withdrawals are signed on your machine and go to the chain and our relayer like any other Notol transfer. The MCP server logs to your machine only, and never logs a key or a link. See the MCP docs.
How long we keep it
On-chain data is permanent. Of what we store, idempotency records go after 24 hours, signing nonces after a few minutes, and webhook deliveries after 7 days. Transfers, payees, names, keys and counts are kept while the service runs, because they back what is on chain and stop names from being reused.
You can delete your name in the app at any time. It stops resolving to your address, and stays reserved so nobody else can claim it. Developers can revoke their API keys and delete their webhooks in the developer portal. Nothing on the blockchain can be deleted, by you or by us.
Contact
Questions about this page or about data tied to your address: support@notol.app. We will update this page when how Notol handles data changes, and change the date at the top. The app is at app.notol.app.