Live on Solana mainnet, small limits. Status page.Reviewed internally. Early. Real money. Use with caution.Report a problemState as of October 2026

Privacy

The preview and the sandbox demo use a test network and test tokens. The live demo and a separate live account use real USDC on Solana mainnet (see Live demo and Live account below).

Last updated 29 October 2026. This note covers payzilla.ai, the invite form, the sandbox demo, the live demo, the chat (paywith.payzilla.ai/chat), the MCP service (paywith.payzilla.ai/mcp), the partner dashboard, the live account on Solana mainnet, the seller start app and the buyer view. They are run by Espor Medya ve Teknoloji Anonim Sirketi, Türkiye. Contact: [email protected].

Who is responsible. Espor Medya ve Teknoloji Anonim Sirketi, Türkiye.
Contact: [email protected]

What we collect, feature by feature

The website

  • We set no cookies of our own on the public site. Signing in to the partner dashboard involves cookies set by Cloudflare (see Partner dashboard below).
  • Cloudflare, which delivers our website, measures how pages load with its own Web Analytics script. The script sets no cookies. Cloudflare states that it collects timing metrics, does not track individual visitors across its customers’ sites, and does not log query strings. See Cloudflare’s page on data origin and collection.
  • Your theme choice (dark or light) is kept in your browser, only if you press the theme button. It stays on your device.
  • Apart from the Cloudflare Web Analytics script, every script, font and image comes from this site.

Interest form

If you ask for an invite, the form sends the details you type (email address, name, organisation, role, a short note and the two consent choices) to us as one email to [email protected]. There is no database behind the form.

To limit abuse, the form service keeps a keyed fingerprint of the connecting address for up to one hour. The key changes every hour. The fingerprint is held in memory only, is not written to disk or to logs, and is gone within the hour. The load balancer’s access logs are off. The service’s event log is kept for 14 days and holds event names and counters only, with no email addresses and no IP addresses. Your name, email address and note exist only in the one email and in transit; no AWS log holds them. In the preview environment, our cloud network keeps connection records (visitor IP address, ports, times, no content) for 30 days for security. This includes visitors to the form service, which is reached directly, not through Cloudflare.

Sandbox demo

The sandbox demo runs on a test network with test tokens. It has two parts.

  • Test-token faucet. The devnet address you type is checked and used as a daily limit key. It is held in the demo’s memory and in a temporary file that resets each UTC day and is lost when the service restarts. Your connecting address is used the same way as a limit key, and an old address can stay in the temporary file past midnight until the next request or until the service restarts. When the human check runs, your connecting address and the check token are sent to Cloudflare Turnstile. The test tokens are minted in a public devnet transaction, which stays on the chain. When a mint succeeds or fails, the event is logged with the address and kept for 30 days.
  • Pay with your own wallet. The service stores your wallet address and the payment attempts in its database in the EU (Frankfurt) region. Storage is encrypted and backups are kept for 7 days. These are devnet test payments. We do not delete old test payments on a schedule; deletion requests are handled on request.

Live demo (real payments)

The live demo takes a real payment of 0.01 USDC on Solana mainnet. For each attempt, our service handles:

  • Your wallet address and the payment: the amount, asset, network, memo and transaction id, and the payer’s partially signed transaction as we received it. These are kept in the live account’s database, in the EU (Frankfurt), for as long as the demo account exists, like other live payment records. The payment is also public on the Solana blockchain, which we cannot change.
  • The name your browser reports for your wallet (for example “phantom” or “solflare”), so we can tell which wallets work. It is written to one line of the demo service’s log, with no other wallet detail, for 90 days. It is not stored in the database.
  • Your connecting address. It is held in the demo service’s memory to apply limits (by the minute and the hour) and sent, with the check token, to Cloudflare Turnstile for the human check. We do not write it to the demo service’s log. Cloudflare, which delivers the site, handles it as described under Who receives data. Cloudflare, which delivers the site, sees it, and our cloud network’s connection records (90 days) hold Cloudflare’s addresses, not yours.
  • Refused payments. If a payment is refused, the log line holds a fixed error code and the ids of the programs the transaction contained (public data), never your keys or the human-check token.

We keep no card data. The live demo has no sign-up and sets no cookies of our own; the Cloudflare human check may use its own.

Chat (paywith.payzilla.ai/chat)

The chat is an automated assistant. It lists Marketplace services and prepares a payment. It cannot pay for you: you check the amount and the receiver, and your wallet signs. It uses no AI model. If we add one, we will change this page before it is turned on.

What we keep. The chat stores no message text and no visitor data. Only our own settings (chat on or off, a copy of the list of listings) are in the database. If you make a payment, the pay link records it as described under Live account, and it is public on the Solana blockchain.

Logs. The chat and pay-link logs hold fixed words only: time, event, outcome, reason class and listing id. They hold no IP address, wallet address, message, payment reference or browser name. Chat logs are kept 90 days and pay-link logs 30 days, in AWS in Frankfurt (eu-central-1).

Limits. To limit abuse, the service counts requests per network address, in memory only: your IPv4 address as it is, or the first 64 bits of an IPv6 address. The address is used for the limit only, is not stored or logged, and is lost when the service restarts.

Human check. Cloudflare Turnstile checks that you are a person. Your connecting address, browser signals and a check token go to Cloudflare. Cloudflare acts for us in this check and, to improve its bot detection, for itself (see Cloudflare’s Turnstile privacy addendum). The chat page sets no cookie and uses no browser storage of its own.

Wallets. We show public blockchain data (wallet addresses and transactions) in the chat. It is public and we cannot remove it. The chat never holds or asks for your keys or seed phrase. Do not type secrets in the chat.

Not running today. We may later keep chat records. If we do, we will change this page first. The plan is to keep, for 90 days, the messages of a chat in which a payment was prepared, the prepared request, its outcome and the session times.

MCP service (paywith.payzilla.ai/mcp)

AI assistants can connect to our MCP service to search and read Marketplace listings and to start a payment. With the payer tool, an assistant pays within the cap you set without asking you each time. The read-only part needs no sign-in. We receive only the request the assistant sends us, for example a search term or a listing id. We do not receive your conversation with the assistant; its provider handles that under its own policy.

Logs. The MCP log holds fixed words only: time, event, outcome, listing id and counters. It holds no IP address, browser name, wallet address or search text. Cloudflare, which delivers the service, keeps its own logs, and they include IP addresses.

Limits. To limit abuse, the service counts requests per network address, in memory only: your IPv4 address as it is, or the first 64 bits of an IPv6 address. The address is used for the limit only, is not stored or logged, and is lost when the service restarts.

Payments. When a payment is made through MCP, the MCP service keeps the payment request and the receipt, including the paying wallet’s address, for about 24 hours. Cases that are not resolved stay until we look at them. A payment reference lets the AI assistant ask for the state of that payment during that time. Our request limits count requests per network address in memory only, and we keep one total amount per day; neither holds a wallet address. The payment itself is also recorded in our payment records, including the paying wallet’s address, as described under Live account. It is public on the Solana blockchain and we cannot remove it. If payments from a wallet fail again and again within an hour, we may put the wallet on our deny-list. An automatic entry lifts after about a day; an entry added by a person or by sanctions screening stays until we remove it. We never see or hold a wallet key.

Payer tool (open source)

The payer tool runs on your own computer, not on ours. It keeps small files in a folder in your home directory (whether a payment is open, and the times of recent attempts, which is also how the tool limits repeat payments); they hold no key. Your wallet key stays in your operating system’s key store (the Keychain on macOS, the Secret Service on Linux, a protected file on Windows), or in memory when you type it at a hidden prompt for one payment. None of these is sent to us. What we receive is the request the tool or AI assistant sends us, and the signed payment, as described for the MCP service. The code is published on GitHub, which has its own privacy policy.

Partner dashboard

  • Signing in needs an email address. The one-time code is sent to it. The address is processed by Cloudflare Access, which keeps its own sign-in log (application, decision, email, country and time) under its own policy; see Cloudflare’s privacy policy.
  • Cloudflare sets its own sign-in cookies in your browser on the dashboard. The dashboard itself sets no cookie and loads no analytics or third-party scripts. Cloudflare may add its own analytics script tag to the page, which the dashboard’s security policy blocks.
  • Only addresses on our access list can complete the sign-in. The dashboard keeps no database, no session store and no copy of your address beyond the list.
  • The dashboard logs only denied sign-ins, as a short hash of the email address, kept for 30 days.
  • The list of people allowed in (email, role and label) is held in AWS Secrets Manager. The previous version of the list stays there until it is replaced, so a removed address can remain in it for a while.

Live account (Solana mainnet)

A separate live account runs our own-funds payments on Solana mainnet, and sellers can create their own accounts (see Seller accounts). For a payment we store the payer’s wallet address, the payment (amount, asset, network, memo and transaction id) and the payer’s partially signed transaction as we received it, which we keep so that a payment can resume after a crash. Payment, ledger and payer records are kept for as long as the seller’s account exists. The partially signed transaction is kept together with the payment record. We hold a deny-list of wallet addresses (public US sanctions entries and entries we add ourselves). The live account holds no card data; there is no card provider on it.

The live account’s application and service logs, its database log and its account activity trail are kept for 90 days. AWS network connection records (address, port, protocol, size and time, no content) are also kept for 90 days. The load balancer accepts web traffic only from Cloudflare, so for that traffic the records hold Cloudflare’s addresses, not the visitors’ own; they also hold internal addresses. The database is encrypted, is not reachable from the internet, and its automated backups are kept for 14 days, plus stored snapshots.

Services a seller registers

A seller can register services: a name, a price, an optional route note and a status, with a dated history of changes. The name is copied into each payment record at the time of the request. When a change is made through the dashboard, the note records the signed-in person’s email address. A service is paused, not deleted, and these records are kept with the seller’s account.

If you email us

When you write to [email protected] we receive your address and your message. We use them to reply to you. We do not add you to a mailing list and we do not sell your details.

Seller accounts (start.payzilla.ai)

When you create a seller account we handle:

  • Your email address. You sign in with a one-time code that Cloudflare Access sends to it; Access only proves that you can read the address. We keep the address in your account record, to sign you in and to write to you about your account.
  • The name you choose (1 to 80 characters). A builder sees it next to a payment to you.
  • Your receiving wallet address and a signed message that shows you control it. We check the signature when you send it and do not keep it; we keep the wallet address, the time and the result.
  • Your choice about product news. A separate box, not ticked. We record that you ticked it, and when.
  • Your API key. It is shown once. We keep only a fingerprint of it, so we cannot show it again.
  • Your connecting address. It is turned into a keyed fingerprint to limit abuse, held in memory for about an hour, and not stored in your account record.
  • Your payments, as for the live account above.

The start page sets no cookie of its own; Cloudflare’s sign-in sets its own. We keep no card data. We do not sell your data and do not use it for advertising.

Closing your account. Use “Close my account” on the start page. Your key and service stop at once, and we erase your email address and contact details within 30 days. Records of your payments stay: they record payments that took place and are public on the blockchain. Audit rows that hold only a keyed fingerprint of the email, and no wallet, also stay.

Buyer view (opening an account)

Anyone can ask for an account while sign-up is open. We may limit or close sign-up at any time. A visit alone creates no record. To open an account you sign in with Cloudflare Access (a one-time code sent to your email), tick that you have read the Terms and this page, and press “Open my account”.

What we store. Your email address and a random account number. For each wallet you claim: its address, the name you give it and the time you claimed it. A signed message shows you control the key. We check the signature and never keep it. The sign-in request itself, which includes the wallet address, stays until a clean-up that runs within a day. We never see or hold a wallet key. We keep a short record of each claim action (claimed, released, locked, takeover) with your account number, a claim number, the time and the date of the Terms. It holds no email address, name, wallet address or IP address. Your alert settings, and a short list of alert events for 90 days. Alert emails are off. If we turn them on, they go only to accounts we invited, not to accounts opened through sign-up, and say only that something happened.

What the view shows. The payments made through Payzilla from the wallets you claimed: time, amount, status, the seller’s display name and the service name. These come from our own payment records, not from the blockchain, and anyone who proves control of the wallet’s key can see them. The view starts when you claim a wallet. A claim proves control of a key, not ownership of funds. If another account later proves the same key, it can ask to take over the claim after a 72-hour wait.

Closing your account. Use “Close my account”. It stops at once: you can no longer see anything, your wallets are released, and your alert settings and pending sign-in requests are deleted. For 30 days we still hold your email address and wallet addresses, only so the account stays closed. Nobody can see them in the view, and the same email address cannot open a new account in that time. A daily clean-up then replaces your email address with a placeholder and deletes your wallets, names and alert records. This can come up to a day after the 30 days.

What stays. The random account number, how the account was opened (invited or sign-up), the dates it was opened, closed and erased, and the claim record. Our operators also keep a short record of each open, close and erase with the account number and no email address. The payment copy is not deleted. It still holds the wallet address and the Solana transaction id, so after the erase it is no longer linked to your account, but it still shows that wallet’s payment. Payments are public on the Solana blockchain and cannot be removed.

Others who hold some data. Buyer data is held in AWS in Frankfurt (eu-central-1), encrypted. Our service logs are kept 90 days and hold only a keyed fingerprint of your email address, no wallet address or signature. To limit abuse we turn your connecting address into a keyed fingerprint that is kept in memory for about an hour at most, not written to our database or logs. Database backups are kept 14 days, so a copy of erased data can remain in a backup for up to 14 days after the erase. Cloudflare keeps its own sign-in log with your email address, and its own logs of requests, which include IP addresses. Closing your account does not remove Cloudflare’s logs or these copies.

Not offered today. A copy of your data in a file, and reopening a closed account before the 30 days are over. You can write to [email protected] to ask for access, correction or deletion; we reply within 30 days.

We keep no card data, do not sell your data and do not use it for advertising. The buyer view sets no cookie of our own; Cloudflare’s sign-in sets its own.

Blockchain data

Wallet addresses and transactions on a public blockchain are public, and we cannot remove them. We do not ask for or hold your keys or seed phrases.

Who receives data

  • Google Workspace: our email.
  • Amazon Web Services: sends the form email, hosts parts of the service, and for the live account hosts the database, the key service for the network-fee key and the logs.
  • Solana RPC providers: the pay-link service sends payment calls (latest block, send, status) to its provider. These can include the payer’s wallet address and the signed transaction. Helius is used today. The payment verifier uses Helius, Chainstack and Alchemy.
  • Cloudflare Turnstile: the human check in the chat. AWS (Frankfurt, eu-central-1): the chat, pay-link and MCP services, database and logs.
  • The public US Treasury sanctions list: we download it and send nothing about users.
  • Cloudflare: web analytics, Access sign-in, the Turnstile check and delivery of this site, the demo and the dashboard. As our provider it handles requests, including IP addresses, for that delivery. Cloudflare Access also keeps the email address used to sign in, in its own sign-in log.

In the preview environment, our hosting provider (Amazon Web Services) keeps technical records of network connections, including IP addresses, time and size but not content, for 30 days for security.

We do not pass your details to anyone else.

How long we keep it

  • Buyer view: your account while it is open. After closing, 30 days, then your email address is replaced and your wallets, names and alert records are deleted; the claim record and the operator record of opening, closing and erasing stay, and hold no email or wallet address. Alert events: 90 days. Buyer service logs: 90 days. Database backups: 14 days.
  • Invite emails stay in our mailbox until we delete them on request or remove them in a periodic clean-up.
  • Demo and dashboard logs: 30 days, as described above. Backups of the demo database: 7 days. Cloudflare Access sign-in logs: kept by Cloudflare under its own policy.
  • Chat: no message text is stored. Request counters: in memory only, for about ten minutes at most. Chat logs: 90 days. Pay-link logs: 30 days.
  • MCP logs: 30 days.
  • The form service’s event log: 14 days. Event names and counters only.
  • Live account: payment, ledger and payer records, for as long as the seller’s account exists; the partially signed transaction is kept together with the payment record.
  • Live demo: payment records as for the live account; the wallet-name log line, 90 days.
  • Live account: application and service logs, the account activity trail and AWS network connection records, 90 days; automated database backups, 14 days plus stored snapshots.
  • The hourly fingerprint disappears within the hour. In the preview environment, AWS network records of connections to our services (IP address, time and size, no content): 30 days.

Where data is processed

These providers process data outside Türkiye, in the United States and the European Union. The live account is hosted in the European Union (Frankfurt). The chat, pay-link and MCP services run in AWS in Frankfurt (eu-central-1). Cloudflare handles the human check and delivery of the page.

Your rights

You can ask us for access to your details, to correct them, to delete them, or to stop using them, and you can complain to the authority responsible for data protection. Write to [email protected]. We reply within 30 days.

Security, children, changes

We keep access to these systems limited. The service is not for children. When this note changes, the date at the top changes.