Privacy Policy

Effective 18 November 2026

We built the service to need as little personal data as possible: funds go straight to the merchant's wallet, payers do not create accounts, and we never see private keys. This policy describes the data we do handle.

1. Who this policy covers

This policy explains how BrightGatePay (“we”) handles personal data of two groups of people:

  • Merchants: people who create an account to accept payments.
  • Payers: customers of a merchant who open a checkout page or send a payment.

For payers, the merchant decides why and how a payment is requested and is responsible for its own privacy notice; we process the payment data on the merchant's behalf.

2. What we collect

From merchants

  • Account details: your email address, the display or business name you enter, and when you signed up. If you set a password we store only a one-way hash of it. If you sign in with Google we receive your Google account identifier, email address, name and the address of your profile picture from Google, and nothing else from your Google account.
  • Sign-in sessions: for each device you sign in on, the time, the IP address and the browser description, so you stay signed in and we can protect the account.
  • Service settings: your public wallet addresses, the names of your API keys, your webhook addresses, and your API and webhook secrets (stored encrypted).
  • Billing records: the fees charged on your payments and the fee payments recorded on your account.

About payments

  • What the merchant sends when it creates a payment: the amount, the network, the merchant's own order reference, optional return addresses and optional extra data (“metadata”). We ask merchants not to put personal data in these fields.
  • What appears on the public blockchain for a matched transfer: the sending and receiving wallet addresses, the amount, the time and the transaction identifier. This information is public and permanent on the blockchain whether or not we store a copy.
  • A log of the notifications (webhooks) sent to the merchant and whether they were delivered.

From everyone who uses the site

  • The IP address of requests, used for a short time to limit abuse (too many sign-in attempts, sign-ups or status checks), and standard server logs kept by our hosting provider.

We do not ask payers for a name, an email address or an account. We never collect private keys or seed phrases from anyone.

3. How we use it

  • To provide the service: create payment requests, watch the blockchain for matching transfers, show status, and notify the merchant.
  • To run accounts: sign you in, confirm your email address, reset your password, and send service and security messages.
  • To calculate and bill fees.
  • To keep the service secure: prevent abuse and fraud, investigate problems, and enforce our Terms of Service.
  • To meet legal obligations, such as responding to a lawful request from an authority.

4. Cookies

We use only the cookies needed to make sign-in work:

  • a session cookie that keeps a merchant signed in (up to 30 days, removed when you sign out);
  • a short-lived cookie used during “Continue with Google” to protect that sign-in (10 minutes).

We do not use advertising or analytics cookies, tracking pixels or third-party trackers. The checkout page sets no cookies.

5. Who we share it with

We do not sell personal data. We share it only with:

  • Service providers that run the service for us and may only use the data for that purpose: our hosting and database providers, our email delivery provider (your email address and the message we send you), and Google when you choose to sign in with Google.
  • Blockchain data providers: to detect payments we ask network nodes for transfers to the merchant's public wallet address. They receive that public address and nothing else about you.
  • The merchant: receives the details of the payments made to it, including the public blockchain data of the transfer.
  • Authorities or other parties when the law requires it, or when needed to protect our rights, our users or the public.
  • A successor, if the service is merged or sold, under terms no less protective than this policy.

Our providers may process data in countries other than yours. Where the law requires safeguards for such transfers, we rely on the safeguards our providers offer.

6. How long we keep it

  • Account details: for as long as the account exists, and afterwards for as long as needed for billing, tax, dispute and legal purposes.
  • Sign-in sessions: until you sign out or they expire (30 days). One-time email links expire within 48 hours.
  • Payment, transfer and notification records: for as long as the merchant's account exists, and afterwards as needed for the purposes above.
  • Abuse-prevention counters that contain an IP address: normally no longer than a day.

7. How we protect it

Passwords are stored as salted one-way hashes. API and webhook secrets are encrypted at rest. Sign-in sessions and one-time links are stored only as hashes. Connections to the service use HTTPS, sign-in attempts are rate-limited, and access to our systems is restricted. No system is perfectly secure; if we learn of a breach that affects your data we will notify you as the law requires.

8. Your choices and rights

In your dashboard you can change your name and password, replace or disable API keys, and remove your wallet addresses at any time.

Depending on where you live, you may have the right to ask for a copy of your personal data, to have it corrected or deleted, to object to or restrict certain uses, to receive it in a portable form, and to complain to your data protection authority. To use these rights, contact our support team. We will answer within the time the law sets. We may need to keep some records where the law requires it, and we cannot change or erase data that is recorded on a public blockchain.

If you are a payer, please contact the merchant you paid first: the merchant decides how your payment data is used.

9. Children

The service is for businesses and is not directed at anyone under 18. We do not knowingly collect personal data from children.

10. Changes to this policy

We may update this policy. The date at the top shows when the current version took effect. If a change is significant we will tell merchants by email or in the dashboard before it applies.

11. Contact

The service is operated by BrightGatePay. For any question about this policy or your personal data, contact our support team.