Privacy Policy

Last updated: 28 October 2026 Effective: on first publication at https://vacayi.app/privacy

---

The short version

• We collect what a travel guide needs to be about you rather than about anyone: who is travelling, roughly how old they are, what you like, and where you are going.
• We use AI to write your guides. That means your trip details are sent to our AI providers to produce them.
• We do not sell your information, and we do not use it for advertising. There is no advertising SDK and no analytics tracker in this app.
• You can export everything we hold, and you can delete your account from inside the app. Deletion is real: it removes your guides, your uploaded images and your crew details. The one thing it cannot reach is a guide a friend built with you on one of their trips, which keeps your first name and what was written from your age range and interests (section 9a).
• Guides are private to you and the people you choose to share a trip with.
• Your location and your photos stay on your phone unless you deliberately share a photo to a trip — and even then we strip its GPS data first. The one other exception is a profile photo, if you choose to add one: your friends and the people on trips you share can see it, and it is re-saved without its location data too. Photos you put on your crew's cards are never sent to us, except the one on your own card, which is your profile photo.
• Your friends see what you choose to show them, and nothing else. With "Share my profile with friends" on, your friends see your age range and your interests beside your photo and name. Sharing your profile never includes your allergies, dietary requirements or mobility needs. You can switch it off, or stop sharing with one friend, at any time.
• Sharing your profile also lets a friend put you on one of their trips. A guide they build with you ticked is written with your first name, your age range and your interests, and a guide already built keeps what it was built with. If you agreed to the earlier wording, the app asks you once to confirm this, and until you do, no friend can add you to a trip.

---

1. Who we are

vacayi is operated by Vacayi LLC, a limited liability company formed in the Commonwealth of Massachusetts, United States.

For anything in this policy, or to exercise any right described in it, contact support@vacayi.app.

For users in the EEA or UK, Vacayi LLC is the controller of the information described here.

---

2. What we collect, and why

Everything below is collected because a feature needs it. Nothing here is collected "just in case".

2.1 Your account

2.2 Your travel crew

This is the part that makes a guide personal, and the part we treat most carefully.

We ask for an age RANGE, never a date of birth or an exact age. The guide only ever needs to know which band someone falls into, so that is all we store. The AI is never told a number either — it receives the band.

Who someone is to you stays on their crew card. It is optional for every person, and a crew with no labels works exactly as before. It is never printed in a guide — a guide will not say "your wife Maria" — and it is never sent to our AI providers as a list of labels: what the AI receives is only the shape of the group it adds up to, such as "a family of four across three generations" or "one person travelling alone". Like the rest of your crew, only you can see it; people you share a trip with cannot.

Photos on your crew's cards are never sent to us. A photo you add to a traveller's card — often a child's — is saved in the app's own storage on that phone. It is never uploaded: it is not sent to us, not shown to anyone else, and not sent to our AI providers. So it does not follow you to another phone, and a new phone shows initials until you add photos there — unless you set it up from your old phone or its backup, which can bring them back. The one card that works differently is your own (the one marked me): its photo is your profile photo, which your friends and the people on trips you share can see (2.10), and the app says so on that card. Your phone's own backup — iCloud, or Google's Android backup, which vacayi leaves switched on — may include these photos like any other app data; that backup is between you and Apple or Google, and we never receive it. Deleting your account from a phone removes that phone's copies, and removing the app removes them too.

Friends in your crew. When you and another vacayi user become friends, each of you can add the other to your Crew tab. What you see there is read-only and live: their photo, their name, and — only while they share, and only if they have not excepted you — their age range and their interests, exactly as they have them right now. Sharing a profile never includes dietary requirements, allergies, mobility needs or accessibility needs — not theirs with you, and not yours with them.

We keep no copy of what a friend shares with you for your Crew tab (the one exception is a guide you build with a friend on the trip, below): if they stop sharing, it is gone from your Crew tab the next time the tab loads. Your own phone does keep the last list it loaded, in the app's own storage, so the tab has something to show while it reloads — the same as every other screen in the app. That copy is replaced the next time the tab loads successfully — if a load fails, your phone keeps showing the last one it has — and it goes when you delete your account from that phone or remove the app. Like the photos on your crew's cards, a backup the phone has already made keeps its copy, and we never receive it.

A friend comes on a trip only when you tick them for it, and only if they allow it. A friend allows it by sharing their profile with you — the same switch, Share my profile with friends, that shows you their age range and interests. Someone who agreed to the earlier wording agreed only to being seen, so they are asked once to confirm, and until they do they cannot be ticked. When you tick a friend who allows it, that trip's guide is planned and written using their first name, their age range and their interests, the same way it uses your travellers', and those three are sent to our AI providers for that purpose (section 6) — never their photo, never your label or nickname for them, and never any dietary requirement, allergy, mobility need or accessibility need of theirs. We check that they still allow it every time that trip's guide is built, rebuilt or repaired, and if they have stopped, the next build uses nothing of theirs — not their first name, age range or interests — though a name you typed yourself, as an answer (whose birthday the trip is for, say) or in your notes, stays until you change it. A guide already built keeps what it was built with — their first name and what was written from their interests — like a printed itinerary. A rebuild does not remove it: every rebuild keeps the earlier version in the trip's history, and a copy of the trip carries its guide too. It belongs to your trip: whoever you share the trip with sees it, its PDF and its shared link carry it, and it stays until you delete the trip (and any copy of it) or your account. A friend in your crew who is not ticked is not on the trip, and removing them from your crew does not end the friendship.

A word about the free-text boxes. Notes are yours to fill and we do not police them, which means health details can end up there even though the structured fields deliberately keep them at the level of the whole party. Write what the guide genuinely needs, and leave out what it does not.

2.3 Dietary requirements, allergies and accessibility needs

Your trip carries a single list of the whole party's dietary requirements, allergies and accessibility needs — not one per person. We deliberately do not record which traveller an allergy belongs to.

This information exists so a guide does not send you somewhere you cannot eat or cannot get into. It is used to shape restaurant choices and to add reminders to your packing list.

In some places, including the EEA and the UK, this counts as health-related information and gets extra protection.

These fields are optional — every one of them can be left empty, and vacayi works without them; you simply get a guide that knows less about you. You can remove them at any time by clearing the fields, and the next guide you make will not use them.

2.4 Your trips

Destination, starting point, dates, arrival and departure times, lodging, budget, the reason for the trip, what the trip is about (up to three focuses, such as food or history), the kind of trip, and any notes you write. Plus the guides we generate for you, which are stored so you can open them again and download them for offline use.

Building the guide looks two things up in public reference pages: the name of the town around each end of your trip, and a freely licensed photograph of the place you are going, which is saved into the guide with its credit so that it still works offline. What those pages receive is the destination you typed (or the city your guide settled on) and two map points rounded to about a kilometre — never your home, never a word about where you are staying. Section 4 sets out exactly what leaves and what does not.

2.5 Images you upload

You can attach booking screenshots to a trip so the AI can read your confirmed flights and hotels.

Please read this one. A booking confirmation usually contains other people's information — a travelling companion's name, a flight number, an address. When you upload it, that information is sent to our AI providers along with everything else. Only upload what you are comfortable sharing, and consider covering anything that is not yours.

We keep them for as long as the trip exists, not just until the guide is built. That is deliberate: rebuilding a guide reads your confirmations again, so the flights and hotels you attached stay in the new one instead of being lost. They are deleted when you delete the trip, and when you delete your account.

2.6 Your messages to the assistant

When you ask the in-guide assistant a question or request a change, we store the request and the reply so the conversation is still there when you come back, and so a request survives closing the app.

We read these. Not routinely and not for advertising — but when someone reports that a guide got something wrong, that message is how we find and fix it. Please do not put anything in a chat message that you would not want a person at vacayi to read.

2.7 Purchases

Credits and subscriptions are bought through Apple's or Google's payment systems. We never see or receive your card details. We receive a confirmation that a purchase happened, an identifier for it, and which product it was, so we can add the credits to your account.

We keep a record of credits added and spent. Some of this is financial record-keeping we are required to retain even after you delete your account — see section 8.

2.8 Notifications

If you turn them on, we store a push token for your device so we can tell you your guide is ready. Preferences are per-category and you can switch any of them off.

2.9 Location

Optional, and it never leaves your phone. The guide map has a "Where am I?" button. If you use it, your device's location is drawn on the map on your device. It is not sent to us, not stored, and not shared. Decline the permission and everything else still works.

2.10 Photos you share to a trip, and your profile photo

Photos stay on your phone unless you share them. vacayi can look at when and where your photos were taken to place them in your own guide — that happens on your device, and nothing is uploaded.

If you choose to share a photo to a trip, that photo is stored on our servers so the other people on that trip can see it. What we store: a reduced-size copy of the photo, a small thumbnail, which stop and day of the trip it belongs to, and who shared it. We remove the photo's hidden location data (GPS) before it is stored — we re-encode the image, which drops it — so the trip placement is the only location-shaped fact we keep.

Who can see it: only the people on that trip — the owner and the collaborators they invited. Shared photos are never public and are never used for anything except showing them to the trip's members.

How it leaves: you can delete a photo you shared at any time, and it is removed for everyone. The trip's owner can remove any photo on their trip. If a photo should not be there, anyone on the trip can report it from the photo itself: it is hidden for them at once, and it is removed for everyone automatically — immediately if a second person reports it, and otherwise within 24 hours unless the trip's owner reviews it and keeps it. If you leave a trip or are removed from it, the photos you shared are removed with you. Deleting a trip deletes its photos; deleting your account deletes every photo you ever shared.

If you report a photo, we record that you were one of the people who reported it. We have to, in order to count reports and to stop the same person reporting twice — but we keep it somewhere nobody can read, including the person who shared the photo and including the trip's owner. It is deliberately not possible for someone to find out who reported them.

Your profile photo is a separate thing, and entirely optional. You can add one from the Friends tab, or on your own crew card. It is a small square picture stored with your account. It is re-saved on your phone before it is sent, which drops its hidden location data (GPS), just as a photo shared to a trip is.

Who can see it: you, your friends, and the people on trips you share — a trip's owner and everyone it is shared with. You become friends when one of you accepts the other's friend request, or when one of you uses the other's friend code: a friend code makes you friends at once, so give yours only to people you want as friends. The app says so where you share your code, and tells you when someone uses it. The app shares a trip only with a friend, but anyone who has a trip's invite code can join it, and then sees the names and photos of the people on it. No one else who uses vacayi sees your photo: search results and friend requests show your initials, it never appears in a guide, a PDF or a share link, and it is never sent to our AI providers. A person at vacayi may see it while looking into a report about it (below).

How it leaves: remove it at any time and it is gone for everyone, and deleting your account deletes it. It is also taken down if two of your friends report it (below).

Blocking and reporting. From the Friends tab, or from the people on a trip you share, you can block or report someone.

• Blocking someone ends any friendship or friend request between you, stops requests between you, and stops a friend code working between you, and an invite code to a trip either of you owns. It also hides each person's photo from the other everywhere, even on a trip you are both still on, where your names still show; a block does not take anyone off a trip. They are not told, and only you can undo it.
• Reporting someone's photo hides that photo from you at once. If two of their friends report the same photo, it is taken down automatically, and the app tells them; a report from anyone who is not their friend never counts toward that. You can also report a name, spam or unwanted requests, or something else.
• Every report reaches our support queue, so a person at vacayi can look at it. Nobody is told who reported them. We record who made each report, so we can count reports and act on them, somewhere nobody else can read.

2.11 What you tick off, and what you save for later

Your progress through a guide. Ticking a stop, a packing item, a quest or a booking is stored so it is still ticked on your other devices and, on a shared trip, so the people you are travelling with can see what is done. We also count these in aggregate — what fraction of a guide's stops get ticked — to judge whether guides are actually useful. That counting is about guides, not about people.

Your idea list. Places and ideas you save for "one day", with whatever note, tags and destination you add. If you save one by sharing a link from TikTok, Instagram, YouTube or Facebook, we store that link, and the post's caption is sent to our AI provider once so it can work out which place you meant. We do not follow you on those platforms and we receive nothing else from them.

2.12 Working on a trip with other people

If you share a trip, the people on it produce a shared record together, and we store it: comments, checklist items, reactions, and an activity feed of what changed and who changed it. Each of those carries who wrote it, because a shared list nobody is accountable for is not much use.

We also store, for you alone: which trips you have starred, when you last looked at a trip, and whether you have muted its notifications.

Live presence. While you have a shared trip open, the other people on it can see that you are there — and, so that two people do not unknowingly edit the same thing, that you are typing or editing. This is sent live to the other people on that trip and is not stored: it disappears when you close the trip, and a few minutes of silence turns it into "active a few minutes ago". Only people you have shared the trip with ever see it.

2.13 When you contact us

If you send a support message or report a mistake in a guide, we store what you wrote, the address you want a reply at, and a small technical snapshot taken at that moment: your app version, platform and operating system, your language and region, whether you were offline, and your credit balance. It is there so the first reply can be an answer rather than five questions.

If you rate a guide or tell us what went wrong with it, we store that too — it is the main way we find out that something is broken.

2.14 Records the app keeps so that it can work

Two of these are worth naming because they are copies of things you might expect to exist only once:

• Undo history. Every change to a guide — yours, the assistant's, and the automatic repairs we run — stores the guide as it was immediately before, so the ↩ Undo button can put it back. Automatic repair snapshots are deleted after 30 days; snapshots of changes a person made are kept with the trip.
• Earlier versions of a guide, kept so a rebuild does not destroy the one you had.

We also keep a cached translation of a guide when a collaborator reads it in another language, the short "crafting" messages shown while a guide is being built, and records of each build for cost and reliability. All of it is deleted with the trip or the account.

2.15 Features you tell us you want

Some choices in the app are marked coming soon — today a wedding trip, an event trip, visiting family and camping. Tapping one shows a short note and records, once, that you tapped it: your account, which feature, and when. Tapping it again changes nothing. We use it to count how many people want each feature, so the most wanted is built first. It is not used for anything else, it is not shared with anyone, and it is deleted with your account.

---

3. What we do NOT do

Stated plainly because these are the things people most often assume:

• We do not sell your personal information, under any definition, including the California CCPA/CPRA definition of "sale" or "share".
• We do not show you advertising and there is no advertising network in the app.
• We do not track you across other apps or websites. There is no tracking SDK, no advertising identifier, and no cross-app profiling. (One thing sits near this line and is not it — booking links. See below.)
• We do not use your crew details for anything but your own guides — and what a friend shares with you is shown to you on your Crew tab and used for nothing else, with one exception that they control: a friend who shares their profile with you, and whom you tick for a trip, is planned for in that trip's guide and by its assistant, using their first name, age range and interests (2.2). Nothing a friend shares is ever used for any trip they are not ticked on.
• We do not do automated decision-making that produces legal effects about you.

Booking links — what actually happens when you tap one

Some links in your guide go to booking sites that pay us a commission (see the Terms). Tapping one passes through our own redirect, so we should be exact about what that does.

What we record: a counter row, and nothing that is about you. It says a booking link of a certain type was tapped, for a certain destination, in a certain language — "a hotel link for Lisbon, in English". It carries no account, no trip, no name, no IP address and no device identifier, and there is nothing in it that could be traced back to you or joined to anything else we hold. We keep it to learn which parts of a guide are useful, which is the only question it can answer.

What happens next is the booking site's, not ours. Once you leave, the booking network typically sets a cookie on their site so that a booking made later can be credited to us. That processing is theirs and is governed by their privacy policy, not this one. We do not receive your name, your email, your payment details, or what you booked — a commission report tells us that a booking happened, never who made it.

What the link itself carries, which is the part most people would want to know. So that a hotel search opens on the right rooms rather than on a stranger's default of two adults, a hotel link passes the booking site how many adults and how many children are travelling, your dates, and the hotel's own name and coordinates. It carries no names, no ages, nothing about allergies, mobility or diet, and nothing identifying you or your account. Other kinds of link (a car, a tour, a transfer) carry the place and the dates and no party details at all.

You can simply not tap them. Nothing about a guide depends on it, and no part of the app behaves differently either way.

---

4. Who we share it with, and why

We use a small number of service providers. Each gets only what its job requires.

Services that receive a place, never a person

The rest of what we call gets a destination, a coordinate or a date, and nothing about you — no name, no account, no crew, nothing from section 2.2 or 2.3. We name them anyway, because "some third-party APIs" is not a disclosure:

The two map points sent to Wikimedia, precisely, because one of them is usually where you sleep. Each is rounded to two decimal places — about a kilometre — so it points at a neighbourhood, not at a door. They are the bed on your first night and the bed you wake in on your last day, or that day's first or last planned stop when there is no bed. A point within about a kilometre of the starting point you set is not sent at all, so a trip that begins at home does not send your home. Nothing in words travels with them: not a hotel's name, not a stop's, not a booking, not your notes, and nobody in your crew. Wikipedia and Wikidata receive the point and the names above; Commons receives only the file and category names the other two give back. When a place has no good photo of its own, we look one step up, at the region or country Wikidata says it belongs to, using public place IDs Wikidata itself gave back. There is no key and no account in any of it. The map points never reach an AI model; a model is shown only the candidate photo and the place's name, to check that the picture really is of the place.

One limit worth saying: we recognise your home only by the starting point you set. If you have not set one, or it is not where you actually are, we cannot tell that a stay is your home, and its rounded point is sent like any other.

We also read the public websites of places in your guide — a hotel's own page, a restaurant's own page — so the guide can tell you things their listing does not, such as which of a resort's restaurants are included. We only ever read pages that are public, we only quote them word for word, and those sites receive a request from our server with nothing about you in it.

Fonts. When a guide opens, your phone or browser asks Google's font service for the typefaces the guide is set in, as many websites do. Google receives your device's IP address and the ordinary details of that request, and nothing from your account, your crew or your trip. A guide you read with no signal makes no such request.

Booking partners

When you tap a booking link we pass you to one of these, with the information described in section 3: Stay22, Travelpayouts (and through it partners such as Aviasales, Localrent, Kiwitaxi, Welcome Pickups, Klook, Tiqets and Yesim), Viator, and Impact for event tickets. What each does once you arrive is governed by their own privacy policy, not this one.

Beyond all of these, we share information only where the law requires it, or to protect someone's safety.

Collaborators

When you share a trip, the person you share it with can see the trip, the guide, the map, the shared checklist, the comments and reactions, the activity feed of what changed, any photos shared to that trip, and — while you both have it open — that you are there and are typing or editing. That includes the party-level dietary and accessibility needs written into the guide, because those shape the recommendations.

Anything you do on a shared trip is attributed to you by name: a comment, a ticked item, an edit to the guide. That is the point of sharing one, but it is worth saying plainly.

They cannot see your crew list or the photos on your crew's cards, the friends in your crew, what any friend shares with you, anyone's age range, who anyone is to you, your other trips, or your account details. Two things they do see: what the guide itself says — a guide built with a friend on the trip names that friend by their first name and is shaped by their interests, exactly as it is by your travellers' — and which friend accounts are ticked on the trip, as account ids, which name no one to a stranger. Sharing is per-trip and you can revoke it at any time.

The app shows you this before you share.

Everyone on a trip sees everyone else's name and profile photo (if they have added one): the people you share a trip with see your name and profile photo, and you see theirs. The app lets you share a trip only with a friend, but anyone who has the trip's invite code can join it too, and sees the same. Anyone on a trip can report or block anyone else on it, from the trip's list of people, and a block hides each person's photo from the other even on a trip they share (2.10). The app says who sees your photo where you add it.

---

5. Where your information goes

Our database is hosted in Canada. Our AI providers process in the United States.

If you are in the EEA or UK, that means your information is transferred outside your region. Where required we rely on the European Commission's adequacy decision for Canada and on Standard Contractual Clauses with our US providers.

---

6. AI, and what it means for your information

vacayi's guides are written by AI. Three things follow that we would rather say than have you discover:

1. Your trip information is sent to our AI providers to produce a guide. They act as our processors and are contractually barred from using it to train their models.
2. AI also reads public web pages for you. To answer things a listing cannot — which restaurants at a resort are included, whether a tour has an age limit — we fetch the place's own public website and have a model pull out sentences from it. It only ever quotes those pages word for word, and those sites are sent nothing about you.
3. AI can be wrong. Guides are grounded against real place data and checked automatically, but opening hours change, restaurants close, and a model can still make a mistake. Confirm anything that matters — allergen safety, step-free access, prices and bookings — directly with the place. Guides say this too.

---

7. Children

vacayi is for adults. You must be 18 or over to hold an account, and we do not knowingly let children create one. We do not ask for a date of birth, so this is a condition of use rather than something we verify.

We do let you describe children who are travelling with you, because a guide that does not know there is a toddler is a guide that will exhaust you. For those children we store a first name or nickname and an age range — nothing more precise, and nothing that identifies them beyond your own account. A photo you add to a child's crew card is saved on your phone and never sent to us (2.2).

If you believe a child has created an account, contact support@vacayi.app and we will remove it.

---

8. How long we keep things

---

9. Your rights

Wherever you are, you can:

• See what we hold, and take it with you — Settings → Export my data gives you a machine-readable file. It covers your profile (your profile photo included), your crew (including who each person is to you), your pets, your trips (with the friends you ticked for each), your idea list, the coming-soon features you tapped, whether you share your profile with your friends, and the friends in your crew with your own label and nickname for each. The photos on your crew's cards are not in it, because they are on your phone, not with us. It does not yet include the guides themselves, your assistant conversations, or the shared material on a trip (comments, checklists, photos) — email us and we will send you all of it, within 30 days and usually sooner.
• Correct it — edit any of it in the app
• Delete it — Settings → Delete my account, or email us. Section 9a sets out exactly what goes and what we are required to keep.
• Turn off notifications, per category
• Refuse location, and keep using everything else

If you are in the EEA or UK you also have the right to object to processing, to restrict it, to withdraw consent at any time, and to complain to your data protection authority.

If you are in California you have the right to know, delete, correct, and to opt out of sale or sharing — we do neither, so there is nothing to opt out of. We will not discriminate against you for exercising any right. Because we do not sell or share personal information, there is nothing for a Global Privacy Control signal to switch off; we honour it by never having started.

To exercise anything here, use the app or email support@vacayi.app. We respond within 30 days.

---

9a. Deleting your account

You can delete your account and everything in it at any time, and you do not need the app installed to ask.

In the app — Settings → Delete my account. It takes effect immediately.

Without the app — email support@vacayi.app from the address your account uses, with the subject Delete my account. We will confirm and complete it within 30 days, and usually the same week. If you can no longer send mail from that address, write from any address and we will verify another way before deleting anything.

What is deleted

• Your profile, your crew and your pets — names, age bands, who each person is to you, dietary, accessibility and mobility notes
• Every trip and every guide you have made, including guides shared with you and guides you shared with others
• Uploaded booking images and any photographs stored with your guides
• Every photo you ever shared to a trip, including photos you shared to trips belonging to other people
• Your assistant conversations, and the undo history and earlier versions of your guides
• Your idea list, and your progress, stars, read state and mute settings
• The coming-soon features you tapped
• Checklists, comments and reactions on your own trips
• Your support messages and any guide feedback you sent
• Push notification tokens for your devices
• Your friendships and any pending invitations
• Whether you share your profile with your friends, and your label and nickname for every friend in your crew — and the rows that put you in their crews, so you leave every crew you were in, and no later build of any friend's guide can include you
• Your profile photo, everywhere your friends and the people on your trips saw it, and the blocks you placed
• The record of reports you made, and of reports anyone made about you
• The photos on your crew's cards, on the phone you delete your account from. We never had them, so we cannot delete them anywhere else: on another phone they stay in the app's storage until you remove vacayi from that phone, and a backup a phone has already made keeps its copy

What is kept, and why

Very little. Your credit balance, every charge against it, and the records of each guide being built are all deleted with your account. There are two exceptions that keep the text while removing you from it, and two that can still name you.

What you wrote on someone else's trip stays on their trip, with your name taken off. A comment, a checklist item you added or ticked, and the line in the activity feed recording a change you made all survive — as anonymous entries, permanently unlinked from you. We do it this way because the alternative is worse for the people you travelled with: deleting your account would silently tear items out of a shared list they are still using. If you want something you wrote removed as well as anonymised, delete it before you delete your account, or ask us and we will.

The log of purchase notifications sent to us by Apple, Google or RevenueCat. We keep those, with your user ID removed, because they record a transaction those companies also hold and it is how a payment dispute gets resolved months later. Once your account is gone they cannot be connected back to you.

A report somebody else made about you. If someone reported your profile, the report reached our support queue filed under their account. It records your vacayi account id, and names you by your @handle or display name if you have one. It is theirs, not yours: we keep it so we can act on the report, and it is deleted when they delete their account, not when you delete yours. The record of who reported whom is deleted when either of you deletes your account.

A guide a friend built with you on the trip. If you shared your profile and a friend ticked you for a trip, the guide built for their trip names you by your first name and was written around your age range and interests. That guide is part of their trip, not your account, so it stays until they delete the trip (and any copy of it) or their own account — the same as a printed itinerary somebody else is holding. A rebuild does not remove it: every rebuild keeps the earlier version in the trip's history. Nothing in the guide links back to your account, and no later build can include you; their trip does keep your account id in its list of ticked friends, and so does their data export, but it no longer leads to an account. If you want the guide gone, ask us and we will contact them.

Aggregate counts that never identified anyone — how many guides were built in a month — also remain. Apart from a report about you, and a first name and an old account id on a friend's trip, nothing kept can be used to identify or contact you, and none of it can rebuild an account.

Credits

Deleting your account forfeits any unused credits, and they cannot be restored or transferred afterwards. If you have a Pro subscription, cancel it in your device's App Store or Google Play settings — deleting your vacayi account does not cancel a store subscription, and we cannot cancel it for you.

---

10. Security

Access to your data is enforced at the database level, so one account cannot read another's even if the app is modified. Guides are kept in private storage and served through expiring links. Payment card details never reach us.

No system is perfectly secure, and we will not claim otherwise. If a breach affects you, we will tell you and the relevant authority as the law requires — in the EEA and UK that means notifying the supervisory authority within 72 hours of becoming aware of it, and telling you directly without undue delay where the risk to you is high.

---

11. Changes

If we change this policy materially we will tell you in the app before the change takes effect. The date at the top always shows the current version.

---

12. Contact

Vacayi LLC support@vacayi.app

Last updated 28 October 2026 · vacayi · Vacayi LLC