Privacy policy
[Operator legal name] is responsible for the personal data described here. Contact: [privacy contact].
Data the service stores
- Account data: email address, a password hash, optional two factor enrolment and sign-in history.
- Project data: names, branding, webhook addresses, API key hashes and audit events.
- Payment data: references, amounts, currencies, status, an optional customer reference, an optional customer email and metadata that your application supplies.
- Provider data: provider credentials are sealed at rest and are never shown again. Provider payment identifiers are stored with attempts.
- Technical data: IP addresses and user agents in the audit log and in rate limiting, and request logs.
The service does not store card numbers. Card details go to the card provider.
Why
To run the service, secure it, keep an audit trail, prevent abuse and meet [legal obligations the operator must list].
Retention and deletion
The operator can purge old data on a schedule and can export or delete the personal data held about a customer reference or email on request. [Operator to state the retention periods in use.]
Sharing
Data goes to the providers a project connects and to the project's own webhook endpoints. [Operator to list any other processors and hosting locations.]
Your rights
[Operator to describe the rights that apply in its jurisdictions and how to use them.]