Privacy policy
Agent Data Tools is operated by SpellzCode in Sweden. This page says what the service stores when you or your agent use it. Contact: spellz111122@gmail.com.
What we store
- Request counts. Per tool and per day: how many calls were quoted, paid, free, failed or paid with credits. No inputs or outputs are stored in these counts.
- Request processing logs. Our host, Cloudflare, records request logs (including IP address, user agent, URL and timing) for operations and debugging, kept for Cloudflare's standard retention period. Tool inputs passed in the URL appear in those logs.
- Visit counts without cookies. Counted events, with no cookie, no identifier and no address in them: an event name and the page path (never its query string); the family of the site a visit came from (for example "google" or "direct", never the full referring address); the kind of software that asked (for example "browser", never the full user agent); the country Cloudflare reports for the request; and a campaign tag if the page address carried one. For AI crawlers that name themselves we count which crawler read which page per day, and for an app that connects over MCP the name of the software and the tag in its connection address. A page opened with a campaign tag passes that tag to its Stripe payment links, so a purchase can be attributed to the campaign; it names no person.
- Uploaded PDF files. A PDF you send in a request body is read in memory to answer that one request and then dropped. It is not written to any store, cache or log, and it is not fetched again. A payment quote for an upload names the file by a one-way hash, never by its content.
- Free calls. A one-way hash of your IP address and a count of free calls used. The IP address itself is not stored for this.
- Crypto payments (x402). For each settled payment: the paying wallet address, amount, network, transaction reference and tool. Blockchain payments are public by nature.
- Agent memory. What you save with the memory tools (/memory/set), under a one-way hash of the namespace you choose, until it expires (at most 30 days) or you delete it with /memory/delete. Anyone who knows a namespace can read it.
- Card credits. A one-way hash of your API key with its balance and purchase history, and the Stripe Checkout or payment reference that created it. The key itself is kept with that reference only so that reopening your claim link shows the same key. Card details are handled by Stripe and never reach us.
- Free keys by e-mail. When you ask for a free key we send one message with a link to the address you give. We keep a one-way hash of that address, so one address gets one key, with the key's hash, its count of free calls this month, and the key itself so that reopening your link shows the same key. The address itself is not stored and is not used for anything else, with one exception that you choose: the form has a box, unticked unless you tick it, to be e-mailed about new tools and price changes (at most monthly). If you tick it and then open the link in the message, we store that address with the time you agreed, and use it only for those messages. If you do not tick it nothing is stored, and an address whose link is never opened is not kept: until the link is opened it exists only in a form that the link itself is needed to read, and that is deleted when the link expires after 24 hours. To be removed, write to spellz111122@gmail.com from that address and we delete it. A hash of your IP address and a count are kept for two days to limit sign-ups.
- Free voice test keys and the free transcription trial. When you ask for a free voice test key (POST /keys/voice-test) or a free trial file (POST /credits/trial, the "Try Pro free" button on the voice pages), no e-mail address is asked for. We keep a one-way hash of your network address (for IPv6, of its /64 prefix) with a count for up to two days, so one address gets one test key and one free trial file a day, and a one-way hash of the key with its count of calls until the key expires. The address and the key themselves are not stored. Audio and text sent with such a key are handled as with any other key.
- Sign-in from apps (OAuth, for example ChatGPT). The app's registration (its name and redirect addresses) and one-way hashes of the access and refresh tokens issued to it, linked to your account. Tokens stop working when they expire.
Why we keep it
Only to run the service: to answer and bill tool calls, to count and limit free calls, to keep a payment and credit record, to sign apps in, and to find and fix failures. Nothing is used for advertising or profiling.
How long we keep it
- Request logs: Cloudflare's standard retention (days, not months).
- Agent memory: until you delete it, at most 30 days.
- Sign-in tokens: until they expire.
- Request counts, free-call counts, payment and card-credit records: while the service runs, because they are the accounting record. You can ask us to delete card-credit records (see below).
What we do not do
- We do not sell or share data with advertisers, and we do not track you across other sites. The pages set no cookies.
- We do not keep the content you ask a tool to read or compute, beyond the request logs above and what you save with the memory tools.
- Tools that read the web fetch the public URL you give them; that site sees a request from our servers.
Third parties
Cloudflare (hosting, and the AI models behind the AI tools: the text you send to an AI tool is processed by Cloudflare Workers AI to produce the answer), Brave (the query you send to the web and news search tools), Stripe (card payments), Coinbase Developer Platform (x402 payment settlement), and the public data sources each tool names in its description. They receive only what is needed to answer that call.
Hosted pages
HTML published through /page/publish is stored for the number of days the publisher chose (at most 7) and then deleted; its text is sent to the moderation model before storage. We keep no record of who published a page beyond the payment receipt.
Your choices
To ask what we hold about an API key or wallet, or to have card-credit records deleted (this ends the key's balance), write to spellz111122@gmail.com.
Last updated 26 October 2026. Agent Data Tools is a SpellzCode service · About · Privacy · Terms · Support · Status · Changelog