Privacy policy
Last updated: . This page explains what information easyway stores when you use the website, the dashboard, the hosted checkout or the API, what we use it for, and what we never collect.
Who this covers
Merchants: people and businesses with an easyway account. Payers: customers of a merchant who open an easyway checkout page or payment link. Visitors: anyone reading the public website.
For payer data, the merchant decides what is collected and why, and easyway handles it on the merchant's behalf to provide the service. If you are a payer with a question about your order or your data, the merchant you paid is the first point of contact.
What we never collect
Private keys, seed phrases and wallet passwords. easyway is non-custodial: it does not hold funds and has no way to move them, so it has no use for a secret, and input that looks like one is refused. We also do not collect card numbers or bank account details; plan fees are paid in cryptocurrency.
What we store
| Data | Whose | Why |
|---|---|---|
| Sign-in email, password hash, and your Google account id if you sign in with Google | Merchant | To create and secure your account and to send account notices |
| Business name, website, support email | Merchant | Shown to payers on your checkout pages; used to contact you |
| Receiving wallet addresses and extended public keys | Merchant | To show payers where to pay and to detect payments. An extended public key reveals all addresses of that wallet account |
| Two-factor authentication secret | Merchant | To verify the codes from your authenticator app |
| API keys (as hashes), webhook URLs and signing secrets, IP allowlists | Merchant | To authenticate your servers and deliver events to them |
| Invoices, payment links and their history: amounts, order ids, descriptions, metadata you attach | Merchant | To provide the service and your records |
| Plan orders and plan payment records | Merchant | Billing |
| Activity log: sensitive actions and each sign-in, with time, IP address and browser user agent | Merchant | Security, and so you can review what happened in your account |
| Support tickets you open in the dashboard, and our replies | Merchant | To answer you and keep the conversation in one place |
| Whether you have unsubscribed from news and offers | Merchant | So we stop sending them |
| Payer email address, only if the merchant sends it with an invoice or the payer enters it on a payment link | Payer | The merchant's records and support; delivery of a purchased item on product links |
| Name and message a payer chooses to enter on a donation link | Payer | Shown to the merchant, and on the merchant's on-screen alert widget if the merchant uses one |
| On-chain details of a payment: transaction id, sending address, receiving address, amount, memo, time | Payer / public | To match the transfer to an invoice. This information is public on the blockchain |
| Webhook delivery log: the payloads sent to the merchant's server, status codes and errors | Merchant | Retries and troubleshooting |
| Emails you send to support | Anyone | To answer you |
Cookies and browser storage
The public website sets no advertising or analytics cookies and loads no third-party trackers. We use only what the product needs to work:
| Item | Purpose |
|---|---|
| Language preference cookie (NEXT_LOCALE) | Remembers the language you picked. Set only when you use the language switcher. Lasts one year |
| Session token | Keeps you signed in to the dashboard after you log in |
| Short-lived sign-in cookie | Protects the Google sign-in redirect against forgery. Lasts about ten minutes |
| Campaign tag cookie (ew_utm) | Set only when you arrive through a tagged link (utm_source) from one of our social accounts. Holds the network and campaign name, nothing about you, so a sign-up can be attributed to that link. Visits are counted once per browser session. Lasts 30 days |
| Local settings in the dashboard | Remembers small interface choices, such as a hidden checklist, in your browser only |
Server logs
Like any web service, our servers process the IP address and user agent of each request in order to answer it, apply rate limits and investigate abuse or faults. API keys with an IP allowlist are checked against the request's IP address.
How we use data
To run the service you asked for: creating invoices, showing checkout pages, detecting and matching payments, sending webhooks and emails. To keep accounts secure, including security emails when a wallet or a sensitive setting changes. To bill plans. To answer support requests. To send merchants occasional news and offers by email; every such email has an unsubscribe link, and account emails (sign-in codes, payment and security notices) are not affected by it. To prevent abuse and meet legal obligations. We do not sell personal data and do not use it for advertising.
Who receives data
The merchant sees everything about its own invoices and payments, including a payer email address where one was given. The merchant's server receives webhook events containing invoice and transaction details. Service providers that we need to operate (hosting, email delivery) process data on our instructions. Blockchain data providers and public nodes are queried about wallet addresses and transactions, which are public information; these queries carry addresses, not names or emails. Exchange-rate sources are asked for prices only. Google is involved only if you choose to sign in with Google. We may also disclose information where the law requires it.
Blockchains are public
Payments made through easyway are ordinary blockchain transactions. The sending address, receiving address, amount and time are visible to anyone and cannot be edited or deleted by us, by the merchant or by the payer. Because a merchant may use one receiving address for many invoices, payments to that merchant can be seen together on a block explorer.
How long we keep it
Account data is kept while the account is open. Invoices, payment records and the activity log are kept for as long as the account exists, because merchants rely on them for accounting, and afterwards for as long as the law requires or as needed to resolve disputes. When an account is closed we delete or anonymise its personal data once those periods have passed. Data on a blockchain is permanent and outside our control.
How it is protected
Passwords and API keys are stored as hashes. Webhook signing secrets and two-factor secrets are stored encrypted. Access to a merchant's data requires that merchant's session or API key, and test and live data are kept apart. More detail is on the security page. No system is perfectly secure; the non-custodial design means that a breach of easyway could expose the data listed above but could not move funds from a merchant's wallet.
Your choices and rights
Merchants can view and change their business details, wallets, keys and webhooks in the dashboard, export their payments as CSV, and ask us to close the account. Depending on where you live, you may have legal rights to access, correct, delete or receive a copy of your personal data, or to object to its use. To use them, email support@easyway.cash from the address the request concerns. Payers should contact the merchant first; we will help the merchant respond.
Children
The service is for businesses and is not directed at children. We do not knowingly collect data from children.
Changes
We will update this page when what we collect or how we use it changes, and change the date at the top. Significant changes are also announced to account owners by email or in the dashboard.
Contact
Privacy questions and requests: support@easyway.cash. See also the terms of service.