Security and trust

This page describes security practices relevant to users and integrators. It is not a guarantee of absolute security, regulatory approval, insurance coverage, or uninterrupted availability.

Custodial model

Tempest Touch Wallet is a custodial service. Platform-managed wallet operations and key material are handled server-side according to the implementation and operational controls. Users must protect account credentials and review Terms and Privacy.

Merchant integration controls

Keep TEMPEST_SECRET_KEY and webhook secrets on trusted backend servers only.
Use Idempotency-Key for charge creation retries.
Verify Tempest-Signature against the raw webhook body before parsing/fulfilling.
Use webhook event IDs for idempotent processing.
Fulfill only after verified paid events or server-side charge retrieval; never trust browser redirects alone.

Operational controls

HTTPS/TLS in transit, security headers, and rate-limited/proxied service routes where implemented.
Role-based admin flows and audit-oriented operational functions in the platform codebase.
Secrets should be managed through environment/secret managers; never committed to source control.

Independent audits, certifications, bug bounty scope, and insurance details should be published here only when formally established and approved.

Reporting

See /.well-known/security.txt for reporting metadata. Send reports to support@tempesttouchwallet.com with reproduction details and impact. Do not include secrets or attempt to access other users’ data.