Privacy Policy
Last updated 27 October 2026
In short
Jiola plans trips. To do that it keeps the account you sign in with, the trips you make, whether you have an active subscription, and a short record of when you were shown the subscription screen and whether you then started a trial or subscribed, together with the test group your account is in while we compare two versions of the app. It also keeps a usage record of what you do in the app, described under “Analytics and advertising” below.
It reads your device's location only when you tap to use it — on the Map tab, to plan a hangout near you, or for nearby suggestions — and never stores it. It opens your photo library only when you ask it to build a scrapbook, and only after iOS has asked your permission. It contains no third-party analytics, no advertising and no crash-reporting service, and it has no advertising identifier. The usage records it keeps for itself are described under “Analytics and advertising” below.
This policy describes the version of the app you are reading it in. It was written from the app's own source code rather than adapted from an earlier version of Jiola.
Your account
You can sign in with an email address and a password, or with Sign in with Apple or with Google.
If you sign in with an email address, we hold that address and the display name you choose. The password itself is handled by our authentication provider and is never visible to us.
If you sign in with Apple or Google, that provider tells us who you are and may pass along the name and email address held on your account there. Apple lets you hide your real address and pass on a relay address instead; if you do, the relay address is all we ever receive.
The app reads your display name to greet you and your email address to show you which account you are signed in to. It does not read a profile picture, a phone number, a birthday, a contact list or anything else from your provider.
Your trips
A trip holds what you put in it: its title, its dates, the destinations you chose, how you plan to get around, and for each stop its name, its place, its arrival time, how long you plan to stay and any note you write on it, and for each night, where you are staying, whether you told the app you booked it (when, and on which booking site), and a confirmation number if you typed one.
Trips are stored on our servers so that they survive reinstalling the app and follow you to another device. They are stored against your account and the database is configured so that a trip can only ever be read, changed or deleted by the account that owns it.
We also look at totals across all trips, such as how many trips go to each city, to understand where travelers go and to improve the app. These totals never name you or show anyone's trip.
When you ask the AI planner for a plan, our server sends what you entered to Anthropic, and looks up places for the plan with Google, Apple's map service and Wikipedia (see “Who your information reaches”). To apply daily limits and subscriptions, our server counts your plan requests by account. The searches it runs for the cities in your plan, and whether each place has a free photo, may be kept in shared caches (searches for up to 90 days, photo results for up to 30 days); they aren't linked to your account. A city's shared place list may also appear on the Map tab for everyone, but only after at least five different people have planned that city; to count them, we keep a tally that does not record who planned it or when. If you save the plan, it's stored like any other trip, including how you'll get around. Jiola doesn't save your note, your pace, the styles you picked, your arrival and departure times or who's traveling to your account, and none of these go into those caches. The plan's title and descriptions are written by the AI model and may reflect your note; if you save the plan, they're saved with it.
A trip made by the AI planner is also stored with a random save identifier. The app makes it up for that one trip, and it is not linked to your device or to anything outside the app. It is there only so that, if saving the trip has to be tried again, the trip is not stored twice.
You can delete any trip from inside the app. Deleting it removes the stored trip.
Location
When you use the nearby-suggestions option in a stop's Guide tab, the app reads your device's location once, when you tap, to pick a starting point. It is sent to our server only to generate that suggestion and is not stored. Our server passes it to the AI model that writes the suggestion; neither stores it.
Apart from this, the app reads your location only when you tap the locate button on the Map tab or choose Near me for a hangout; both are described below. The app never follows you in the background, never records where you have been, and never asks for location on its own — only when you tap one of these options. iOS asks your permission the first time and you can refuse; if you refuse, those options cannot use your location, the Map tab still works, and nothing else in the app changes.
Maps and coordinates elsewhere in the app are about places, not about you. When you search for a place, the search is answered with that place's coordinates; when a trip shows a map, it is drawn around the stops in that trip. If a search is narrowed to an area, the area is the region your trip is about, except on the Map tab, which is described in its own section below.
Location on the Map tab
When you tap the locate button on the Map tab, Jiola asks your device for your location once. It uses that location to center the map and to search for places near you.
To find nearby places, Jiola sends our server, and through it Google, a search area about 5 km across, centered on your location. As you type a search, Jiola also sends the words you type and the map area on screen to Apple's map service so that it can suggest places; after you tap the locate button, that area is centered on your location. While the Map tab is open and zoomed in, Jiola also tells our server which map square the middle of the map falls in — a square about 5 to 10 km across, never a more exact point. Our server uses it to show recommended places from Google for that square and the squares around it, keeps one shared copy per square for up to 30 days, dated only by the day, and doesn't link it to your account. For Pro subscribers, if we don't have that square yet and there aren't already enough places to show, our server asks Google for places in an area around it (about 12 to 15 km across), sending nothing about you.
Jiola doesn't save your location to your account or your device, and it never reads your location until you tap the button.
If you don't allow location access, the Map tab still works. It starts at your next trip's destination, at a major city in your region (guessed from your device's time zone and language settings), or at a view of the whole world.
Saved places and lists
When you save a place, Jiola stores it on your account so you can see it on any device where you sign in.
For each saved place we store the place's Google ID, name, address, map coordinates, rating and number of ratings, place types, the trip city you saved it from (if any), and when you saved it.
We don't store photos, reviews, or opening hours. You can remove any saved place at any time, with or without a subscription. When you delete your account, all your saved places are deleted with it.
If you make lists of your saved places, Jiola stores each list and the name you give it on our servers with your account. When you delete your account, your lists and their names are deleted with it.
Hangout
When you ask for a hangout plan, you either type a place or choose Near me. If you choose Near me, Jiola asks your device for your location once, when you tap. It never reads your location before that, and it doesn't save it to your account or your device.
Jiola sends the place you typed, or your location, to our server together with how long you have, when you want to start, how many people are going, the vibes and filters you picked, any note you write, your app language, and your device's time zone (used to work out times).
Our server rounds your location to about 1 km and sends it to Google to search for places nearby. If you picked the Drinks filter, our server keeps only the places Google lists as bars, pubs or wine bars. It then asks Anthropic's AI model to choose a few of those places and suggest how long to spend at each.
Anthropic receives the place you typed (if any), your vibes, your other filters, how many people are going, your note, your language, your time window and the list of places. It never receives your location itself, but if you chose Near me, every place on that list is close to you, so the list shows roughly what area you're in.
Your note is sent to Anthropic as you wrote it, so leave out anything you'd rather not share. Jiola doesn't save your note, group size or filters to your account, and they never go into the shared search cache. The plan's title and short descriptions are written by the AI model and may reflect your note; if you save the plan, they're saved with it.
We don't send your name, your email address, or your account identifier to Google or Anthropic.
To apply daily limits and subscriptions, our server counts your hangout requests by account. If you typed a place, that search may be kept in a shared search cache for up to 90 days; it isn't linked to your account.
Saved hangouts
When you save a hangout, Jiola stores that plan on your account: the places in it (their names, Google IDs, categories and map coordinates), the times and the travel times between them, a short title, and the notes the plan came with.
We don't store photos or opening hours, and we never store your starting point or your location. Because the places are near where you asked from, a saved plan does show roughly that area.
You can delete a saved hangout at any time. When you delete your account, all your saved hangouts are deleted with it.
Photos
The scrapbook lays your own travel photos onto a trip, and to do that the app opens your photo library. iOS asks your permission the first time, and you can refuse. If you refuse, nothing is read, and every other part of the app carries on exactly as before.
What the app reads from a photo is the location and the time your phone already saved with it when you took it. When a scrapbook is built from an existing trip, those two things are compared to that trip's stops, on your device, and nothing about the photo ever leaves your phone. When a scrapbook is built from photos alone, with no trip behind it, the app instead works out one approximate point for each day — the center of where that day's photos were taken, rounded to two decimal places, about a kilometer — and sends only that point to Apple's map service so that it can put a name to the area. No photo, no part of a photo, and no photo identifier is ever part of that request, and at most 15 of these requests are sent for one scrapbook. Either way, no photo is sent to our servers, no photo is uploaded anywhere, and no model is ever shown a picture.
To hand over that information, iOS also gives the app a small preview image of each photo. For each photo you put into a scrapbook, the app keeps a small copy on this phone so the scrapbook can show it. Neither the previews nor those copies are ever sent anywhere.
If you allow that trip-matching route access to selected photos only, rather than to your whole library, it gets none of them, and the scrapbook will tell you it received no photos; nothing else in the app changes. Building a scrapbook straight from photos, with no trip behind it, is a separate route and is not affected by that choice: it opens iOS's own photo picker, which shows you your own photos and hands the app only the ones you tap, nothing more, and because of that iOS never asks you for photo library permission on this route at all. Backing out of that picker hands over nothing, and nothing else in the app changes either.
Jiola saves a page you made to your Photos only when you tap Save; the page is made on your device and never uploaded.
Separately from any of this, the photographs you see beside places are pictures of those places, fetched for you when a screen needs them. They are not yours and they are not uploaded by you.
Subscriptions and payment
Subscriptions are sold through the App Store. Apple takes the payment. The app never sees your card, your billing address or your Apple ID.
We use RevenueCat, a subscription service, to tell the app whether your subscription is active. RevenueCat receives an identifier for your account, the purchase information Apple gives it and, while we compare two versions of the app, the label of your test group. It tells us in return whether you are subscribed, which product you bought, whether it began as a free trial, the price and currency you paid, the store, the purchase's transaction numbers, whether it was shared through Family Sharing, and when it renews, expires, is cancelled or is refunded. We keep these purchase records, linked to your account, for up to 90 days, and delete them when you delete your account. Separately, the app itself records in our own database when the subscription screen was shown to you, which part of the app it was opened from, and whether you then started a free trial or bought a plan, with that plan's price and currency, and, when you tap to buy, that you started a purchase and for which plan. That is what we store about your subscription in our own database. When the subscription screen is shown, the app also tells RevenueCat that it was shown, so that we can count how often it appears and compare versions of it. This is sent with the same identifier for your account, so it is linked to your account.
If you subscribe and later want to stop, you manage and cancel the subscription in your Apple account, not here — the app links you to the right page.
Identifiers
Your account has an identifier that our servers use to know which trips and which subscription are yours. The same identifier is what we give the subscription service, so that the two agree about who you are.
Separately, the app makes a random code on this phone the first time it opens and uses it only for the welcome-page entries described under “Analytics and advertising”. It is not your account identifier, it is never sent together with it, and it stays on the phone until you delete the app.
The app has no advertising identifier, does not ask for permission to track you, and does not link you to anything you do in other companies' apps or on other websites.
As with any service reached over the internet, our servers see the network address a request arrives from. It is used to keep the service from being abused, and is not used to build a profile of you.
To apply our Fair Use Policy and protect the service from abuse, our server keeps, for each account, a running total for the current month of what the requests you make cost us to serve (for example map searches, photos, routes and AI requests). It is used only for that, is kept for up to 2 months, and is deleted with your account.
Who your information reaches
These are every outside company the app sends anything to, and exactly what each one gets.
When you ask for a plan, we send the destination you typed, the number of days, the start date if you picked one, your answers to the planning questions (how you will get around, your pace, the styles you picked, your arrival and departure times if you gave them, and, on your first plan, who is traveling), any note you typed (up to 200 characters), and the language you are reading in. When you open a stop's guide, or ask for suggestions near a stop, we also send that place's coordinates and its name — and, if you chose the option that starts from where you are, your device's location instead. We do not send your name, your email address or your account identifier, and once the plan is made we don't keep your note or your answers, apart from what a trip you save holds (see “Your trips”). When you ask for a hangout plan, we send the place you typed (if any), your vibes, how many people are going, your note, the filters you picked other than Drinks, your language, your time window and the list of places to choose from — never your location, your name, your email address or your account identifier.
When you search for a place, we send the text you typed, the language you are reading in, and — if the search is narrowed to a region — that region's boundaries. On the Map tab, after you tap the locate button, that region is a search area about 5 km across, centered on your location. When you ask for a hangout near you, our server rounds your location to about 1 km and sends it to Google to search for places nearby. When you ask for a plan, our server searches Google for places in the cities the plan covers, such as sights, restaurants and hotels. If your note names a place you want to visit or a hotel you're staying at, our server sends just that name to Google to find it, and then asks Google for that place's details; your note itself is never sent to Google. We do not send your name, your email address or your account identifier. Separately, when you tap a navigation button and Google Maps is the map app you picked, your phone opens a Google Maps link carrying the coordinates of the stop you are heading to — and, for a whole day's route, the coordinates of the places on that route, in order. Your phone opens that link itself; nothing about you travels with it and nothing comes back to us. Likewise, when you tap “Reserve a table” on a restaurant outside the United States, or on one the app cannot tell is in the United States, your phone opens Google Maps with that restaurant's name and Google's own identifier for that place (or, when the app has no identifier, its name and the address saved with it). Nothing else about you or your trip is sent, and nothing comes back to us. As with opening any website, Google's servers see the network address the page is requested from. When a Pro subscriber opens a place on the Map tab and we have no introduction to it yet, our server may ask Google for a short introduction to that place, sending only Google's identifier for it; that introduction is kept in a shared cache for up to 30 days and isn't linked to your account.
When the app draws the route between two stops on your plan, we send those two stops — each one either as Google's own identifier for that place, or, when we do not have one, as its coordinates — together with the way you chose to travel between them. Stops are sent two at a time, from our servers rather than from your device, and only for pairs we do not already have a saved route for. We do not send your name, your email address, your account identifier, your device's location, or the dates of your trip. When the AI planner builds a plan that moves between cities, our server also asks Google for the travel time between the centers of those cities, by their coordinates, for driving and, unless you chose to drive, for public transport too; these answers aren't kept.
Maps in the app are drawn by Apple's map service, which receives the map area being drawn, and travel times between your stops are worked out by the same service from the coordinates of those stops. When you type in a search field, the words you type go to the same service as you type them, together with the map area on screen (after you tap the locate button on the Map tab, an area centered on your location), so that it can suggest places; a city name you type is also looked up there, so that the map can move to it. When you tap one of Apple's own places on the Map tab, the map asks the same service for that place's name, category and address, so Apple learns which place this device asked about; the answer is only shown, never kept. While the Map tab is open and zoomed in, the map also sends the same service the middle of the map on screen, rounded to about 100 meters (after you tap the locate button, that is near your location), so that it can list the places it knows around that point; these answers are only shown and are not kept. When you tap a navigation button and Apple Maps is the map app you picked, your phone opens an Apple Maps link carrying the coordinates of the stop you are heading to. Your phone opens that link itself; nothing about you travels with it and nothing comes back to us. When the AI planner builds a plan, our servers, not your device, also ask this service for travel times between the cities in it, using the coordinates of their centers, and, if needed, for an airport near a city, using the city's name and the coordinates of its center. Nothing about you is sent with these requests, and the answers are used for that one plan and not kept. Separately, when a scrapbook is built from photos alone, with no trip behind it, we send this same service one approximate point for each day — the rounded center of where that day's photos were taken, never a photo, an image, or a photo identifier — so that it can tell us the name of the area; at most 15 of these requests are sent for one scrapbook.
The App Store takes the payment for a subscription and confirms the purchase.
Our servers and our database run on Supabase, so your account, your trips, your saved places and lists, your saved hangouts, and the subscription-screen record and usage record described under “Analytics and advertising” are stored there on our behalf.
To find a free photograph for the places in a plan, our servers look those places up on Wikipedia and Wikimedia Commons by their names and map coordinates. Whether a photograph was found, and which one with its credit, is kept in a shared cache for up to 30 days (up to 7 days when none was found), so that the next plan with the same place doesn't ask again; it isn't linked to your account. Where a place's photograph comes from Wikimedia Commons, your device loads that image from Wikimedia directly rather than through us. As with loading any image from any website, Wikimedia's servers see the network address it is requested from. We send them nothing about you. When you open a place on the Map tab, our server may also look that place up on Wikipedia by its name and map coordinates, to show the opening section of its Wikipedia article with credit and a link to it; what was found, or that nothing was, is kept in a shared cache for up to 30 days (up to 7 days when nothing was found) and isn't linked to your account.
Receives an identifier for your account, your purchase information from Apple, a note each time the subscription screen is shown to you and, while we compare two versions of the app, the label of your test group. It tells the app whether your subscription is active.
Only when you tap an Expedia button in your plan, your phone opens Expedia's website with a search. For a hotel in your plan, one the app suggests for your trip, or one you're looking at for your trip, the search carries its name and the address saved with it; for a city in your trip (“Where to stay”, “Find a place to stay” or “Find another place in <city>”), it carries the city's name. Your check-in and check-out dates go with it when the app has them, and so does the number of travelers you set for the trip when it is 1 to 8. The link may carry our own partner code, which tells Expedia the visit came from Jiola and says nothing about you. Nothing else about you or your trip is sent, and nothing comes back to us. As with opening any website, Expedia's servers see the network address the page is requested from. From there, Expedia's own privacy policy applies.
Only when you tap an Agoda button in your plan, your phone opens Agoda's website with a search. For a hotel in your plan, one the app suggests for your trip, or one you're looking at for your trip, the search carries its name and the address saved with it; for a city in your trip (“Where to stay”, “Find a place to stay” or “Find another place in <city>”), it carries the city's name. Your check-in and check-out dates go with it when the app has them, and so does the number of travelers you set for the trip when it is 1 to 8. The link may carry our own partner code, which tells Agoda the visit came from Jiola and says nothing about you. Nothing else about you or your trip is sent, and nothing comes back to us. As with opening any website, Agoda's servers see the network address the page is requested from. From there, Agoda's own privacy policy applies.
Only when you tap a Booking.com button in your plan, your phone opens Booking.com's website with a search. For a hotel in your plan, one the app suggests for your trip, or one you're looking at for your trip, the search carries its name and the address saved with it; for a city in your trip (“Where to stay”, “Find a place to stay” or “Find another place in <city>”), it carries the city's name. Your check-in and check-out dates go with it when the app has them, and so does the number of travelers you set for the trip when it is 1 to 8. The link may carry our own partner code, which tells Booking.com the visit came from Jiola and says nothing about you. Nothing else about you or your trip is sent, and nothing comes back to us. As with opening any website, Booking.com's servers see the network address the page is requested from. From there, Booking.com's own privacy policy applies.
Only when you tap an Agoda, Booking.com, Expedia or Vrbo button in your plan, the link may go through Stay22, a service that sends you on to that booking site. Your phone first opens Stay22's website with the search the button carries: for a hotel in your plan, one the app suggests for your trip, or one you're looking at for your trip, its name and the address saved with it; for a city in your trip (“Where to stay”, “Find a place to stay” or “Find another place in <city>”), the city's name; your check-in and check-out dates when the app has them; the number of travelers you set for the trip, when it is 1 to 8; our own partner code; and a fixed label saying the visit came from Jiola and which part of the app the button was in (for example, “Where to stay”). Neither the code nor the label says anything about you. Stay22 then sends you on to the booking site you tapped, sometimes through one of Stay22's own partners, with that search. Nothing else about you or your trip is sent, and nothing comes back to us. As with opening any website, Stay22's servers see the network address the page is requested from. From there, Stay22's own privacy policy applies, and then the booking site's.
Only when you tap a Vrbo button in your plan (the search for a whole home), your phone opens Vrbo's website with a search for a city in your trip: it carries the city's name. Your check-in and check-out dates go with it when the app has them, and so does the number of travelers you set for the trip when it is 1 to 8. Nothing else about you or your trip is sent, and nothing comes back to us. As with opening any website, Vrbo's servers see the network address the page is requested from. From there, Vrbo's own privacy policy applies.
Only when you tap the Airbnb button for a whole-home search in your plan, your phone opens Airbnb's website with a search for that city. Your check-in and check-out dates go with it when the app has them, and so does the number of travelers you set for the trip when it is 1 to 8. The link carries no partner code of ours, and nothing else about you or your trip is sent; nothing comes back to us. As with opening any website, Airbnb's servers see the network address the page is requested from. From there, Airbnb's own privacy policy applies.
Only when you tap a Trip.com button in your plan, your phone opens Trip.com's website with a search. For a hotel in your plan, one the app suggests for your trip, or one you're looking at for your trip, the search carries its name and the address saved with it; for a city in your trip (“Where to stay”, “Find a place to stay” or “Find another place in <city>”), it carries the city's name. The link may carry our own partner code, which tells Trip.com the visit came from Jiola and says nothing about you. Nothing else about you or your trip is sent, and nothing comes back to us. As with opening any website, Trip.com's servers see the network address the page is requested from. From there, Trip.com's own privacy policy applies.
Only when you tap “Reserve a table” on a restaurant in the United States, your phone opens OpenTable's website with a search for that restaurant's name and its city. Nothing else about you or your trip is sent, and nothing comes back to us. As with opening any website, OpenTable's servers see the network address the page is requested from. From there, OpenTable's own privacy policy applies.
Some place information and photographs come from Google. Where the app shows them, it shows Google's mark alongside, as Google requires.
Analytics and advertising
The app contains no third-party analytics service, no crash-reporting service, no advertising service and no advertising identifier, and it does not track you across other companies' apps or websites.
It keeps two records of its own. The first is about the subscription screen. When you are signed in and the subscription screen is shown to you, the app writes an entry to our own database, linked to your account: that the screen was shown, which part of the app it was opened from, and whether you then started a free trial or bought a plan, with the plan, its price and currency, and the version of the app you were using, and, when you tap to buy, that you started a purchase and for which plan. While we compare two versions of the app, it also writes an entry when your test group first applies to you (see below), with the version of the app you were using.
We use that record only to improve the subscription and what it includes, for example by comparing two versions of the app. It is not sold, not used for advertising and not shared with anyone. It is deleted when you delete your account.
When we compare versions of the app, your account may be placed in one of up to four test groups. This happens the first time you open the app, or the first time you see the subscription screen, while that comparison is running. The group is picked at random and doesn't change for the rest of that comparison. Depending on what we're comparing, your group decides which version of a screen, a feature or the subscription screen and its plans you see, or which Journal features for making new books, pictures and videos need a subscription. Books already on your phone can always be read and shared, in every group. We store your group in our own database, linked to your account, along with the record above, the time your group first applied to you, and the version of the app you were using. We delete it from our database when you delete your account. A copy is also kept on your phone. It's removed when you sign out or delete your account, or when the app next checks in and finds the comparison has ended; otherwise it stays until you delete the app. Your group's label may also be sent, linked to your account, to RevenueCat, the service that handles subscriptions. Deleting your account doesn't remove it from RevenueCat's records.
The second is a usage record. While you are signed in, the app notes which screens you open and which buttons you tap, using fixed labels for them, and when you use its main features: when an AI plan starts, finishes (with how long it took and how many stops it has) or fails; when you search (only the kind of place and whether anything was found, never what you typed); when you open the map or a place, save or remove a place, make a list, create, change or delete a trip, add where you're staying, tap a booking link or tell us whether you booked, see or close the subscription screen, open or export your journal, share something, or open a notification; and a short code when something goes wrong. Each entry is stored in our own database, linked to your account, with the version of the app, a random code for that app session and the time.
Before you sign in, while you go through the welcome pages, the app notes which pages you see, how long you stay on each, which of the offered answers you pick, such as your home region (never anything you type), the page you were on if you leave the app, and whether you reach the sign-in page. These entries carry a random code that the app makes on this phone the first time you open it, the language you're reading in and the version of the app. That code is not linked to your account and is never sent together with it, the entries don't record when you sign in, and their times are kept only to the hour.
The usage record never includes anything you write (notes, trip or list names, photos), what you type into a search, place names, addresses, your location or your network address. We keep each entry for 90 days; after that, only daily totals remain, which hold counts and no account or code. Entries linked to your account are deleted when you delete your account. Welcome-page entries can't be found by account, so they are removed only when their 90 days are up. Like the record above, the usage record is not sold, not used for advertising and not shared with anyone.
Apart from these records, and the note sent to RevenueCat when the subscription screen is shown to you (see Subscriptions and payment), nobody is sent a note of which screens you opened or what you tapped.
Notifications
The app can set a reminder before a free trial ends. That reminder is scheduled by your own phone, from your phone, and nothing is sent to it from our servers.
It is only scheduled if you allow notifications. If you do not, nothing is scheduled and nothing else changes.
What stays on your phone
Some things are kept on the device itself: whether you have been through the introduction and how far you got in it, which language you are reading in, the answers you are part-way through giving while you plan a trip, your signed-in session (which includes your email address and your display name), the scrapbooks you have saved, a copy of your trips so that you can still read them offline, any trip that could not be saved to our servers at the moment it was made, and the subscription service's own record of your account identifier and your subscription status (see “Subscriptions and payment”).
A saved scrapbook holds, when it is made from an existing trip, that trip — its title, its dates, and one page for each day. When it is made from photos alone, with no trip behind it, it holds no trip: just its own date range and one page for each day, each one also naming the area that day's photos were taken in. For each photo you chose, it holds the location and the time your phone saved with it, a copy of the photo itself kept on this phone, and an identifier for that photo — the one your phone's photo library uses, when the scrapbook is made from an existing trip, or one the app makes up itself, when it is made from photos alone, because the picker used for that route never hands over a library identifier.
Scrapbooks and their photo copies are kept only on this phone and aren't tied to your account. If someone else signs in to Jiola on this phone, they can see the scrapbooks made here. Deleting a scrapbook, or deleting your account in the app, removes them.
If you start making something from a scrapbook in Make, your unfinished draft — the photos you swapped in, the size and any words you typed — stays on this device so you can come back to it. Deleting that scrapbook, or your account, removes it.
For each scrapbook, this device keeps the look you chose for its page-flip video and the pages you left out of it. The video itself is made on your phone and is saved only where you put it.
When a trip cannot be saved to our servers at the moment it is made, that one trip is kept on this phone instead, so that it is not lost: the trip itself, the name of its destination, the date it starts on, how you chose to get around, the account it was made under, the time it was made, and the random save identifier described under “Your trips”. The app tries to save it again the next time you open the app, or when you tap retry, and removes it from the phone once it has saved. Only the most recent such trip is kept. Signing out does not remove it, so that it is not lost: it is only ever saved to the account it was made under, and another account signed in on this phone sees at most a note that a trip from another account is waiting, never the trip itself.
So that your trips can still be opened without a connection, the app keeps a copy of each of your trips on this phone: the whole trip, including your notes, and the time the copy was made. The copies are filed under your account and are only shown to that account: while it is signed in, and, when the phone cannot reach our servers, to read without editing for the account last signed in on this phone. If that account was signed out somewhere else, the copies stay readable here until the phone next reaches our servers. They are refreshed whenever your trip list loads while you are online, and a trip you delete is removed from them. Signing out does not remove them; deleting your account does.
The first time you tap a navigation button, the app asks whether you would rather open Apple Maps or Google Maps, and the phone remembers which map app you chose so that it does not ask again. That is the whole of what is kept: the name of one of the two, and nothing about where you were going. Press and hold the navigation button to change it.
If you are offline, the notes and checklist ticks you make are kept on this phone until you reconnect, and are then sent to your account. If you change only a stop's note and saving it fails, for example because your connection drops, that note is kept the same way. Only those edits are kept this way — not the rest of the trip — and they are removed from the phone as soon as they have been sent. If you sign out or delete your account before they have been sent, they are discarded.
The questions in the introduction are kept here too, if you answered them: the options you picked and the date you picked them, and nothing you typed. They stay until you build your first trip from them or clear them yourself; signing out, deleting your account or removing the app removes them.
If the app has asked you to rate it, it remembers here that the question was put to you, so that it is only ever put once. That is the whole of what is kept: that it was asked. Whether you answered, and what you said, are between you and the App Store — the app is not told, and does not keep it. Deleting your account does not clear this, so that signing up again does not mean being asked a second time.
The search field remembers the last 8 searches you submitted, exactly as you typed them, on this phone only (running a search still sends it to our server), until newer searches replace them or you sign out, delete your account or remove the app.
So that your trips and the places in them open faster, the app also keeps a cache on this phone: copies of place photos (the ones you have looked at, and the ones of the stops in a trip you opened, fetched ahead so that they appear quickly), and whether each of those places has a free photo, for up to 30 days; and the public-transport and scooter travel times and routes between your stops, for up to 90 days (an answer that two stops have no public-transport route, for up to 7 days). Walking and driving times are not kept. The cache holds at most 100 MB and drops the oldest first. It is not uploaded anywhere, and signing out or deleting your account removes it.
If the app cannot finish clearing these things when an account signs out, it notes on this phone which account still needs clearing (the account identifier and nothing else) and finishes the job the next time the app opens or a different account signs in. The note is removed once the clearing is done, or when that same account signs in again.
While we're comparing two versions of the app (see Analytics and advertising), the app also keeps on this phone which test group your account is in, your account's identifier, and whether your group has been recorded. This is removed when you sign out or delete your account, or when the app next checks in and finds the comparison has ended; otherwise it stays until you delete the app. The app also notes, once, whether this phone already had a book on it when the comparison could first begin. Phones that did are left out of comparisons of Journal features. This note isn't linked to your account and stays on the phone until the app is deleted.
While we compare versions of the app, your test group and which compared settings you have already been shown are also kept on this phone, until you sign out. Usage entries and purchase records that could not be sent yet wait on this phone for at most six days, are sent only for the account that made them, and are deleted when you sign out.
The app also keeps on this phone the random code it uses for the welcome-page record (see Identifiers). It isn't linked to your account; signing out or deleting your account doesn't remove it, and it stays until you delete the app.
Removing the app removes all of it.
Your choices
You can delete any trip from inside the app.
You can sign out at any time.
You can change or turn off the notification and photo permissions in your phone's Settings, and it takes effect immediately.
You can delete your account from inside the app. Deleting it removes the account and the trips, saved places and saved hangouts stored against it, and clears from this phone the scrapbooks you saved, any planning answers you had part-finished, the introduction answers, the copies of your trips kept for reading offline, any notes and checklist ticks you made offline that had not been sent yet, any trip of yours that was still waiting to be saved, and your recent searches.
Contact and changes
If this policy changes, the updated version appears here, on this page, inside the app.
To ask about anything in this policy, or to ask what we hold about you, write to: