Map My ItineraryGet the app

Privacy Policy

Last updated 15 November 2026

Who we are

Map My Itinerary: Trip Planner (the app) and the website at https://mapmyitinerary.com (the website) are operated by Apptractive Pty Ltd (ABN 37 627 379 800), an Australian company with its registered office at 3/79 O'Donnell Street, North Bondi NSW 2026. In this policy, “we”, “us” and “our” mean that company.

We are bound by the Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs). This policy explains what personal information we collect, why, who we disclose it to, where it is held, and how to access, correct or delete it. It applies to the app, to the website, and to the public trip pages the app can publish on the website.

Questions about this policy go to privacy@mapmyitinerary.com.

What we collect, and why

Your account

When you sign up we create an account for you in Amazon Cognito. It holds your email address and a password, and, if you choose to give them, your given and family name, your profile photo, and your locale (the language and region your device reports). We do not ask for a phone number. We use your email address to send a 6-digit verification code, to reset your password, and to send the account emails described below. If you turn on multi-factor authentication, codes come from your authenticator app.

If we offer sign-in with Apple or Google and you use it, Apple or Google sends us your name and email address (or, with Apple, a relay address if you hide your email). We use them to create or match your account. We do not receive your Apple or Google password.

Before you sign up (guest mode)

You do not have to tell us who you are to use the app. Guest mode needs nothing from you. Your device is given an anonymous identifier, and trips you make as a guest are stored against that identifier, either on your device or on our servers in the same place as everyone else’s trips, depending on the app version. They are not linked to a name or an email address, because we do not have one for you yet. If you sign up, the app joins your guest trips and any purchase you made as a guest to your new account, and deletes any copy left on the device.

An account needs a working email address, because that is how we verify it, reset a password, send invitations and send receipts. Your name and profile photo are optional and you can use any name you like. Inviting someone to a trip, restoring a purchase and buying an itinerary all need an email address.

What you put in a trip

Your itineraries and everything in them: destinations, flights, accommodation, car hire, transport and activities, dates and times, place names and map coordinates, booking references, costs and budgets, who paid for what, your notes (including photos you embed in them), your checklists, and places you save to a wishlist. If you invite someone to a trip, we record that you and they are on that trip together and who invited whom.

If you store frequent-flyer or loyalty programme details in the app, we hold the programme name and membership number against your account. The app shows only the last four digits.

Photos and documents you attach

Photos you attach to a stop, and PDFs or images that arrive by email (see below), are stored in Amazon S3 in a private folder tied to your identity. We do not ask you to upload identity documents such as passports. Store only what you are comfortable storing.

Sensitive details in a trip

Some things you put in a trip can say something sensitive about you: a medical appointment, a place of worship, a political event, or a dietary or accessibility note in a booking email. We do not ask for any of this and we do not treat it differently from the rest of your trip. It is stored, processed and shown back to you as ordinary trip content. If you put it in a trip, you are asking us to hold it for you, and you can delete it at any time. If you would rather we did not hold it, leave it out of the trip or the email you forward.

Booking emails you forward

Each trip has its own private inbound email address ending in @docs.mapmyitinerary.com. If you forward a booking email to it, we receive the whole message: sender, subject, body and every attachment, and we record which address it came from against the booking it produced. Booking emails routinely contain your full name, booking references, seat and room numbers and payment summaries, so forward only what you want stored. See how forwarded email is processed below. Anyone who knows the address can send items into that trip (they cannot read it), and you can reset the address at any time. Because of that, we sometimes receive things nobody asked for. A message from someone who is not a member of the trip is not processed at all, the raw message is deleted after 30 days either way, and if something arrives that we would not have collected ourselves we delete it.

Links you share into the app

When you share a web link or text into the app, or paste a link, we receive the link and any text sent with it. We use the link to fetch that web page and extract a place or booking from it. See how link import works below.

Purchases

If you subscribe or buy a lifetime unlock in the app, the App Store or Google Play takes the payment. We receive your account identifier, which products you hold and when they expire. We never receive your card details. If you buy an itinerary on the website, Stripe takes the payment and we receive your email address, the name you gave at checkout, the amount, currency and tax, and a reference for the payment.

Your device

If you allow notifications, we store a push notification token for your device so we can send trip alerts, and on iOS a Live Activity token so the lock screen can show your next leg. If you allow location access, the app uses your position on the device only, to centre the map and show where you are. Your location is not sent to us or to anyone else, and we keep no history of where you have been. The app asks for camera or photo library access only when you add a profile photo or attach a photo; we receive only what you choose to add. The app does not record audio; the microphone permission it declares is not used by any feature today, and location is never used in the background.

On iOS the app keeps a small copy of your next travel leg and today’s plan on the device so widgets and Live Activities can show it. That copy stays on your device and is cleared when you sign out.

How you use the app

We record product analytics: which screens are opened and which actions are taken (for example “paywall viewed” or “link import added”), tied to your account identifier, together with basic device details (operating system and version, device model, app version and a device identifier). We do not record the content of your trips in analytics. There is no analytics switch in the app today. If you would rather we did not record analytics about you, email privacy@mapmyitinerary.com and we will ask Mixpanel to delete the profile and events tied to your identifier and stop keeping them for your account. We also keep standard server logs (request times, error messages and IP addresses) to run and secure the service.

The app also uses Google Analytics for Firebase to tell which of our own Google Ads campaigns led to an install or a subscription. It records when the app is first opened, sessions, screens viewed, and purchase and subscription events, with an app-instance identifier, your account identifier (or an anonymous identifier before you sign up), basic device details and an approximate location that Google works out from your IP address. The app does not read your device’s advertising identifier. If you would rather Google did not keep this data, email privacy@mapmyitinerary.com and we will ask Google to delete the analytics data tied to your identifier.

Emails and notifications we send you

Most of what we send is transactional: a verification code, a password reset, a trip invitation, a receipt, or a reply telling you why a forwarded booking was not imported. You cannot turn those off while you have an account, because they are how the service works. We do not run a marketing mailing list today. If we ever start one we will ask you to opt in first, and every message will carry an unsubscribe link. Push notifications are opt-in on your device, and you can turn each category off in Settings or turn them all off in your device settings at any time.

The website

See cookies and the website below for what the website itself collects.

How forwarded emails and documents are processed

This is the part of the product most worth reading carefully, because it involves automated systems reading your travel documents.

  1. You forward a booking email to your trip’s address. Amazon SES receives it and writes the raw message, attachments included, to a private Amazon S3 bucket. Messages over 10 MB, and attachments other than PDF, JPEG, PNG and TIFF, are ignored.
  2. Attachments are sent to Amazon Textract, which converts the document into text. If there is no attachment, the email body is used as the text.
  3. That text is sent to Amazon Bedrock, running the Amazon Nova Lite model, which picks out the flight, stay, car hire, transport or activity details and returns them as structured data.
  4. The extracted details are added to your trip marked for your review, and the attachment is saved against the stop. Nothing is booked, paid for or sent on your behalf, and no decision about you is made from it. Extraction can be wrong: always check it against the original booking.

Textract and Bedrock are Amazon Web Services products used here as processors on our behalf. Textract runs in the same region as the rest of the service. Bedrock uses Amazon’s US inference routing, so a single request may be handled in any of Amazon’s United States regions. The raw forwarded messages are automatically deleted 30 days after they arrive. The extracted details and the saved attachment stay in your trip until you delete them.

Forwarding is a paid feature and is processed only when the trip’s owner holds an active subscription. Someone who is not a member of the trip and emails its address gets no reply and their message is not processed.

We do not use computer programs to make decisions about you that could significantly affect your rights or interests. Automated systems pull booking details out of emails and links, suggest stops, and, when you connect one, let an AI assistant act for you; you review the results.

Trips you share with other people

You can invite someone to a trip by entering their email address. If they already have an account, we email them an invitation. If they do not, we create an account for them from that address and Cognito emails them a sign-in invitation, which names you and the trip. By inviting someone you are giving us their email address, so only invite people who expect it. An invitation does not sign them up to any marketing.

Everyone on a trip can see the whole trip: stops, costs, notes and attached documents. Members see each other’s first name (or the invited email address until they join) and role. A member with edit access can also forward bookings to the trip’s inbound address.

You can also subscribe to a trip as a calendar feed. The feed link contains a token and works without signing in; anyone holding the link can read the schedule until you reset it in the app.

If your name, email address or booking details are in someone else’s trip and you do not have an account with us, you can still ask us what we hold about you, ask us to correct it, or ask us to remove it. You do not need an account to ask. Email privacy@mapmyitinerary.com and tell us which trip or booking it relates to. We may check the facts with the person whose trip it is, but we do not need their permission to act on your request.

Connecting an AI assistant

You can connect your account to an AI assistant, such as Claude (made by Anthropic) or ChatGPT (made by OpenAI), and ask it about your trips or have it change them. Connecting your own account is up to you. When you connect, you sign in with us and choose one level of access: Read only, Read and edit, or Read, edit and share (which also lets it invite and remove people and publish trips).

When you ask the assistant something, it asks us for what it needs and we send it, within the access you chose. That can include your trips with their stops (including booking references and flight details), costs, who paid and who owes whom, checklists and notes; details taken from booking emails forwarded to a trip, and the type of each attachment; a trip’s forwarding address, public page link and group chat link; your email address, name, bio, language, notification settings and wishlist, and your frequent-flyer numbers (the last four characters, as the app shows them, or in full when you ask the assistant for a number); and, on a trip you share, the first names and roles of the other travellers, what each of them paid and owes, the names and suggestions of guests on the trip’s group link, and what each of them added. Member lists never include other travellers’ email addresses, but an email address or other personal detail someone typed into a trip is sent like any other text, and so is the address you give when you ask it to invite someone. It never receives your photos or files, your calendar link or your password.

Trips can hold sensitive details, such as health, religious or political information (see “Sensitive details in a trip” above). A connected assistant receives them like the rest of the trip. Leave them out of trips you use with an assistant, and do not put identity document numbers, card details or passwords in a trip.

This is a disclosure you ask us to make, and it goes to the assistant’s provider. The provider is not one of our service providers. It handles what it receives under its own terms and privacy policy, or under your organisation’s agreement with it if you use a work account, and its retention and training settings may differ from ours. For Claude and ChatGPT, the sign-in screen names the provider and links to its privacy policy before you agree. If you connect another app, such as one on your computer, it sends what it reads to whichever AI company runs its model, so check that company’s privacy policy first.

The provider may hold what it receives outside Australia, mostly in the United States. When you allow the connection, you agree to us sending your information to that provider overseas, and the sign-in screen tells you that, because we cannot make the provider follow the Australian Privacy Principles, APP 8.1 will not apply to what we send about you. For other travellers’ information on trips you share, we remain responsible for that disclosure under the Privacy Act. Only connect an assistant you are comfortable sharing your trips with, including what other travellers added to trips you share.

If someone else on a trip you are on connects an assistant, it can see your first name, what you added to that trip, and what you paid and owe, as they can, even if you have not connected one yourself. Guests who make suggestions through a trip’s group link should know the same applies to their name and suggestion. Leaving the trip does not remove what you already added, which stays part of the trip, and nothing can recall what an assistant already received. Email privacy@mapmyitinerary.com if you want something of yours taken out of a trip.

For each connection we keep your email address, which assistant it is, the access you chose, when it was connected and last used, and its sign-in to your account, stored encrypted. We delete that record when the connection ends, and cancel its sign-in. We also keep a list of what each assistant did: the action, whether it worked and a short description without the content of your trips. Each entry is deleted automatically 90 days after the action; the database can take a few more days to clear it. Records that stop a change being applied twice hold only identifiers and are deleted after about 30 days.

You can lower a connection to read-only, or disconnect it, in the app at any time: Profile, Settings, Connect Claude or ChatGPT. A connection also ends 30 days after it was last used, when the assistant’s app tells us you removed it, when you reset a forgotten password, and when you delete your account. Removing the connector in Claude does not tell us, and ChatGPT may not either, so disconnect it in the app too. Ending a connection stops further access. It does not delete what the provider already received; ask the provider for that.

Who we disclose your information to

We use the following providers to run the service. We disclose to them only what each one needs.

Each provider is bound by its own terms and privacy policy and may hold data outside Australia (see the next section). We may also disclose information where the law requires it, to a regulator, to establish or defend a legal claim, or to a buyer of our business if we are acquired, in which case this policy continues to apply. We do not sell your personal information. Apart from measuring our own ads with Google as described above, we do not disclose it to third parties for advertising. Selling a trip is different, and it is your decision: what goes to a buyer is set out under “When you sell or buy a trip”.

Some booking links in the app are affiliate links (Booking.com via Awin, Viator, DiscoverCars, and Skyscanner via Impact). If you follow one, the provider knows you arrived from us, receives the search you asked for (place, dates, number of travellers) and a reference made of the trip id, and we may earn a commission on a booking you make. We do not send them your name, email or account identifier. What you do on their site is covered by their privacy policy, not this one.

Your information is held overseas

We are based in Australia, but the service runs in Amazon Web Services’ us-east-1 region in the United States. Your account, your trips, your uploaded photos and documents and the emails you forward are all stored and processed there, not in Australia.

The other providers named above (OpenAI, Stripe, RevenueCat, Google, Mixpanel, Expo and Apple) also operate outside Australia and may hold or process your information in the United States or elsewhere.

This is an overseas disclosure under Australian Privacy Principle 8. We do not ask you to consent to it. Running the service outside Australia is a decision we made, so we stay accountable for what our overseas providers do with your information, as APP 8.1 requires. Before we use a provider we check that it publishes its security practices, and we contract with it on terms that include data-processing commitments. You should know that overseas providers are not themselves bound by the Australian Privacy Principles and are subject to the laws of the countries they operate in.

An AI assistant you connect is different: it is not one of our providers, and we send it your information only because you ask us to. When you allow the connection, we tell you that the provider may hold your information outside Australia, mostly in the United States, and that APP 8.1 will not apply to what we send about you, and you agree to that. For other travellers’ information on trips you share, we remain accountable under the Privacy Act. See “Connecting an AI assistant” above.

When you publish a trip to the web

Publishing is entirely your choice, it is off until you turn it on, and only the trip’s owner can turn it on: a collaborator who can edit the trip cannot publish it. Publishing produces a page on this website at a long, unguessable web address that anyone holding the link can open without signing in.

A published page includes:

A published page never includes:

The published page is built by a single piece of code that names every field it is allowed to copy, so a field added to your trip later cannot leak onto the page by default. Published pages are not indexed by search engines unless the trip is listed for sale, and you can switch indexing off for any page. Anyone with the link can open a published page, and it may be read by third parties, including search engines and AI systems, which we do not control. You can unpublish a page or reset its link at any time. Unpublishing deletes the published copy and the page stops working immediately. It cannot, however, undo a copy someone already made or a screenshot they already took.

When you sell or buy a trip

If you sell a trip (selling is currently by invitation), the buyer receives a private copy that contains more than the public page does. As well as the stops, dates and times, that copy carries your notes on the trip and on each stop (including photos embedded in notes), the titles and amounts of your costs, and flight details including airline, flight number and stopovers. Read your notes before you list a trip: anything personal you left in them goes to every buyer.

What the copy does not carry is your identity or your files. Buyers do not receive your email address, your phone number, your uploaded photos or documents, your budget, or the names of anyone else on the trip. The seller is not told who bought their trip.

If you buy a trip on the website, we create an account for you from the email address you give at checkout (or use your existing one), copy the itinerary into it, and email you a receipt with a sign-in link. That link works once and expires after 72 hours; the QR code on the confirmation page expires after 15 minutes. We keep a record of the purchase (your email, the name you gave Stripe, the amount, currency, tax and the Stripe reference) for as long as tax and accounting law requires.

Accessing, correcting and deleting your information

Correcting it yourself

Most of what we hold is editable in the app. Your name, email, photo and locale are in your profile; every trip, stop, cost, note, checklist and attachment can be edited or deleted from the trip it belongs to. Notification categories are under Settings.

Deleting your account

In the app, open your Profile, go to Settings and choose Delete account. If you cannot reach the app, email privacy@mapmyitinerary.com from the address on the account and we will do it for you.

Deleting your account immediately removes your sign-in, your profile and your membership of every trip. It also deletes the trips only you are on, with their stops, costs, notes, checklists, invites and any page you published; every photo and file you uploaded, including ones in trips you share; your notifications and link-import counter. It ends every AI assistant connection and deletes its record; the list of what each one did is deleted within 90 days. We also ask Mixpanel to delete your analytics profile. The same steps are on our delete your account page.

A trip with other travellers is not deleted. If you own it, it passes to another traveller on it and any page you published for it is taken down. Stops, notes and costs you added to a shared trip stay in it, because they are part of everyone’s plan; email us if you want something of yours taken out of it. Some things necessarily outlive the account: records of purchases and billing, including the record RevenueCat holds of your store purchases, which we keep for tax and accounting purposes and so that a lifetime purchase can be restored; a copy of any trip you sold that a buyer already owns, which is now their own itinerary; and continuous backups, which age out within 35 days. Deleting your account does not cancel an App Store or Google Play subscription, so cancel it in the store first.

Asking for a copy of your information

You can ask us for access to the personal information we hold about you, for a copy of it in a portable format, or to correct it, by emailing privacy@mapmyitinerary.com. We will ask you to verify that the account is yours. We will respond within 30 days, and we do not charge for a request. If we refuse access or a correction, we will tell you why in writing and how to complain.

Complaints

If you think we have mishandled your personal information, email privacy@mapmyitinerary.com and tell us what happened. We will acknowledge your complaint and respond within 30 days.

If you are not satisfied with our response, you can take the complaint to the Office of the Australian Information Commissioner (OAIC), the regulator for the Privacy Act 1988.

How long we keep things

Your account and your trips are kept until you delete them or delete your account. We do not expire trips you have finished travelling.

The raw booking emails you forward are the exception: they are deleted automatically 30 days after they arrive. Only the details and attachments extracted into your trip remain after that.

How your information is protected

Traffic between the app, the website and our servers travels over HTTPS, and the AWS storage behind it encrypts data at rest. Signing in is handled by Amazon Cognito, and you can turn on multi-factor authentication in the app. API keys and secrets are held in a secrets manager, not in the app.

Photos and documents you upload are stored under a folder tied to your own identity, which only your account can read. They are not attached to a published page and are not included in a trip you sell. Email arriving at a trip inbox is accepted only over an encrypted connection. Published pages and calendar feeds are protected by long random tokens; whoever holds the link can read them.

This is not end-to-end encryption. We hold the keys, and our own systems read your content in order to work; reading a forwarded booking email is the whole point of that feature. No online service can promise perfect security, and we do not.

If there is a data breach

If personal information we hold is lost or accessed without authorisation and that is likely to cause you serious harm, we will notify you and the OAIC as the Notifiable Data Breaches scheme in the Privacy Act requires, and tell you what happened and what to do.

Cookies and the website

The website sets no cookies for its own pages. Two things can set them:

Videos embedded in blog posts are loaded from YouTube’s privacy-enhanced domain, which sets no cookies until you play the video. The website also reads your browser’s user-agent to send you to the right app store from the download page; it is not stored.

Children

The app is built for adults planning travel and is not directed at children. We do not knowingly collect personal information from anyone under 13, and in the UK and the EEA we do not knowingly hold an account for anyone under 16 without a parent’s or guardian’s permission. We do not show ads in the app. If you are a parent or guardian and you believe your child has an account or is in someone else’s trip, email privacy@mapmyitinerary.com and we will delete what we hold.

If you are in the UK or the European Economic Area

Apptractive Pty Ltd is the controller of your personal information. We process it on these legal bases: to perform our contract with you (running your account, trips and purchases); our legitimate interests in running, securing and improving the service (analytics, measuring our own advertising, logs, fraud prevention); your consent, which you can withdraw at any time (push notifications, location access, the reset reminder); and our legal obligations (tax records, responding to lawful requests).

When you connect an AI assistant, we send it what it asks for, within the access you chose, to perform our contract with you. When it reads a trip you share, it also receives other travellers’ first names and what they added; we do that on the basis of our and your fellow travellers’ legitimate interest in planning a shared trip with the tools each of them chooses. If you are on someone else’s trip, you can turn on Hide my name from others’ AI in the app (Profile, Settings, Connect Claude or ChatGPT), and their assistants then see you as “Traveller”. You can also object by emailing privacy@mapmyitinerary.com. What you added to a trip is still sent with it; to stop that, leave the trip or take out what you added, and we will help you do that. The assistant’s provider is not our processor. Depending on your account with it, it acts as a separate controller, or as your organisation’s processor if you use a work account.

You have the right to access, correct, delete and receive a copy of your information, to restrict processing, to object to processing we base on legitimate interests, including analytics (email us and we will stop Mixpanel analytics for your account and ask Google to delete your Firebase analytics data), to withdraw consent without affecting what we did before, and to complain to your local data protection authority. You do not need an account to make a request. Email privacy@mapmyitinerary.com to exercise any of them. Where the law requires it, we tell the people we disclosed your information to about a correction, deletion or restriction.

Your information is transferred to the United States and other countries as described above. For our own providers, where a provider is not in a country with an adequacy decision, we rely on the standard contractual clauses in our agreement with it. An AI assistant you connect is not one of our providers: we send your information to it because you ask us to. In the UK, the EEA and Switzerland that is generally the provider’s European company (for Claude, Anthropic Ireland, Limited), which decides where it processes it. You can ask us for details of the safeguards we rely on. No decision with legal or similarly significant effects on you is made by automated means.

If you are in California

We do not sell your personal information. The app sends Google Analytics for Firebase usage and purchase events so we can measure our own Google Ads campaigns, as described above. California law may treat that as sharing for cross-context behavioural advertising. You have the right to know what personal information we collect, to delete it, to correct it, and not to be discriminated against for exercising those rights. The categories we collect are listed under “What we collect” above. Email privacy@mapmyitinerary.com to make a request; we will verify it against the account. You can also use an authorised agent to make a request for you; we will ask for proof that you authorised them. When you connect an AI assistant, we send it information because you direct us to; that is not a sale or sharing. We offer these rights to anyone who asks, whether or not the California law applies to us.

Changes to this policy

When we change what we do with your information, we update this page and the date at the top. If a change materially affects you, we will tell you in the app or by email rather than relying on you to re-read this page.

Contact us

For anything in this policy, including access, correction, deletion or a complaint, email privacy@mapmyitinerary.com, or write to Apptractive Pty Ltd, 3/79 O'Donnell Street, North Bondi NSW 2026. Our Terms of Use set out the agreement for using the service.