Paiflow

/ PRIVACY

Privacy.

LAST UPDATED: 2026-09-17

What we store

What we do not store

Third parties

Stellar Horizon and Soroban RPC see the public network traffic required to read or submit your transactions. Optionally, error traces are sent to Sentry; this is off unless the operator configures SENTRY_DSN.

Product analytics are sent to PostHog (US) when enabled. They help us understand product use and errors. Approved navigation and builder controls record stable action identifiers, without their visible text, labels, form contents or account and credential panels. Errors use categories and safe diagnostic locations rather than unrestricted messages. Signed-in activity uses an internal account ID, never your username or email. Public signing wallet addresses and transaction hashes are included deliberately for transaction traceability; recipient addresses, private keys, signed transaction payloads and graph contents are excluded. Anonymous signing activity has no account profile. API caller IDs and account IDs remain separate from the wallet that signs. Wallet connections and submitted transaction outcomes are also stored in our database; unsuccessful analytics delivery may be retried. New analytics disable geographic enrichment and do not collect country, city or coordinates. Historical records remain under their earlier collection policy. We do not record your screen or your session.

The homepage embeds a YouTube video in privacy-enhanced mode (youtube-nocookie.com). When the video loads or plays, your browser connects to YouTube, and Google’s privacy policy applies to that connection.