Privacy notice

How your data is used

Underwriter · Version 2026-10-21-r8-d4 · Effective 21 October 2026 · Draft for legal review
For every Flight Delay Pass sold by Underwriter, wherever you found it. Each pass's terms are linked from its emails.

1. Who is responsible

Underwriter (Sample underwriter for testing purposes only) sells the Flight Delay Pass where you live and funds your pre-loaded rescue cards. It is responsible for your personal data ("the Underwriter"), from the booking you forward until it is purged. GetThere runs the service for it and handles your data on its behalf and on its instructions, under a contract between them ("we", "us" below means GetThere acting for the Underwriter).

Write to privacy@underwriter.getthere.now with any question, request or complaint about your data. It is read and answered by Underwriter's data protection officer or, if you live in India, its grievance officer, within the time the law where you live sets. A page that is still in testing says it is a consumer demo: passes bought there are test passes and no real money moves.

2. What is collected

• The booking email you forward, including its attachments: the names of the travellers, the booking reference, flights, fare and taxes, and anything else the airline put in it, such as contact details or the last digits of the card used.
• Your email address, the one you forward from. Your bookings and passes with Underwriter are kept together under it, to answer you and for the limits in section 3. It is purged once nothing else of yours is kept.
• Your mobile number, if you choose WhatsApp at checkout or later from your confirmation email (it's optional: without it, or while WhatsApp isn't available, everything comes by email), so your pre-loaded rescue card can be sent there too. Your agreement is kept with that pass. A code is sent to it on WhatsApp to check it's yours, and WhatsApp messages go to it only once you've entered that code. Another code goes there, or by email without one, before your pre-loaded rescue card's number shows on a device. It is kept with that pass. It always comes from you, never from a partner. Reply STOP to any of our WhatsApp messages, or write to privacy@underwriter.getthere.now, and no more go to it; email carries the same links. Reply START, or tick the WhatsApp box at a new checkout, to have them again.
• Your legal name, date of birth, home address and the country you live in, given at checkout so the pre-loaded rescue card can be issued in your name. They are kept with that pass, so you give them again for each pass. Your date of birth and home address are removed as soon as your pre-loaded rescue card is issued: from then only the card issuer holds them. A coded form of your name and date of birth, from which they can't be read back, stays with the pass for the limits in section 3 until its details are purged.
• Payment details: you type your card details into the payment provider's form on the checkout page. Your card number is never seen or stored; only the payment's result and amount are.
• Your pre-loaded rescue card's use: where it was used, the amount and when.
• Flight status for your flights, from flight-data providers.
• When a partner makes you an offer: what it sends with it, such as your booking's details and its own reference for you, and the country you live in.
• When you open an offer page, such as one linked from a partner's app or an ad: the page you came from, any campaign tags in the link (such as utm_source), and when.
• What you write to help@underwriter.getthere.now or privacy@underwriter.getthere.now, and the answers: your email address and name as your email gives them, its subject and text, and the names of any attachments (the attachments themselves aren't kept). It is kept with your bookings and passes with Underwriter, so its customer service, data protection officer and grievance officer can answer you with them at hand. Only they read it.
• A complaint you make, by email or any other way: when it came in, what it is about and what you said, when it was acknowledged and resolved, the outcome and any payment, whether it went to the grievance officer, an ombudsman or a regulator, and who at Underwriter handled each step. It is Underwriter's complaints register, which it may have to show its regulator.
• Delivery records for the messages sent to you, and basic technical logs.
• A record of each time someone at GetThere looks up your details or changes something about your pass: who, when, what they did, and the internet address and browser they used.

3. Why it is used

• To price your pass and decide whether one can be offered, including checks that the booking and fare are real.
• To watch your flights and send your pre-loaded rescue card when a flight is delayed or cancelled.
• To send you your price, pass, alerts and pre-loaded rescue card, and to answer your questions.
• To count how many people see an offer and go on to forward a booking, and which links bring them.
• To prevent fraud and misuse, including the limits on passes below, and to meet legal, regulatory and accounting obligations.
• To keep a record of who at GetThere looked at or changed your details, so every look and change can be checked.

Limits on passes. Before a price is sent, and again at checkout, an automatic check counts the pre-loaded rescue cards Underwriter paid in the last 12 months on passes bought with your email address or held by someone with your name and date of birth. With 2 or more, no pass is offered. It also counts the passes your email address bought in that time for bookings you aren't travelling on: with 3 or more, no pass is offered for another one. Only Underwriter's own passes are counted, and the partner you found the pass through may set lower limits. If you think the check got it wrong, write to privacy@underwriter.getthere.now and a person will look at it.

Your data is used because it's needed to provide the pass you ask for, for the legitimate interest in preventing fraud, and where the law requires it. Where a use needs your agreement, such as WhatsApp messages, it is asked for first, and you can withdraw it at any time.

If you live in India, your data is used with the consent you give when you forward a booking and when you buy a pass, for the purposes above, and for the uses India's Digital Personal Data Protection Act allows without consent, such as meeting a legal obligation. You can withdraw your consent at any time by writing to privacy@underwriter.getthere.now. Data already used stays as it was, but a pass can't be watched or paid out without it.

4. Who it is shared with

• GetThere, which runs the service for the Underwriter, and the providers GetThere uses under contract: hosting and file storage, email delivery, WhatsApp messages, flight data, payments, card issuing, and, for a booking email the service can't yet read on its own, an AI service that reads a copy of its text to find the flights and fare. In that copy the travellers' names, the booking reference, email addresses and phone numbers, and any date of birth, passport or frequent flyer number, postal address or card's last digits it labels, are replaced with made-up ones; an email in which the names and reference can't be found isn't sent to it. GetThere's subprocessors page names each one, what it does and where.
• The card issuer receives your legal name, date of birth, home address, email address and mobile number when you buy a pass, to check your identity (including sanctions screening) and issue the pre-loaded rescue card in your name. It may ask for an identity document if it can't confirm who you are.
• The airline, to check your booking is still active before a pre-loaded rescue card is sent.
• The partner you found the pass through, only as section 5 says.
• Regulators and authorities, when the law requires it.

Your data is never sold or used for advertising.

5. If you found the pass through a partner

Some partners, such as banks and travel sites, offer the Flight Delay Pass to their customers. A partner is a separate organisation with its own privacy notice. Data is shared with it only as below, with its own reference for you and its order number, never your email address or phone number:

• Every partner is told when your pass is issued (the plan and what you paid), when a pre-loaded rescue card is sent (its amount and why), and when the pass ends (expired, refunded or cancelled, and any refund). A loyalty program uses this to credit or take back points; a bank shows it in its app and to its customer service.
• If you used the partner's pass voucher: that it was used, or ran out unused.
• A travel site is also told when it corrects the travellers' names on your pass, and what you spent with the pre-loaded rescue card and where, as you rebook on its site.
• To show alerts about your pass in the partner's app: the alert's wording and link. You can turn these alerts off in the app.
• If you bought the pass with a booking on a travel site: the site sends the details you gave it for the pass, and is told whether the pass was issued.

A partner is never told whether you added WhatsApp, whether an email to you bounced, or why a pass was cancelled.

6. Where it's stored

Your data is stored on servers in Singapore. Some providers process it in the United States: email delivery, WhatsApp messages, payments, flight data (flight numbers and dates only) and the AI service that reads a new kind of booking email. The card issuer processes it in Singapore and the other countries it operates in. GetThere's subprocessors page names each provider and where it works. Each transfer is made under a contract that holds the provider to the standard the law where you live requires, using standard contractual clauses where that law calls for them.

Your date of birth, home address and phone numbers, and the emails you forward and are sent, are stored encrypted with a key only the service holds, on top of the hosting provider's own encryption of its disks.

7. How long your personal data is kept

Your personal details are kept only while the stage your booking is at needs them. When that stage ends, they are purged: removed from every record that held them. The records themselves stay, without anything that identifies you, as the account of what was offered, priced and sold, for counting and accounts.

• 1. An offer from a partner. What the partner sent with it, such as your booking's details and its own reference for you, and the page you came from. Purged when the offer ends: if no booking is forwarded on it within 12 months, once what you forwarded on it couldn't be priced, or once its prices ran out unbought and the flight's sales closed. If you buy a pass on it, it stays with your pass (stage 4). Why: to check that the booking you forward is the one the offer was made for, to price it again if you forward it again, and to tell the partner about your pass.
• 2. Your forwarded booking. The booking email and everything read from it: the travellers' names, the booking reference, flights and fare. Purged straight away once you've been told if no price can be offered or it can't be read. If a person needs to read it, it is kept until they have, for up to 7 days. Why: to read your booking and decide whether a price can be offered.
• 3. Your price. The booking, anything you or a travel site gave for the checkout, and the copies of the messages sent to you. Purged about an hour after your price runs out or is withdrawn, if you don't buy a pass. Why: so you can buy while the price stands, and a payment already started can finish.
• 4. Your pass. The booking, the pass holder's name and, until the pre-loaded rescue card is issued, their date of birth and address (the country stays: it says who sold the pass), your WhatsApp number, any proof of a disruption you sent, the partner's and travel site's references for you and your order, and the copies of the messages sent to you. Purged 12 months after your pass ends: once your flights are over with no claim, your pre-loaded rescue card has closed, or the pass is refunded or cancelled. Why: to watch your flights, send your pre-loaded rescue card, answer questions or complaints about your pass, and keep the policy record Underwriter must keep. Links in emails to your pass and pre-loaded rescue card work for 12 months after your trip. The pass's record, its payments, the terms and Privacy Notice it was sold under, and what you agreed to (the boxes you ticked, and when) are kept without your other details.
• Updates sent to a partner about your pass, with its reference for you. Purged 180 days after they're sent. Why: to send them again if they didn't arrive, and to answer the partner's questions.
• What you write to help@underwriter.getthere.now or privacy@underwriter.getthere.now, and the answers. Purged 12 months after the last message in the conversation, once it has been answered or closed, but not before the copies of the messages sent to you (stages 3 and 4). Why: to answer you, and any follow-up, with what you wrote at hand.
• A complaint in Underwriter's register. Kept 7 years after it was resolved, even once your other details are purged. If you ask us to delete your data, what you said and what was done are removed, and only the dates, what it was about, the outcome and any payment stay. Why: the register is the record Underwriter keeps of how it handled complaints, for its regulator.
• Your email address. Purged once none of the above is kept.
• The record of GetThere's looks and changes: who looked up your details or changed something about your pass, and when. Names, email addresses and phone numbers are left out of what it notes they sent. Kept 7 years, then deleted. The internet address and browser the person at GetThere used are removed after 12 months. Why: so every look at your details and every change can be checked, for as long as complaints, disputes and audits can come up.
• A coded form of a number that asked for no more WhatsApp, with when: a one-way code that tells us the number said STOP, from which the number can't be read back. Kept until you ask for WhatsApp again, even after your other details are purged. Why: so a number that said STOP is never messaged again.
• Payment and pre-loaded rescue card records are kept for as long as the law requires.

The hosting provider keeps database backups for up to 7 days, so a purged detail is gone from every backup 7 days after it was purged. Service logs, which can record an email address or a page visited, are kept for up to 30 days.

When a detail is purged here, the copies the providers hold go too, as far as they allow. The messaging provider's copies of the WhatsApp messages sent to you are deleted. The email provider keeps the emails it sent or received for 45 days, then deletes them. The payment provider and the card issuer keep their records of a payment, a pre-loaded rescue card and its identity check for as long as the law requires them to.

What stays without your details: anonymous figures, such as the flight and the price, to improve pricing, and a count of offers and prices. When an airline's email is seen for the first time, a copy with the travellers' names, booking reference and contact details removed is kept until the service has learned to read it.

8. Your choices and rights

You can ask for a copy of your data, to correct it, or to delete it, by writing to privacy@underwriter.getthere.now. Depending on where you live, you may also have the right to object to some uses, to withdraw consent, or to complain to your privacy regulator. To stop WhatsApp messages, reply STOP to one of them.

Forward a booking only if you are a traveller on it or have the travellers' agreement to share their details.

9. Cookies

These pages don't use cookies for tracking or advertising. The pre-loaded rescue card page keeps one cookie on a device where its code was entered, for 30 days, so the code isn't asked for again there. It holds no personal details.

10. Changes

A change to this notice is posted at https://underwriter.getthere.now/privacy.html with a new version. The version shown when you bought a pass is kept with it.