TokTravel Privacy Policy
Effective date: 9 October 2026
Translations of this policy are provided for convenience. If a translation differs from the English text, the English text prevails.
This policy explains how TokTravel handles personal information when you use the app, submit a travel link, save places, create or share a trip, use Kuki, or contact us. It also explains how we handle information about people who appear in the travel videos users submit and people who wrote the Google reviews shown in the app.
1. Who we are
The controller responsible for your personal information is Kozhan Oksana, trading as TokTravel, business ID 3617011-6, Kaivokselantie 5, 01610 Vantaa, Finland.
For privacy questions, requests about your information, or complaints, email info@toktravel.app.
We have not appointed a data protection officer.
2. A short summary
We use your account information and the travel content you provide to run TokTravel.
- AI: reading a link or asking Kuki a question sends selected text to Google Gemini. Section 6 explains exactly what is sent.
- Sharing: your account, notes, lists and trips are private. If you create a trip share link, anyone with the link can see the shared itinerary and forward it.
- Shared catalogue of places: places found from a link you submit, and the link to the source video, join a shared catalogue. Other users can see them as suggestions. Your name is not attached.
- Crash and usage reports: the app can send crash reports and usage reports to our own server. Each has its own switch in Settings. Both start off, and the app sends neither until you turn it on.
- Booking links: if you tap a Book link on a trip, Booking.com receives the trip's city, or Kiwi.com receives the trip's city and country (never a date). If you tap the Booking.com button on a hotel's page, Booking.com receives that place's name and location. A Booking.com partner link passes through CJ (Commission Junction), which receives the click and a place tag.
- No advertising: we do not sell your personal information or use it for advertising or marketing emails, apart from the one launch email to people who asked for it on our website. We do not request your device's GPS location. The places, dates and routes you save can still show where you plan to travel.
- Your control: you can edit your content, export your data, stop sharing a trip and delete your account in the app, or email us instead.
- Your right to object: where we rely on our legitimate interests, you can object at any time on grounds relating to your situation. See section 13.
3. Information we collect
Account and sign-in information
We process your email address, account identifier, and authentication and session information. Your display name starts as a name taken from your email address, and you can change it in the app.
You can sign in with Apple or Google. Apple may give us a private relay email address if you use Hide My Email. We do not receive your Apple or Google password, and sign-in does not request your contacts or access to your social-media accounts.
If you sign in with Apple, we store an encrypted authorisation token on our server. We use it to disconnect Apple sign-in when you delete your account.
Information you save or enter
This includes saved places and their source links, lists, trips, destinations, scheduled stops (and any dates or times you entered in an earlier version), notes, the preferences you choose, dish likes, and your messages to Kuki together with Kuki's replies.
Your content can reveal personal information about you or other people. Please do not include identity documents, confidential information, or details about your health, religious or philosophical beliefs, political opinions, sex life or sexual orientation — in notes or in messages to Kuki.
Earlier versions of the app offered "gluten-free" and "nut-free" as diet preferences. Because they can reveal health information, we no longer accept them and have deleted any we held.
Links you submit and public information about places
When you ask us to read a link, we process the link and the public information attached to it: the video's description, its written caption and, for YouTube links or when the written caption is short, a caption track of the video (automatic captions or the uploader's subtitles), which is a transcript of what is said in the video. We use this text to find the places mentioned. We do not keep the description or captions after reading them. We keep the link, the places found and any place names we could not confirm.
We then look up those places with Google Places to get names, addresses, coordinates, photos, opening hours and up to five Google reviews. For restaurants we also ask Wolt for a public menu. Few places return one.
The places found from a link you submit, and the link to the source video, join a shared catalogue. Other users can see these places as suggestions, with a button that opens the source video. Your name and account are not shown with them.
We do not ask for your TikTok, Instagram or YouTube password to read public links.
Searching for a place by name
If you search for a place by name, we process the text you type, send it to Google Places, and keep the search text and its results, not connected to your account, to answer repeat searches. Search text and results older than 30 days are deleted by a daily clean-up. We also record, with your account and the time, that you made a new search. We use this record to apply a daily limit on look-ups. It is deleted when you delete your account.
Activity history
We record certain actions in the app — saving a place (including your very first save), visiting a place, liking a dish and opening a place's menu — to calculate Miles, streaks and badges.
Crash reports
If crash reporting is on, the app sends crash categories and code locations, failed-request categories, timestamps, app version and build, operating-system information and a session identifier. The app keeps a crash record on your device until it can send it.
Usage reports
If usage reporting is on, the app sends identifiers for the screens you open and the controls you tap, with timestamps, app version and build, operating-system information and a session identifier. The app holds these reports on your device briefly before sending them.
What reports contain and exclude
Crash and usage reports are linked to your account, so they are not anonymous. We may look at a short sequence of events around a failure to find its cause.
Reports never include your typed messages, pasted links, search text, place names, precise coordinates, sign-in credentials, screenshots or the text of crash messages. They are not screen recordings, and we do not use any third-party analytics or crash-reporting service.
Website launch list
If you leave your email address in the "Notify me" box on toktravel.app, we keep it, with the date and the version of the notice you saw, only to email you once when TokTravel is on the App Store. Then we delete it. We do not store your IP address or set cookies for this. We send that email from our mailbox at Namecheap.
Support emails
If you email us, we process your email address, your messages and any attachments you send.
Server logs
Our server keeps technical logs of the requests it handles: when a request arrived, its type, the kind of page or action it was for (for example "a shared trip", never the link or code inside it), the result and how long it took. The logs do not record your IP address, the links you submit, or the searches our server makes on your behalf. When a provider refuses a request from our server, only its error code and status are written to the log. A request our server does not recognise is logged without its address. We keep these logs to keep the service secure, prevent abuse and fix faults, based on our legitimate interest in doing so. Logs are kept by our hosting provider for 7 days and are not removed when you delete your account.
Request limits
We use your IP address to limit how many requests one connection can make. For most requests it is held only in memory. For link-reading requests, a per-minute count is kept in our database for a short time (normally minutes) and then deleted. The count is kept under your account identifier, or under the IP address when the request is made without a valid sign-in.
4. People who appear in videos, and authors of Google reviews
This section is for people who are not necessarily TokTravel users.
Where the information comes from. From public video links that TokTravel users submit, from Google Places, which supplies the reviews shown for a place, and from Wikimedia Commons, which supplies some licensed place photos.
What information. From videos: names, usernames and places that appear in the link or in the video's description, captions or caption track. From Google Places: the reviewer's display name, rating, review text and review date. From Wikimedia Commons: the photographer's name, shown as the credit for the photo.
Why, and on what legal basis. We process this information on the basis of legitimate interests (Article 6(1)(f) GDPR). The interest is helping our users find and choose the places recommended in public travel content: reading a video lets us identify the places it mentions, and showing reviews helps users decide whether to visit. We only send the video's text to our AI provider to find places, and we do not keep the description or captions afterwards.
How long. The link a user submitted and the places found are kept as described in section 11. Stored place information, including reviews and photos, is kept while TokTravel offers the service, as a shared catalogue not connected to any account. Other TokTravel users can see places from this catalogue as suggestions, with a button that opens the source video. When a place is shown, information from Google older than 30 days is fetched again (reviews: older than 7 days). You can ask us to remove a link or place (section 4).
Your right to object. You can object to this processing at any time on grounds relating to your situation, and exercise your other rights described in section 13, by emailing info@toktravel.app. Tell us the link or the place concerned so we can find the information.
5. How we use information and our legal grounds
| Purpose | Information involved | Legal ground |
|---|---|---|
| Create your account and sign you in | Email, account identifiers, session details and sign-in grants | Contract (Article 6(1)(b)) |
| Store and organise your places, lists, notes and trips | Your account identifier and your content | Contract |
| Share a trip when you ask | The trip information you choose to share | Contract |
| Identify places from a link you submit, and answer Kuki messages | The link's text, your message and up to 15 saved-place names | Contract |
| Tell you once when TokTravel is on the App Store | The email address you leave on toktravel.app | Consent (withdraw it any time by emailing info@toktravel.app) |
| Show place information, menus and routes | Place queries, identifiers, coordinates and travel mode | Contract |
| Order suggestions using the preferences you choose | Your preferences and relevant app content | Contract |
| Calculate Miles, streaks and badges | Activity history | Legitimate interests (Article 6(1)(f)): offering rewards that encourage you to explore and plan travel |
| Process information about people in videos and Google review authors | See section 4 | Legitimate interests: helping users find and choose recommended places |
| Crash reports | See section 3 | Your consent (Article 6(1)(a) GDPR), which you give by turning crash reports on in Settings and can withdraw at any time by turning them off |
| Usage reports | See section 3 | Your consent (Article 6(1)(a) GDPR), which you give by turning usage reports on in Settings and can withdraw at any time by turning them off |
| Keep server logs and limit requests | Request time, type, route pattern, result and duration; IP addresses for rate limiting, held in memory, and for link reading a short-lived count in our database under your account identifier or IP address (section 3) | Legitimate interests: keeping the service secure, preventing abuse and fixing faults |
| Prevent abuse and unauthorised access | Account, request and security records | Legitimate interests: protecting users and the service |
| Monitor operating costs | Usage and cost records | Legitimate interests: running a sustainable service |
| Answer support requests about your account | Contact details and correspondence | Contract |
| Answer other enquiries | Contact details and correspondence | Legitimate interests: responding to people who contact us |
| Meet legal duties and answer rights requests | Information needed for the obligation | Legal obligation (Article 6(1)(c)) |
| Establish, exercise or defend legal claims | Relevant records only | Legitimate interests: protecting legal rights |
Legitimate interests. Where we rely on legitimate interests, we have weighed our interest against your rights. You can ask for a copy of that assessment by emailing info@toktravel.app, and you can object (section 13).
Consent. Where we rely on your consent, you can withdraw it at any time in Settings (for the website launch list, by emailing info@toktravel.app). Refusing or withdrawing consent never stops you using TokTravel's core features, and it does not make earlier processing unlawful.
What you must provide. You are not legally required to give us any information. We need an email address and sign-in information to create an account. Everything else is optional, but a feature needs the details it works with: without a link we cannot read it, and without stops we cannot show a route.
6. AI features
TokTravel uses Google Gemini for two features.
Identifying places from a link. Gemini receives up to 4,000 characters of the video's text: its description, its written caption and, for YouTube links or when the written caption is short, a caption track of the video (automatic captions or the uploader's subtitles; a transcript of what is said in the video). The app does not analyse the video's images or sound itself.
Kuki, the travel assistant. Gemini receives your message and the names of up to 15 of your saved places. It does not receive your preferences, your email address or your sign-in details. Your message itself may still contain personal information.
We ask first. The first time you read a link or write to Kuki, the app shows what would be sent to Google Gemini and asks Allow or Not now. Until you choose Allow, nothing is sent to Gemini; link reading and Kuki stay unavailable and the app says why. You can withdraw the permission at any time in Settings, under "Allow AI reading (Google Gemini)". Your choice is kept on your device, with its date, not on our server. It is removed from the device when you sign out, so the app asks again after the next sign-in. If this notice changes in a way that matters, the app asks again. This permission is the one Apple's App Store rules require before information is shared with a third-party AI service; it does not change the legal ground in section 5.
Google's role. Google acts on our behalf under the paid Gemini API terms and does not use this content to train its models.
We do not use your content to train AI models ourselves.
AI answers can be wrong. The app labels AI-generated results and Kuki's replies.
Profiling, not automated decisions. We use the preferences you choose to order travel suggestions. This is profiling. It does not produce decisions with legal or similarly significant effects on you, such as decisions about credit, employment or insurance.
7. Who receives information
We share only the information a feature needs.
| Recipient | What it receives and why | Role |
|---|---|---|
| Supabase | Sign-in and storage of your account and app information. It also stores the licensed place photos from Wikimedia Commons, which your device loads directly from Supabase | Processes information on our behalf |
| Supabase (including its sign-in email service) | Your email address, to send the sign-in link | Processes information on our behalf |
| Fly.io | Hosting of our server, including the server logs in section 3 | Processes information on our behalf |
| Google (Gemini API) | The AI inputs in section 6 | Processes information on our behalf |
| Google Places and Photos | The place name, location hint and country found in a link, the text you type when you search for a place by name, and place identifiers for photos. Never your device's location. | Independent controller |
| Apple or Google sign-in | Sign-in and authorisation information for the method you choose | Independent controller |
| Apple Maps | Map display and directions you request on your device. It also receives the place names, area hints and countries found in a link you read, sent from your device so that the app can show each place on an Apple map before you save it. Apple's answer is shown only on your device, is never stored, and never reaches our server | Independent controller |
| Wolt | A restaurant's name and city, to find its public menu | Independent controller |
| The platform behind a link you submit (for example TikTok, Instagram, YouTube) | A request from our server for the link's public information | Independent controller |
| Booking.com and Kiwi.com | When you tap a Book link: Booking.com receives the trip's city, or the name and location of the hotel whose button you tapped; Kiwi.com receives the trip's city and country | Independent controller |
| CJ (Commission Junction; for people in the EU, its controller is Epsilon International UK Ltd, London) | When a Booking.com link is a partner link: the click (your IP address and browser information, as with any website), our partner codes, and a tag: the word "trip" for a trip's link, or the tapped place's ID. For a place you added yourself, only we can connect that ID to your account | Independent controller |
| Namecheap | Support emails: the mailbox that stores the email you send us, and from which we send the one launch email to the website launch list | Processes information on our behalf |
| Cloudflare | Hosting of our website, toktravel.app (it sees visitors' IP addresses, as any web host does), and storage of the website launch list | Processes information on our behalf |
| People with a trip share link | The shared itinerary in section 9 | — |
A provider that processes information on our behalf may use it only to provide its service to us. An independent controller handles the information under its own privacy policy.
Booking links. When you tap a Book link on a trip, the app opens Booking.com (stays) with the trip's city filled in, or Kiwi.com (flights) with the trip's city and country filled in; no date is sent. From that point, Booking.com or Kiwi.com handles your information as an independent controller under its own privacy policy. Where a link is a partner link, it also carries our partner code so that the service can recognise the visit came from TokTravel. A hotel's page can also have a Booking.com button, which opens Booking.com with the place's name and location filled in. When a Booking.com link is a partner link, your tap first passes through CJ (Commission Junction), the network that runs Booking.com's partner programme. CJ records the click, our partner codes and the place tag, then forwards you to Booking.com, and handles that information as an independent controller under its own privacy policy.
Other external links. When you open a place or route in Apple Maps, Google Maps or another external service, that service receives the information in the link, such as a place or destination. It may connect this with your account on that service.
We may give necessary information to professional advisers or competent authorities to meet a legal obligation or deal with a legal claim. If the business changes ownership, your rights under this policy continue.
8. Crash and usage report switches
Settings has a separate switch for crash reports and for usage reports. Both switches start off: the app does not store or send any crash report or usage report until you turn that switch on, and turning it off again deletes any reports of that kind not yet sent.
Turning a switch off stops future reports of that kind and deletes unsent reports of that kind from your device. Reports already received are deleted once they are older than 30 days, by a clean-up that runs every day (section 11). You can ask us to delete them sooner.
9. Sharing trips
Sharing is optional. Anyone who has a trip's share link can open it without a TokTravel account.
The shared page shows the trip name, country and dates, and each scheduled stop's day, time, type, title and location. It is shown in the language you use in the app. Stops you have not placed on a day are not shown, and your email address is never shown. Text you write can still identify you.
The link works until you stop sharing. Stopping sharing turns the link off for everyone. It cannot remove screenshots or copies that others have already made.
Exporting information or using your device's share sheet also gives the chosen information to the person or service you pick.
10. Where information is processed
Our server runs on Fly.io in Amsterdam, the Netherlands. Our database is hosted by Supabase in the West EU (Ireland) region.
Some providers are based in, or can access information from, the United States. When personal information goes outside the European Economic Area, we protect it as follows:
| Provider | Safeguard |
|---|---|
| Fly.io, Inc. | EU-US Data Privacy Framework certification |
| CJ (Epsilon International UK Ltd, United Kingdom) | Your device sends the click to CJ directly. The United Kingdom has an EU adequacy decision; CJ stores data on servers in the United States under Standard Contractual Clauses, according to CJ's own EU privacy policy |
| Namecheap, Inc. (USA) | Standard Contractual Clauses, according to Namecheap's privacy policy; it stores data on servers in the United States |
| Cloudflare, Inc. (USA) | The launch list is stored in Cloudflare's EU jurisdiction; EU-US Data Privacy Framework certification and Standard Contractual Clauses in Cloudflare's data processing addendum |
| Supabase, Inc. (including its sign-in email service) | Standard Contractual Clauses approved by the European Commission (Supabase data processing agreement) |
| Google LLC | EU-US Data Privacy Framework certification |
| Apple (Apple Distribution International Ltd., Ireland) | Inside the EEA; Apple's onward transfers use Standard Contractual Clauses |
If the Data Privacy Framework stops applying to a provider, we rely on Standard Contractual Clauses instead.
You can ask for a copy of these safeguards by emailing info@toktravel.app. We may remove commercially confidential parts first.
11. How long information is kept
| Information | How long we keep it |
|---|---|
| Your account, places, lists, trips, notes and preferences | Until you delete the item or your account |
| Kuki conversation | Until you delete your account |
| The record that your account searched for a place by name, with its time | Until you delete your account |
| Search text and results from search by name | Not connected to any account. Deleted once older than 30 days, by a daily clean-up |
| Request counts for link reading (under your account identifier or IP address) | A short time, normally minutes |
| Activity history for Miles, streaks and badges | 730 days |
| The link between your account and a link you submitted | 365 days, after which the submitted link is no longer connected to you |
| Operating cost records | 400 days |
| Crash and usage reports | Deleted once they are older than 30 days, by a clean-up that runs every day. You can ask us to delete them sooner |
| Server logs | 7 days |
| Sign-in service logs held by Supabase | 1 day |
| Support emails | 24 months after the matter is closed |
| Website launch list | Until the launch email is sent, and at most 12 months: deleted automatically after 12 months |
| Apple sign-in authorisation token | Until it is revoked when you delete your account. If Apple is unavailable, we try again every day until it succeeds. |
| Places found from links, their source links, place names we could not confirm, Google reviews and place photos | Kept while TokTravel offers the service, as a shared catalogue not connected to any account. Other users can see places from it as suggestions. When a place is shown, information from Google older than 30 days is fetched again (reviews: older than 7 days). You can ask us to remove a link or place (section 4) |
| Backups | We do not keep separate copies of our database. Our store of place photos is copied daily, and each copy is deleted after 5 days. |
Stopping use of the app or uninstalling it does not delete your account.
Once a submitted link is no longer connected to your account, the link itself can still identify the person who posted the video. We therefore continue to treat it as personal information.
If a legal obligation or a specific legal claim requires us to keep something longer, we keep only the information needed, and only for as long as needed.
12. Your controls and deleting your account
You can edit your content and preferences, stop sharing a trip, export your data and delete your account in the app. If you cannot use the app, email info@toktravel.app.
Deleting your account.
When you delete your account, we delete your account records, places, lists, trips, notes, preferences, dish likes, activity history, Kuki conversation, crash and usage reports, the record of your searches by name, and the link between your account and the links you submitted. We also delete your sign-in identity and revoke Apple sign-in if you used it. The links you submitted, and the places found from them, stay in the shared catalogue without your account (section 11). After deletion, nothing more is stored for that account, even from a device that was still signed in.
Copies in backups are deleted when those backups expire (section 11). Deleting your account cannot remove copies that other people made of information you shared with them.
13. Your privacy rights
You have the right to:
- access your personal information and get a copy;
- correct inaccurate information;
- have information deleted, or its use restricted;
- receive the information you gave us in a portable format;
- object to processing based on legitimate interests; and
- withdraw consent where we rely on consent.
Exporting your data.
The in-app export gives you a file with: your email address, display name and preferences; your saved places, with their lists, notes, visited status and source links; your lists; your dish likes; your trips and their stops, and whether each trip is currently shared; the links you submitted; your activity history; your full Kuki conversation; the crash and usage reports linked to your account; whether we hold an Apple sign-in authorisation for you; and the dates and times you searched for a place by name. You can ask us by email for any other personal information we hold.
Right to object. Where we rely on legitimate interests, you can object on grounds relating to your situation. We will stop unless we have compelling legitimate grounds that override your interests, or we need the information for legal claims.
Making a request. Email info@toktravel.app. We reply without undue delay and within one month. If a request is complex, we may need up to two more months, and we will tell you within the first month. We may ask for information to confirm your identity. Requests are free, except where the law allows a fee for clearly unfounded or excessive requests. If we cannot meet a request, we will explain why and how you can complain or go to court.
Complaints. You can complain to Finland's Office of the Data Protection Ombudsman at https://tietosuoja.fi/en/home, or to the data protection authority where you live, work or think your rights were infringed. You do not need to contact us first.
14. What the app stores on your device, and security
The app stores the following on your device:
| Stored item | Purpose | Type |
|---|---|---|
| Session token and refresh token | Keep you signed in | Strictly necessary |
| "Intro seen" and "splash seen" flags | Avoid showing the introduction again | Strictly necessary |
| A link you shared into TokTravel from another app | Hand the link from the share sheet to the app, until the app reads it | Strictly necessary |
| Your crash-report and usage-report switch settings | Remember your choice | Strictly necessary |
| Your answer to the AI permission, and its date | Remember your choice | Strictly necessary |
| "Example tried" flag | Avoid showing the example card again | Strictly necessary |
| The saved crash record and unsent reports | Send crash and usage reports | Reporting — stored only after you turn on the matching switch: the crash record and unsent crash reports after you turn crash reports on, unsent usage reports after you turn usage reports on |
Storing or reading information on your device that is not strictly necessary for a feature you use requires your permission. Sign-in pages and external websites you open may use their own cookies.
We protect information with encrypted connections, access controls and protected storage of sign-in credentials. No system is completely secure. We assess every personal-data breach and notify the authorities and affected people when the law requires.
15. Children
TokTravel is for people aged 18 and over. If you believe a younger person has given us personal information, email info@toktravel.app and we will delete it.
16. Changes to this policy
When we change this policy, we update the effective date at the top. If a change affects how we use your information, we tell you in the app or by email before it takes effect, and we ask for your consent where the law requires it.
Privacy contact: info@toktravel.app