The fine print
Privacy Policy
What we collect, why we need it, and what we never do with it. Short version: we store what it takes to run a payment service, and nothing for advertising. The rules of use live in our Terms and Conditions.
Last updated: September 10, 2026
1. Who we are
SelfSettle (selfsettle.site) is a non-custodial stablecoin payment service for merchants. This policy explains what personal data we collect and why.
For any privacy question or request — access, correction, deletion, anything below — write to sales@selfsettle.money. It is our single inbox for sales, support, and all legal and privacy matters.
2. Who this covers
This policy covers three groups of people:
- Merchant account users — anyone who registers or logs in to the dashboard.
- Systems acting on a merchant's behalf — API activity performed with the merchant's keys.
- Checkout customers — people paying a merchant through a hosted checkout page.
The service is not directed at persons under 18, and we do not knowingly collect their data. If you believe a minor has provided us personal data, let us know and we will delete it.
3. Data we collect
We collect exactly the following — nothing more, nothing invented:
- Account data: merchant name, user email, and password — stored only as an argon2 hash, never in plain text.
- Branding: logo URL (https) and brand color, used to render your checkout pages.
- API keys: key name, public prefix, key hash, scopes, chain network, and last-used timestamps. The full key is shown once at creation and never stored.
- Wallets: network, address, normalized address, and an optional label.
- Payment records: asset, amount, external order id, expiry, status, expected sender, detected transaction id, and received amount. Order details you attach are displayed on the public checkout page; metadata stays merchant-private.
- Withdrawal requests: destination address, amount, and metadata — a tracking feature processed manually by the merchant.
- On-chain observations read from public blockchains: transaction ids, sender and recipient addresses, amounts, and block information.
- Webhook endpoints and delivery logs: endpoint URL, encrypted secret, and the delivery log (payload, status, errors).
- Security and audit logs: audit events (actor, action, target, time), idempotency records (key and request hash), and ephemeral in-memory IP rate-limit counters.
- One strictly-necessary session cookie: an httpOnly cookie holding the dashboard's HMAC-signed session token. There are no analytics or tracking cookies and no third-party trackers in the app.
4. How we use it
We use this data only to run and protect the service:
- Operate merchant accounts and authenticate dashboard sessions.
- Verify payments on-chain and report their status.
- Deliver webhooks to merchant endpoints.
- Secure the service — rate limiting, audit trails, and abuse prevention.
- Respond to support and legal requests.
We do no automated profiling, we sell no data, and we maintain no marketing lists. If you email us, we use your email to reply — nothing else.
5. Legal bases
Where the GDPR or a similar law applies, we process personal data on these bases:
- Performance of a contract — running accounts and verifying the payments you ask us to verify.
- Legitimate interest — keeping the service secure (rate limiting, audit logs, abuse prevention).
- Legal obligation — keeping records where the law requires it, such as for accounting or responding to lawful authority requests.
6. On-chain data
Anything written to a public blockchain is public and effectively permanent. We read transaction ids, addresses, amounts, and block information from public networks to verify payments — and so can anyone else.
We cannot erase or correct data that lives on a blockchain. Merchants: do not put your customers' personal data on public chains beyond what a transfer itself requires.
7. Who we share it with
- Infrastructure and hosting providers — the services strictly needed to run SelfSettle (hosting, databases). They process data only on our instructions.
- The merchant — merchants receive their own customers' payment details and decide what goes into order and metadata fields, so for that content the merchant is the controller.
- Public blockchains — transfers you make are visible to the whole network by design (see the previous section).
- Authorities — where legally required, for example under a valid court order.
We never sell personal data. There is no “data business” here.
8. Cookies
One cookie, and one only: the strictly-necessary httpOnly session cookie that keeps you logged in to the dashboard. No tracking cookies, no third-party analytics, no consent banner needed because there is nothing to consent to.
9. Retention
We keep account data while the account is active. Payment, webhook, and audit records are kept for a reasonable period for accounting and dispute resolution. Ephemeral rate-limit counters live only in memory and disappear on their own.
Ask us to delete your data sooner and we will — wherever no legal duty requires us to keep it. Note the exception in section 6: public blockchain data cannot be deleted by anyone.
10. Your rights
Depending on where you live, you may have the rights of access, rectification, erasure, restriction, data portability, and objection to processing.
To exercise any of them, email sales@selfsettle.money. We will respond within the reasonable period required by applicable law. If you are a checkout customer asking about data a merchant controls (such as order contents), we may point you to the merchant — they decide what goes in those fields.
11. Security measures
- Passwords hashed with argon2 — never stored in plain text.
- HMAC-signed dashboard sessions and HMAC-SHA256-signed webhooks.
- Encrypted webhook secrets.
- HTTPS everywhere, plus rate limiting and audit logging.
And a reminder that protects you most: we never ask for seed phrases or private keys, and we never store them. Anyone asking for them in our name is a scammer.
12. International transfers
Our infrastructure may sit outside your country, so your data may travel across borders. Where the law requires safeguards for such transfers, we apply them.
13. Changes to this policy
If this policy changes, we will post the updated version here with a new “Last updated” date. Material changes will additionally be announced by email or in the product.
14. Contact
One inbox for everything privacy-related: sales@selfsettle.money. Tell us what you need — access, correction, deletion, or just a question — and a human will answer.