Privacy
Privacy Policy
Zentrfi (Zentra Finance) is a Web4 AI travel planning swarm. This page explains what we collect in this demo UI, how it’s used, and what we recommend for production-grade compliance (encryption, least-privilege, and secure identity handling).
Data we collect (demo UI)
In this prototype, any trip prompts and booking details you enter are used to simulate planning and booking flows. The API routes are mocked and exist for UI realism.
Booking identity requirements
For real airline bookings, providers typically require Secure Flight fields (legal name, DOB, gender) plus contact info for ticket delivery and gate alerts.
Crypto settlement + wallet info
When you connect a wallet, we can display your address and request a mock signature for an escrow-style authorization step. We do not store private keys.
Security model (recommended)
Use encryption-at-rest for identity fields, short-lived access tokens, strict audit logs, and role-based access controls. Store only what’s needed for fulfillment.
Notes for 2026 identity
Digital Travel Credentials (DTC)
If you integrate DTC/KYC providers, treat identity as a secure enclave: minimize exposure, keep verification proofs separate from user-entered data, and restrict access to only the booking worker and compliance services.
Contact
For privacy questions, contact support via your project’s preferred channel. (Replace this with your actual support email/URL when you deploy.)
Last updated: 3/9/2026