FIZZL.WALLETBack to the dashboard

Privacy statement

Fizzl Agent Wallet (wallet.fizzl.eu) · last updated 13 November 2026 (approval requests on WhatsApp, if you connect it)

This statement explains what personal data the Fizzl Agent Wallet processes, why, for how long, and what your rights are. We keep it short because we collect little: no passwords, no names, no e-mail addresses (only a fingerprint if you sign in with e-mail), no tracking across sites, only anonymous usage counts.

1. Who is responsible

The controller is Frits Zwager, trading as Fizzl, the Netherlands. For anything about your data, contact Fizzl13@protonmail.com.

2. What we process, and why

DataWhyLegal basis (GDPR)
Your wallet address (Ethereum or Solana) and the date you signed upIt is your account: you sign in by signing a message with your wallet (or with e-mail, below). No password.Contract (art. 6(1)(b))
Your agents: the names you give them, a SHA-256 hash of each agent key (never the key itself), when each was last seen, and each agent's public wallet address (if you enter it, or taken from a payment it signs)So your agents can use the service and you can manage them, and so Test my setup can look up the agent wallet's USDC balance on the public blockchainContract
Your rules: limits, allow list, paused or notTo apply your spending rulesContract
What your agents ask to sign: method, network, recipient address, amounts, the safety verdict from presign-guard, what the agent says it is buying (a URL and a description, if your agent sends them), and what it got back (the paid service's answer, up to 16,000 characters, if your agent sends it); your approvals and denialsTo check requests against your rules, ask you for approval, and show you receipts (including what was bought) and an activity logContract
Payments an app asks for through the connector (ChatGPT, Grok and other apps connected at wallet.fizzl.eu/mcp): the API request the app asks to pay for (URL, method, headers and body), the price, the seller's payout address, the result of the sanctions screen and of x402 Doctor's lookup of the seller, your wallet's USDC balance on Base, and, once you sign, your signature and the API's answer. For a payment in USDC on Solana: the Solana address you sign with, its USDC balance, and the transaction you sign. For a payment in RLUSD on the XRP Ledger: the transaction you sign in Xaman, the XRPL account that signed it and its RLUSD balance, and a token from Xaman so your next payment request goes straight to your Xaman app (Xaman ends it after 30 days without use). The request is kept one hour; the receipt like other receipts; the Xaman token until it is replaced. When the connector's own checks stop a payment before you are asked (the payout address on the sanctions list, a price above the limit, a network it doesn't pay on) and the seller's 402 asks to be told, the seller gets the reason and which of its offers it was, for the API's address without the query: nothing about you or your request. Your own "no" is never passed on.To show you what you are asked to sign, send the payment you signed, and give the answer to the app you connectedContract
Telegram (only if you connect it): your chat id, user id and usernameTo send you approval requests, plan reminders, a test message when you ask for one, and alerts about new providers in the categories you follow (if you pick any); and to accept your tapsContract
WhatsApp (only if you connect it): your phone number and WhatsApp profile name. The dashboard shows only the country code and the last two digitsTo send you approval requests with Approve and Deny buttons, and to accept your tapsContract
Fizzl Pass (comes with Pro): for each wallet the pass covers (yours and your agents') the pass tier and its end date, kept until the pass endsSo partners and Fizzl's services can check a wallet's pass: anyone can ask whether a wallet has a pass and until when, never whose it is. The credit back is kept by Fizzl's services (x402 Doctor, presign-guard, Ichimoku Signal, Fizzl Buy) per wallet: only the balance, for 12 months after the last credit; the dashboard asks x402 Doctor for it with your pass proofContract
Payments for Pro: transaction hashes, amounts, dates, until when you paid; for automatic payment, what the subscription contract and USDC show for your address (next payment date, paid-through date, the approval you gave, your USDC balance)To give you Pro, remind you before a payment, and keep the records the law requiresContract; legal obligation for bookkeeping (art. 6(1)(c))
Anonymous usage statistics: that something happened (a sign-up, an agent added, a purchase allowed or asked, an approval and how fast, a search and how many results, which button on a search result was used, the result of Test my setup, a Pro payment), with the time, the seller's host name and amount for a purchase, a short code instead of your account, and, if you came through a link on a Fizzl website, that site's name (e.g. fizzl.eu). Never your address, keys, Telegram details, what was bought or the receipts. The code is made with a secret and can't be turned back into your address.To see how the wallet is used and where people get stuck, so we can improve itLegitimate interest: improving the service (art. 6(1)(f))
Endpoints you watch (endpoint monitor): their URLs, and the result of each hourly check (status, response time, payment networks offered)To check them every hour and tell you on Telegram when one stops asking for payment correctlyContract
Your alert webhook (optional): the Discord, Slack or other webhook URL you addTo send the messages you'd get on Telegram there too (approval requests, endpoint alerts, Pro reminders, new providers). We send the message text (and, for other webhooks, a short JSON description of the event); the URL is never shown back in fullContract
Your e-mail (only if you sign in with it or add it): a fingerprint of the address (a one-way hash) and a hint like "f…@gmail.com". The address itself is not storedTo recognise you when you sign in with a code. We mail the code once, through Resend; it works for 10 minutesContract
Passkeys (only if you add Face ID or a fingerprint): the passkey's public key, its id, a device name and when it was added and last usedTo check that a sign-in really comes from your device. Your face or fingerprint never leaves your phone; the private key stays on your device or in iCloud Keychain / Google Password ManagerContract
Feedback you send (only if you use the feedback box): your message, with your account's short address or e-mail hint and planDelivered to the owner's Telegram so it can be read and fixed; not kept on this server, and only its length goes into the usage statisticsLegitimate interest
Feedback your agent sends (only if it uses the feedback tool or /v1/feedback; or anyone, without an account, at /feedback): its type, message, the tool or route it is about, its contact if it gives one, the payment it is about if it names one (a transaction hash or receipt id, with the network), and for an agent with a key: the agent's name and your account's short address or e-mail hint and plan, plus that agent's own receipt for the payment it names (what, how much, to which site, the transaction and what came back)Delivered to the owner's Telegram so it can be read and fixed. The usage statistics keep the type, the tool, the agent's name, the payment's network and the first 200 characters of the message with a coded account id, never the contact, the transaction or the receiptLegitimate interest: improving the service (art. 6(1)(f))
Notifications on your devices (optional): for each phone or computer where you turn them on, the push address your browser gives us and a device name (like "iPhone · app")To show approval requests and alerts as notifications. The message goes, encrypted so only your device can read it, through the push service of your device's maker (Apple, Google or Mozilla). Turn it off per device on the Account tab; addresses that stop working are deletedContract
Your IP address, brieflyHeld in memory only, to slow down repeated wrong logins and sign-in floods. Not stored by us.Legitimate interest: security (art. 6(1)(f))

Please don't put other people's personal data in agent names, rules or purchase descriptions. What your agents send is up to you.

3. Cookies and local storage

No third-party analytics, no advertising, no tracking pixels, no third-party scripts, and no cookies for statistics: the anonymous counts above are made on our own server. Even the fonts are served from this server.

3a. The Fizzl websites (fizzl.eu and its subdomains)

fizzl.eu, ai.fizzl.eu, projects.fizzl.eu, cv.fizzl.eu, lab.fizzl.eu and atlas.fizzl.eu count visits with a small script from this server: which page was opened and the name of the website whose link brought you there (e.g. x.com or reddit.com; only its name, never the page you came from), and clicks from those pages to this wallet or a Fizzl service, with the time and the kind of browser (e.g. "browser" or a bot's name). No cookies, no local storage, no IP address, nothing that identifies you, and nothing at all when your browser sends Do Not Track or Global Privacy Control. A link to this wallet carries the name of the site you came from (?ref=fizzl.eu), so we can see whether the website leads to sign-ups. Legal basis: legitimate interest (art. 6(1)(f)); kept at most 2 years, like the other anonymous statistics.

Google Analytics, only if you say yes. The Fizzl websites ask once, in a bar at the bottom, whether they may count visits with Google Analytics (Google Ireland Ltd.). Only after a yes does the page load Google Analytics, which then sets its cookies (_ga) and receives your IP address and the pages you view. Without a yes nothing is sent to Google. Your answer, yes or no, is kept for a year in a cookie fizzl_analytics on .fizzl.eu, so every Fizzl website remembers it; delete that cookie to be asked again. Legal basis: your consent (art. 6(1)(a)), which you can withdraw at any time by deleting the cookie.

YouTube videos, only if you press play. The film on the sign-in page of wallet.fizzl.eu and some project videos on projects.fizzl.eu are shown as a still image from our own server. Only when you press play does the page load the video from YouTube (Google Ireland Ltd.), in its privacy-enhanced mode (youtube-nocookie.com). YouTube then receives your IP address and that you watch that video, and may store data in your browser for playback, under Google's privacy policy. Before you press play, nothing is sent to YouTube. Legal basis: your consent, given by pressing play (art. 6(1)(a)).

The heart ("Like") button on those sites keeps one number per site. So that one visitor counts once a day, the server makes a mark from your network address and browser together with a secret that changes every day and on every restart, keeps only that scrambled mark for 24 hours, and then forgets it. Your browser remembers that you liked the page (in its own storage, never sent to us), so the button stays filled. No cookies, and the address itself is never stored.

4. What we never do

5. Who helps us (processors)

Render, Upstash, Sentry and Anthropic are companies based in the United States, and TypeSafe may process data outside the European Economic Area too. Where data is processed outside the European Economic Area, this happens under the safeguards these providers offer, such as the EU standard contractual clauses.

6. The blockchain is public

Pro payments happen on a public blockchain (Base, Arbitrum, Optimism, Polygon, Ethereum or Solana), automatic payment on Base. Your address, the amounts and the times are public there and permanent. That is how blockchains work, and nobody, including us, can delete them.

7. How long we keep it

DataKept
Account, agents, rules, Telegram and WhatsApp linkUntil you delete your account (or disconnect Telegram or WhatsApp)
Receipts (what each payment was for and what came back)7 days on Free, 90 days on Pro
Spending records for your limits31 days
Approval requestsShown for 24 hours after they are decided, deleted after 7 days
Activity logThe latest 500 events
Payment records for Pro (and withdrawals with their refund)7 years (Dutch bookkeeping law), also after you delete your account
Sign-in codes and Telegram and WhatsApp link codes10 to 15 minutes, used once
Anonymous usage statisticsAt most 2 years. They can't be linked back to you, so they stay when you delete your account.

8. Your rights

You have the right to access, correct and delete your data, to get it in a portable format, to object to processing based on legitimate interest, and to ask us to restrict processing.

If you think we handle your data wrongly, you can complain to the Dutch data protection authority, the Autoriteit Persoonsgegevens. We'd appreciate hearing from you first.

9. Security

10. Age

The service is not meant for anyone under 16.

11. Changes

If we change this statement in a way that matters to you, we'll say so on the dashboard (and on Telegram, if you connected it) before it takes effect. The date at the top shows the current version.