Privacy policy

Everything we hold about you falls into four groups.

• Your account. An email address, a hashed password, and the times you signed in. The email is how we invoice you and how we warn you before your paid time runs out; there is no way to run a prepaid subscription without one.
• Your store settings. A store name, your extended public key or receiving address, and your currency and webhook configuration. The key is public by construction — it can derive addresses and watch them, and it cannot spend.
• Invoice metadata. BTCPay records what it needs to tell you whether an invoice was paid: amount, currency, status, the derived address, timestamps, and any reference your own system attached. We can see this. It is the service working.
• Server logs. IP address, request path and user agent, kept briefly for debugging and abuse handling.

No passport, national ID, selfie, proof of address or company document. We do not run KYC on you, and we do not ask you to run it on your customers, because we are not in the payment path and have no basis to demand it.

No private keys and no seed phrases. Not encrypted, not in escrow, not in a backup. Nothing in the system has a field for one.

Nothing about your buyers. They do not have accounts with us. We never see their names, emails or addresses unless you choose to put such data in an invoice field yourself — which we would rather you did not.

Blockchains are public ledgers, and that is not something a privacy policy can change. Every payment to an address derived from your extended public key is visible to anyone, permanently, along with its amount and timing.

Anyone who holds your extended public key can see the balance and full history of every address it derives. That is exactly why it should be treated as sensitive even though it cannot spend, and why the system asks for it once rather than passing it around.

We hold your account and store settings because we cannot perform the contract you bought without them. We hold logs on the basis of our legitimate interest in keeping the service secure and working. We send service email — invoices, expiry warnings, security notices — because it is part of the service, not marketing; if we ever send marketing, it will be because you opted in and it will have an unsubscribe link.

As few parties as we can manage, and none of them for advertising.

• Our hosting provider, which operates the physical server our software runs on.
• Our email provider, which receives your email address in order to deliver invoices and notices to it.
• Blockchain nodes. We run our own Bitcoin node rather than asking a third-party API what happened, specifically so that your addresses are not disclosed to one. For chains where we use an external node, it sees the addresses being watched and nothing about you.

We do not sell data, we do not share it with advertisers, and we do not run third-party analytics or advertising scripts on this site.

The public site sets no cookies at all, which is why you were not asked to dismiss a banner. The merchant panel sets one session cookie, strictly necessary to keep you signed in. That is the entire list.

Account and billing records are kept while your account exists and for as long afterwards as we are required to retain financial records. Server logs are kept for a short period and then discarded. Invoice metadata lives in your BTCPay store for as long as the store does.

Deleting your account removes your account record and store settings. It cannot remove anything from a blockchain, and it does not erase records we must keep by law.

You can ask us for a copy of what we hold about you, ask us to correct it, ask us to delete it, or object to a particular use. Write to support@ownrails.com and we will answer within 30 days. You can export your own invoice history from the panel at any time without asking.

Depending on where you live you may also have the right to complain to a data protection authority. Nothing here is intended to discourage that.

Changes are posted here with a new effective date. If a change materially affects how we handle your data, we will email you before it takes effect rather than relying on you to re-read this page.

This policy is published by the individual operating this service in Iraq. See also our terms of service.