Skip to content

Privacy Notice

Last updated

This Privacy Notice describes how 402pay.co ("402pay", "we", or "us") collects, uses, shares, and protects personal data, and the choices available to you. "Personal data" means any information about an identified or identifiable person, such as a name, an email address, or an IP address.

1. Who this notice covers

This notice applies where we determine how and why personal data is used, which makes us the controller of that data. It covers:

  • visitors to our website and readers of our developer documentation;
  • merchants, meaning the businesses that use 402pay and the individuals acting on their behalf;
  • payers, meaning individuals who pay a merchant through 402pay, with respect to the data we use for our own purposes, such as preventing fraud; and
  • anyone who contacts us.

When we operate a merchant's checkout, we process payers' data on behalf of that merchant, as its processor. The merchant determines how that data is used, so questions about it should be directed to the merchant first. If you send us a request about data we process for a merchant, we will forward it to that merchant.

This notice does not cover services we do not operate, such as the providers that process card payments or the wallets and exchanges from which payers send funds. Those services have their own privacy notices, which we encourage you to read.

2. What we collect

2.1 What merchants give us

  • Account details: the email address you use to sign in, and your password, which we store only as a one-way hash that cannot be reversed.
  • Passkeys, if you use them to sign in: for each passkey, a credential ID, its public key, a signature counter, the name you give it and, where your browser provides it, the password manager or device that created it, and when it was added and last used.
  • Business details, such as your business's name, website, and support email address, and the settings you select.
  • Content you create in the Services, such as payment links, customers, notes, API keys, and webhooks.
  • Wallet data: public keys, addresses, balances, and transactions. If you create or import a wallet with us, we also store its recovery phrase, but only after your browser has encrypted it with a password we never receive.
  • Messages you send us, and information you provide to verify your business.

2.2 What payers give us

  • Your email address, which checkout requests for every card payment, and for crypto payments where the merchant chooses to request it. A merchant may also provide it to us directly.
  • Your country, derived from your browser's language settings.
  • The amount, currency, coin, and network you use to pay.

2.3 What we collect automatically

  • Log data: your IP address, your browser, the pages or API endpoints you request, and the time of each request.
  • Session data for merchants: the device and browser of each signed-in session, its IP address and approximate location, and when it was last used, as well as the devices and countries from which you have recently signed in, so that we can notify you of a new one.
  • Activity in the Dashboard, which we record in your business's audit log.
  • On the sign-up, sign-in, and password reset pages, the result of a Cloudflare Turnstile security check, which reads technical details of your browser and connection, such as your IP address, to distinguish people from bots.

2.4 What we get from others

  • From public blockchains: the address from which a crypto payment was sent, its transaction hash, and its confirmations.
  • From the independent providers that process card payments: whether a card payment was approved and, if a payment failed, the reason it failed.
  • From the providers that help us verify businesses.

2.5 What we do not collect

We never store your password itself, only a hash of it, and we never see your wallet's encryption password. We never receive, in readable form, a recovery phrase or a private key that can spend funds. A passkey's private key never leaves your device or password manager, and the fingerprint, face, or PIN you use to unlock it stays on your device, so we receive neither. Full card numbers, expiry dates, and security codes are sent to the provider that processes the card payment and never to us. We do not collect sensitive data, such as health or biometric data, and we do not buy data from data brokers.

3. How we use personal data

We use personal data only for the purposes set out below. For individuals in the European Economic Area, Switzerland, and the United Kingdom, the table also identifies the legal basis on which we rely.

PurposeDataLegal basisHow long we keep it
Providing the Services to merchants, including checkout, receipts, webhooks, and support.Account details, business details, content you create, wallet data, messages.Performance of our contract with the merchant.While the account is open.
Keeping accounts secure, including sign-in with a password or passkey, confirmation of email addresses, password resets, two-step verification, sessions, security emails, and the check that keeps bots out of sign-up, sign-in, and password resets.Account details, passkeys, session data, security check results, log data, activity.Our legitimate interest in keeping accounts secure.While the account is open.
Preventing fraud and abuse.Payment data, log data, data from blockchains and card payment providers.Our legitimate interest in protecting merchants, payers, and the Services.Up to five years after the payment.
Meeting legal obligations, such as record keeping.Business details, payment data.Compliance with a legal obligation.As long as the law requires, typically five years.
Understanding how the Services are used, so that we can fix and improve them.Log data and activity, aggregated wherever possible.Our legitimate interest in improving the Services.Up to 12 months, unless aggregated.

We do not sell personal data or share it for cross-context behavioral advertising. Our fraud and abuse checks may block a payment automatically. If one of your payments is blocked in this way, you may ask us at [email protected] to have a person review the decision.

4. Who we share it with

We share personal data only with:

  • the merchant a payer has paid, so that the merchant can fulfill the order, answer questions, and handle refunds;
  • the independent provider that processes a card payment, under that provider's own terms and privacy notice;
  • Cloudflare, which operates the security check on our sign-up, sign-in, and password reset pages. Cloudflare processes the check on our behalf, and uses what it learns to improve the check, under its own privacy policy;
  • service providers that host and operate the Services for us, deliver our emails, or help us verify businesses, each of which is bound by contract to use the data only to perform services for us (we provide the current list on request);
  • professional advisers, such as lawyers, auditors, and insurers, who are bound to keep it confidential;
  • authorities and other parties, where the law or legal process requires it, or where necessary to enforce our agreements or to protect the rights, property, or safety of our users, the public, or 402pay; and
  • a buyer or successor, if 402pay is involved in a merger, acquisition, or sale of assets. We will notify merchants before their data becomes subject to a different privacy notice.

5. Aggregated and de-identified data

We may convert personal data into aggregated or de-identified data that can no longer reasonably be used to identify anyone, such as the number of payments made on each network, and we may use or share that data for lawful purposes, including to understand, improve, and promote the Services. We keep such data in aggregated or de-identified form and do not attempt to identify anyone from it.

6. Public blockchains

Crypto payments are recorded on public blockchains. Anyone can view a transaction's addresses, amount, and hash, and no one, including 402pay, can change or delete them. We do not publish the identity of the person behind an address, but others may be able to link an address to a person using other information.

7. International transfers

We operate on cloud infrastructure with servers in many countries, so your personal data may be processed outside the country in which you live, including in the United States. When we transfer personal data out of the European Economic Area, Switzerland, or the United Kingdom, we rely on safeguards recognized by law, such as the European Commission's standard contractual clauses and the UK addendum to them.

8. Communications from us

We send merchants the messages the Services require, such as codes that confirm an email address, password reset links, notices about their account and payments, and changes to our terms. We email merchants about their account's security, such as sign-ins from a new device and changes to their email address, password, passkeys, two-step verification, or wallet, and these emails cannot be turned off while the account is open. We do not email payers; a payer's receipt is a page the payer can open, print, or save. If we send merchants product news, each such email includes a link to stop receiving it. You cannot opt out of messages we must send to operate the Services or that the law requires.

9. Your rights

9.1 What you can ask for

Depending on where you live, you may have the right to:

  • know what personal data we hold about you, how we use it, and with whom we share it, and obtain a copy of it;
  • correct it if it is inaccurate or incomplete;
  • have it deleted, unless we are required by law to keep it;
  • object to or restrict our use of it, and withdraw your consent where we rely on consent;
  • receive it in a portable, machine-readable format, or have us send it to another party;
  • opt out of the sale or sharing of personal data, and of profiling that has legal or similarly significant effects; and
  • appeal a decision we make about your request.

These rights are subject to conditions and exceptions under the law, and we may keep data we need to meet legal obligations, resolve disputes, or prevent fraud. Exercising your rights will not affect how we treat you.

9.2 Making a request

Merchants can view and update most of their data in the Dashboard. For any other request, email [email protected] and describe your request in enough detail for us to locate your data, such as by providing a receipt or naming the business involved. We will verify your identity before we act, using information we already hold, so we may ask a merchant to write from the email address they use to sign in, or ask a payer to share a receipt.

Where the law allows, you may have an authorized agent make a request on your behalf with your signed permission, and we may confirm the request with you. We do not charge for requests unless they are manifestly unfounded or excessive, and we respond within the time the law allows, usually 30 days, or 45 days under U.S. state laws, extended where the law permits. If we process your data on behalf of a merchant, we will forward your request to that merchant.

9.3 Residents of U.S. states

California, Colorado, Connecticut, Virginia, and other states give their residents rights over their personal data. In the preceding 12 months, we collected the categories of personal data described in “What we collect”, from the sources listed there, for the purposes described in “How we use personal data”, and disclosed them for business purposes to the recipients listed in “Who we share it with”. We have not sold personal data or shared it for cross-context behavioral advertising, and we do not use sensitive personal data to infer characteristics about anyone. We treat a Global Privacy Control signal from your browser as a request to opt out of sale and sharing. If we decline your request, you may appeal by replying to our decision, and if we deny your appeal, you may contact your state attorney general.

9.4 The European Economic Area, Switzerland, and the United Kingdom

402pay.co is the controller of the personal data this notice covers, and the table in “How we use personal data” identifies the legal basis for each use. Where we rely on our legitimate interests, you may object to our use of your data, and where we rely on consent, you may withdraw it at any time without affecting the lawfulness of our use before you withdrew it. You may also lodge a complaint with the data protection authority where you live or work, or where you believe a breach occurred, although we would welcome the opportunity to address your concern first.

10. How we protect it

We hold as little sensitive data as we can and protect the data we do hold, including by encrypting data in transit and at rest, encrypting recovery phrases before they leave the browser, storing passwords and other secrets only as hashes, and limiting staff access to those who need it. No system is completely secure. If a breach affects your personal data, we will notify you and the relevant authorities as the law requires.

11. How long we keep it

We keep personal data for the periods set out in the table above. When a merchant closes its account, we delete or anonymize its data, except data we must keep for legal and tax purposes, to resolve disputes, or to prevent fraud. When we no longer need data, we delete it securely.

12. Cookies and local storage

We do not use advertising cookies or third-party trackers. We use only a small number of our own entries, each of which is necessary for the Services or remembers a choice you have made:

  • a cookie that keeps you signed in to the Dashboard;
  • a cookie that links a sign-up to the browser in which it started, for up to one day, so that only that browser can complete it without your password;
  • a cookie that recognizes a browser you have signed in with, for up to 90 days after your last sign-in in that browser, so that failed sign-in attempts from elsewhere cannot lock you out of it;
  • a cookie that ties a passkey sign-in to the browser that started it, for up to five minutes, so that no other browser can complete it;
  • a cookie that remembers the business you last opened;
  • a cookie that remembers your cookie choices; and
  • local storage entries that remember your theme, the language and appearance you select at checkout, and choices you make in our developer documentation, such as your code language and checklist progress, and session storage that keeps your place in sign-up and carries your email address between the sign-in pages until you close the tab.

Any other cookies, such as cookies that measure how the site is used, are set only if you allow them, and you may change your choice at any time in Cookie settings. You may also clear cookies in your browser settings, although clearing the first cookie listed above will sign you out.

The security check on the sign-up, sign-in, and password reset pages runs in Cloudflare's own frame and reads only the information it needs to distinguish people from bots. Because it is necessary to keep accounts secure, it is not subject to these choices.

13. Children

The Services are not intended for anyone under 18, and we do not knowingly collect personal data from children. If we learn that we have done so, we will delete that data promptly. If you believe a child has provided personal data to us, please contact us at [email protected].

14. Changes to this notice

We may update this notice by publishing a new version on this page, and we will notify merchants of material changes before they take effect, by email or in the Dashboard. Each version applies to data collected while it is in effect. This notice forms part of our Terms of Service.

15. Contact us

402pay.co is responsible for the personal data this notice covers. For questions about this notice, our use of personal data, or your rights, email [email protected]. For questions about your account, email [email protected]. To report a security vulnerability, email [email protected].