Features
Integrations Pricing Developers Guides
Legal

Privacy Policy

This policy explains what personal data Paysana collects, why we hold it, who we share it with, and the choices you have. It covers merchants who use Paysana and, separately, the buyers who purchase from them.

Last updated 7 August 2026
1

Scope and our role

Paysana is operated by Meetcyberjob Network (CA0406723-K). Where this policy says "we", that is the entity responsible for your data, and requests about it can be sent to hello@paysana.co.

This policy applies to the Paysana platform, our website, and the emails and messages we send. It does not cover a merchant's own website or the separate privacy policy each merchant publishes on their storefront.

Two different roles matter here. For merchant account data — your name, business details, billing — Paysana is the controller. For buyer data captured through a merchant's checkout, the merchant is the controller and Paysana is a processor acting on their instructions. Buyers with questions about a purchase should contact the merchant they bought from.

2

Information we collect

Account data
Name, business name, email address, phone number, country, business address, subdomain, and your password in hashed form.
Verification data
Business registration details and any documents you submit for account verification, plus tax identifiers you choose to store for your invoices.
Billing data
Your subscription plan, invoices we issue you, and card details limited to the brand, last four digits, expiry and a token from our payment provider. We never store full card numbers.
Buyer data (processed for merchants)
Names, email addresses, phone numbers, delivery and billing addresses, order contents, answers to a merchant's checkout questions, and attendee names for events.
Transaction data
Orders, invoices, ledger entries, refunds, payouts and commission records generated by activity on your account.
Integration data
Credentials for the providers you connect, stored encrypted, plus the identifiers those providers return.
Usage and technical data
IP address, browser and device information, pages viewed, timestamps and error logs, used to run, secure and debug the Service.
Communications
Support tickets and correspondence, and whether marketing emails you send were opened or clicked.

We do not knowingly collect special-category data (such as health or biometric data) and ask that you do not submit it through checkout questions or support messages.

3

How and why we use it

To provide the Service
Creating checkouts, processing the actions you initiate with your gateway, issuing receipts and invoices, delivering downloads and tickets, syncing your integrations. Legal basis: performance of our contract with you.
To bill you
Charging subscriptions, credit packs and platform fees, and keeping the records behind them. Legal basis: contract and legal obligation.
To keep the platform safe
Detecting fraud, abuse and security incidents, enforcing limits, and investigating breaches of our Terms. Legal basis: legitimate interests.
To support and inform you
Answering tickets and sending service messages about your account, billing or security. Legal basis: contract and legitimate interests.
To improve the Service
Understanding which features are used and where errors occur, using aggregated or de-identified information wherever possible. Legal basis: legitimate interests.
To meet legal duties
Retaining financial records and responding to lawful requests. Legal basis: legal obligation.

We do not use buyer data for our own marketing, and we do not sell personal data to anyone.

4

Who we share it with

We share personal data only where it is needed to run the Service, and only with categories of recipients you can anticipate:

  • Payment gateways you connect — to create the charges and refunds you initiate.
  • Email, messaging and marketing providers — to deliver the emails and messages you or the Service send, including buyer sync where you enable it.
  • Shipping and accounting providers you connect — to book shipments and write sales documents on your instruction.
  • Infrastructure and hosting providers — to store and serve the data behind the Service.
  • Our own payment provider — to bill your subscription and fees.
  • Professional advisers, and authorities where a valid legal request requires it.
  • A successor entity, if Paysana is involved in a merger, acquisition or asset sale — with notice to you.

Providers acting for us are bound to use the data only for the services they provide to us.

5

International transfers

Paysana serves merchants and buyers in many countries, and our providers may process data outside the country where you or your buyers live. Where data moves across borders we rely on appropriate safeguards, such as standard contractual terms with the recipient, and we take account of the protections available in the destination.

6

Cookies and similar technologies

Essential cookies
Keep you signed in, protect forms against cross-site request forgery, and remember interface preferences such as your theme. The Service does not work without these.
Affiliate attribution
A first-party cookie set when a buyer arrives through an affiliate link, lasting for the window the merchant configures, so commissions can be attributed correctly.
Cart and session storage
Keeps a storefront basket and wishlist available while a buyer shops.
Email open and click tracking
Marketing emails sent through the Service may include a tracking pixel and redirect links so the sending merchant can measure opens and clicks. Transactional receipts are not tracked this way.

We do not run third-party advertising trackers in the merchant dashboard. A merchant may add their own analytics or advertising pixels to their own checkout and storefront pages; those are the merchant's responsibility and are governed by the merchant's privacy policy.

7

How we protect data

  • Passwords are hashed; they are never stored or transmitted in readable form.
  • Integration credentials and two-factor secrets are encrypted at rest.
  • Full card numbers never reach Paysana — card data is handled by our payment provider, and we keep only a token and display details.
  • Optional two-factor authentication with single-use recovery codes is available on every account.
  • Access to production data is restricted to staff who need it, and administrative actions are recorded in an audit log.
  • Webhooks in both directions are signed so their authenticity can be verified.

No system is perfectly secure. If a breach affects your personal data we will notify you and, where required, the relevant authority, without undue delay.

8

How long we keep it

  • Account data: for as long as your account is open, then deleted or anonymised after closure, subject to the periods below.
  • Transaction, invoice and fee records: retained for the period tax and financial regulations require, typically several years after the transaction.
  • Buyer data processed for a merchant: kept while the merchant's account is open and on their instruction; deleted or returned when they ask or when their account closes.
  • Support correspondence: retained while needed to handle your request and to show how it was resolved.
  • Logs and technical data: retained for a short operational period, then discarded.
9

Your rights

Subject to the law that applies to you, you may have the right to access your personal data, correct it, delete it, restrict or object to processing, withdraw consent, and receive a copy in a portable format.

  • Access and portability: export your orders, customers and transactions from your dashboard at any time.
  • Correction: update your business and contact details in settings.
  • Deletion: send a request from our data deletion page — it lists exactly what is removed, what we are required to keep, and how long it takes.
  • Objection and complaints: contact us first, and you may also complain to your local data-protection authority.
Request data deletion

We do not charge for exercising these rights and will respond within the timeframe the applicable law sets.

10

If you are a buyer

When you buy from a business using Paysana, that business decides what data is collected and why — they are the controller. Paysana processes it on their behalf to complete the purchase, send your receipt and deliver what you bought.

To access, correct or delete data about your purchase, contact the merchant you bought from; their contact details are on your receipt and on their storefront. If you cannot reach them, send the request through our data deletion page and we will route it to them as the controller. Where a merchant enables it, you can also look up your own orders on their storefront using your order reference and email address.

Send a deletion request
11

Children

The Service is not directed at children, and merchant accounts require an adult. We do not knowingly collect personal data from children. If you believe a child has provided data to us, contact us and we will remove it.

12

Changes to this policy

We may update this policy as the Service and the law change. The "last updated" date always reflects the current version, and we will give notice of material changes by email or in the dashboard before they take effect.

13

Contact us

For privacy questions, data requests or to report a concern, email help@paysana.co. Please tell us whether you are writing as a merchant or as a buyer, so we can route your request correctly.

Still have a question? Email help@paysana.co and a real person will read it.
Contact us

Ready when you are.
Start selling today.

Join the businesses already using Paysana to collect payments, send invoices and grow.

Free plan forever · No card to sign up · Your own gateway
We use cookies to measure how this site is used and how well our advertising works. They are optional — the site works exactly the same either way. Read our privacy policy.