Privacy notice

Who we are

payclose.app and the Payclose app at run.payclose.app are run by the Payclose team, who decide how the data below is used. For anything about your data, email hello@payclose.app.

This notice covers the app, this website with its free tools, and the waitlist this site ran before the app opened.

What the app stores

When your team uses Payclose at run.payclose.app, we store:

• Your account: your email address, your name if you add one, and the organizations you belong to with your role in each. Sign-in links and sessions are kept only as one-way hashes.
• Sign-up answers: if you answer the two optional questions when you create an organization, which networks your team pays on today and how it pays (a Safe, a regular wallet, an exchange, a payroll provider). We use them only to decide which networks to support next. Nobody in your organization sees them.
• Passkeys: the public key of each passkey you add, used to check your approvals. The private key never leaves your device.
• Your team: the same details for the people you invite, and who invited them.
• Recipients: the names of the people your company pays, their email addresses if you add them, their usual amounts, and their payout address on each network, with who proposed and who approved each address.
• Recipients who use the app: when an organization invites a recipient, they get a Payclose account with their email address, to see the payments made to them and to manage their payout addresses. We store each address they confirm or propose, with the signature from their wallet that proves they control it. If the organization turns receipts on, we email the recipient a receipt for each payment: the organization, the payout, the amount and token, the network and the transaction.
• Payouts: each payout’s lines (recipient, address, token, amount, invoice number, note), the versions sent for approval, the approvals (who approved, when, and the passkey signature) and the transactions: their hashes, the wallet address that proposed them, and how each transfer matched on-chain.
• Payout proofs: a member of an organization can download a proof file for an approved payout, so anyone can check it without trusting us. The file holds the payout’s lines, the approvers’ names and email addresses, their passkey signatures and, once the payout is paid, its transactions. The organization decides whom it shares the file with. Checking a file on payclose.app/verify happens in your browser: the file is not uploaded.
• Company wallets: the public addresses of the wallets you pay from, Safes or regular wallets. Never keys or seed phrases.
• Activity log: every change, who made it and when. The log refers to people, recipients and addresses by internal ids, not by name, email or address.
• Feedback you send from the app: your message, the page it was sent from and, if you leave them attached, technical details such as your browser and recent error codes. It is stored with your account and emailed to us.

Why the app uses it

Only to run Payclose for your team: signing you in, keeping your team and recipients, checking and comparing payouts, collecting approvals, preparing Safe transactions and checking them on-chain, and emailing you about this work (sign-in links, invitations, approval requests, payout updates, passkey changes, and for recipients, invitations to see their payments and payment receipts). The app sends no marketing email and has no advertising or analytics trackers.

Your company decides whom it adds as recipients and what it records about them. We use those details only to run its payouts.

To stop abuse, the sign-in page runs Cloudflare Turnstile, and we count sign-in links per email address, new accounts per IP address, and emails sent, per day. The counters keep a one-way hash of the email or IP address, never the address itself.

The app sets one cookie, which keeps you signed in for up to 30 days. Our own server log lines hold ids, transaction hashes and error types, never email addresses, wallet addresses or amounts. Cloudflare also keeps a log of the requests to the app, which can include your IP address, so we can find and fix errors.

This website

We use Google Analytics on payclose.app to see which pages and links bring visitors and which buttons they click, such as Get started. In the European Economic Area, the UK and Switzerland these tools only set cookies if you choose Allow in the banner; if you decline, Google receives limited signals without cookies.

When you make a choice in the banner, we store it for 180 days in one cookie, pc_consent, so we don’t ask again on every visit. You can change it at any time with “Cookie settings” at the bottom of the page.

No email address, company name or anything you put into the free tools reaches analytics. The tools run in your browser: the files and lists you check are never uploaded, and the page only counts how many rows and findings a check produced.

These tags run only on payclose.app. The app at run.payclose.app has none.

The waitlist

Before the app opened, this site had a waitlist form. The form is gone, but if you joined, we still hold what you sent:

• Your work email, and your company name if you added it.
• Your answers to the optional questions: team size, how many people you pay in crypto, how you pay today, what’s hardest, and what pricing would feel fair.
• How you reached the page: the ad or email campaign (UTM tags), the referring website and which version of the page you saw.
• Your approximate country, derived from your IP address by our hosting provider. We don’t store the IP address itself.

We use it only to email you about Payclose, for example to tell you the app is open, and to understand which problems matter most to teams like yours. We rely on the consent you gave by submitting the form. We don’t send newsletters, and we never sell or share your details for marketing.

Who processes it for us

• Cloudflare, Inc.: hosts this website and the app, stores app data and waitlist submissions in its D1 database, sends the app’s emails through its Email Service, and runs Turnstile on the app’s sign-in page.
• Safe Transaction Service, run by Safe: when you propose a payout, the transaction goes there, signed by the owner who proposed it, so your Safe’s other owners can confirm and execute it. It carries your Safe’s address, the recipients’ addresses and amounts, and the proposer’s wallet address. Anyone who knows a Safe’s address can see its queue, and executed transactions are public on the blockchain.
• Blockchain node (RPC) providers: our servers read public chain data through them, such as whether an address is a contract, who owns your Safe, and transaction receipts. The requests carry public addresses and transaction hashes only.
• Google LLC: ad measurement and analytics on this website only.
• Google Workspace: our email, and spreadsheets we may use to review waitlist submissions.

Some of these providers are based in the United States. Transfers rely on the EU Standard Contractual Clauses and the providers’ data processing terms.

How long we keep it

• App data: while your organization uses Payclose. If you ask us to delete it, we remove names, email addresses and payout addresses from your account, recipients and payout records within 30 days; the activity log keeps only internal ids. Database backups (Cloudflare D1 Time Travel) roll over within 30 days, so deleted data leaves them too.
• Feedback: while your organization uses Payclose, or until you ask us to delete it.
• Sign-in links expire after 15 minutes, invitations after 7 days and sessions after 30 days.
• Abuse counters: deleted within 7 days.
• Request logs of the app: kept by Cloudflare for 7 days.
• Waitlist submissions: no longer than 24 months after you submitted the form, or until you ask us to delete them.

Your rights

You can ask to see, correct or delete your details, or withdraw your consent, at any time by emailing hello@payclose.app. We’ll reply within 30 days. If you’re in the EU or UK, you can also complain to your local data protection authority.

If a company pays you through Payclose, that company decides what it records about you: ask it first, or write to us and we’ll help.