Privacy Policy

Who this covers

It covers merchant staff who sign in, businesses that apply for access, workspace agents who process withdrawals, and customers who open hosted checkout and submit a transfer reference or withdrawal destination.

Information we collect

• Account data from Google sign-in: name, email, and profile image, plus the session we create for dashboard access.
• Business application and profile data: legal or display name, phone, country, product category, website, and related support details.
• Receiving-account details you configure (bank or wallet rail, account identifiers, holder name). Identifiers are stored for routing and verification, shown masked in the product, and are not meant to be logged in full.
• Order and verification data: amounts, currency, payment method, assigned receiver version, submitted transaction IDs or references, bank-verification outcomes, timestamps, and duplicate-protection hashes.
• Withdrawal destination details the customer confirms at checkout, and agent-submitted transfer references.
• Technical and security logs: request IDs, coarse IP and user-agent data, webhook delivery attempts, and audit events for operational actions.

How we use it

We use this information to authenticate you, review merchant access, route checkout to an eligible receiving account, verify transfers, prevent the same real-world transaction from being reused, notify your backend with signed webhooks, operate dashboards and reports, and keep the platform secure.

PeerPay does not build a customer-money ledger or wallet balance from this data. Status, evidence, and notification state are operational facts, not custody of funds.

How we share it

• Banks and mobile-wallet providers, to confirm that a submitted transaction ID or reference matches the assigned receiver, amount, currency, and timing rules.
• Google, only as needed to complete sign-in.
• Your own systems, through API responses and webhooks you configure.
• Infrastructure providers that host the application, database, and object storage under our direction.
• Authorities or counterparties when the law requires it, or when we must respond to a clear abuse or fraud investigation.

We do not sell personal information. Platform operators can inspect cross-tenant operational data with masking by default; revealing sensitive identifiers is an audited action.

Cookies and sessions

The merchant dashboard uses HttpOnly session cookies after Google sign-in so we can keep you logged in. Checkout uses a public token in the URL rather than a customer login. We do not run a marketing pixel or advertising cookie program on these pages.

Retention

Account, application, order, verification, webhook, and audit records are kept for as long as needed to operate the service, handle disputes, and meet accounting or legal requirements. Secrets such as API key material are hashed or shown once at creation. Evidence and identifiers may be redacted in exports.

Security

We use HTTPS, hashed API keys, encrypted or masked account identifiers where the product requires it, signed webhooks, and role separation between merchant sessions and platform operators. No method is perfect; you still need to protect keys, webhook secrets, and staff access.

Your choices

Merchants can update business profile details in the dashboard and revoke API keys. To correct account email or close access tied to Google, start from your Google account and your PeerPay dashboard profile. Customers should contact the merchant they paid; PeerPay does not operate those customer wallets.

Changes

If our practices change, we will update this page and the “Last updated” date. Continued use means you accept the revised policy.

Contact

Privacy questions can be sent through the merchant dashboard or the public site at peerpayment.org. Related reading: Terms of Service.