App Privacy Policy

• 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 it 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.

2.1 Account and authentication data

• Email address, hashed password, display name, phone number, profile photo, role, and the organization you belong to.
• If you ask to join an organization, the organization you asked for and when you asked. Administrators of that organization see your name, email address and phone number so they can decide whether you are who you say you are. Withdrawing the request, or being declined, removes it; nothing about you is shared with an organization you have not asked to join.
• Session tokens issued after sign-in, held in the app’s own storage on the device so you do not have to re-enter your password. This storage is private to the app and is cleared when you sign out, but it is not additionally encrypted by the app beyond the protection the operating system gives app data.

2.2 CRM content entered by staff

When you use the app you may create, view or edit:

• Lead contact details — name, phone, email, WhatsApp or 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 or Instagram and routed through the TripzoCRM backend.
• Files, images and PDFs — for example tickets or brochures — that staff upload or attach.

This content is stored on the TripzoCRM backend that serves your organization. To make the app usable on a slow connection, the most recent conversations and message threads are also cached in the app’s private storage on your device. That cache is cleared when you sign out and when you switch organization.

2.3 Device and technical data

• Device model, operating system version and app version, sent with API requests for troubleshooting and to decide which over-the-air update to serve.
• A push-notification token if you enable notifications, so the backend can deliver alerts about new leads, messages and tasks.
• Usage and diagnostic events — which screen was opened, which action was taken, how long a request took, and the text of any error. These are recorded against your user account and your organization so we can see which features are used and find faults that only appear in the field. They contain no passwords and no message content.

2.4 Permission-gated data

The app only reads these when you explicitly invoke a feature that needs them:

• Camera and Photos — when you attach an image to a conversation, a lead, or your organization’s branding.
• Files and Documents — when you pick a PDF or file to upload.
• Notifications — to display push alerts you have opted into.
• Clipboard — only when you use a copy or paste action in the app.

We do not collect location, your device’s 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 and reports.
• To send and receive messages with customers on channels the agency has connected.
• To deliver push notifications you have opted into.
• To operate the over-the-air update mechanism so bug fixes reach the app without a new store release.
• To diagnose crashes and errors, and to keep the service secure.

We do not use your data for advertising, do not sell it, do not share it with data brokers, and do not track you across other companies’ apps or websites.

• 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, 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 Expo’s push service and, from there, Apple Push Notification service on iOS or Firebase Cloud Messaging on Android. 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, and all traffic between the app and the backend uses HTTPS/TLS.

• 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.
• Session tokens and the on-device cache are cleared when you sign out.
• Usage and diagnostic events are retained for 90 days, then deleted.
• 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 by agency staff and holds records about their customers, the party you contact depends on who you are:

• Agency staff can delete their own account from inside the app: open Settings and use Delete account at the bottom of the screen. It signs you out immediately, prevents any further sign-in, removes your profile from your organization’s team list, drops your device’s push registration, and takes you out of the lead rotation. You can also email us at the address below and we will do it for you.
• 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, contact us and we will facilitate the request.

CRM records created in the course of the agency’s business — a lead, a booking, an invoice — belong to the agency rather than to the individual member of staff who entered them, so closing a staff account does not delete the agency’s records. For the same reason the account row itself is retained in a closed state rather than erased: the agency’s invoices and bills are recorded against it, and removing it would take the authorship off financial records the agency is required to keep. Everything that makes it a usable account is revoked, and it no longer appears anywhere in the product.

Depending on your jurisdiction (GDPR, India’s 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, and 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, and 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 — a passenger on a family trip, for example — it is processed under the same terms as any other customer record and can be removed on request.

The app relies on a small number of well-known services to function:

We do not embed advertising SDKs, third-party analytics trackers, or social login providers.

We may update this policy from time to time. The “Last updated” date at the top of this page 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: support@tripzocrm.com
• Website: www.tripzocrm.com

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.