Traveley
Englishen Españoles Catalàca Françaisfr Italianoit Русскийru
Get the app

Traveley

Privacy Policy

What data Traveley collects, how it is used, and the choices you have.

AvakiamLast updated August 6, 2026

Traveley (“the App”) is developed and published by Avakiam (“we”, “us”, “our”), based in Girona, Spain. Traveley builds day-by-day travel itineraries from a destination and a set of dates or a trip length, using an artificial intelligence model, and lets you save the itineraries you like. This Privacy Policy explains what information the App collects, how it is used, and the choices available to you. It applies to the version of Traveley distributed on Google Play (package name com.avakiam.traveley) and, where applicable, other app stores and the web version.

Who is responsible for your data

Avakiam is the data controller for the information described in this policy. You can reach us through the contact form on our website at avakiam.com.

Summary

Traveley shows ads, and they are how the App pays for itself. It contains no analytics or tracking SDK, and it never asks for or reads your device's location. Creating an account is optional and is only needed to save itineraries, and to buy extra ones — on its own it does not change how many itineraries you get. The two identifiers used to run the free plan — your device identifier and your IP address — are never stored in readable form: only an irreversible hash of each is kept.

Information we collect

The trip details you enter

To generate an itinerary the App sends the destination you typed, the dates or number of days you chose, and any preferences or refinement instructions you wrote, to our server function, which passes them to Google's Gemini model to produce the itinerary. These inputs describe a trip, not you: we do not ask for your name, age, or any personal detail in order to plan a trip, and you should not enter personal or sensitive information in the free-text fields.

Device identifier

The free plan allows a limited number of itineraries per device, so the App needs a way to recognise the same device across sessions. On Android this is the Google Play advertising ID; on other platforms, and on Android devices without Play services, it is a random identifier generated by the App and stored in the operating system's secure storage (the Keychain on iOS).

This identifier does two jobs. It counts your free itineraries, and — only if you allow it — it is what Google AdMob uses to choose which ads to show you. See Advertising below for the choice you are given and how to change it.

For counting itineraries it never reaches our database in readable form: before it is stored, it is combined with a secret value held on our server and converted into an irreversible SHA-256 hash. We do not build an advertising profile of you ourselves, and the ad network tells us nothing about you in return. On Android you can reset the advertising ID at any time from Settings > Google > Ads, where you can also switch off ad personalisation altogether.

IP address

When the App contacts our server, your IP address is visible to it, as it is to any internet service. We use it as a secondary anti-abuse signal, to stop one person exhausting the free plan by resetting their device identifier. Like the device identifier, it is never stored as an IP address: only an irreversible hash of it is written to our records, and we cannot recover the original address from that hash.

Account information (optional)

You can generate itineraries without an account. Signing in is required only to save them, so they are waiting for you on any device where you sign in; it does not give you more itineraries, as the free allowance is the same with or without an account. Sign-in is handled through Google, and we receive your name, email address and profile picture from your Google account to create and identify your account. We never see or handle your Google password.

Itineraries you save

If you are signed in and choose to save an itinerary, the itinerary itself — destination, dates, daily plan, and the places it suggests — is stored in our database, linked to your account, so you can find it again on any device where you sign in. Itineraries you do not save are not stored on our servers.

Usage records

We keep a minimal ledger of generation activity: the hashed device identifier, the hashed IP address, a timestamp, and whether the request was a new itinerary or a refinement of an existing one. We also record extra itineraries you have been given — one earned by watching a rewarded video, and any you have bought — so the allowance can be counted correctly. This is what enforces the free plan. It contains no trip content and no account details.

Reports you send

Every itinerary carries a report button, so you can tell us when the AI produces something offensive, wrong or unsafe. If you use it, we store the reason you picked, anything you chose to write, and a copy of the itinerary you were looking at, linked to your account. Nothing is stored unless you tap the button and send the report.

Booking link taps

Some stops in an itinerary are things you can book, and those carry a link to a booking partner. If you follow one, we record that the tap happened: which partner, whether it came from a single activity or from the destination card, the destination, the search term we sent the partner, the type of activity, the interface language, and a timestamp, linked to your account or to your anonymous session. The search term is a public place name that we compose from the itinerary — it is never anything you wrote about yourself. We use these records to learn which suggestions travellers actually find useful, so the links can be shown where they help and taken away where they do not. We do not receive any information about what you then view, book or pay on the partner's site.

Advertising

Traveley shows two kinds of ad, both served by Google AdMob:

  • A banner at the foot of the screen while your itinerary is being generated.
  • A video you can choose to watch when you have used your free itineraries, in exchange for one more.

The ads are what pay for the App: every itinerary costs us a request to an AI model, whether or not you ever book anything. There is no ad anywhere else — in particular, none on the itinerary itself.

To serve them, Google receives technical information from your device, including your advertising identifier, your IP address, and general information about your device and the App, and may use it to select, cap and measure ads under its own privacy policy. We receive none of that back. We tell the ad network nothing about your trips: the destination you typed and the itinerary you were given are never sent with an ad request.

If you are in the European Economic Area, the UK or Switzerland, you are asked first. On first run the App shows a consent form from Google's User Messaging Platform, where you choose whether ads may be personalised. If you decline, you still see ads, but they are chosen without your advertising identifier. You can change or withdraw that choice at any time from Ad privacy choices on the App's About screen.

Watching a rewarded video is always optional, and declining one takes nothing away from you.

Purchases

You can buy a pack of extra itineraries. We never see your card. The payment is handled entirely by Google Play or the App Store, who take the money and tell us only that a purchase was made.

What we store is the store's own transaction identifier, which product it was, how many itineraries it is worth, and the date — linked to your account. The identifier is what stops the same purchase being credited twice, and it is what we use to find your purchase if you ever ask us about it.

Buying requires signing in, and not for our convenience: a purchase is attached to your account so it follows you to a new phone. Bought without an account it could only be tied to the handset that made it, and would be lost with that handset.

Trips kept on your device

The trips you have saved are also written to your phone's own storage, so you can read them with no connection — which is when an itinerary is usually needed. That copy never leaves your device, is removed when you sign out or delete your account, and goes with the app if you uninstall it.

Device language

The App reads your device's language setting to display the interface in English, Spanish, Catalan, French, Italian or Russian, and generates your itinerary in that language. This setting stays on your device.

What we do not collect

  • Location. The App does not request location permission and never reads your position. “Open in Maps” simply hands a place name to Google Maps.
  • Contacts, photos, files, camera or microphone. None of these are accessed.
  • Analytics, and anything about your trips. There is no third-party analytics SDK in the App, and nothing you do inside it — the destinations you search for, the itineraries you are given, the notes you write — is shared with advertisers. Ads are served by Google AdMob, which receives technical information about your device but no trip content; see Advertising above. The App does contain affiliate booking links, which are labelled as such where they appear: if you follow one, the partner's own website may set a cookie so that a booking can be attributed to us. That happens on their site and under their privacy policy, not ours — see “Booking link taps” above for the only part we record.

How this information is used

  • To generate the itinerary you asked for, and to refine it when you request changes.
  • To store and retrieve the itineraries you choose to save.
  • To authenticate you when you sign in.
  • To count free itineraries and refinements, and to prevent abuse of the free plan.
  • To display activity photos and let you open a place in Google Maps.
  • To review itineraries you report, and to correct what the app produces.
  • To see which booking suggestions travellers find useful, so the links appear where they help and are removed where they are ignored.
  • To show the ads that fund the App, and to add an itinerary to your allowance when you choose to watch a rewarded video.
  • To confirm a purchase with the store and credit the itineraries it paid for, and to answer questions or refund requests about it afterwards.

We do not sell your personal data, we do not use it to build advertising profiles, and we do not use it for any purpose beyond operating the App and the services described here.

Where the EU General Data Protection Regulation applies, we rely on: performance of a contract for generating and saving your itineraries, managing your account, and delivering anything you have bought; and our legitimate interest in keeping the service available and affordable, both for the anti-abuse measures described above (device and IP hashing) and for the record of booking link taps, which tells us which suggestions are worth keeping.

For personalised advertising we rely on your consent, which is requested through the form described under Advertising and which you can withdraw at any time from the App's About screen. Where consent is declined, or is not required in your country, ads are shown without your advertising identifier on the basis of our legitimate interest in funding the App.

Third-party services

The App relies on the following third-party services, each of which processes some data under its own privacy policy:

Some of these providers process data outside the European Economic Area. Where that happens, the transfer relies on the safeguards those providers put in place, such as the European Commission's standard contractual clauses.

Data retention

Saved itineraries are kept until you delete them in the App or delete your account. Account details are kept for as long as your account exists. Usage records, which contain only hashed identifiers and timestamps, are kept for as long as they are needed to enforce the free plan's lifetime and monthly limits; the same applies to the record of itineraries earned from rewarded videos. Purchase records are kept for as long as tax and accounting rules require, and because a refund or a support question can only be answered from them. Records of booking link taps are kept while they remain useful for deciding where the links belong, and they survive the deletion of an account with the link to your identity removed, so that past demand for a destination is not silently rewritten. Trip details sent for generation are not retained by us beyond producing the itinerary; if you do not save it, we do not keep it.

Your rights

If you are located in the European Economic Area, the UK, or another jurisdiction with similar data protection laws, you may have the right to access, correct, delete, or export your data, and to object to or restrict certain processing. You can delete any saved itinerary directly in the App, and you can delete your whole account from the menu in the App — see how to delete your account for the steps and for what is removed. To exercise any other right, use the contact form on avakiam.com. You also have the right to lodge a complaint with your local supervisory authority; in Spain this is the Agencia Española de Protección de Datos.

Please note that hashed device and IP records cannot be linked back to you by us, so we may be unable to identify and delete them on request without additional information from you.

Children's privacy

Traveley is not directed at children under 13, and we do not knowingly collect personal data from children. If you believe a child has provided us with personal data, please contact us so we can remove it.

About AI-generated content

Itineraries are produced by an AI model and may contain inaccurate information about places, opening hours, prices or travel times. They are suggestions, not verified travel advice — please check important details, such as bookings and opening times, before relying on them.

Security

Access to saved itineraries is restricted at database level so an account can only reach its own data. Traffic between the App and our servers is encrypted in transit, the device identifier is held in the operating system's secure storage, and the identifiers used for quota enforcement are stored only as irreversible hashes. No method of electronic storage or transmission is 100% secure, but we work with reputable providers and keep the App's dependencies up to date.

Changes to this policy

We may update this Privacy Policy from time to time, for example when the App adds or removes a feature or service. Material changes will be reflected by updating the “Last updated” date at the top of this page.

Contact

Questions about this Privacy Policy or your data can be sent through the contact form on avakiam.com.

Traveley plans trips with AI, and an AI can be wrong. Check opening hours, prices and availability before you travel — and especially before you book or pay for anything.