Sandbox Privacy Notice
How Mesta uses your details when you ask for access to, accept an invitation to, sign up for or use a sandbox: who is responsible, what is collected and why, the lawful basis, who receives it, where it is kept, for how long, and your rights.
Sandbox Privacy Notice
Version sandbox-2026-10, effective 17 November 2026. It describes the sandbox as of that date.
Last updated 17 November 2026.
This notice explains how Mesta uses your details when you ask for access to a Mesta sandbox, accept an invitation to one, sign up for one or use one: the sandbox portal at ohana.sandbox.mesta.xyz, the sandbox API at api.sandbox.mesta.xyz and the access request, invitation and sign-up screens. The sandbox is open only to people Mesta admits. At launch, Mesta admits people by invitation only. Later, Mesta will also offer sign-up on the sandbox site, and this notice covers both. The personal details this notice covers are yours, as a person who asks for access, is invited, signs up or uses a sandbox. The Sandbox Terms require synthetic data and forbid real personal, bank or identity data in a sandbox. If such data is entered anyway, Mesta uses it only to find and delete it. You do not accept this notice. It tells you what Mesta does. Mesta's privacy policy for its other services is at mesta.xyz/privacy.
Who controls your details
The controller of your sandbox details is Mesta Payments LLC, 700 El Camino Real, Menlo Park, CA 94025, USA. Send any question or request about your details to [email protected], with your sandbox id.
Mesta is appointing representatives in the European Union and the United Kingdom and will name them here.
Mesta has not designated a data protection officer, because its activities do not require one.
What we collect
- When you ask for access or sign up, or someone asks Mesta to invite you: your name, your email address, your organization, your role, your organization's website and country, the country you work from and, if you give it, what you intend to build, and, for an invitation, who asked for it. If you reach the access request or sign-up form from Mesta's website or documentation, the form records which one. Access requests come through Mesta's sales team and a ticket in Mesta's help center at customer.support.mesta.xyz and, once Mesta offers sign-up, through the public form on the sandbox site.
- When Mesta reviews the request or sign-up: the decision, the member of staff who made it and when it was made.
- When you accept your invitation or complete sign-up: the country you choose, the password you set (stored hashed), the second factor you set up at your first sign-in (an authenticator app or a passkey), and the version of the Sandbox Terms you accepted, with the time, a keyed hash of the network address you accepted from and the family of your browser or client.
- When you sign in or call the API: the
Signature-Agentheader if your client sends one. Where Mesta runs checks that protect access requests, sign-up and sign-in from automated abuse: a keyed hash of your network address and of its network prefixes, the family of your browser or client and the result of a bot-protection check. On the sign-up form, Mesta runs the bot-protection check before it creates anything, and records keyed hashes of your network address and its network prefixes and the family of your browser. When you accept an invitation, Mesta runs no bot-protection check and records a keyed hash of your network address and the family of your browser. - When you use the sandbox: the requests your keys make and the events your sandbox produces, with their times, your sign-in, second-factor and verification-code attempts and their results, and an error report when something fails.
- When you use the mesta-dev MCP server, which Mesta runs: the tool calls your client makes under your sandbox key, with their times, their parameters with secrets removed, the result status and any error. These are kept with your request logs for 90 days.
- When you write to Mesta or ask for production access: your message, or your request with your sandbox id, merchant name and email address and the answers you give in the go-live form (your business's legal name, country, website and use case, expected monthly volume, target month and any note).
Most of these details come from you. If someone at your organization or at Mesta asks Mesta to invite you, Mesta receives your name, email address and organization from them. Mesta checks, through a public DNS lookup, that your email domain can receive mail.
You need an email address, a name and a password to accept an invitation or to sign up. Without them Mesta cannot give you a sandbox. Mesta creates your sandbox only when you accept your invitation or complete sign-up on the sandbox site, after you accept the Sandbox Terms.
Why we use it, on what basis and for how long
Article numbers refer to the GDPR and the UK GDPR.
| Purpose | Your details | Lawful basis | How long we keep them |
|---|---|---|---|
| Decide whether to give you access | Your access request, your organization, who asked for your invitation and the decision | Mesta's legitimate interest in giving access only to people and businesses it has approved and can lawfully serve (Article 6(1)(f)) | An approval record: one year after access ends. A declined request: one year after the decision. |
| Provide the sandbox: accept your invitation or sign-up, sign you in, send your verification codes and notices, keep the sandbox for you and answer your requests | Email address, name, country, password hash and second factor, your sandbox and everything in it, your requests | Where you use the sandbox on your own behalf, performing the Sandbox Terms, our contract with you (Article 6(1)(b)). Where you use it for an organization, Mesta's legitimate interest in providing the sandbox to that organization (Article 6(1)(f)) | Until you delete the sandbox, your access ends, it is closed, or it expires because it was not claimed within 7 days or its email address was not verified within 72 hours, then purged within 24 hours. A sandbox with no API call and no sign-in for twelve months is closed, with notices 30 and 7 days before. Uploaded documents are deleted with the sandbox, and in any case 90 days after upload. |
| Keep a record that you accepted the Sandbox Terms | Your account identifier and sandbox id, the version of the terms and of the consent wording you saw, the time of acceptance and the portal build, plus a keyed hash of the network address and the client family at acceptance | Mesta’s legitimate interest in being able to show that the terms were accepted (Article 6(1)(f)) | Three years after the sandbox is purged, the period for bringing a contract claim under Delaware law |
| Keep the sandbox secure and enforce its limits: rate limits and budgets, protect sign-in, investigate reports and close sandboxes for cause | Request and security logs (which hold your network address), your sign-in and code attempts, the Signature-Agent header, and any keyed hashes (of your network address and its prefixes, and of the email addresses on the sandbox), client family and bot-protection result Mesta records | Mesta's legitimate interest in keeping the sandbox available, secure and free of abuse (Article 6(1)(f)) | The sandbox record with any keyed hashes: 90 days after closure, then the hashes are removed. Request and security logs: 90 days. Figures aggregated from them: 13 months. A closure for cause, with its keyed hashes: 24 months. |
| Find and fix faults | Error reports from the sandbox portal, described under error monitoring below | Mesta's legitimate interest in running a working service (Article 6(1)(f)) | Up to 90 days, after which the error-monitoring provider deletes them |
| Measure and improve the sandbox | Product events for your sandbox and its keys (created, claimed, verified, first API call, first order, resets and deletion) with their times | Mesta's legitimate interest in improving the sandbox (Article 6(1)(f)) | Purged with your sandbox. Figures aggregated from them: 13 months |
| Answer your request for production access | Your sandbox id, merchant name and email address and your go-live form's answers. Mesta stores those answers with your sandbox and sends them to its sales team. | Steps you ask Mesta to take before entering into a contract (Article 6(1)(b)) | The answers stored with your sandbox: until the sandbox is purged. A new request replaces them. The sales team's copy: for as long as Mesta has a relationship with you, and ten years after it ends |
| Answer you when you write to Mesta | Your messages and your sandbox id | Mesta’s legitimate interest in answering you (Article 6(1)(f)) | For as long as Mesta has a relationship with you, and ten years after it ends |
When a period ends, Mesta deletes the details or keeps them only in a form that no longer identifies you. Deleted details may remain in backups until they are overwritten in the normal backup cycle, and are not used in the meantime.
Mesta does not use your sandbox details, including your access request, for marketing.
Who receives it
Mesta's service providers process your details for Mesta, on Mesta's instructions:
| Type of provider | What for | What it receives |
|---|---|---|
| Cloud hosting and email delivery | Hosting, storage, logs, and sending your invitation, verification codes and notices | The details above that Mesta holds. The email delivery service keeps its mail logs for its own retention period. |
| Bot protection | The check that tells people from automated traffic, where Mesta runs it | What the check reads from your browser, including your network address |
| Error monitoring | Error reports for the sandbox portal | Error reports, described below |
| Telemetry | Operational telemetry for the mesta-dev MCP server | Its traces, metrics and logs, described below |
| Address lookup | Address suggestions while you type an address in the portal | What you type in the address field, your network address and browser details |
| Image delivery | Country flag images in the portal | Your network address and browser details, as for any web request |
| Help center | Mesta's help center at customer.support.mesta.xyz: access requests, support requests and appeals | What you write in a ticket, with your name and email address |
| Email and office software | Mesta's email, including privacy@, contact@, support@ and [email protected] | Messages you send and Mesta's replies, and production-access requests sent to [email protected] |
The error-monitoring provider receives an error report when the sandbox portal fails: what failed, the page or request address with tokens and secrets removed, your browser and device type, and your account identifier. Error reports carry no name, email address, token or value you type. Session replay is off on the sandbox portal, so the provider does not record what you do on a page. The sandbox services do not send it error reports.
The telemetry provider receives the traces, metrics and logs of the mesta-dev MCP server: the tool calls described above, with their times, their parameters with secrets removed, the result status and any error. Mesta keeps all other logs and metrics of the sandbox services in its own cloud hosting account.
The sandbox offers no test-network wallets yet, so no wallet provider receives anything.
At the date of this notice, the sandbox calls no AI or language-model provider. Its onboarding wizards take Mesta's specimen files only, and nothing you send to the sandbox reaches a provider of that kind.
When Mesta is enrolled in a code-hosting service's secret-scanning program, that service will report sandbox secrets that it finds in public code to Mesta, so that Mesta can revoke them. The service learns only the format of sandbox secrets from Mesta, never your details.
Who at Mesta can see it
Mesta staff see sandbox details only to review requests for access, to support you when you ask, to answer your request for production access and to review abuse. Showing a sandbox user's email address to a staff member requires that operator's second factor and is recorded. Staff and contractors who can see sandbox details work in the United States and India.
Where it is kept, and transfers
Mesta stores and processes your sandbox details on cloud infrastructure that Mesta operates in the United States. Uploads and backups are kept in the same region, and the sandbox's email is sent from there. The error-monitoring, telemetry, image delivery, help center and email providers process your details in the United States. The bot-protection provider runs its check in its data center nearest to you, which may be outside the United States, and processes the result in the United States. The address lookup provider processes what you type in the address field in the United Kingdom and the European Union.
If you are in the European Economic Area or the United Kingdom, your details are therefore processed in the United States. Where the transfer rules apply, Mesta relies on standard contractual clauses or another safeguard the law allows. If staff or contractors outside the United States can see sandbox details, that access is covered by standard contractual clauses.
Your rights
Depending on where you live, you can ask Mesta for a copy of your details, to correct them, to delete them, to restrict how they are used and to receive them in a portable format, and you can object to their use for Mesta's legitimate interests. Send your request to [email protected] from the email address on your sandbox account, with your sandbox id. If a request comes from another address, Mesta confirms it with you at your account address before acting on it.
You can also delete your sandbox yourself at any time from the sandbox portal. Everything in it is removed from the live system within 24 hours, and backup copies are overwritten in the normal backup cycle.
No decision about you is made solely by automated means with legal or similarly significant effects. For an invitation or an access request, a person at Mesta decides whether to give you access. The sandbox's rate limits and abuse checks are automatic and can refuse a request. You can try again later, or ask a person at Mesta to review a refusal by opening a ticket in Mesta's help center at customer.support.mesta.xyz.
You can complain to a data protection authority: in the United Kingdom, the Information Commissioner's Office. In the European Economic Area, the authority in the country where you live or work, or where you think your rights were infringed.
Cookies and storage
The sandbox portal keeps your sign-in session in your browser's storage (local storage and IndexedDB, or session storage where IndexedDB is not available) so that you stay signed in, and it keeps a cache of the portal's API responses so that pages load quickly. Where Mesta runs the bot-protection check, it runs in your browser. The portal does not store your API secret in the browser. It holds the secret in memory only while it shows it to you, once. The cache of API responses is held in memory only and is cleared when you close the tab. The portal also keeps, in local storage, your display preferences and unfinished form drafts and, if you tick "Remember me", your email address, and, in session storage, your invitation link while you accept it and the page to return to after you sign in. The portal sets no cookies. This storage is strictly necessary for the sandbox to work, so it needs no consent.
The sandbox portal loads no tag manager or other analytics tag. The error-monitoring provider stores nothing in your browser on the sandbox portal and records no session replay there. The bot-protection check runs in a frame from its provider, reads signals from your browser to tell people from automated traffic and may set the provider's own cookies there, which are strictly necessary. The documentation site at docs.mesta.xyz, run by a documentation hosting provider, keeps in your browser's storage your color scheme, the state of its API explorer and a random identifier for the open tab, and the network that serves the site sets a strictly necessary bot-protection cookie that expires after 30 minutes.
Do Not Track and Global Privacy Control: at the date of this notice, the sandbox portal loads no analytics or advertising tags and does not track you across other sites, so it treats every visitor the same whether or not the browser sends these signals.
Changes to this notice
Mesta publishes every change to this notice on this page, with a new version and date, and emails you before a material change takes effect.
Updated about 16 hours ago

