Effective Date: 2026-10-14
Privacy Policy
This Privacy Policy explains how Zoyn collects, uses, stores, shares, and protects personal data in connection with the Zoyn platform. "Zoyn" is the software platform operated by Zoyn Technologies Inc., a Wyoming corporation, doing business as "Zoyn" ("Zoyn," "we," "us") — company details at /legal/company-details. "You" means a merchant, sales partner, Authorized User, buyer, or website visitor whose personal data Zoyn processes. Annex A (Cookies and Browser Storage) and Annex B (Sub-processors and Other Recipients) are part of this Policy.
Zoyn is a software-as-a-service platform. Zoyn holds no merchant or buyer funds at any point, and no buyer payment passes through a wallet Zoyn controls. A buyer pays an on-chain settlement contract directly; that contract's payees and shares are fixed when it is created; and the only value Zoyn receives is its own software fee, paid by that contract to a fixed address in the same transaction. Zoyn does not receive, store, or process payment-card numbers or other cardholder data (Section 3).
Zoyn does not operate buyer accounts or keep buyer profiles. Section 2.5 describes what Zoyn may hold about people who pay a merchant.
This Policy covers personal data Zoyn collects in operating its software. It does not cover transaction data recorded on public blockchains, which is public and outside Zoyn's control, or data that independent third parties (such as on-ramp and hosted-checkout providers) collect directly from buyers under their own privacy policies.
1. Who is responsible for your data
Data protection law distinguishes the controller (who decides why and how personal data is processed) from the processor (who processes it on the controller's documented instructions). Zoyn is both, depending on the data:
- Zoyn is the controller of personal data about its own users — merchants, sales partners, Authorized Users, and site visitors — including onboarding and administrative data, account data, and operational and security data. Zoyn Technologies Inc. d/b/a Zoyn is the controller of record.
- Zoyn is a processor of personal data about a merchant's buyers and end-users that the merchant sends through the Service (for example, buyer wallet address, buyer email where captured, and transaction metadata). For that data the merchant is the controller, and Zoyn processes it only on the merchant's documented instructions under the Data Processing Agreement at
/legal/data-processing-agreement, which is not repeated here.
Data-protection contact: dev@zoyn.com, subject "Privacy"
2. Personal data Zoyn collects
2.1 Merchant and partner onboarding and administrative data (Zoyn as controller)
| Category | Examples | Purpose |
|---|---|---|
| Identity | Name, business name, job title | Account creation, Zoyn's own application review |
| Contact | Email address, phone number | Communications, notices, support |
| Account credentials | Email and/or username, session and authentication tokens. Zoyn stores no password. Passwords and multi-factor secrets are held by Zoyn's sign-in provider and never sent to or stored by Zoyn | Account access |
| Business information | Business type, business category (MCC), country (and U.S. state) of organization and operation, website | Onboarding review, compliance |
| Financial configuration | Payout wallet address; the merchant's thirdweb credentials (encrypted at rest) | Payment configuration |
| Compliance | The fact, time and version of beneficial-owner and sanctions attestations, and country self-declarations | Compliance |
| Acceptance record | The accepting user's Zoyn account identity, the network address and user agent at acceptance, and the slug and version of each document accepted (with a content hash where one was captured) | Executing and evidencing agreements (E-SIGN/UETA attribution). Recorded by Zoyn in its own systems; no third-party e-signature service is used |
| Communications | Support tickets, attachments, email correspondence | Customer service |
2.2 Data collected automatically
| Category | Examples | Purpose |
|---|---|---|
| Account activity | The time of your most recent authenticated request | Account security, support |
| Technical data | Network address, browser type, operating system, device type | Security, fraud prevention |
| Log data | Application request logs, error reports, sign-in events, and an append-only audit record of actions taken on merchant data | Security, debugging, audit |
Zoyn does not use advertising or cross-site tracking.
2.3 Data from third parties
| Source | Data received | Purpose |
|---|---|---|
| Sign-in provider (Clerk) | Sign-in events, login timestamps | Account security |
| thirdweb | Payment event notifications, which include the buyer's wallet address, transaction hash, amount and token, and payment status | Transaction records (Zoyn as the merchant's processor) |
Payment notifications from thirdweb are stored as received and may contain fields set by thirdweb beyond those listed.
Zoyn does not receive payment-card data, cardholder names, or identity documents from on-ramp or hosted-checkout providers; those providers collect such data directly from buyers as independent controllers (Section 3 and Annex B).
2.4 Children
The Service is not directed to children under 13, and Zoyn does not knowingly collect personal data from them. If Zoyn finds it has collected a child's data, it will close the account, stop processing the data, and withdraw the records from use. Zoyn's systems are built so that records are marked as withdrawn rather than erased, and some records are kept long-term and are designed not to be changed or deleted (Section 8); where one exists, Zoyn will restrict access to the minimum necessary and use it only for the purpose the record serves. If you believe Zoyn holds a child's data, contact dev@zoyn.com (subject "Privacy") immediately. (The Service itself is only for people aged 18 or over — Terms of Service §1.1.)
2.5 Data about buyers
When a person pays a Zoyn merchant, Zoyn's systems may hold, for example:
- the buyer's wallet address, from the payment event notification, with the amount, token, chain, transaction hash, and status of that payment;
- an email address, and sometimes a name, only where the merchant chose a feature that needs one — an invoice addressed to a named payer, a recurring payment request, or a receipt the merchant asked Zoyn to send for it; and
- the content the merchant put on the payment page the buyer opened.
Zoyn does not create buyer accounts or track any buyer's balances or holdings. The country Zoyn's content-delivery network derives from a buyer's request is read for that request and discarded, not stored against anyone (Section 15). A buyer's browser may hold a few values set by the checkout page (Annex A, Part 3); they stay on the buyer's device.
For all of this data the merchant is the controller and Zoyn is its processor. Section 11.5 says what a request about it can achieve.
3. What Zoyn does not collect
3.1 Cardholder data
Zoyn does not collect, receive, or store payment-card numbers, expiry dates, or security codes.
Where a buyer pays by card, the card details are handled by an independent on-ramp or checkout provider shown at payment, under its own privacy policy.
3.2 Other data Zoyn does not collect
Zoyn does not ask merchants or partners for tax identifiers, identity documents, or the identity details of beneficial owners during onboarding, and does not screen people by name. Identity verification on the card step, where any is done, is done by the payment provider under its own terms.
4. Legal bases (GDPR)
For people in the EEA, UK, or Switzerland, Zoyn relies on these legal bases for the data it controls:
| Processing | Legal basis |
|---|---|
| Providing the Service under the Merchant Services Agreement or Partner Agreement | Performance of a contract (Art. 6(1)(b)) |
| Account management and communications | Performance of a contract (Art. 6(1)(b)) |
| Compliance with sanctions and other legal obligations | Legal obligation (Art. 6(1)(c)) where a law requires it; otherwise legitimate interests (Art. 6(1)(f)) in lawful operation and avoiding facilitation liability (Section 15) |
| Fraud prevention and security | Legitimate interests (Art. 6(1)(f)) — protecting the platform |
| Platform improvement using aggregate counts and Zoyn's own operational records | Legitimate interests (Art. 6(1)(f)) — improving the Service |
| Marketing emails to existing merchants and partners | Legitimate interests (Art. 6(1)(f)) — opt-out available |
| Anything Zoyn expressly bases on consent | Consent (Art. 6(1)(a)) |
For buyer data Zoyn processes as a processor, the merchant, as controller, establishes the legal basis; Zoyn processes on the merchant's instructions under the Data Processing Agreement.
5. How Zoyn uses personal data
Zoyn uses personal data to:
- create, manage, and maintain merchant and partner accounts;
- review merchant and partner applications (this is not identity verification);
- configure, operate, and improve the Service;
- record payment events reported by thirdweb (as the merchant's processor);
- send transactional emails (account confirmations, security alerts, payment notifications) and, on a merchant's instruction, receipts and payment requests to addresses the merchant supplies;
- respond to support requests and complaints;
- detect and prevent fraud, abuse, and security incidents;
- comply with legal obligations (including sanctions and tax-related obligations);
- enforce the Terms of Service, Merchant Services Agreement, Partner Agreement, and Acceptable Use Policy; and
- improve and develop features using aggregate counts and Zoyn's own operational records. Zoyn builds no behavioural profiles (Section 2.2).
6. Sharing personal data
Zoyn does not sell personal data. Zoyn shares it only as follows.
6.1 Sub-processors and service providers
Zoyn uses third parties that process personal data for it. The complete list — each provider, what it processes, whose data, and the region — is Annex B, Part 1, and it is the same list the Data Processing Agreement adopts; there is one list, not two. Each provider processes data under its own published data-processing terms.
Some third parties are not Zoyn sub-processors and act as independent controllers for the data they collect or generate under their own terms — including Non-Fungible Labs, Inc. d/b/a thirdweb (payment infrastructure, hosted checkout, settlement-contract execution, and vendor payment records), on-ramp providers (card and identity data during conversion to stablecoin), and blockchain networks (public on-chain data). Annex B, Part 3 describes them.
Blockchain node endpoints. Reading the public blockchain — how Zoyn verifies a settlement and performs the address screening in Section 15 — requires a request to a blockchain node, which discloses the address being read to that node's operator in the ordinary course. No identity data is sent, no account is created, and no screening vendor receives a request from Zoyn; the sanctions check is a read of a public smart contract, not a query to a service.
6.2 Business transfers
If Zoyn is involved in a merger, acquisition, or sale of all or substantially all of its assets, personal data may be transferred as part of it, subject to this Policy. Zoyn will notify affected users where the law requires.
6.3 Legal obligations
Zoyn may disclose personal data when required by law, court order, regulator, or valid legal process. Zoyn may challenge requests it considers legally deficient.
6.4 Law enforcement and safety
Zoyn may disclose personal data to authorities where it reasonably believes it necessary to prevent fraud, crime, or harm to anyone; to make a sanctions or other report the law requires; or to protect the rights, property, or safety of Zoyn, its merchants, or the public.
6.5 Professional advisers
Zoyn may share personal data with its lawyers, accountants, and other professional advisers under confidentiality obligations.
6.6 Merchants and complaints
If you contact Zoyn about a payment or a merchant's conduct, Zoyn collects your name and contact details and uses them only to handle your complaint, and shares them with the relevant merchant only as needed to resolve it (Terms of Service §§6.7 and 17).
6.7 California "Shine the Light"
Zoyn does not share personal data with third parties for their own direct-marketing purposes (Cal. Civ. Code § 1798.83).
7. International transfers
Zoyn Technologies Inc. d/b/a Zoyn is based in the United States. If you are in the EEA, UK, or Switzerland, your personal data will be transferred to and processed in the United States. Zoyn relies on:
- the EU Standard Contractual Clauses (Commission Decision 2021/914), using the applicable module for each transfer;
- the UK International Data Transfer Addendum for UK-to-US transfers (issued by the ICO under s.119A(1) UK GDPR); and
- adequacy decisions where the European Commission has issued one for the recipient country.
Where a provider's published data-processing terms include one of these mechanisms, Zoyn relies on them. Some providers operate globally distributed infrastructure, so data may be processed in several regions.
A description of the applicable safeguards is available from dev@zoyn.com (subject "Privacy").
8. Retention
Read this section as a description of what Zoyn's systems do, not as a deletion schedule. Zoyn's default is to retain. Zoyn keeps personal data for as long as needed for the purposes in this Policy — including to provide the Service, meet legal, tax, and record-keeping obligations, resolve disputes, and enforce agreements.
Zoyn does not run an automatic deletion or anonymization process, and this Policy does not set a period after which a record is removed. Where a record is withdrawn, Zoyn's systems mark it as deleted and stop using it rather than removing it; the underlying row remains. Audit logs, payment records, and records of agreement acceptance are kept long-term and are designed not to be changed or deleted at all, because their integrity is needed for security, legal, and dispute purposes; personal data in those records may therefore remain after it has stopped being used elsewhere.
A merchant's thirdweb Secret Key is the exception and is handled differently: it is kept until the merchant revokes or replaces it, at which point it is erased, or until the account is closed.
Where the law gives you a right to have data deleted, Section 11 explains how to ask and what Zoyn is able to do.
9. Security
Zoyn uses administrative, technical, and physical safeguards appropriate to the risk, such as encryption of sensitive data in transit and at rest, access controls, and logging.
A plain-English security summary is at /legal/security-overview. No security measure is perfect, and Zoyn cannot guarantee unauthorized parties will never defeat its measures. You are responsible for the security of your own sign-in details, keys, and wallets.
10. Data breach notification
If Zoyn discovers a security incident that results, or is reasonably likely to result, in unauthorized access to, disclosure of, or destruction of personal data, Zoyn will:
- notify affected merchants and partners whose data was involved without undue delay (and, where Zoyn is controller and notice is legally required, within the time the law sets);
- where Zoyn is processor, notify affected merchants without undue delay so they can meet their own controller duties (Data Processing Agreement §9);
- notify supervisory authorities where and as the law requires; and
- cooperate with affected people's and authorities' investigations.
11. Your rights
11.1 Rights for everyone
Anyone may contact dev@zoyn.com (subject "Privacy") to ask for confirmation of processing; a copy of their data; correction of inaccurate data; deletion, where the law gives that right and subject to legal retention obligations and to Section 8; or restriction of processing in certain circumstances.
What Zoyn can actually do with a deletion request, stated plainly. Zoyn handles these requests by hand; there is no self-service delete button and no automated erasure process. Zoyn will stop using the data and withdraw the records from use, and will erase data only where its systems allow it and no legal obligation requires the record to be kept. Zoyn does not undertake to erase a record Section 8 describes as kept long-term.
11.2 EEA, UK, and Swiss residents
You also have the rights of access (Art. 15), rectification (Art. 16), erasure (Art. 17, subject to retention obligations), restriction (Art. 18), portability (Art. 20), objection (Art. 21, including to direct marketing), withdrawal of consent, and complaint to your supervisory authority (in the UK, the ICO at ico.org.uk).
Where Zoyn processes buyer data as a processor, buyers should send requests to the merchant as controller; Zoyn will forward them and help the merchant under the Data Processing Agreement (§10). Section 11.5 says what that help can achieve.
11.3 California residents
California residents have the rights to know, to delete (subject to exceptions), to correct, to opt out of sale or sharing, and to non-discrimination. Zoyn does not sell personal data or share it for cross-context behavioural advertising. To exercise these rights, email dev@zoyn.com with the subject "California Privacy Rights Request."
11.4 How to make a request
- Email dev@zoyn.com with the subject "Data Rights Request — [type]".
- Include your full name, account email (if you have an account), and the action you want.
- Zoyn responds within the time the law requires.
Zoyn may verify your identity before acting. Zoyn charges no fee for reasonable requests and may decline manifestly unfounded or excessive ones, with an explanation. Privacy complaints: subject "Privacy Complaint."
11.5 If you paid a Zoyn merchant
Zoyn is not the party you bought from, and holds no account for you. The merchant you paid is the controller of your data; send your request to that merchant. If you send it to Zoyn, Zoyn will tell you so and forward it to the merchant.
What Zoyn can do, if the merchant asks. Zoyn can help a merchant find and produce the records in Section 2.5 where the merchant or you can identify the specific record — by naming the merchant and giving the transaction reference, the wallet address used, or the email address the merchant sent to. On that basis Zoyn can find the record and provide it. Zoyn also gives every merchant an export of its own payment, invoice, recurring-request, buyer-email, and payment-link records, flagged so the merchant can see which files carry data identifying a payer.
What Zoyn cannot promise to do. Zoyn does not have an erasure function. A request to remove a record is handled by hand, is limited to what Zoyn's systems allow, and does not extend to the records Section 8 describes as kept long-term. Zoyn will say so rather than leave a request open.
Limits. Zoyn's records are not organized by person, so Zoyn cannot answer a request about "everything held about me" unless the request names the merchant and a specific identifier (a transaction reference, wallet address, or email address).
Some records, such as payment records, are kept long-term for the reasons in Section 8 and may not be removable on request.
12. Cookies and browser storage
Annex A describes every cookie and every value Zoyn's software stores on, or reads from, your device. In summary: Zoyn uses only strictly necessary sign-in cookies (set by its sign-in provider) on its own pages, sets no cookies on a merchant's payment address, and uses a few browser-storage values for the working state of the page you are on. Zoyn uses no advertising or cross-site tracking cookies. The wallet component supplied by thirdweb on checkout pages sends connection information (such as wallet address and network) to thirdweb under thirdweb's own terms.
13. Marketing emails
Zoyn may email merchants and partners about platform updates, new features, and Zoyn news. You can opt out at any time by contacting dev@zoyn.com, or by using the unsubscribe link where the message includes one. Transactional and account emails (payment notifications, security alerts, account and legal notices) cannot be opted out of while your account is open.
14. Changes to this Policy
Zoyn will update this Policy from time to time. For material changes Zoyn will email registered users at least 30 days before the change takes effect. Changes needed urgently for legal, regulatory, or security reasons may take effect sooner, with notice as soon as practical. The version and effective date at the top identify the revision in force. Continuing to use the Service after an update means you accept the updated Policy. Because buyers have no account and Zoyn holds no contact details for them, changes affecting buyer-facing pages take effect on publication.
15. Sanctions and location data
To meet its compliance needs, Zoyn may use the country (and U.S. state) a merchant declares, screening of blockchain addresses against public sanctions data, and approximate location derived from network addresses on Zoyn-served checkout pages. These controls use public blockchain data and declared or approximate location, not identity documents. Zoyn does not screen people by name. Legal basis: legal obligation where a law requires it, otherwise legitimate interests in lawful operation. Buyers who pay by card give identity and card data directly to the payment provider shown at payment, under that provider's privacy notice.
16. Contact
Data-protection and privacy questions: dev@zoyn.com (subjects: "Privacy" for questions; "Data Rights Request" for requests; "Privacy Complaint" for complaints). This is Zoyn's only contact mailbox.
Controller of record for merchant and partner account data: Zoyn Technologies Inc. d/b/a Zoyn (/legal/company-details). Postal and registered-agent address for formal notices:
Zoyn Technologies Inc., d/b/a Zoyn c/o Registered Agents Inc. 30 N Gould St Ste R Sheridan, WY 82801
Zoyn responds to requests within the time the law requires.
Annex A — Cookies and Browser Storage
Part 1 — What this Annex covers
This Annex covers every way Zoyn's software stores information on your device or reads information already stored there, not only cookies:
- Cookies — small text files a website sends and your browser returns on later requests;
- Local storage — values your browser keeps for a website until deleted, including after you close the browser;
- Session storage — values your browser keeps only until you close that tab; and
- anything equivalent — indexed databases, cache storage, and similar facilities.
The laws that govern this — the EU ePrivacy Directive, the UK Privacy and Electronic Communications Regulations, and comparable rules — treat all of these the same way, and reading a value counts as well as writing one. Values held only in a page's working memory while it is open, and lost when it closes, are not stored on your device and are not covered; where Zoyn relies on that distinction, the tables say so.
Part 2 — The test Zoyn applies
There are two categories only:
- Strictly necessary — storage without which a service you explicitly asked for cannot be delivered. It needs disclosure but not consent. The tables say which items Zoyn puts in this category and why.
- Everything else — convenience, memory across visits, attribution, measurement, or analytics. It needs your consent before it is stored or read.
Part 3 — The checkout page (what a buyer's device holds)
This is the page at a merchant's own payment address (for example pay.examplestore.com). You are not a Zoyn account holder and Zoyn holds no account for you.
Zoyn sets no cookies at all on a merchant payment address. Any cookie the application would otherwise send is removed at the network edge before the response reaches you. What follows is browser storage.
| Name | Mechanism | What it holds | Why | Lifetime | Category |
|---|---|---|---|---|---|
zoyn.checkout.paid.<payment code> | Local storage | The time your payment completed | Stops you paying twice. After you pay, the record can take up to an hour to reach Zoyn's servers; in that window, pressing Back or reopening the link would otherwise show a live payment form again, and a second on-chain payment cannot be reversed by anyone. | 2 hours, then ignored and deleted | Strictly necessary |
zoyn.checkout.paid.<payment code> | Session storage | The value 1 | The same protection, for the tab you paid in | Until you close the tab | Strictly necessary |
zoyn.checkout.receipt.<payment code> | Session storage | The amount the page requested and the blockchain transaction reference reported to the page | This is the only receipt you get from the page. Zoyn holds no contact details for you. Without it, switching tabs after paying erased the amount and reference from the screen. | Until you close the tab | Strictly necessary |
checkout-form-open:<payment code> | Session storage | The time you last opened the payment form | If you come back from your wallet app and the link now shows as unavailable or expired, the page adds a reminder to check your wallet before doing anything else, because a payment you just approved may already have gone through. It is never sent anywhere. | Until you close the tab; ignored after 15 minutes | Strictly necessary |
None of these is sent to Zoyn, and none identifies you. They are a timestamp, the digit 1, and an amount and transaction reference the page already showed you; the payment code in each name is the one in your address bar.
Legacy values are deleted, not read. An earlier build briefly wrote the receipt to local storage; that was removed, and any such value left on your device is deleted the next time the page runs and never read.
One value is read but never written here. The page reads a display-theme preference under zoyn-web-theme (Part 4). On a merchant payment address no code can set it, so the read always finds nothing — but it is a read, so it is disclosed.
Your wallet provider. To pay, you connect your own wallet through a payment component supplied by thirdweb that runs inside the checkout page. When you connect, that component stores the following under names it chooses:
| Name | Mechanism | What it holds | Lifetime |
|---|---|---|---|
thirdweb:connected-wallet-ids | Local storage | Which wallet types you connected | No expiry |
thirdweb:active-wallet-id | Local storage | The wallet in use | No expiry |
thirdweb:last-used-wallet-id | Local storage | The wallet you used last | No expiry |
thirdweb:active-chain | Local storage | The network in use | No expiry |
tw:connected-wallet-params | Local storage | Connection settings per wallet | No expiry |
lastAuthProvider | Local storage | The sign-in method last used with a wallet | No expiry |
Connecting a wallet for the payment you are making is strictly necessary — you cannot pay without it. Remembering that wallet after the payment is finished is convenience, not necessity, and Zoyn does not claim otherwise. These values are not deleted when you leave; you can remove them yourself (Part 7). When you connect and pay, the component also sends your wallet address, wallet type, and network to thirdweb's own systems — a transmission, not storage on your device — under the merchant's thirdweb account, not Zoyn's.
And the wallet you choose talks to its own provider, not to Zoyn. Depending on which wallet you pick, the component may open a connection to that wallet's own service — including the WalletConnect relay or Coinbase's wallet service — and that service may store its own values on your device under names it chooses. Zoyn does not set them, does not read them, and cannot list them. Annex B, Part 3.
Part 4 — The merchant dashboard and application forms
These are Zoyn's own pages, used by people who have or are seeking a Zoyn account.
Cookies
| Name | Set by | What it does | Lifetime | Category |
|---|---|---|---|---|
__client | Clerk (sign-in provider) | Identifies your browser to the sign-in system | Set by Clerk | Strictly necessary |
__session | Clerk | Keeps you signed in | Set by Clerk | Strictly necessary |
__clerk_db_jwt, __clerk_handshake | Clerk | Sign-in handshake and development sessions | Set by Clerk | Strictly necessary |
Without these you cannot sign in. The full set of cookies Clerk places is set by Clerk, not Zoyn, and is listed in Clerk's documentation; the four above are the ones evidenced in Zoyn's code. Clerk also briefly writes and immediately deletes a value named __lsbc__… in local storage to keep multiple open tabs of your account in step.
Browser storage
| Name | Mechanism | What it holds | Lifetime | Category |
|---|---|---|---|---|
zoyn-onboarding-business-draft:<your id>:<business id> | Local storage | Your in-progress application form — business name, contact name, website, description, reason for applying | 72 hours after you last edit it, or sooner: deleted when you save the step, or when the saved record changes underneath it | Strictly necessary in purpose |
zoyn-onboarding-answer-draft:<your id>:<business id> | Local storage | Your in-progress answer to a reviewer's question, and the question | 72 hours after you last edit it, or sooner: deleted when you submit it | Strictly necessary in purpose |
zoyn-web-theme, and zoyn-web-theme:<your id> once signed in | Local storage | Light or dark appearance, as you chose | No expiry | Strictly necessary (a setting you asked for) |
zoyn.activeMerchantId | Session storage | Which of your businesses you are viewing | Until you close the browser | Strictly necessary |
zoyn-web:location-filter:<business id> | Session storage | The branch you filtered to | Until you close the browser | Strictly necessary |
zoyn-web:location-filter-name:<business id> | Session storage | That branch's name, so a deleted branch can still be named | Until you close the browser | Strictly necessary |
zoyn-web:report-period, zoyn-web:report-range | Session storage | The reporting period and date range you picked | Until you close the browser | Strictly necessary |
banner:<name> | Session storage | That you dismissed an on-screen notice | Until you close the browser | Strictly necessary |
zoyn.idle.lastActivity.<sign-in session> | Local storage | The time you last used the app, so you are signed out after a period of no use — including while your device was locked or the tab was in the background | Deleted when you are signed out for no use. If you sign out yourself, it stays in this browser but is never read again, because your next sign-in is a new session | Strictly necessary (account security) |
zoyn_business_type_hint | Session storage | The kind of business you picked on our website (for example "coffee shop"), so the sign-up form can suggest it | Until you close the browser or sign out, whichever comes first | Strictly necessary (a choice you made, carried to the form you asked for) |
zoyn_referral_code | Session storage | An 8-character partner referral code from a ?ref= link you arrived through | Until you close the browser, or until sent with your application — whichever comes first | Not strictly necessary |
This table deliberately does not call the two form drafts strictly necessary without qualification — they are exempt in purpose and arguably not in lifetime — and does not call the referral code strictly necessary at all: it exists so Zoyn can credit your sign-up to a partner and pay them, which is Zoyn's commercial interest, not a service you asked for.
Bot protection. Zoyn's public forms — merchant sign-up, the partner application, and the marketing-site contact form — show a Cloudflare Turnstile challenge before first submission. Turnstile is run by Cloudflare, and any storage or cookie it sets is Cloudflare's, under Cloudflare's terms.
The admin console (Zoyn staff only). Zoyn runs a separate internal console at admin.zoyn.com, used only by Zoyn staff to review and manage merchant accounts; no merchant, applicant, or member of the public can sign in to it. Disclosed for completeness:
| Name | Mechanism | What it holds | Lifetime | Category |
|---|---|---|---|---|
zoyn.admin.merchants.statusFilter | Session storage | The merchant-status filter a staff reviewer chose | Until the tab is closed | Strictly necessary |
zoyn-admin-theme, and zoyn-admin-theme:<staff id> once signed in | Local storage | The staff member's light or dark appearance | No expiry | Strictly necessary |
zoyn.admin.nav.collapsedGroups | Local storage | Which menu sections a staff member collapsed | No expiry | Strictly necessary (a setting the staff member chose) |
zoyn.idle.lastActivity.<sign-in session> | Local storage | The time the staff member last used the console, so they are signed out after a period of no use | Deleted when the staff member is signed out for no use. After a sign-out they do themselves, it stays in the browser but is never read again, because the next sign-in is a new session | Strictly necessary (account security) |
Part 5 — The public website (zoyn.com)
The marketing website loads no analytics script. The bot-protection challenge on its contact form is described in Part 4.
Part 6 — What Zoyn does not do
- No advertising, retargeting, or marketing cookies, and no marketing pixels of any kind (Meta, Google Tag Manager, TikTok, or otherwise);
- no behavioural profiling or interest-based advertising;
- no cross-site tracking;
- no device fingerprinting;
- no analytics script of any kind on a checkout page a buyer visits;
- no error-reporting or session-recording software on a checkout page a buyer visits — Zoyn's browser error reporting runs on the merchant dashboard and admin console only, is limited to errors, and records no session replay; and
- no selling or sharing of any of the above.
Part 7 — Your choices
You can delete everything Zoyn stores on your device at any time in your browser settings ("Clear browsing data," "Cookies and site data," or per-site controls), or block storage entirely. If you do: on the merchant dashboard, you will not be able to sign in, and your appearance, selected business, and filters reset; on a checkout page, the page still works and you can still pay, but the protection against paying twice during the settlement window is weaker and the on-screen receipt will not survive switching tabs — the pages are built to keep working when storage is refused and fall back to the server's answer. Clearing storage does not delete anything in Zoyn's own systems; for that, see Section 11.
Part 8 — Changes to this Annex
Zoyn will update this Annex whenever it changes what it stores on or reads from a device. Material changes are reflected in the version and date and emailed to account holders at least 30 days before they take effect, except that a change describing storage already in use is corrected on publication. Because buyers have no account, changes affecting Part 3 take effect on publication.
Annex B — Sub-processors and Other Recipients
This Annex lists the third parties Zoyn engages to process personal data — both data Zoyn controls and data it processes for merchants under the Data Processing Agreement — and, separately in Part 3, third parties that receive data but are not Zoyn sub-processors. The Data Processing Agreement adopts Part 1 as its sub-processor list; there is one list. Zoyn reviews this Annex whenever a provider is engaged or ended.
Part 1 — Current sub-processors
| Sub-processor | Purpose | Personal data | Region |
|---|---|---|---|
| Clerk, Inc. | Sign-up, sign-in, session and multi-factor management. Zoyn proxies Clerk's browser interface through Zoyn's own domain, so Zoyn's servers sit in the sign-in path | Merchant, partner, and Authorized User email, username, name, session and login data | US |
| Amazon Web Services, Inc. (Key Management Service) | Encryption of platform secrets — merchant thirdweb credentials, the treasury and operations signing keys, and the webhook signing secret | The secret itself. Zoyn sends each secret to AWS over an encrypted connection whenever it encrypts or decrypts it, and AWS returns the result to Zoyn | US (us-east-1, the configured region) |
| Plus Five Five, Inc. d/b/a Resend | Transactional email — platform-to-merchant and platform-to-partner email from Zoyn's own sending domain, and buyer-facing receipts and payment requests sent under a merchant's own verified sending domain | Merchant, partner, and Authorized User email; buyer email address and message contents where a merchant used a feature that sends one | US |
| Replit, Inc. | Application hosting, runtime, and the provisioning of the managed PostgreSQL database | All operational data | US |
| Neon, Inc. | Operates the managed PostgreSQL database instance provisioned through Replit. The production database runs on a Neon endpoint, so Neon's infrastructure holds the stored data | All operational data | US |
| Google LLC (Google Cloud Storage bucket provisioned through Replit) | Storage of uploaded brand logos and support-ticket attachments | Uploaded images; attachment contents | Not specified |
| Cloudflare, Inc. — content delivery, edge routing, TLS, and key-value configuration | Terminates every connection to a merchant's branded payment domain (pay.<merchant>.com), issues and renews its certificate, holds the hostname-to-merchant routing entry, and supplies the country value used for the buyer-side geographic control (Section 15). Zoyn also sends a single network address to Cloudflare's public network-information service when a Zoyn reviewer opens the details of an application, to show the reviewer where a sign-up came from | Network address, headers, and connection metadata of everyone who opens a Zoyn-served checkout or payment page; the merchant's custom hostname; a single network address on a reviewer lookup | Global edge network |
| Cloudflare, Inc. — Turnstile | Bot protection on Zoyn's public forms: merchant sign-up, partner application, and the marketing-site contact form. Runs in the applicant's browser | Applicant network address and browser signals. Not a buyer-facing surface | Global edge network |
| Functional Software, Inc. d/b/a Sentry | Error reporting from Zoyn's servers, the merchant dashboard, and the admin console. Not loaded on the buyer checkout | Error diagnostics, scrubbed before sending: fields whose names identify personal data are dropped without their values being inspected, and default personal-data capture and performance tracing are off. Sentry still observes the sending network address, which it derives itself and Zoyn cannot scrub | Multi-region |
Part 2 — What Zoyn does before engaging a sub-processor
Before engaging a sub-processor that processes merchant personal data, Zoyn: checks that the provider's published data-processing terms cover confidentiality, security, and assistance obligations appropriate to the processing; assesses the provider's security against the processing it will do; and remains fully liable to the merchant for the provider's performance of Zoyn's obligations under the Data Processing Agreement. Zoyn does not represent that a separately negotiated agreement is signed with any provider.
Part 3 — Recipients that are not sub-processors
A list naming only contracted processors does not fully answer "who sees my data." Each party below receives data in the ordinary running of the Service, and none is engaged by Zoyn as a processor.
Independent controllers — collecting data directly, for their own purposes, under their own terms:
- Non-Fungible Labs, Inc. d/b/a thirdweb — payment infrastructure, hosted checkout, settlement-contract execution, and vendor payment records; thirdweb decides the purposes and means of that processing. Zoyn receives the payment event notification it needs for its merchant record.
- On-ramp and hosted-checkout providers (the provider shown at payment) — payment-card and identity data collected from buyers during conversion to stablecoin. Zoyn does not receive that data. thirdweb may route a payment to any of these, and the list may change; Zoyn makes no representation about any provider's licensing or compliance.
- Blockchain networks — transaction data on Base is public and processed by validators and node operators Zoyn neither engages nor controls; wallet addresses are pseudonymous public identifiers. Automated exchange, bridge, and routing services chosen by thirdweb at payment time may also receive a buyer's wallet address and amount; Zoyn does not choose, and cannot list in advance, which ones.
- The wallet service you choose at checkout. Connecting a wallet is a conversation between your browser and the wallet you pick, not between you and Zoyn. Depending on which wallet you choose, the payment component may connect to that wallet provider's own systems — including the WalletConnect relay (WalletConnect, Inc.) and Coinbase's wallet service (Coinbase, Inc.) — which receive what they need to establish the connection under their own terms. Zoyn does not choose your wallet and receives none of that exchange.
Recipients of data in transit, under no agreement with Zoyn (no processing agreement is claimed):
- Public DNS resolvers. When a merchant checks whether its custom domain's DNS records have propagated, Zoyn queries two public DNS-over-HTTPS resolvers, one run by Google and one by Cloudflare, to preview what the world's resolvers see. Only the domain name being checked is sent, from Zoyn's server.
- The public Base network endpoint at
mainnet.base.org, used to read on-chain state independently of any vendor. Only a wallet address, contract address, or transaction hash — all already public — is sent. Zoyn has not verified which entity runs this endpoint and does not assert one.
Part 4 — International transfers
Zoyn is established in the United States; assume personal data processed under this Annex is transferred to and processed in the United States. For transfers from the EEA, UK, or Switzerland to a country without an adequacy decision, Zoyn relies on the mechanisms in Section 7. A description of the safeguards is available from dev@zoyn.com (subject "Privacy").
Part 5 — Changes to this Annex — notice and objection
- Zoyn will notify merchants at least 30 days before adding or replacing a sub-processor, by updating this Annex and notifying merchants by email or dashboard announcement.
- A merchant may object on reasonable data-protection grounds by contacting dev@zoyn.com within 14 days of the notice; because that window sits inside the 30 days, an objection always arrives before the change takes effect.
- If an objection cannot be resolved, the merchant may terminate the affected processing services under the Data Processing Agreement.
- Removing a sub-processor, or correcting a statement here so it describes processing already happening, is not an addition and does not carry the 30-day notice.