Skip to content
Sandbox open: magic test cards, hosted checkout and signed webhooks · 55 payment methods in the catalogue, cards to crypto · Built and hosted in the EEA · Read the API reference at /developers

Sandbox open: magic test cards, hosted checkout and signed webhooks

Privacy policy

What personal data Cleared-pay processes, why, for how long, and your rights.

Last updated

On this page

Version 1.0, effective 7 October 2026.

Controller and contact

Cleared-pay is the trade name of Kesheron Digital Ltd., a corporation incorporated on 24 February 2026 under the Business Corporations Act (Alberta), Canada, Alberta corporate access number 2027926902, with its registered office at 13-4205 30 Street NW, Edmonton, Alberta T6T 2G9, Canada. Kesheron Digital Ltd. is registered with FINTRAC, the Financial Transactions and Reports Analysis Centre of Canada, as a Money Services Business, registration N300001079. In this notice "we", "us" and "Cleared-pay" mean Kesheron Digital Ltd.

Where we decide the purposes and means of processing, we are the controller under the General Data Protection Regulation (GDPR) and the organisation accountable under Canada's Personal Information Protection and Electronic Documents Act (PIPEDA) and Alberta's Personal Information Protection Act (PIPA).

We have not yet appointed a representative in the European Union under Article 27 GDPR, nor a named data protection contact. Both are being appointed. Until they are, every privacy request, question or complaint goes to legal@cleared-pay.com, or by post to the registered office above. We will update this notice when the appointments take effect.

Who this notice covers

This notice covers four groups of people.

  • Visitors to cleared-pay.com, including the documentation and blog.
  • Prospective merchants who submit the qualification form or write to us.
  • Merchant users: the people who hold an account in the merchant portal, and the directors, beneficial owners and signatories whose details a merchant gives us during onboarding.
  • Payers: the customers of a merchant whose details pass through the hosted checkout page, the API or a payment link.

For visitors, prospects and merchant users we are the controller. For payer data we act on the merchant's instructions: the merchant is the controller, and Cleared-pay is its processor under Article 28 GDPR and its service provider under PIPEDA and PIPA. The exception is the payer and transaction data we must keep under anti-money-laundering law, card scheme rules and fraud prevention; for those records we are the controller, because the law, not the merchant, decides what we keep. The merchant's own privacy notice explains how it uses payer data, and questions about a purchase go to the merchant first.

Data we process

Visitors. Server logs hold the IP address, user agent, requested page, timestamp and a request identifier for each request. The site sets no analytics or advertising cookies; the cookie policy lists exactly what is stored in the browser.

Prospective merchants. The qualification form collects the company name, website, contact name, business email, phone (optional), country, industry, expected monthly volume, the payment methods of interest, the licence jurisdiction and prior chargeback ratio where relevant, a free-text message, and the page the form was submitted from. We also record the submitting IP address for rate limiting.

Merchant users. Name, business email, role, password (stored only as an Argon2id hash), two-factor authentication secret (stored encrypted) and backup codes (stored hashed), sign-in history including IP address and user agent, active sessions, and the actions you take in the portal. For the merchant entity: legal and trading name, registration and VAT identifiers, address, website, merchant category, expected volumes, and the directors and beneficial owners with their name, date of birth, nationality and ownership percentage. Onboarding documents (certificate of incorporation, proof of address, bank statement, identity document, licence, processing history) are stored as private objects in encrypted storage. Payout bank account details are stored with the account number encrypted; only the last four characters are shown in the portal.

Payers. A payment carries the amount, currency, the merchant's order reference, the payment method, the payer's email and name where the merchant collects them, the billing address and metadata the merchant supplies, the payer's IP address and user agent, country, and the outcome returned by the acquirer or authentication service, including authentication status, risk score and decline reason. Cleared-pay does not store a card number or a security code; a stored payment instrument is limited to brand, last four digits, issuing range, expiry, issuer country and a fingerprint. The fingerprint is a keyed hash of the card number that lets the same card be recognised again without the number being kept. Card details entered on the hosted page are tokenised inside the request that receives them and are excluded from logs.

Everyone. Our append-only audit log records who did what, when, from which IP address and user agent, with a request identifier. Our API request log records the method, path, status, duration, IP address, user agent, and the request and response bodies with secrets and card numbers removed.

PurposeDataLegal basis under the GDPR, and the position under PIPEDA and PIPA
Running the website and keeping it secureVisitor logs, request identifiersLegitimate interests (Article 6(1)(f)) in operating and defending the service. A reasonable purpose under PIPEDA and PIPA.
Answering an enquiry and assessing whether we can serve a businessQualification-form dataSteps before a contract at the prospect's request (Article 6(1)(b)) and legitimate interests in following up. Implied consent under PIPEDA and PIPA.
Providing the merchant account, portal, API and hosted checkoutMerchant and merchant user data; payer data on the merchant's instructionsPerformance of the merchant contract (Article 6(1)(b)). For payer data, the merchant's documented instructions.
Verifying a business, its owners and its source of funds; monitoring transactions; reporting where requiredOnboarding data, documents, transaction recordsLegal obligation (Article 6(1)(c)) under Canada's Proceeds of Crime (Money Laundering) and Terrorist Financing Act and under card scheme rules. Required by law under PIPEDA and PIPA.
Preventing fraud and abuseRisk lists, card fingerprints, IP addressesLegitimate interests (Article 6(1)(f)) of Cleared-pay, merchants and payers. Permitted without consent under PIPEDA and PIPA for investigating a breach of an agreement or a contravention of law.
Keeping accounting, tax and dispute recordsTransaction, settlement, refund and dispute recordsLegal obligation (Article 6(1)(c)); legitimate interests in defending claims.
Sending service messagesEmail addressPerformance of the contract. Invitations, password resets, security alerts and export links are service messages, not marketing.
Optional measurement cookies, if ever introducedBrowser identifiersConsent (Article 6(1)(a)), which you can withdraw at any time. None are set today.

We do not sell personal data and we do not use it for advertising.

Fraud prevention and automated decisions

Two kinds of logic act on a payment.

The first is ours. Cleared-pay keeps block lists and allow lists, either for a single merchant or across the platform, keyed on issuing range, email address, IP address, country, card fingerprint or device. Each entry records a reason, its author and an optional expiry. Today these lists are maintained and reviewed by our team and are not applied automatically in the payment path, so no payment is declined by a Cleared-pay rule without a person involved. This section will be updated before any automatic enforcement goes live.

The second comes from the acquiring partner and the card issuer: authorisation, 3-D Secure authentication and any risk score they return. We record the result on the payment. A result marked for review goes to a queue where a member of our team accepts or rejects it. In test mode no real money moves and the risk score is simulated. Live processing starts only through a regulated acquiring partner, as the imprint explains.

If a payment of yours was declined and you believe the decision was wrong, you can ask for a human review. Contact the merchant first; the merchant can raise the case with us, or you can write to legal@cleared-pay.com with the merchant's name, the approximate time and the last four digits of the card. A person reviews the record and tells you the outcome.

Retention

We keep personal data for as long as the purpose requires and then for as long as the law requires. A statutory period limits erasure: we cannot delete a transaction record on request while the law obliges us to keep it. Where no period is set yet, the table says so.

RecordPeriodWhy
Onboarding and verification records: identity of the merchant, its directors and beneficial owners, documents, screening results, transaction monitoringFive years after the end of the merchant relationshipRecord keeping under Canada's Proceeds of Crime (Money Laundering) and Terrorist Financing Act
Payment, refund, dispute, settlement and payout recordsSix years from the end of the tax year they relate to, and never shorter than the anti-money-laundering period aboveCanadian tax and accounting law; defence of disputes and chargebacks
Audit logAppend-only. Kept for the life of the account and then for the statutory period that applies to the records it describesIt is the evidence of who did what; the application's database role cannot alter or delete it
API request logAppend-only. A purge routine exists but no retention period is set and the routine is not scheduled, so entries are kept for the life of the account until a period is fixed and published hereDebugging and dispute evidence for merchants
Portal and backoffice sessionsA portal session ends after 30 minutes without activity or 12 hours in total; a backoffice session after 15 minutes or 8 hours. Expired and revoked sessions are deleted 30 days laterSecurity
Email verification, password reset and recovery tokensSingle use; expire at their stated deadlineSecurity
Idempotency keys and the API responses stored with them24 hoursSafe retries
Rate-limit counters, including the one keyed on the IP address that submits the qualification formRemoved after 24 hours of inactivityAbuse prevention
Sandbox card tokensUsable for 15 minutes. Expired token rows are removed by a purge routine that is not yet scheduledTest mode only; no real card is involved
Checkout sessionsOpen for between 30 minutes and 7 days as set by the merchant (24 hours by default); then marked expired and kept as part of the transaction recordContract
Qualification-form leadsNo automatic deletion is configured. We keep a lead while the enquiry is open and delete it on requestFollow-up
Test-mode dataNo automatic deletion is configured; it stays until the merchant deletes it or the account is closedDevelopment and integration
Database backupsPoint-in-time history of seven daysRecovery

When a merchant account closes, data that is not subject to a statutory period is deleted or anonymised, and data that is subject to one is restricted to that purpose until the period ends.

Sub-processors and transfers

Cleared-pay runs in the European Economic Area. The current list is published on the Trust Center and is reproduced here as of the effective date.

Sub-processorServiceLocation of processing
Vercel Inc.Hosting of the application, API and hosted checkoutFrankfurt, Germany
Neon Inc.Managed PostgreSQL databaseFrankfurt, Germany
Cloudflare Inc.Object storage for onboarding documents and dispute evidenceEuropean Union jurisdiction
ResendTransactional emailRegion confirmed on countersignature of its agreement
Acquiring partnersAuthorisation, authentication and settlement of live paymentsAs named on the imprint, once agreements take effect

No analytics, advertising, error-monitoring or support-desk vendor receives personal data today. We will update this list and give merchants notice before a new sub-processor handles their data.

Kesheron Digital Ltd. is established in Canada, and our staff access these systems from Canada. Canada is covered by the European Commission's adequacy decision for recipients subject to PIPEDA. Where a sub-processor's own staff may access data from outside the EEA, the transfer relies on the mechanism in that sub-processor's data processing terms, which we will list on the Trust Center as each agreement is countersigned. A live payment is also shared with the acquiring partner and, through it, with the card schemes and the payer's issuer, wherever the card was issued.

Security

The security statement describes our controls in detail: encryption in transit with HTTP Strict Transport Security, Argon2id password hashing, mandatory two-factor authentication, session expiry on inactivity, row-level security isolating each merchant's data, AES-256-GCM encryption of bank account numbers, two-factor secrets and webhook signing secrets, tokenisation of card numbers, an append-only audit log, peppered hashes for API keys, and a strict content security policy on the hosted checkout. A third-party penetration test is scheduled and not yet performed, and our PCI DSS attestation is pending; both facts stay on the security statement until they change.

If a breach of security affects personal data, we notify the merchant without undue delay so that it can meet its own obligations, notify the supervisory authority within 72 hours where the GDPR requires it, and notify the Office of the Privacy Commissioner of Canada, the Alberta Commissioner and affected individuals where PIPEDA or PIPA requires it.

Your rights

Under the GDPR you may ask for access to your personal data, for rectification, for erasure, for restriction of processing, and for a portable copy of data you gave us, and you may object to processing based on legitimate interests. You may withdraw consent at any time where consent is the basis, without affecting processing that took place before. Under PIPEDA and PIPA you may ask what personal information we hold about you, how it is used and to whom it has been disclosed, and ask for inaccurate information to be corrected.

To exercise a right, write to legal@cleared-pay.com from the email address on your account, or by post to the registered office. We may ask for enough information to confirm who you are, and no more. We answer within one month under the GDPR, extendable by two further months for a complex request, and within 30 days under PIPEDA, extendable where the Act allows; we tell you if we need the extension. There is no fee unless a request is manifestly unfounded or excessive.

If you are a payer, the merchant you paid is the controller of most of your data. Send your request to the merchant; if it reaches us instead, we forward it to the merchant and help it respond. Where we hold your data as controller for anti-money-laundering or fraud purposes, we answer directly, subject to the retention periods above and to legal limits on disclosing suspicious-transaction reporting.

Merchant users can see and end their active sessions, change their password and manage two-factor authentication in the portal without writing to us.

Complaining to a supervisory authority

You can complain to us first, and we would like the chance to put things right. You also have the right to complain to a supervisory authority at any time.

  • In Canada: the Office of the Privacy Commissioner of Canada for matters under PIPEDA, and the Office of the Information and Privacy Commissioner of Alberta for matters under PIPA.
  • In the European Economic Area: the supervisory authority of the member state where you live, where you work, or where the alleged infringement took place. The European Data Protection Board publishes the list of national authorities.

Cookies

The site sets cookies only to keep you signed in to the portal or backoffice and to remember which mode the portal is in. No analytics or advertising cookie is set. Your consent choice is stored in your browser's local storage, not in a cookie. The cookie policy lists what this site sets, with each cookie's name, purpose and lifetime.

Changes

We change this notice when our processing changes, when a sub-processor is added or removed, when the EU representative and data protection contact are appointed, and when a retention period listed as unset is fixed. The version number and effective date at the top identify the text in force. For a change that reduces your rights or adds a purpose, merchant account holders get at least 30 days' notice by email. Earlier versions are available on request.