Privacy policy
This page explains what personal data Wayvin handles, what for, who else sees it, and what you can ask us for. It describes what the product does today: when the product changes, this page changes with it.
Who handles your data
The data controller is the entity that operates Wayvin. Its details are still to be confirmed and will be published here before this policy takes effect.
- Registered name: [PENDIENTE: razón social]
- Tax number: [PENDIENTE: CIF/NIF]
- Registered address: [PENDIENTE: domicilio social]
- Contact email: [PENDIENTE: email de contacto]
- Data protection officer: [PENDIENTE: DPD designado o no]
What data we handle
Only what we need to create your account and generate itineraries. Everything below is either entered by you or produced by the service itself.
- Account: your email address and your display name. The name reaches us from WorkOS, built from your first and last name.
- Travel preferences: pace, budget and interests. These are picked from a closed list of options that the service validates on arrival; they are not free text.
- Trips: the title you write, which is free text; how many adults, how many children and how many extra companions are travelling; the language the itinerary is written in, chosen from a closed list when the trip is created; the ways you move between activities in a city, chosen from a closed list; notes you write for the trip, which are free text; and each destination with its city, country, coordinates, exact start and end dates, and optional arrival and leave times.
- Itinerary: the hour-by-hour plan the service generates, with each slot of the day and the alternatives for each slot.
- Credits: your balance and your transaction history, both purchases and spending.
- Identifiers from our providers: your WorkOS user id, your Stripe customer and subscription ids, and the ids of the events both of them send us.
- What we do not store: no Wayvin table holds your IP address, your user agent, a device id or your geolocation. The only coordinates we store are those of the destination you choose, never those of your device.
What we use the data for
Every use answers a specific purpose. There is no advertising profiling and no automated decisions with legal effects on you.
- Giving you access to your account and keeping your session open. Legal basis: performance of the contract you accept when you sign up.
- Generating and revising itineraries from your trip's destinations, dates, notes, language and preferences. Legal basis: performance of the contract.
- Processing credit pack purchases and keeping a record of your balance. Legal basis: performance of the contract and our accounting obligations.
- Sending you a receipt when you buy a credit pack. It is the only email the service sends: there is no newsletter and no marketing. Legal basis: performance of the contract.
- Limiting how many actions one account can take in a given window, so nobody can exhaust the service. The counter is keyed to your internal user id, not to your IP address. Legal basis: our legitimate interest in keeping the service available.
Who else sees your data
We do not sell data and we do not share it for advertising. This is the complete list of providers involved and exactly what each one receives.
| Provider | What for | What it receives |
|---|---|---|
| WorkOS | Identity and authentication | Your email address and your first and last name. Signing in happens on WorkOS's own domain, not on Wayvin. |
| Cloudflare | Hosting, database, file storage, request rate limiting, background task execution, trip PDF rendering and technical logs | Everything described in the section above: Wayvin's database and files are hosted on Cloudflare. Rendering a trip PDF also sends that itinerary's HTML to Cloudflare's browser service. |
| OpenAI, Anthropic and Google (Gemini) | Generating and revising itineraries | The destination cities, the exact travel dates, how many adults, children and extra companions are travelling, your pace, budget and interest preferences, the ways you move between activities in a city, any notes you have written for the trip, the itinerary language, any arrival or leave times you set on a destination, and the per-day windows, timezone and gaps the planner derives from those dates, along with a trip identifier. When the itinerary is not already in that language, the draft place names and one-line reasons are sent back up to twice on that vendor so they can be rewritten. Nothing else. |
| Google Places | Checking that a place in the itinerary exists and fetching its photo | The place name and the city, taken from the itinerary, plus our server's IP address. None of your data and no user identifier. |
| Google Maps Platform (city search) | Suggesting cities while you add a stop to a trip, and fetching the chosen city's country and coordinates | What you type in the city field and the city you pick, sent straight from your browser to Google together with your IP address and the page's address. Only when you use that search; it carries no email, name or user id. |
| Wikimedia Commons | A photo for a place when Google Places has none | The same data as Google Places: the place name and the city. No user identifier. |
| Stripe | Charging for credit packs | Only your internal user id, the pack reference and the number of credits. Never your email, your name or your address. Your card details are collected by Stripe on its own page and never pass through Wayvin's systems at any point. |
| Resend | Sending the purchase receipt and the confirmed-trip email | Your email address and your display name. When you confirm a trip, also the attached PDF of that itinerary. |
| Google (Google Analytics and Google Tag Manager) | Website usage analytics, only if you accept the analytics cookies | If you accept: the pages you visit on Wayvin, technical details of your browser, and your IP address, which Google uses to infer an approximate location, together with the random identifier in its cookies. We send it neither your email, nor your name, nor your user id. If you refuse analytics, Google receives nothing whatsoever: its script is never loaded. |
About the three language models: they are chained, so if the first one fails the next one is tried. That is why the content of a single trip can reach all three during one failing generation. What never leaves Wayvin is your identity: not your email, not your name, not your user id, and not the title you gave the trip. What travels with the request are internal identifiers for the trip and its destinations, which on their own do not identify you.
International transfers
Wayvin pins no region for its data. Neither the database nor the file storage carries a geographic restriction, and the code runs on whichever Cloudflare node serves each request, wherever that is. Several of the providers in the table above are United States companies. In particular, if you accept analytics, the data Google Analytics collects is processed by Google LLC in the United States — a transfer that happens only with your consent and that stops if you refuse it or withdraw it. In short: your data may be processed outside the European Economic Area.
Transfer mechanism: [PENDIENTE: confirmar mecanismo de transferencia por proveedor — DPF / cláusulas contractuales tipo]
How long we keep your data
There is no automated deletion today. We keep your data while your account is active and erase it when you ask us to: no scheduled process removes it on its own. Planned retention period: [PENDIENTE: plazo de conservación]
The credit transaction history is kept for as long as our accounting and tax obligations require, even if you have asked us to erase everything else.
Your rights
You can exercise these rights over your data:
- Access: find out what data we hold about you.
- Rectification: correct anything inaccurate.
- Erasure: ask us to delete it.
- Restriction: ask us to stop using it without deleting it.
- Portability: receive your data in a machine-readable format.
- Objection: object to processing we base on our legitimate interest.
All of them are exercised by writing to [PENDIENTE: email de contacto]. Worth stating plainly: Wayvin has no button today to delete your account and no feature to export your data. Erasure and portability are handled by hand when you write to us, and we promise no other route.
If you believe we have not handled your request properly, you can lodge a complaint with the Spanish Data Protection Agency (AEPD), which is the competent supervisory authority.
Cookies
Wayvin uses four cookies the service needs in order to work and, only if you accept them, two Google analytics cookies. None of them is for advertising. The details are in the cookie policy.
Changes to this policy
If we change what we do with the data, we will update this page and the date above. While any field is still marked as pending, this policy is not yet complete.