Privacy Policy

Draft for owner / legal review · Last updated 18 October 2026

Not final legal advice

This draft describes intended product practices for Itiravo. It must be reviewed and approved before being treated as binding.

Who we are

Itiravo (“we”) provides travel discovery, planning, and trip management software on iOS, Android, and the web at itiravo.com. Contact: support@itiravo.com.

Data we process

Account data: email, authentication identifiers, display name and preferences you provide
Trip data: destinations, dates, itinerary stops, notes, expenses, booking metadata you save
Usage data: product analytics and AI usage metering when those services are enabled
Support messages you send to us
Technical logs needed for security and reliability

How we use data

To provide and sync your trips across devices via Supabase Auth and PostgreSQL with RLS
To generate AI itinerary drafts when you request them — provider keys stay server-side
To operate discovery, creator review, and (when approved) booking comparison
To respond to support and account-deletion requests
To secure the service and prevent abuse

Processors

Authentication and primary database are hosted on Supabase (project ref yknjpxfnnoxvinlfarmf). AI generation may use authorised providers such as Google Gemini or AWS Bedrock through Itiravo servers — never with API keys in the browser. Hosting for itiravo.com may use Netlify or another commercial host approved by the owner.

Retention & deletion

You may request account deletion via /delete-account. Cloud trip wipe uses the secured RPC itiravo_delete_own_cloud_data. Full Auth user deletion requires the deployed delete-account Edge Function — until that is live, deletion requests are handled manually by the owner after verification.

Your rights

Depending on your location, you may have rights to access, correct, export, or delete personal data, and to object to certain processing. Contact support@itiravo.com to exercise these rights.

Children

Itiravo is not directed at children under 16. We do not knowingly collect their personal data.

Changes

We will update this page when practices change and note the revision date. Material changes will be communicated in-product when feasible.