TripMazerTripMazer
TripMazer for Agencies • Mazer Labs Private Limited

TripMazer for Agencies: Data Processing Agreement

Effective: 11 November 2026

This Data Processing Agreement ("DPA") is between the Agency and Mazer Labs Private Limited, a company incorporated in India with its registered office at Vallachira Temple Road, Vallachira, Thrissur, Kerala, India 680562 ("TripMazer"). It forms part of the Agency Terms and is accepted with them. Words defined in the Agency Terms have the same meaning here.

It is the contract that section 8(2) of India's Digital Personal Data Protection Act, 2023 ("DPDP Act") requires between a data fiduciary and a data processor. Where the GDPR or the UK GDPR applies, it also sets out the terms Article 28 requires.

1. Who does what

For Customer Data, the Agency is the data fiduciary (or controller) and decides why and how it is processed. TripMazer is the Agency's data processor and processes it only for the Agency.

For the personal data of the Agency's Team and billing contacts, TripMazer acts on its own account, as explained in the Agency Privacy Notice. This DPA does not cover that data.

2. What is processed

Purpose

Providing the Service to the Agency: answering Customers, keeping their records, preparing and sending quotes, invoices, vouchers, document requests, supplier requests, broadcasts and trip messages, and supporting and securing the Service.

People the data is about

  • the Agency's enquirers, clients and their contacts;
  • travellers named on the Agency's quotes and bookings, who may include children;
  • staff of the Agency's suppliers, where the Agency sends them requests.

Kinds of data

  • names, phone numbers, email addresses and, where given, postal address and GSTIN;
  • chat messages, notes, tags and the history of each enquiry;
  • trip details: destinations, dates, travellers, preferences, quotes, bookings, supplier confirmations and feedback;
  • payments the Agency records: amounts, dates and references. TripMazer does not receive card or bank details of Customers;
  • travel documents where the Agency asks for them: nationality, passport number and expiry, visa status, and passport or visa images the Customer uploads.

How long

For as long as the Agency keeps the data in its account, and then as section 10 sets out.

3. Processing only on the Agency's instructions

TripMazer processes Customer Data only on the Agency's documented instructions. These are the Agency Terms, this DPA, and what the Agency and its Team set and do in the Service (including the jobs the Agency switches on). TripMazer does not process Customer Data for its own purposes, sell it, use it for advertising, or use it to train AI models.

If the law requires TripMazer to process Customer Data otherwise, it will tell the Agency first, unless the law forbids that. TripMazer will tell the Agency if it believes an instruction breaks data protection law.

4. What the Agency is responsible for

  • having a lawful basis for the Customer Data it puts into the Service, and giving Customers the notice section 5 of the DPDP Act requires (section 12 has text it can use);
  • getting consent where it is needed, including before sending marketing broadcasts or WhatsApp messages, and respecting withdrawals and unsubscribes;
  • getting verifiable consent from a parent or lawful guardian before processing a child's personal data where the law requires it, and not tracking, profiling or targeting advertising at children;
  • collecting only what each trip needs. For example, ask for passport images only when a trip requires them;
  • answering Customers' requests to access, correct or erase their data, and handling their grievances, using the tools in section 8;
  • keeping its Team's access to the Service limited to the people who need it.

5. TripMazer's people

Only TripMazer staff and contractors who need access to provide, support or secure the Service may access Customer Data, and they are bound to keep it confidential. TripMazer staff look at an Agency's Customer Data only to give support the Agency asked for, to investigate a security or abuse issue, or when the law requires it.

6. Security

TripMazer takes reasonable security safeguards to protect Customer Data against breach, as section 8(5) of the DPDP Act requires. Today these include:

  • encryption of data in transit (TLS) and at rest in the database and file storage;
  • separation of each agency's data in the database by row-level security rules, tested with automated isolation checks;
  • roles for each Team member (owner, admin, agent), and limits on what each role can change;
  • private file storage for travel documents and booking files, opened only through short-lived signed links;
  • unguessable links for quotes, trip pages, vouchers and document requests, which reveal only what that page needs (vouchers show no prices);
  • a log of the actions the Assistant, jobs and copilot take, with undo for many of them;
  • restricted, logged access to production systems and secret keys, and daily database backups;
  • monitoring for errors and misuse, and a plan for responding to incidents.

TripMazer may change these measures as long as the overall level of protection does not go down.

7. Sub-processors

The Agency allows TripMazer to use the sub-processors listed below. TripMazer has a written contract with each one that protects Customer Data at least as well as this DPA does, and TripMazer remains responsible to the Agency for their work.

  • Supabase, Inc.: database, sign-in, file storage and server functions. The primary database is hosted in India (Mumbai).
  • OpenRouter, Inc., and the AI model providers it routes requests to (currently including Google and Alibaba Cloud): generating the Assistant's replies, drafts and summaries. Requests may be processed in the United States or other countries. These providers may not use the data to train their models.
  • Resend, Inc.: sending emails on the Agency's behalf (quotes, follow-ups, document requests, supplier requests, broadcasts) and alerts to the Team.
  • Fly.io, Inc.: background workers for website previews, page screenshots and document processing.
  • Google LLC (Firebase Cloud Messaging): delivering phone alerts to the Team, which may include a Customer's name.
  • Meta Platforms, Inc. and its affiliates (WhatsApp Business Platform): only when the Agency connects WhatsApp, for sending and receiving the Agency's WhatsApp messages.

TripMazer will give at least 14 days' notice by email to account owners before adding or replacing a sub-processor. The Agency may object on reasonable data protection grounds within that time. If we cannot resolve the objection, the Agency may end the affected part of the Service and get back what it prepaid for the time left.

8. Helping with Customers' requests

The console lets the Agency find, export, correct and delete a Customer's data. TripMazer will help, where it reasonably can, with requests TripMazer cannot handle through the console. These include requests under sections 11 to 14 of the DPDP Act (access, correction, completion, erasure, nominating someone, and grievances) and under Chapter III of the GDPR.

If a Customer sends a request about Customer Data to TripMazer, TripMazer will pass it to the Agency without delay and will not answer it itself, unless the Agency asks it to or the law requires it.

TripMazer will also give reasonable help with data protection impact assessments and with questions from regulators about the Service.

9. Personal data breaches

If TripMazer becomes aware of a personal data breach affecting Customer Data, it will tell the Agency without undue delay, and within 24 hours wherever possible. The notice goes to the account owners by email and in the console. It will say, as far as known then: what happened and when, the kinds and rough number of people and records affected, the likely consequences, and what TripMazer has done and recommends.

This lets the Agency meet its own duty to inform the Data Protection Board of India and the affected Customers. TripMazer will send updates as it learns more, help the Agency with those notices, and take reasonable steps to contain the breach. TripMazer will also make the reports the law requires of it, such as reports to CERT-In.

Telling the Agency about a breach is not an admission of fault.

10. Deleting or returning data

When a Team member deletes Customer Data in the console, it is removed from the live Service.

When the Agency's account ends, the Agency may export Customer Data for 30 days. TripMazer then deletes it within the next 60 days. Copies in backups are overwritten in the normal backup cycle, and are not restored except to recover from a disaster. TripMazer may keep data only where the law requires it to, and only for as long as it requires.

11. Information and audits

TripMazer will give the Agency the information reasonably needed to show that it meets this DPA, for example by answering a security questionnaire once a year. On a Custom plan, the Agency may also audit TripMazer's compliance, at the Agency's cost, with 30 days' notice, during business hours, without seeing other agencies' data, and under a confidentiality agreement. A regulator may audit as the law allows.

12. A notice you can give your Customers

You can adapt this short notice for your website, pre-chat form or booking forms. Replace the parts in brackets. You may need to add more for your business.

"[Agency name] uses TripMazer to answer enquiries and manage trips. When you chat with us or book with us, we collect your name, contact details, trip details and, where your trip needs them, passport and visa details. We use them to plan and book your trip, keep you updated and look after you while you travel. Our first replies may come from an AI assistant, and you can ask for a person at any time. Your data is stored with TripMazer, which processes it for us, and is shared with the hotels, airlines and other suppliers needed for your booking. To see, correct or delete your data, or to withdraw consent, contact [email or phone]. You may also complain to the Data Protection Board of India."

13. Data outside India

Customer Data is stored mainly in India. Some sub-processors in section 7 process it in other countries, mainly the United States. The DPDP Act allows this except to countries that the Government of India restricts by notification. TripMazer will not transfer Customer Data to a country restricted in that way.

Where an Agency is subject to the GDPR or the UK GDPR, transfers of Customer Data to TripMazer in India are made under the European Commission's Standard Contractual Clauses (Module 2, controller to processor, and Module 3 for onward transfers to sub-processors), with the UK Addendum where the UK GDPR applies. These are incorporated into this DPA by reference. For those clauses: the Agency is the data exporter and TripMazer the data importer; Annex I is section 2 of this DPA; Annex II is section 6; Annex III is section 7; the optional docking clause applies; and the governing law and courts are those of Ireland. If these clauses conflict with the rest of this DPA, the clauses prevail.

14. General

This DPA lasts as long as TripMazer processes Customer Data for the Agency. Liability under it is subject to the limits in the Agency Terms, except where the law does not allow that. Where this DPA and the Agency Terms differ about personal data, this DPA prevails.

TripMazer may update this DPA to follow changes in the law or its sub-processors, with the notice described in the Agency Terms and in section 7. Questions go to privacy@tripmazer.com.

Also for agencies: Terms of Service · Privacy Notice

© 2026 Mazer Labs Private Limited.