Privacy Policy
Version {{ version }} · in force from {{ effective }}
Two very different people read this page, and they need opposite answers. Start with the one that describes you.
1. Who we are, and which of us holds your data
Paymint (we, us) lets businesses accept card and bank payments. We are the controller of the personal data belonging to the businesses that use us — their account, their identity, their trading history.
We are not the controller of data belonging to the customers of those businesses. When you buy something through a Paymint payment link, the business you bought from decides what to collect and why. We hold that data on their behalf, under our agreement with them. That distinction decides who you ask when you want something changed or deleted, so it is worth reading section 2 before you write to us.
Payments are processed by Stripe, which is a separate controller of the data it receives. Section 4.
2. If you bought something
You paid a business. That business is who your data is about and who decides what happens to it. We are the payment system it uses.
What we hold about you
| What | Why we have it |
|---|---|
| Your email address, and your name if it is given | You enter your email when you pay. We use it to send your receipt and the other emails listed below, so the business can see who bought, and so a returning customer is recognised rather than duplicated |
| What you bought, the amount, the currency, and when | It is the record of the sale |
| Card brand, the last four digits, issuing country, and whether it is debit or credit | To defend a chargeback, and to show you which card is on file |
| Whether the security code and billing address matched, and your billing address | A card issuer deciding a chargeback weighs exactly these; without them a disputed sale cannot be defended |
| A risk score produced by Stripe's fraud checks | Fraud prevention |
| For a subscription: its status, amount, interval, and renewal date | To bill you correctly and to tell you when a payment fails |
| Your IP address, when you open a payment page or a card-update page | Rate limiting. It is held in a counter in memory for 15 minutes, is never written to disk, and is not attached to your payment |
| Briefly, a copy of the message Stripe sends us about your payment | So the payment can still be recorded if something fails on our side. It is stripped of anything we do not need before it is written, and discarded once the payment is recorded |
We never receive or store your full card number, and we never receive your security code. Both go from your browser to Stripe directly and do not pass through Paymint. The four digits we keep are the ones already printed on your receipt. We do not keep your card’s expiry date, and we do not keep the fingerprint Stripe uses to recognise the same card across different businesses — both are removed before anything is written to disk.
Who to ask about your data
Ask the business you bought from. They hold the relationship with you, they know what they sold you, and under data protection law they are the ones who owe you an answer.
If you cannot reach them, or they will not respond, write to support@paymint.gg and we will help — but expect us to involve the business rather than act over their head, and expect us to keep the record of the payment itself. A completed payment is a financial record, and we explain in section 8 why we cannot simply erase one.
Emails you may get from us
Only emails about a payment you made, sent in the name of the business you paid:
- a receipt when you pay;
- if the business refunds you, a note saying so;
- if you subscribed: a receipt for each renewal; a link to update your card if a payment fails, or to confirm a payment your bank asks about; and a note when the subscription is cancelled or ends.
Replying to any of them reaches the business, not us. We do not give Stripe an email address to write to you at, so emails about your payment come from us, in the business’s name, and not from Stripe.
That is a service message about a payment you already agreed to, not marketing. We send you no promotional email, and we do not give your address to anyone who will.
3. If you sell with Paymint
Your account
When you sign up we collect your name, your email address, and a password. We store the password as a scrypt hash with a per-account salt; we cannot read it and we cannot recover it for you.
We record the version of the terms you accepted, the moment you accepted them, and the IP address you accepted them from. That last one exists so we can show what you agreed to if it is ever disputed.
Your application
Before an account exists, you apply. We keep everything the application form asks: your email address, business name, website, country, what you sell and how it is delivered, your expected volume and typical order, where you take payments today, your past chargebacks, and your refund policy. We also keep the IP address the application came from, for 90 days, to spot the same applicant applying repeatedly under different names.
The application itself is kept after it is decided, including when it is declined. That is deliberate: someone declined who reapplies under a new name is exactly what the review exists to catch. Section 8.
Those are the only two places we keep an IP address beyond 15 minutes, apart from a record of Paymint staff signing in to the admin tools.
Your business and your identity
To take payments you must be verified. That process runs inside Stripe's own onboarding, and the identity documents, the government ID, the bank details and the ownership information you enter there go to Stripe, not to us. We do not receive, see or store your ID documents or your bank account number.
What we do hold is what Stripe tells us about the outcome: your business name, your country and currency, whether you are cleared to take payments and to be paid out, what Stripe still needs from you, and whether a bank account is attached.
Your trading records
We hold every payment you take, every refund, every dispute, every payout, and the fees we charged — including the customer details listed in section 2, because they are attached to the sale. We also hold your products, prices, payment links and subscribers.
We hold the reserve assessment we make about your account: the tier, the rate applied, and any note explaining it. Section 5 of the terms explains what that is and why it exists.
What you owe your own customers
You are the controller of your customers' personal data. This policy does not discharge that. You need your own privacy notice, telling your customers what you collect and why, and you are the one who must answer them when they ask. We are your processor for that data and act on your instructions.
4. Stripe
When you provide personal data in connection with Paymint, Stripe receives that personal data and processes it in accordance with Stripe's Privacy Policy.
Stripe is an independent controller of what it receives, not merely our subcontractor. It uses that data to run the payment, to meet its own legal obligations around identity and money laundering, and to detect fraud across its network. We cannot instruct it otherwise.
Our payment processor can obtain information from credit agencies to verify your identity. That information will be used for the purposes described in their Privacy Policy.
Card payments are acquired by Stripe's financial partners, identified in the Stripe acquirer disclosure.
5. The other companies involved
There are four, and that is the whole list.
| Who | What reaches them |
|---|---|
| Stripe Payments, verification, payouts | Everything in section 4 |
| Resend Sends our email | The recipient's address and the contents of the message. Nothing else |
| Railway Runs our servers | They host the machine the data sits on. They do not use it |
| Takeback.CC Answers chargebacks for merchants. A separate company under common ownership with Paymint, so a related party | For each merchant: the business name, the contact email and the Stripe account identifier. Through read-only access Stripe grants to it, the disputes on that merchant’s account and the payments they concern — which includes the buyer details listed in section 2, because answering a chargeback means showing the card issuer who bought what. It cannot move money or issue refunds |
There is one more call worth describing precisely, because described vaguely it sounds worse than it is. When you choose a password, we check it against Have I Been Pwned's list of passwords exposed in known breaches. Your password is not sent. We hash it, send the first five characters of that hash, receive back every leaked hash starting with those five characters, and do the comparison here. The service cannot tell which password was being checked, or by whom.
6. What we do not do
This section is short because the list is short, and everything on it is verifiable by viewing the source of any page on this site.
- No analytics. No Google Analytics, no Plausible, no Segment, nothing.
- No advertising pixels and no advertising of any kind.
- No third-party code on our own pages. This page, the marketing site and the sign-in pages load no script from anyone else’s server. Libraries we would normally pull from a CDN, we host ourselves.
- Two exceptions, and they are real ones. The payment page and the card-update page load Stripe’s script directly from Stripe. It has to be Stripe’s own code that touches your card number — that is what keeps the number away from us — but it means that on those two pages Stripe sees your browser, sets its own cookies, and collects device signals it uses to detect fraud. Section 7. And the merchant dashboard loads Stripe’s Connect script, because verification and bank details are entered into Stripe’s own form inside it; when a returning merchant changes those details, Stripe may ask them to confirm it is them in a window of its own.
- We do not sell or share your personal information as those terms are defined under the California Consumer Privacy Act, and we have not in the twelve months before this policy took effect. There is no opt-out to offer you because there is nothing to opt out of.
- No profiling that produces a legal or similarly significant effect about you automatically. Our reserve policy affects how fast a merchant can withdraw, and it is described openly in the terms.
7. Cookies
Paymint sets one cookie, named __Host-pm_session. It holds a random session identifier and nothing else — no name, no email, nothing about you is encoded in it. It is marked HttpOnly and SameSite so it cannot be read by scripts or sent from another site, it lasts up to 30 days (12 hours for Paymint staff), and signing out deletes it. It is strictly necessary to keep you signed in.
Stripe sets its own cookies on the payment page and the card-update page, because Stripe’s script runs there. We do not control them and we cannot read them. Stripe uses them to run the payment and to detect fraud; what it does with them is governed by its privacy policy, and its cookie policy lists them.
None of these are advertising or analytics cookies, and there is nothing here that follows you to another site. If we ever add a cookie that is not strictly necessary, we will ask first.
8. How long we keep things
Some of this deletes itself. Most of it does not, and we would rather tell you that plainly than imply a tidiness we do not practise.
| What | How long |
|---|---|
| Sign-in sessions | 30 days (12 hours for Paymint staff), then deleted automatically |
| Sign-in links, sent only when an account has had many failed sign-ins | 15 minutes, and deleted the moment one is used |
| Email verification links | 24 hours, and deleted the moment one is used |
| Password reset links | 30 minutes, and deleted the moment one is used |
| Unfinished signups | 24 hours, then deleted automatically |
| Rate-limiting counters, which include an email address or an IP address | 15 minutes, held in memory and never written to disk |
| The IP address an application came from | 90 days, then deleted automatically |
| Applications, including declined ones | Kept indefinitely, for the reason in section 3 |
| A record of what Paymint staff did in the admin tools — approvals, account freezes and the like — and of statement descriptor changes | Kept indefinitely. It is how we can answer “who decided this, and when” |
| Daily copies of our database, kept in case of a failure | The last seven days; older copies are deleted automatically |
| Copies of the messages Stripe sends us about payments | Discarded the moment the payment is recorded, which is normally the same second |
| Accounts, payments, refunds, disputes, payouts, subscribers and buyers | Kept indefinitely |
The last row deserves an explanation rather than a footnote. Stripe holds the authoritative ledger; what we keep is a readable copy of it, and it has to stay reconstructable from Stripe for the product to work at all. Financial records also carry retention obligations of their own, and a chargeback can arrive up to 540 days after a sale — if we had deleted the evidence, the merchant would simply lose.
Being straight about the gap: there is currently no button that closes your account and erases your records, and we are not going to pretend otherwise. If you want your data deleted, write to support@paymint.gg. We will delete what we are able to delete and tell you specifically what we are keeping and why, rather than refusing in general terms.
9. Why we are allowed to hold it
If you are in the UK or the European Economic Area, the law requires us to name a lawful basis for each purpose. Ours are:
| Purpose | Basis |
|---|---|
| Running your account and processing payments | Performance of our contract with you |
| Identity and anti-money-laundering checks | Legal obligation, ours and Stripe's |
| Keeping financial records | Legal obligation |
| Fraud prevention, chargeback defence and the reserve policy | Our legitimate interest in not being defrauded, and in protecting honest merchants from bearing the cost of dishonest ones |
| Service emails about a payment or a subscription | Performance of our contract |
| Security, including the breached-password check | Our legitimate interest in keeping accounts from being taken over |
You must give us the account and verification data described in section 3; without it we cannot open an account or let you take payments.
10. Your rights
Depending on where you live, you can ask us to give you a copy of your data, correct it, delete it, restrict or object to how we use it, or send it to someone else in a portable form. If you are in California you can also ask what we have collected, where it came from, and who we disclosed it to.
Write to support@paymint.gg. We will answer within 30 days, and we will not charge you or treat you differently for asking.
Two honest qualifications. If you are a customer of a merchant, we will generally route your request to that merchant, because they are the controller — section 2. And a request to delete does not reach the financial records described in section 8.
If you think we have handled your data badly, tell us and we will try to fix it. You are also entitled to complain to your data protection authority — in the UK the Information Commissioner's Office, and in the EEA your national supervisory authority — without asking us first.
11. Where your data is
Our servers, and the disk your records sit on, are in the eastern United States. Stripe and Resend operate internationally. So if you are in the UK or the EEA, your data is transferred to the United States, and that transfer relies on the standard contractual clauses those companies publish or on an adequacy decision covering the destination.
We do not currently accept merchants established in the EEA or the United Kingdom. We have no establishment in either, and offering the service there would require us to appoint a representative in each under Article 27 and name them here. We have not done that, so we do not offer it — rather than offer it and leave the requirement unmet. The countries we do accept are listed on the application form.
12. Children
Paymint is for businesses, and you must be at least 18 to hold an account. We do not knowingly collect data from children, and we do not offer anything directed at them. If you believe a child's data has reached us through a payment, tell us and we will remove what we can.
13. Security
Passwords are stored as scrypt hashes and are never recoverable. If an account sees a burst of failed sign-ins, the right password alone stops being enough and a one-time link is emailed to the account instead. Session and reset tokens are stored only as digests, so a copy of our database contains nothing that can be used to sign in as you. Payment card numbers never reach our servers. Traffic is encrypted in transit.
One thing worth saying out loud, because a security section that only lists reassurances is not much use. Paymint staff on a named allowlist can see platform-wide reporting, and that reporting includes the names and email addresses of merchants’ customers. It exists so we can investigate fraud and answer support requests. It is restricted to that allowlist and staff actions there are logged, but it is not nothing, and you should know it exists rather than discover it.
What we will not claim: that we are unbreachable, or that any measure here is “industry standard”. If we ever suffer a breach affecting your data, we will tell you and the relevant regulator within the time the law allows.
14. Changes
If we change this policy in a way that materially affects you, we will email the address on your account at least 30 days before it takes effect. Every version is numbered and dated at the top of this page.
15. Contact
Privacy questions, and any request under section 10: support@paymint.gg.
Paymint is operated by Paymint LLC, a limited liability company registered in Delaware, United States, at 1201 N Market St, Wilmington, DE 19801, United States.
Paymint LLC is the data controller for the merchant data described in section 3. For buyer data we act on the merchant’s instructions, as section 1 explains.
Version {{ version }}. Earlier versions are available on request. See also the terms of service.