Draft for review.
This text describes how PayoutGuard handles data today. It has not yet been reviewed by a lawyer and will be replaced by the final version before launch.
Privacy
PayoutGuard verifies stablecoin payouts by reading public blockchain data. This page explains what we store about you and why.
What we collect
- Your account: email address, optional display name, and a password hash (never the password itself).
- Your organisation's data: the wallets you add (public addresses), the payout files you upload, and the verification results, dispositions and reports created from them.
- Security records: sign-in sessions with the IP address and browser they came from, and an audit log of changes with who made them and the IP address of the request.
- Billing: if you subscribe, Stripe processes your payment. We store your Stripe customer and subscription identifiers and the billing notifications Stripe sends us, which can include your billing name, email and address and your card's brand, last four digits and expiry. We never receive or store a full card number.
What we never collect
Private keys, seed phrases or signatures. PayoutGuard is read-only and cannot move funds.
Public blockchain data
Transfers, blocks and addresses we read from the blockchain are public. We store the ones relevant to your batches as evidence. We never reveal to one organisation that another organisation watches the same address.
Who else processes it
- Blockchain data providers receive the public addresses we query. They never receive your account details.
- The Safe Transaction Service receives the Safe transactions you ask us to inspect.
- Stripe processes payments for paid plans.
- Our email provider delivers the emails you ask for.
How we use it
To run verifications, send the emails you ask for (alerts, digests, invitations, account messages), bill paid plans, and keep the service secure. We do not sell your data and do not use it for advertising.
Cookies
We use a session cookie to keep you signed in and a security cookie that protects forms from cross-site requests. No advertising or tracking cookies.
Retention and deletion
Verification history is kept while your organisation exists, so results stay reproducible. When an owner deletes an organisation, members lose access at once. Its data is retained for 30 days; how and when it is then permanently deleted will be stated here before launch.
Contact
Questions about your data: the contact address will be published here with the final version of this page.



