Skip to content
Plinth
Create account

Legal

Privacy policy

What Plinth collects, why, and who else sees it. This is a draft.

Draft: not yet reviewed by legal counsel

Last updated 2026-10-11. Written in plain English from what the product does today. It must be reviewed by qualified counsel and completed by the operator before it is relied on.

1. Who is responsible

[Operator name], of [registered address], decides why and how the data below is used. Contact: [privacy contact].

2. What we process

Merchant account data

  • Business name and sign-in email address.
  • A password, stored only as a scrypt hash. API keys and session tokens are stored only as SHA-256 hashes.
  • Team members you add: their email addresses and roles.
  • Wallet addresses you give us as vault owners or payout destinations.

Payment and invoice data

  • Amounts, order references, descriptions, and any metadata you attach to a payment (up to 20 key and value pairs).
  • For invoices: the customer's name and email address, the memo and the line items you enter.
  • The optional customer email on a payment.
  • Blockchain facts about each payment: the paying address, transaction hashes, amounts and block data. This data is public on the blockchain.
  • Webhook endpoints (URLs), delivery attempts and response codes. Webhook signing secrets are encrypted at rest.

Technical data

  • The IP address of requests, used for rate limiting and recorded on security-relevant audit events such as sign-in and sign-up.
  • Audit events for sensitive actions, with secrets, tokens and signatures redacted.

We do not ask for a postal address, date of birth, identity documents or financial account details, and the service does not run identity or sanctions checks.

3. Why we use it

  • To run your account, detect and verify payments, move funds into your vault, and send you webhooks.
  • To keep the service secure, prevent abuse and investigate incidents.
  • To answer support requests you send us.

[Counsel to state the legal basis for each purpose.] We do not sell personal data, and we do not use it for advertising or profiling.

4. Cookies and similar technologies

The site sets only functional cookies, and only for signed-in merchants:

  • plinth_session keeps you signed in. It is HttpOnly, SameSite=Lax, secure in production, and lasts 7 days.
  • plinth_env remembers whether the dashboard is showing test or live data. It is HttpOnly, SameSite=Lax and lasts 30 days.

The code contains no analytics, advertising or tracking cookies and no third-party tracking scripts, so there is no consent banner. If that changes, this policy and the site will change first. Visitors who are not signed in receive no cookies from us.

5. Other parties who receive data

  • Font providers. Pages load the General Sans typeface from Fontshare and the JetBrains Mono typeface from Google Fonts. Your browser sends those providers its IP address and the usual request headers when it fetches them.
  • Blockchain networks and RPC providers. Transactions are public and permanent. Our servers query RPC providers for chain data, which can include your payment addresses.
  • Your wallet. If you pay with a connected wallet, your wallet software and its provider see the signing request. We receive the address and the signed authorization.
  • Hosting and infrastructure providers. [Operator to list providers for the application, database and logs.]
  • Webhook recipients. Payment data is sent to the endpoints you register.

6. Blockchain data cannot be erased

Anything written to a blockchain, such as a transfer from a customer's address to an invoice address, is public and cannot be altered or deleted by us or anyone else. We can delete or anonymise data in our own systems, subject to the next section.

7. How long we keep it

[Operator to define retention periods.] Today the system keeps payment records, ledger entries and audit events without an automatic deletion job. The session cookie lasts 7 days.

8. Your rights

Depending on where you live, you may have the right to access, correct, delete, export or object to the use of your personal data, and to complain to a data protection authority. Contact [privacy contact]. If you are a merchant's customer, ask the merchant first: they decide what to do with the data you gave them.

9. Security

Passwords, keys and secrets are hashed or encrypted as described above, the dashboard session is HttpOnly, and requests are rate limited. No system is perfectly secure, and the service is pre-audit. Report problems through the process on the security page.

10. Changes

We will update this page and its date when we change how we handle data.