Effective 13 September 2026. Replaces the version dated 11 September 2026.
Scope of this policy.
This policy explains what personal data Plan4Me (“we”, “us”) collects, the purposes for which that data is used, and the choices available to you. It applies to the Plan4Me mobile application and to this website. Plan4Me is the controller of the personal data described in this policy. Plan4Me is operated from Australia, and the service is offered worldwide. We do not limit it to a list of countries: the app is available in every country where the App Store and Google Play distribute it, and this website is open to anyone. The sections below on your rights, on complaints and on sending data overseas name the laws and regulators we are most often asked about. They are examples, not a limit. If a privacy law applies to you where you live, it applies to us in respect of your data. You can reach us at support@plan4me.ai.
Information we collect.
- Account details. Your email address, name, optional avatar and password, which is stored only as a salted hash. If you sign in with Google, Apple or Facebook, we receive your name, email address and an account identifier from that provider. We never receive the password for your social account.
- Travel preferences. Interests, travel pace, budget level, preferred transport, who you usually travel with, and any dietary restrictions or accessibility needs you choose to add. We also learn some of these from what you do in the app, as the section on learning from what you do explains. Please see the section on sensitive information below.
- Content you create. Trips, itineraries and day plans, notes, expenses and budgets, saved places and share links.
- Videos you save. When you share a TikTok video or an Instagram Reel to Plan4Me, or paste its link, we keep the link with its tracking parts removed, the platform, the video’s ID, any note you add, and our own short analysis of the video. The analysis is a title, a one sentence summary, the destination, the places the video names and up to three interests. We do not keep the video, its caption, its creator’s name or its thumbnail. The section on saved videos below explains how this works.
- Travel assistant conversations. Messages you exchange with the AI assistant, retained so that your conversations have context and history.
- Location. Your device location, collected only if you grant the system permission. It is used to show nearby places, to power the live day view, and to let the travel assistant answer questions about places near you. When it goes with a chat message, it is rounded to about 100 metres and it is not stored with the message, as the section on AI processing below explains. You can revoke the permission at any time in your device settings, and the app continues to work without it.
- Payment data. Everything you buy is bought inside the app. On iOS, Apple handles the purchase as an in-app purchase. On Android, Google handles it through Google Play billing. Stripe no longer sells anything: it only keeps running the subscriptions that were bought through it before we moved to the stores. We store your subscription tier, a customer or transaction reference from the processor and your credit balance. We never store your card number.
- Device and usage data. Basic device and app version information, IP address and server logs, used to operate, secure and debug the service, to enforce fair usage limits, and, when an account is created, to look up the approximate location of the IP address so we can see where new accounts come from and tell app-store test devices from real people.
- Push notification tokens. If you allow notifications, the operating system gives us a token that identifies your app installation. We store it against your account so that we can send you a notification, for example when a trip finishes generating. Turning notifications off in your device settings stops it being used.
- Advertising and measurement data. Cookies and similar identifiers set on this website, your device advertising identifier where you allow it, the identifier of the ad or campaign you arrived from, and a hashed copy of your email address used to match a signup or a purchase back to an ad. The section on advertising and measurement below sets out exactly which identifiers are involved and who receives them.
- Support correspondence. Any information you send to support@plan4me.ai.
- Website waitlist, now closed. The waitlist closed when Plan4Me launched. This site no longer offers it and we no longer collect signups. For the people who did join we still hold the email address they entered, the date they joined, the form they used, their browser user agent string and, where they answered it, the optional question about where they heard about us. That question offered a fixed list of choices rather than a text box, so it captured nothing beyond the one channel picked. Where the Meta pixel or the OpenAI ads pixel was running, the same record also holds an event identifier and the ad click identifiers those platforms use: Meta’s
_fbpand_fbccookie values, and OpenAI’sopprefclick reference. They existed so that one signup counted in the browser was not counted a second time when we reported it from our server. The record also holds a salted hash of the IP address and the country that address was in. We used the hash to limit how many signups one address could make in a day, which is how we stopped bot floods, and the country to understand where interest came from. We never stored the raw address. To work out the country we sent the address to ipapi.co, which returned the country code and nothing else. The retention section below says how long we keep these records.
Sensitive information.
Dietary restrictions and accessibility needs can reveal information about your health, disability or beliefs. Providing this information is entirely optional. If you choose to add it, we use it solely to tailor your itineraries, for example by suggesting suitable restaurants or accessible routes, and we protect it in the same way as the rest of your data. You can remove it at any time in your preferences. Please do not enter sensitive information about other people into trips, notes on saved videos or conversations without their agreement.
How we use your information.
We use your data to create and personalize itineraries; to operate the features you use, such as budgets, day plans, offline mode and sharing; to process payments and manage subscriptions; to provide support; to keep the service secure, prevent abuse and enforce usage limits; to measure our own advertising, as described in the next section; and to meet our legal obligations.
Where the GDPR or similar laws apply, our legal bases are these. Performance of our contract with you covers most of the processing needed to run the service, including reading a video you ask us to save and using the choices you make when you generate a trip to fill in your next one. Consent covers location data, optional sensitive preferences, and every advertising or analytics identifier read from or written to your device. Legitimate interests cover security, fraud prevention, debugging and keeping the service working, and learning your interests from the videos you save. You can object to that learning at any time by turning off Learn from saved videos in your preferences, and we then stop. We do not rely on legitimate interests for advertising or analytics identifiers. Legal obligation covers tax and accounting records.
We do not sell personal data, and we do not show advertising from other companies inside the app or on this site. We do advertise Plan4Me itself, which means we measure how our own ads perform. The next section explains what that involves.
Advertising and measurement.
We advertise Plan4Me on Apple Ads, on Meta, on Google and in ChatGPT, and we measure what those ads produce. That involves third party advertising and measurement services. These are the ones we use:
- Google Analytics 4. Traffic measurement on this website. It sets cookies in your browser and receives your IP address.
- Google Ads. Advertising in Google Search and app install advertising, and conversion measurement for them on this website. Google receives the fact that a visit or a tap on an app store button happened. This site no longer collects an email address, so no hashed address is sent from it.
- Meta. The Meta pixel on this website. Meta receives the fact that a visit happened, along with the identifiers listed below. We no longer send a matching report from our own server: the only event that used the Meta Conversions API was a waitlist confirmation, and the waitlist is closed. The mobile app contains no Meta advertising code. It uses Facebook only for the optional sign-in button.
- OpenAI. The OpenAI ads pixel on this website, which measures advertising shown in ChatGPT. It receives the fact that a visit or a tap on an app store button happened, along with the click reference described below. This is separate from our use of OpenAI models to build itineraries, which is described further down.
- Apple Ads. Advertising on the App Store. Apple tells us which campaign produced an app install, in a form Apple controls and aggregates.
- Singular. A mobile measurement partner for the app. It receives install and in-app conversion events, including the device advertising identifier where you have allowed it, and attributes them to the ad that produced them.
Not all of these run at every moment. Where one is not switched on, no data reaches it.
The identifiers involved are these:
- Cookies. On this website Google Analytics sets
_gaand a per-property cookie named after the property, which together tell repeat visits apart. Where the Meta pixel is running it sets_fbpand reads_fbc, which records the ad click that brought you here. Where the OpenAI ads pixel is running it stores a click reference namedopprefin a cookie called__oppref, which records that you arrived from an ad in ChatGPT. Google Ads conversion tracking sets_gcl_au, which records the ad click that brought you here. - IP address. Your browser or device sends it to these services with every request it makes to them. It is used for approximate location and for fraud checks.
- Device advertising identifiers. On iOS this is the Identifier for Advertisers (IDFA). We can only receive it if you allow tracking in the App Tracking Transparency prompt that iOS shows you. If you decline, we do not receive it and we do not track you across other companies’ apps and websites. On Android this is the Google advertising ID. The app declares the
AD_IDpermission and our measurement partner Singular reads the identifier to attribute an install to an ad. You can stop this at any time by deleting the advertising ID in your Android settings, as described in the next section. The app also creates its own installation identifier, which names your install to Singular and to us. It is not shared with other companies and it is not tied to any identifier your device gives out. - A hashed email address. When you subscribe, we may send a SHA-256 hash of your email address to an ad platform so that it can match the conversion to the ad you saw. The plain address is not sent in that request. While the waitlist was open we did the same for a signup.
A hashed email address is still personal information. Hashing keeps the plain address out of the request, but the platform can hash the copy of your address it already holds and match the two, which identifies you. This is the position the Office of the Australian Information Commissioner takes, and we take it too. Hashing is not anonymisation, and we treat a hashed identifier with the same care as the address itself.
Booking partner links carry a similar identifier. Where the app shows a link to a booking partner such as Trip.com or GetYourGuide, the link includes a hashed identifier derived from your Plan4Me account identifier, so the partner can report a completed booking back to us. The partner receives that hash and the trip context in the link, such as the city and dates being searched, but not your name, your email address or the account identifier itself. The identifier is stable, so the same account produces the same hash each time, and everything this section says about hashed identifiers applies to it. The tap that opens a partner link is also counted as an in-app event by our measurement partner Singular. Our affiliate disclosure explains how these links work.
We use this data for two purposes, and they are not the same thing:
- Attribution and measurement. Working out which ad, campaign or channel led to a visit, a tap on an app store button, an app install or a paid subscription, how many of each there were, and what each one cost us. This is the main reason any of this exists.
- Audience building and retargeting. Where we run it, asking a platform to show Plan4Me ads to people who have already visited this site or used the app, or to people the platform considers similar to them. We never upload your trips, itineraries, saved places or assistant conversations for this or for any other advertising purpose.
In the European Economic Area and the United Kingdom, storing information on your device or reading information from it requires your consent, whatever the technology. Article 5(3) of the ePrivacy Directive says so, and the European Data Protection Board confirmed in its Guidelines 2/2023 that this covers pixels, tracking links, software development kits and device identifiers, not only cookies. So we ask first. On this website, the banner shown on your first visit is that request. Refusing takes the same single click as accepting, and until you accept, the website identifiers above are not set. The app works differently, and we would rather say so plainly than imply otherwise. The app shows no banner. On iOS it asks through the App Tracking Transparency prompt, and declining stops the IDFA reaching us. On Android the measurement code starts with the app and reads the advertising ID, and the way to stop it today is to delete the advertising ID in your Android settings, as described above. We are building an in-app consent step to close that gap. Consent is the legal basis for all of it. We do not treat advertising or analytics identifiers as a legitimate interest.
Your advertising and cookie choices.
You can withdraw consent at any time, and withdrawing it is as easy as giving it. Nothing else about the service changes if you do.
On this website. Your choice is stored in your browser under the key p4m_consent in local storage, and it applies to that browser on that device. Use these controls to change it. Clearing site data for this site also clears the choice, after which you are asked again.
Checking your current choice.
On your device. On iOS, open Settings, then Privacy and Security, then Tracking, and turn tracking off for Plan4Me or for every app. On Android, open Settings, then Google, then Ads, and delete the advertising ID. Both stop the advertising identifier from reaching us or our measurement partners. You can also reset the identifier, which breaks the link to everything recorded against the old one.
In your browser. You can delete cookies for this site at any time in your browser settings, and you can install Google’s Analytics opt-out browser add-on to stop Google Analytics on every site that uses it. Google and Meta each publish their own ad settings, where you can limit how they personalise ads to you.
Marketing email. Every marketing email we send carries an unsubscribe link, and one click is enough. You can also email support@plan4me.ai and ask us to stop. We will not ask you for a reason, and there is no charge. If you ask us where we got your address, we will tell you.
AI processing.
Plan4Me itineraries and the travel assistant are powered by large language models. To generate a plan or answer a chat message, we send the relevant trip details, such as your destination, dates, preferences and messages, to our AI provider, which today is OpenAI. If you have allowed the app to use your location, a chat message also carries your approximate location, with the coordinates rounded to about 100 metres, and the name of the area you are in, such as the city, region and country. This lets the assistant answer questions about places near you. Your location is used only to answer that message. We add it to what we send OpenAI for the reply, and we pass the area name to OpenAI’s web search. We do not store it with the message and we do not write it to our server logs. The reply itself is saved with your conversation like any other, including any nearby places it names. If we add or change a model provider we will name it here. We send only what the model needs. When you use the travel assistant or Plan My Day, that includes the name on your account, so the assistant can address you by name. We do not send your email address or your password. Under our API agreements these providers do not use your data to train their models. OpenAI keeps what we send it, including an approximate location, for up to 30 days to run the service and detect abuse, unless the law requires it to keep it longer. Responses are generated by AI. Please treat them as suggestions rather than verified facts, and avoid entering personal information into conversations when it is not needed for planning. When you save a video, we send OpenAI the video’s caption, with the creator’s name, username and any @mentions removed, and your note, without your account identity. We ask OpenAI not to store these requests. OpenAI says it may still keep them for up to 30 days to check for abuse, or longer if the law requires it.
Videos you save from TikTok and Instagram.
You can share a TikTok video or an Instagram Reel to Plan4Me from the share sheet, or paste its link in the app. A shared link waits on your device until you next open Plan4Me, and then the app sends it to us. Saving is always your choice. We do not look at anything else in TikTok or Instagram, and we do not connect to your accounts there.
Reading a TikTok video. Our server asks TikTok for the video’s public details through TikTok’s embed service. TikTok returns the caption and the creator’s name and username. We remove the creator’s name, username and any @mentions, and send the rest of the caption and your note to OpenAI, which returns our analysis. We keep the analysis. We do not keep the caption.
Reading an Instagram Reel. Instagram’s embed service does not give us a Reel’s caption, so we do not read it. If you add a note, or paste the caption into your note, we read that instead. Without a note we keep the link and show the Reel, but we cannot suggest places from it.
What we keep. The link with its tracking parts removed, the platform, the video’s ID, your note, and our analysis: a title, a one sentence summary, the destination, the places the video names and up to three interests. Captions can name other people. We do not keep captions, and we ask the model not to put people’s names in its analysis. If you paste a caption into your note, we keep your note as you wrote it.
Playing a video. The app shows a saved video with TikTok’s or Instagram’s own embedded player. The player comes from them, not from us. When it loads, TikTok or Instagram receives your IP address and basic device details and may set cookies, under their own privacy policies. The player loads only when you tap to play.
Places. We list the places a video names. A place is added to your saved places only when you tap Save. To find the right place we look it up with Google, as we do for other places in the app.
What we learn. When a video is about travel, we note up to three interests from it, such as food or nightlife, and show them on the video. They join the interests we learn from what you do, described in the next section.
Learning from what you do.
Plan4Me learns some of your preferences so you have less to type. When you generate a trip, we note the interests, pace, budget and transport you pick, and whether you travel alone or with children, from the number of travellers you enter. When you save a video about travel, we note up to three interests from it. We use what we learn to fill gaps in your preferences and to suggest trips and places. What you set yourself in your preferences always comes first. Learned values never replace it.
Recent activity counts more than old activity. Each signal counts for half as much after about 90 days, and less after that. It stays stored until you clear it or delete your account. If we hold more than 50 values of one kind, we drop the weakest ones. We never learn dietary needs, accessibility needs or other sensitive information. Those come only from you.
You can see what we noted on each saved video. In your preferences you can clear everything we have learned, and you can turn off learning from saved videos. Turning it off changes nothing else in the app.
Automated decisions.
Plan4Me builds itineraries automatically. A large language model chooses places from a candidate list, and our own code ranks them, orders them and sets the times, using your destination, dates, pace, budget, interests and, if you allow it, your location. These are automated processes and they decide what appears in your plan and in what order. You can change any stop by hand, regenerate a single stop or the whole trip, or ignore the plan entirely.
Reading a saved video is also automated. A model decides whether the video is about travel, which places it names and which interests it suggests. You can change the result: save only the places you want, add a note and try again, delete the video, or clear what we have learned.
Automated rules also count how many trips a free account has generated in a month, and automated checks help us detect abuse and enforce our terms. None of this produces a decision with a legal or similarly significant effect on you. We do not use automated decisions for credit, employment, insurance, housing or anything of that kind, and we do not profile you for those purposes. If an automated check ever restricts your account and you think it is wrong, email us and a person will look at it.
Australia’s Privacy and Other Legislation Amendment Act 2024 requires privacy policies to describe automated decision making from 10 December 2026. We are publishing this now rather than waiting for that date.
Service providers.
We share data with service providers only so that they can perform services on our behalf. These are the ones we name, because you either consent to them, can opt out of them, or should know who sees your trip content:
- OpenAI. Itinerary generation, the travel assistant and reading the videos you save. OpenAI also measures ads shown in ChatGPT, through the pixel on this website.
- Google. Place data, routing, maps data, optional sign-in, traffic measurement through Google Analytics 4, and advertising measurement through Google Ads.
- Meta (Facebook). Optional sign-in, and advertising measurement through the Meta pixel and the Meta Conversions API on this website.
- Apple. Optional sign-in, in-app purchases on iOS, and App Store advertising measurement through Apple Ads.
- Singular. Install and conversion measurement for the mobile app.
Five more are named because they hold or show your content: Mapbox draws the maps in the app, OpenWeatherMap supplies the forecast for your trip dates, YouTube supplies place videos in discovery, and TikTok and Instagram show the videos you save through their own players. TikTok also gives us the caption of a TikTok video you save. Stripe holds the payment records for subscriptions bought before we moved to the app stores.
Behind those sit the ordinary building blocks of any online service. We use providers for application hosting, for the database, for caching, for search, for sending the email you ask us to send, for protecting forms from bots, and for turning an IP address into a country. They only ever process data on our instructions, they do not use it for their own purposes, and none of them advertise to you. We do not list them one by one, because that list changes as we change how the service is built, and a policy that names last year’s tools tells you less than one that does not. Email support@plan4me.ai and we will tell you exactly who is on the list today.
Other disclosures.
Trips you explicitly share are visible to anyone who holds the link or invitation. We disclose data where the law requires it, or where disclosure is necessary to protect our users, the public or the service. If Plan4Me is involved in a merger, acquisition or sale of assets, data may be transferred with appropriate protections. Beyond these cases and the advertising measurement described above, we do not sell personal data and we do not share it with data brokers.
Sending data overseas.
Australian Privacy Principle 8 requires us to tell you which countries we are likely to send your personal information to. They are the United States, where most of our providers are based and where the waitlist database and our main application database are hosted, and Japan, where our application servers run. Our providers also process data in other countries in which they operate, including in the European Union and the United Kingdom. Before we disclose personal information overseas we take reasonable steps to satisfy ourselves that the recipient will handle it in a way consistent with the Australian Privacy Principles, usually through the terms of our contract with them.
Where the GDPR or UK GDPR applies, transfers out of the European Economic Area or the United Kingdom rely on the safeguards our providers offer, such as Standard Contractual Clauses, the UK International Data Transfer Addendum, and the EU-US and UK-US Data Privacy Framework where the provider is certified.
Retention and deletion.
Your data is retained for as long as your account exists. Deleting your account from Settings in the app removes your account and associated data from live systems. Residual copies in encrypted backups are removed on a rolling schedule, typically within 30 days. Revoked share links stop working immediately. Payment records are retained for as long as tax and accounting law requires. The waitlist is closed and the addresses collected for it are no longer used to send anything. We delete them on request, and we will delete the remaining records.
Saved videos stay until you delete them or your account. Deleting a saved video removes the link, your note and our analysis. It does not remove places you saved from it, and it does not undo interests already learned from it. You can clear those in your preferences. We never keep captions: they are held only while a video is read.
Analytics and attribution data is kept on a shorter clock. Google Analytics is set to delete event and user level data 14 months after it is collected, which is the longest period a standard Google Analytics property allows. The attribution records we hold ourselves, including the event and click identifiers that were stored with a waitlist signup, are deleted 26 months after the event they describe. Reports built from this data that no longer identify anyone may be kept for longer.
Your rights.
Depending on where you live, you can ask us to access, correct, delete or export your data, to restrict or object to processing, and to withdraw consent. In the EEA, the United Kingdom and Switzerland these rights arise under the GDPR. In Australia they arise under the Australian Privacy Principles. In California you have the rights to know, correct and delete personal information, and to opt out of its sale or sharing, without being discriminated against for exercising them. In Canada, including Quebec, you can ask for access to your information and for it to be corrected. Wherever you are located, email support@plan4me.ai and we will respond within the time the law allows.
To delete your account and the data attached to it, follow the steps on our delete account page. That page also explains how to delete parts of your data without closing your account, and how to ask us to do it for you if you can no longer sign in.
Complaints.
If you are unhappy with how we have handled your personal information, please contact us first at support@plan4me.ai. We will look into it and reply. If our answer does not satisfy you, you can complain to a regulator:
- Australia: the Office of the Australian Information Commissioner (OAIC).
- United Kingdom: the Information Commissioner’s Office (ICO).
- European Union: the data protection supervisory authority for the country where you live or work, or where you think the problem happened.
- Quebec: the Commission d’accès à l’information du Québec (CAI).
Your choices.
- Analytics and advertising: change your choice in the section above, or reset the advertising identifier on your device.
- Location: grant or revoke the permission in your device settings.
- Notifications: manage them in your device settings or in the app.
- Preferences: edit or remove interests, dietary and accessibility entries at any time.
- Saved videos: delete any saved video from the Videos tab in your profile.
- Learning: see what we noted on each video, clear what we have learned, or turn off learning from saved videos, in your preferences.
- Share links: revoke them at any time in the app.
- Account: delete it from Settings in the app without contacting support.
Children.
Plan4Me is not directed at children under 13 years of age, or the higher minimum age that applies in your country, and we do not knowingly collect their data. If you believe a child has provided us with personal data, please contact us and we will delete it.
Security.
Data is encrypted in transit, passwords are stored as salted hashes, and access to production systems is restricted. No system is perfectly secure. If a breach affects your data, we will notify you and the relevant authorities as the law requires.
This website.
This website runs Google Analytics 4. It sets the _ga cookie and a second cookie named after the analytics property, and it sends Google your IP address, the pages you open and a small set of events about how you use the page. Those events are: opening the waitlist form, reaching the email field, pressing the join button, joining the waitlist, closing the form without joining, reaching the pricing section, scrolling half and then most of the way down, staying on the page for thirty seconds, clicking a link that leaves the site, and two diagnostic events for when a signup fails. None of them record what you typed.
The OpenAI ads pixel receives the same list of events, so that we can see which step of the waitlist form people stop at when they arrive from an ad in ChatGPT. It stores the __oppref cookie described above. The Meta pixel runs on the same basis when it is enabled, and sets the _fbp cookie. All three sit behind Google Consent Mode v2, and in the European Economic Area and the United Kingdom nothing is fetched, stored or read until you accept.
Google Ads conversion tracking runs on the same consent basis and sets the _gcl_au cookie.
Three other features involve third parties. The waitlist form stores the email address you submit in Google Firebase, in the United States. The same form is protected by reCAPTCHA Enterprise, which reads and writes information on your device to tell a person apart from a bot. That runs whether or not you accept analytics, because without it the form is flooded, and protecting a form you chose to use is a purpose you do not have to consent to separately. It is used only for that check. Pages load the Inter typeface from Google Fonts, so your browser sends your IP address to Google when it fetches the font. The site sets no cookies other than the ones named on this page.
Changes and contact.
If this policy changes materially, we will update this page and the effective date, and we will flag significant changes in the app. Questions and requests can be directed to support@plan4me.ai.