We track. We know. We simplify.

Privacy Policy

Effective date: 26 September 2026

1. Local-first use and optional Tripzy Cloud

You can use Tripzy's core features in Guest mode without creating a Tripzy Cloud account. Guest vehicle, fuel, expense, trip and related records are stored in Tripzy's private app storage on your device.

If you choose to sign in to Tripzy Cloud, Tripzy uses Supabase for authentication, database and server-side account-deletion services. For a signed-in workspace, Supabase is the durable account store for confirmed Tripzy records that are eligible for cloud sync, while Tripzy keeps a device-side working cache for app operation. A cloud account may process your email address, authentication provider information, Supabase user identifier and eligible Tripzy records.

Cloud-synced core records currently include vehicle records, fuel entries, expenses, trips, trip stops and trip members, together with technical identifiers and timestamps needed to keep those records associated with your account and synchronized.

Existing Guest data is not automatically attached to a cloud account merely because you sign in. When Tripzy finds Guest data, it asks whether you want to bring that data into the signed-in account and back it up, keep the Guest workspace separate and use only the account's cloud data, or cancel. Account switching never silently reassigns records between users.

2. Information you provide

• vehicle details, registration number, odometer readings and vehicle configuration;
• fuel quantity, price, amount, dates, station and notes;
• expense title, category, amount, date, merchant, optional odometer and notes;
• trip names, route text, dates, passenger counts, budgets, odometers, stops, trip-member names/types and notes;
• account email and authentication-related identifiers when Tripzy Cloud is used; and
• support information you voluntarily send to Tripzy.

3. Smart Transactions and Notification Access

Smart Transactions is optional. Android Notification Access can make notification content from apps on your device available to Tripzy while access is enabled.

Tripzy filters likely payment notifications on-device and may extract amount, merchant/payee, source app, reference information, detected time and suggested category so you can review a possible Tripzy entry.

Detected Smart Transaction candidates are stored locally as pending reviews. Raw notification text is not uploaded to Tripzy Cloud, and Smart Transaction payment details are not sent to advertisers.

A pending review becomes a normal Fuel, Expense or Trip-linked record only after you confirm it. Once confirmed, that normal record may sync if you are signed in and it is owned by your Tripzy Cloud account.

You can disable Smart Transactions in Tripzy and revoke Notification Access through Android settings at any time.

4. Notifications and reminders

Tripzy may request Android notification permission for trip reminders and Smart Transaction review alerts. Trip reminders are scheduled on your device when you enable them.

5. Automatic backup, manual backup and export

Tripzy disables Android automatic cloud backup and device-to-device transfer for its internal database, internal files and app preferences.

User-requested backup and export files are created only when you request them and are saved through Android's file picker to a location you choose. Local backup restore is available for the Guest workspace; while signed in, Tripzy disables local restore to avoid mixing or overwriting account workspaces. You are responsible for copies stored outside Tripzy.

Smart Transaction pending candidates and temporary notification inbox/delivery bookkeeping are not included in the normal Tripzy backup/export dataset.

6. Purposes of processing

Tripzy processes personal data for features you choose to use, including local vehicle management, cloud authentication and synchronization, restoring owned cloud records, Tripzy Plus purchase verification and entitlement management, reminders, user-requested backup/export, duplicate prevention for Smart Transactions, support/privacy requests, service security and legal compliance.

7. Advertising and advertising privacy choices

Tripzy uses Google AdMob / Google Mobile Ads SDK and may use Unity Ads through Google AdMob mediation. Advertising providers may process identifiers, IP address/general location, device/app information, ad interactions, diagnostics and fraud-prevention information under their own policies and applicable consent choices.

Where required, Tripzy uses Google's User Messaging Platform (UMP) to collect/manage advertising privacy choices before ads are requested. Tripzy does not send Smart Transaction payment details to advertising providers.

8. Tripzy Plus and Google Play Billing

Tripzy Plus is an optional recurring subscription purchased through Google Play. When you buy, restore or refresh Tripzy Plus, Tripzy uses Google Play Billing and a server-side verification service to confirm whether the subscription is valid for the signed-in Tripzy account.

For subscription verification and account-linked entitlement management, Tripzy may process and store the Google Play product/base-plan identifier, purchase token and a cryptographic hash of that token, subscription status, expiry time, renewal state, verification timestamps and the Tripzy account identifier associated with the entitlement.

Tripzy does not receive or store your payment-card number, bank-account details or Google Play payment credentials. Google Play handles the payment transaction under Google's own terms and privacy practices.

Tripzy Plus subscriptions renew automatically according to the billing period shown in Google Play until canceled there. Deleting a Tripzy account does not itself cancel a Google Play subscription.

9. Service providers

• Supabase for optional Tripzy Cloud authentication, database and account-deletion backend services;
• Google for Google sign-in where selected, Google Play Billing and subscription verification, AdMob, UMP, Play in-app review and Play in-app updates;
• Unity Ads as an advertising mediation partner where an eligible mediated ad is served; and
• Android system services for Notification Access, notifications, file selection/sharing and local scheduling.

Tripzy's current Supabase project is deployed in the ap-south-1 region in India. Other providers or their subprocessors may process relevant data in other locations under their own legal and contractual safeguards.

10. Sharing and sale

Tripzy does not sell your Tripzy core records or Smart Transaction payment details. Data is shared with service providers only as needed for the features described above or when required by applicable law or a binding government/court/cyber-security requirement.

11. Retention

Local Tripzy records remain on your device until you delete them, clear app storage, restore different data, or uninstall the app.

Cloud account data and cloud-synced records are retained while needed to provide Tripzy Cloud and until you delete applicable records or delete your Tripzy account, subject to limited retention required for security, fraud prevention, backup recovery, dispute handling or applicable law.

Tripzy Plus verification and entitlement records are retained while needed to verify and restore account-linked subscription access and may be retained for limited periods where needed for security, fraud prevention, dispute handling or legal compliance.

Security, access and incident-related records may be retained for periods required by applicable Indian cyber-security or data-protection law.

12. Your choices and privacy rights

You can keep Tripzy local-only, choose whether to create a cloud account, disable Smart Transactions, revoke Notification Access, manage Android notification permission, change applicable advertising privacy choices, edit/delete supported records, sign out, export/backup data, manage or cancel Tripzy Plus through Google Play, and delete your Tripzy Cloud account from the app.

Where applicable law provides additional rights, you may request access, correction/updating, erasure, consent withdrawal and grievance redressal by contacting Tripzy. Reasonable verification may be requested to protect the account.

See Delete your Tripzy account for the external deletion process.

13. Account deletion

Signed-in users can request account deletion inside Tripzy. The server verifies the authenticated account before deleting it. Owned cloud records are linked to the account through database relationships designed to remove those records when the auth account is deleted.

After server deletion succeeds inside the app, Tripzy clears its local databases and relevant app preferences on that device and signs out the local session.

Account deletion does not automatically remove manual backup/export files saved outside Tripzy, provider data independently retained under another lawful basis, or local data on another offline device.

Deleting your Tripzy account does not cancel an active Tripzy Plus subscription in Google Play. If you do not want future subscription renewals, cancel or manage Tripzy Plus in Google Play before deleting the Tripzy account.

14. Security

Tripzy uses safeguards including private Android app storage, disabled Android automatic backup for internal data, HTTPS-only app networking, Supabase authentication, row-level security and per-user ownership policies, server-side privileged account deletion, restricted release logging, and protected Android content sharing.

No electronic system can be guaranteed to be completely secure. Report suspected security incidents promptly using the contact below.

15. Children

Tripzy is intended for adults managing vehicles and related expenses. Tripzy Cloud accounts are intended for users aged 18 or older. Users under 18 should not create a Tripzy Cloud account or submit personal data to Tripzy Cloud.

16. India privacy and grievance contact

17. Personal data breaches and cyber incidents

Tripzy maintains an incident-response process for investigating suspected unauthorized access, containing incidents, preserving relevant evidence and logs, remediating causes, and making legally required notifications to affected users or Indian authorities within applicable timelines.

18. International processing

Some providers or subprocessors may process service or advertising information outside India. Where Indian law imposes conditions on such transfers, Tripzy will apply the legally required conditions.

19. Changes and contact

This policy may be updated as Tripzy features, cloud architecture, permissions, advertising practices, legal requirements or service providers change.

Privacy, grievance, account-deletion and security contact: tripzysupport@gmail.com