App: TripzoCRM
Package: com.tripzo.crm
Effective date: 22 August 2026
Last updated: 22 August 2026
TripzoCRM (“the app”, “we”, “us”) is a private customer‑relationship‑management tool built for staff of travel agencies that subscribe to the TripzoCRM service. It is not a consumer product. Access is restricted to invited users of a subscribed organization, who sign in with credentials issued by their organization’s administrator.
This policy explains what data the app collects, why, where it goes, and the choices you have.
Agency staff who sign in to TripzoCRM to manage leads, itineraries, bookings, invoices, tasks, packages, finances and customer conversations on behalf of their employer.
Customers of those agencies whose contact details and trip information are entered into the CRM by agency staff. Customers do not use this app directly; their data is processed by the app because their travel agency chose TripzoCRM as its CRM.
If you are a customer of an agency and want your personal data removed, contact the agency you are dealing with. They are the data controller; we process data on their behalf.
We only collect data that is necessary to operate the CRM.
Email address, hashed password, display name, role, and the organization you belong to.
Session tokens issued after sign‑in, stored on the device in Expo Secure Store / platform keystore so you do not have to re‑enter your password.
When you use the app you may create, view or edit:
Lead contact details (name, phone, email, WhatsApp / Instagram handle, source, notes).
Itineraries, package assignments, quotes, bookings and travel dates.
Invoices, payments, refunds and other financial records.
Tasks, reminders and internal notes.
Chat transcripts with customers exchanged over WhatsApp, Instagram or in‑app channels routed through the TripzoCRM backend.
Files, images and PDFs (e.g. passports, tickets, brochures) that staff upload or attach.
This content is stored on the TripzoCRM backend (self‑hosted Supabase) that serves your organization.
Device model, OS version and app version, sent with API requests for troubleshooting and to decide which over‑the‑air update to serve.
A push‑notification token (Expo / FCM) if you enable notifications, so the backend can deliver alerts about new leads, messages and tasks.
Basic diagnostic logs (timestamps, request paths, error messages). These do not contain your password.
The app only reads these when you explicitly invoke a feature that needs them:
Camera / Photos — when you tap “attach image” or take a photo of a document to attach to a lead, itinerary or invoice.
Files / Documents — when you pick a PDF or file to upload.
Notifications — to display push alerts you have opted into.
Clipboard — only when you use “copy” / “paste” actions in the app.
We do not collect location, contacts, microphone audio, call logs, SMS messages, health data, or advertising identifiers.
To authenticate you and enforce your organization’s role‑based access controls.
To render the CRM screens: leads, chats, itineraries, invoices, finances, tasks, packages, reports.
To send and receive messages with customers on channels the agency has connected (WhatsApp Business, Instagram, etc.).
To deliver push notifications you have opted into.
To operate the over‑the‑air update mechanism (api.tripzocrm.cloud) so bug fixes reach the app without a Play Store re‑upload.
To diagnose crashes and errors and to keep the service secure.
We do not use your data for advertising, do not sell it, and do not share it with data brokers.
We process data on the basis of:
Contract — providing the CRM service to the agency that employs you or that you are a customer of.
Legitimate interest — keeping the service secure, preventing abuse, fixing bugs.
Consent — for optional features that require a runtime permission (camera, files, notifications). You can decline or revoke consent at any time in your device settings.
The backend runs on infrastructure controlled by TripzoCRM at api.tripzocrm.cloud, backed by a self‑hosted Supabase (PostgreSQL) instance.
Data belonging to an organization is isolated to that organization. Staff of one agency cannot see the leads, chats or finances of another.
Push notifications are delivered through Google Firebase Cloud Messaging (FCM) and Expo’s push service. The message body may contain a short preview (for example the sender’s name and the first line of a chat message).
Messages that flow through WhatsApp or Instagram are also processed by Meta Platforms under their own terms, because those are the channels the customer chose to contact the agency on.
Data is stored on servers located in the region configured for the TripzoCRM backend. Backups are encrypted at rest.
CRM records (leads, itineraries, invoices, chat history) are retained for as long as the agency’s TripzoCRM subscription is active, plus any period the agency is legally required to keep them (for example tax records).
Session tokens on the device are cleared when you sign out.
Diagnostic logs are rotated and deleted after 90 days.
If an agency terminates its subscription, its data is deleted or returned to it within 60 days, subject to legal retention obligations.
Because the app is used both by agency staff and holds records about their customers, the party you contact depends on who you are:
Agency staff may ask their organization’s administrator, or contact us directly, to correct or delete their user account.
Customers of an agency should contact the agency they dealt with — the agency is the data controller for their records. If the agency does not respond, you may contact us and we will facilitate the request.
Depending on your jurisdiction (GDPR, DPDP Act, CCPA and similar) you may have the right to:
access the personal data we hold about you,
correct inaccurate data,
request deletion,
object to or restrict certain processing,
request a copy of your data in a portable format,
withdraw consent for optional features,
lodge a complaint with your local data protection authority.
TripzoCRM is a workplace tool. It is not directed at, marketed to, or intended for use by anyone under 16. We do not knowingly collect data from children. If a child’s personal data has been entered into the CRM as part of a travel booking (e.g. a passenger on a family trip), it is processed under the same terms as any other customer record and can be removed on request.
All traffic between the app and the backend uses HTTPS/TLS.
Passwords are hashed on the backend; we never see them in plaintext.
Session tokens on the device are stored in the platform’s secure keystore (Expo Secure Store, backed by Android Keystore).
The backend enforces role‑based access controls so staff only see data their role permits.
No system is perfectly secure. If we become aware of a breach that affects you, we will notify you and the appropriate authority as required by law.
The app relies on a small number of well‑known services to function:
Service
Purpose
Supabase (self‑hosted by us)
Authentication and database
Expo / EAS
App runtime and over‑the‑air updates
Google Firebase Cloud Messaging
Android push notifications
Meta (WhatsApp Business, Instagram)
Customer messaging channels the agency has connected
We do not embed advertising SDKs, analytics trackers, or social login providers.
We may update this policy from time to time. The “Last updated” date at the top of this document will change and, for material changes, we will notify users through the app or by email before the change takes effect.
For privacy questions, data requests, or to report a concern:
Email: privacy@tripzocrm.cloud
Website: https://tripzocrm.cloud
If you are a customer of a travel agency that uses TripzoCRM, please first contact that agency — they are the controller of your personal data.