Privacy Policy
Last updated: 18 November 2026
This policy explains how Airline Inbox handles personal data. It is written to follow India's Digital Personal Data Protection Act, 2023 (the DPDP Act) and the rules made under it. Where the text says "we", it means [company name: not set].
1. Who we are
[company name: not set], [registered address: not set], runs Airline Inbox, a web service that reads the airline and travel mails of travel agencies, extracts the details from tickets and GST invoices, checks them and sorts them into folders and Excel reports. Support: [support email: not set].
Two roles apply under the DPDP Act. For the personal data of an agency's passengers, the agency decides why and how the data is used, so the agency is the Data Fiduciary and we are its processor (see section 7). For the account data of agency staff, we decide how the service handles it, so we act as the Data Fiduciary.
2. What data we hold
Account data. The agency's name; for each user, the name, work email address, role (owner, admin, accounts, operations or viewer) and a password stored only as an Argon2 hash, never as plain text. We also keep the times of logins, and for each login session the IP address and browser type. Login sessions are identified by random tokens; only a hash of each token is stored.
Mailbox data. When an agency connects a mailbox (Gmail, Microsoft 365, Zoho, or an IMAP mail account), we read the mails that match the agency's sender settings. These are airline mails and their attachments: e-tickets, GST invoices, credit notes, refund and schedule-change mails. They can contain passenger names, PNRs, ticket numbers, GSTINs, invoice numbers, amounts, travel dates and sectors. Mails from senders that are not airlines and are not on the agency's sender list are not opened or stored, with two exceptions. First, forwarded mails (subject starting "Fwd") are opened to check whether they carry airline content. Second, when the agency turns on "Read airline tax invoices sent from any address" (the setting invoice_pdf_any_sender), mails with a PDF attachment from any sender are opened and the PDF is checked; scanned PDFs among them are read too, as described in section 5. A mail that turns out not to be an airline's tax invoice keeps only its headers (sender, name, subject and date). Gmail's search also fetches each matching message in full before the sender is checked; those copies are held in memory and not kept. From the mails we keep the extracted fields, the original mail file in encrypted form, the folder it was sorted into and the review notes.
Mailbox credentials. The mailbox password, or the OAuth refresh token issued by Google or Microsoft, is stored encrypted and is used only to read and sort that mailbox.
Usage and audit logs. A record of who did what in the agency's workspace (for example logins, approvals, settings changes, mailbox changes and report sends), with the time and IP address. Background job records show whether a sync or report mail succeeded. Service monitoring keeps records of problems and when they started and ended, with the agency they belong to.
3. Why we hold it
- To provide the service: reading, sorting and checking mails, producing Excel reports and sending report emails.
- To keep accounts and data secure: login checks, audit records and access control.
- To tell the people who run the service, and the agency, when something stops working.
- To meet legal obligations, for example keeping records that the agency needs for its GST returns.
We do not use this data for advertising, and we do not sell it.
4. Who can see it
Only the agency's own team can see its data, and only as far as its role allows. Agencies are isolated from each other: every query is limited to one agency's rows, and on PostgreSQL the database enforces the same limit again. One agency cannot see another agency's mails, passengers, bookings or reports.
The people who run this service do not open an agency's mails, attachments, extracted details, bookings or reports, and their admin tools give no way to open them. Their admin tools show only: the agency's name and status; its users' names, work emails, roles and last login; each mailbox's provider, email address, status and last sync; counts of mails and usage; the column headings of an invoice table when it is sent for approval of its layout; and the open problems of the service, with the agency each belongs to. Every action they take in those tools is recorded in the audit log.
5. Who else handles the data
Hosting and email delivery. The application, its database and the stored mail files run on servers hosted by [hosting provider: owner decision] in [hosting location: owner decision]. Report and alert emails are sent through the mail server the service is configured with: [email delivery provider: owner decision].
Mail providers. Google, Microsoft, Zoho or the agency's own mail host hold the agency's mail. We connect to them only to read and sort the mail the agency has asked us to handle.
AI reading (Anthropic). This happens only when an agency turns on AI reading in its settings and the service has an Anthropic API key. Then, for each mail that is read, the following is sent to Anthropic to get the structured details back. The items are: the sender's name and address, the recipient addresses, the date, the subject, the names of the attachments, the text of the mail body (cut at 60,000 characters), the extracted text of up to three text-based PDF attachments, and the scanned PDF attachments themselves (up to 8 MB each). When AI is on, the column headings of an invoice table may also be sent to suggest how its columns should be read. [Owner decision: Anthropic's data retention terms that apply to the API account.]
OCR. If an OCR server is configured for the service, scanned PDFs are sent to that server, which is run by the service itself. No hosted OCR service is configured.
We do not use advertising, analytics or tracking providers. No third-party script is loaded into the pages.
6. Security
- Mailbox passwords, OAuth tokens and stored mail files are encrypted with a key that is kept apart from the data.
- Passwords are stored as Argon2 hashes. Login sessions use random tokens, stored only as hashes.
- Access follows roles, and every agency's data is kept apart from every other agency's.
- Forms are protected against forged requests, repeated wrong logins are throttled, and sensitive actions are recorded in the audit log.
- Text written into Excel reports is escaped, so that it cannot run as a formula.
No system is completely secure. If we learn of a breach that affects an agency's personal data, we will inform the agency and take the steps the law requires.
7. The agency's role for its passengers' data
The passenger names, PNRs, ticket numbers and similar details in an agency's mail belong to the agency's business. We process them on the agency's behalf and on its instructions, only to provide the service described in section 3. The agency is responsible for having a lawful basis for that processing and for giving its passengers the notices the DPDP Act requires. Passenger data may include details of minors, and the agency is responsible for handling those lawfully. If a passenger asks us directly for access, correction or erasure, we will pass the request to the agency, which decides what to do.
8. How long we keep data
We keep an agency's data while the agency uses the service. Removing a mailbox deletes the mails stored for it, and the stored copies that no other mailbox still uses. An owner closes the account under Settings → Close account, or by writing to support. Everything is deleted 30 days after the request. Until then the owner can download the data and cancel. Labels or copies already made in the agency's own mailbox stay there. [Owner decision: how long deleted data stays in backups.]
9. Deletion on request
To ask for an agency's data to be deleted, its owner can close the account under Settings → Close account, or write to [support email: not set]. We will confirm the request and delete the data within 30 days of the owner's request to close the account, except data we must keep by law. The owner can cancel the request within those 30 days, and can download the data until then.
10. Your rights and the grievance officer
Under the DPDP Act you have the right to ask what personal data is held about you, to have it corrected, to have it erased, to nominate another person to exercise these rights for you, and to make a grievance. A passenger should first ask the travel agency, which is responsible for that data. Agency staff can write to us. For any grievance, contact our grievance officer:
[grievance officer: not set], [grievance email: not set].
11. Cookies and browser storage
We use no tracking cookies and no advertising cookies. The service uses these:
- sid: the login cookie. It is HTTP-only, and it lasts for the login session (12 hours by default).
- pre_csrf: a cookie that protects the login and sign-up forms against forged requests. It is HTTP-only and lasts one hour.
- Browser local storage: three preferences, stored only in your browser and never sent to us:
theme(light or dark),density(compact or normal) andhaptics(whether touch feedback is on).
12. Children
Airline Inbox is a business service for travel agencies and their staff. It is not intended for children, and we do not open accounts for them.
13. Changes to this policy
When we change this policy, we update the "Last updated" date at the top of the page. For material changes we will tell the owner of each agency by email [notice period before a change takes effect: owner decision].
14. Contact
[company name: not set], [registered address: not set]. Support: [support email: not set]. Grievance officer: [grievance officer: not set], [grievance email: not set].
Questions about this page: [support email: not set].