Privacy Policy

Reveldays helps you turn travel booking emails into organised trips. This policy explains what we collect, why, who processes it on our behalf, and the control you have. The short version: we only ever process the booking emails you choose to forward or upload — never the rest of your inbox — and you can delete everything, anytime.

Who we are

Reveldays (“we”, “us”) is the data controller for the personal data described here. The operating entity is Scopeos Limited, trading as Reveldays (a company registered in England and Wales, number 16775511). For any privacy question or request, contact privacy@reveldays.com.

What we collect

• Account details — when you sign in with Google we receive your name, email address and profile photo. We do not receive your Google password. We use the personal data we collect to improve our AI and our product, and to personalise the service for you. Sign-up and session-report emails sent to the founder are deleted from his mailbox when you delete your account.
• Your account photo — we save a copy of your Google profile photo and use it as your account picture, rather than loading it from Google each time (that way viewing Reveldays doesn’t tell Google what you’re looking at). It appears next to your name to people you invite or share a trip with, and on any trip you choose to publish with your name on it. Our copy is kept in a public storage folder, so anyone who has the picture’s web address can open it; that address is a long code, not your name or email. You can remove it any time in Settings ▸ Account — that deletes our copy — and put it back just as easily. Deleting your account deletes it too.
• Other email addresses you link — if you add a work or shared address in Settings ▸ Email, we keep that address, whether you confirmed it and when, so bookings you forward from it are filed into your trips. We email it once to confirm, with a link that works for 24 hours. You can remove it at any time, and deleting your account deletes it too. When someone whose address we can’t match to an account forwards us a booking, and we can confirm the email really came from that address, we reply once a day to say so. That reply quotes nothing from their email and never says whether anyone has an account.
• The booking emails you send us — the confirmations you forward to your import address or upload as files, and the trip details we extract from them (flights, stays, cars, reservations, dates, places and amounts). An email you forward passes through Postmark, the service that receives it for us (see the list of who processes data for us below). To let you re-check an email when our reading of it improves, we keep the email’s content for about 14 days, encrypted, and then delete it automatically; it is also deleted immediately if you delete the email data or your account. After that, only the extracted trip details remain. Ticket and voucher attachments (like a boarding pass or car-rental voucher PDF) are saved to your trip’s Wallet so you can open them at check-in; they are stored privately and deleted when you delete your email data or your account. We also read the scannable barcode on those tickets (the QR or boarding-pass code) and keep a picture of it, plus what it encodes, so you can scan straight from the app at the gate. A barcode is like the ticket itself, so it stays strictly yours — never visible to people you share a trip with — and it is deleted with your email data or your account.
• Passports you save — if you save a passport in Settings ▸ People (yours, or one you hold for someone you travel with), it is sealed so that only Reveldays can unlock it. We show it back only to you, when you tap Show, for 60 seconds, so you can copy it into an airline’s or a government’s form; for that moment it is released to our server to show you. When you ask Purser about your UK eVisa it can also show you only the last two characters of that passport, when you tap, so you can check it against your UKVI account; they are never sent to our AI provider. Each time it is shown we record when and whose (never the numbers). That record is kept until you delete your account. Removing the passport, or “Forget all saved passports”, deletes the passport itself; deleting your account deletes both. Only save someone else’s passport if you are allowed to hold it for them.
• Your passport country, where you live and your status there — if you tell Purser or save them in Settings ▸ People, we keep them to answer visa, entry and residence questions. Your status is saved only when you tap to save it. They are sent to our AI provider with your questions only while “Use my history” is on, as country and status codes, never beside your name. Your nationality may be part of a web search our AI provider runs for that answer; your status never is. Remove them in Settings ▸ People at any time; deleting your account deletes them.
• Your mobile number for bookings — if you add it in Settings ▸ People, we keep it so you can copy it into a restaurant’s or airline’s booking form. Only you can see it. It is not shown to people you share a trip with, not used to contact you or for marketing, and not sent to our AI providers. Remove it in People at any time; deleting your account deletes it.
• Trips you create, save or copy from a public trip, the people you follow, and any notes or edits you add.
• Minimal product analytics — first-party events (e.g. “a landing page was viewed”, “an import started”) tied to an anonymous device id, so we can understand and improve the product. At the start of each visit we also record how you got here — the referring site’s domain (never the full address) and the utm_source / utm_medium / utm_campaign tags on the link you followed — plus your device type (phone/tablet/desktop), browser family, and the country you connected from. The country is worked out on our own server from your connection address at that moment, against an offline database (GeoLite2 data created by MaxMind). The analytics events do not keep the address (our hosting’s request logs do; see Request logs below). These events never include your IP address, and we don’t fingerprint your device. They carry no email content, prices, booking codes or names. Your browser talks only to us: we use no third-party advertising or tracking scripts. To analyse these events (funnels, feature usage) we mirror them, server-side and with the same minimal content, to PostHog’s EU cloud (see sub-processors below). One exception: Discover searches that find nothing. If a search on Discover or Explore finds no trips, we keep the words you typed (up to 40 characters; anything that looks like an email address, a web address or a long number is dropped) for 90 days, to improve our product. If you are not signed in, they are tied only to the anonymous device id above, and linked to an account only if you create one in the same browser within 2 hours. They are never sent to PostHog, and once they are linked to your account, deleting your account deletes them.
• Device location on the map — only if you ask, never stored. On the trip map you can tap “Show my location” to see where you are relative to your plans. Your location is read once, on your device, in your browser, and used only while that view is open. It is never saved and never sent to our servers or anyone else.
• Device location on a trip day — the place is never stored; the stop is, while “Remember my visits” is on. On a trip’s day view you can tap “Show distances” to see how far away your next stop is. Your location is read once, on your device, and the location itself is never saved and never sent to our servers — not on this flow either. Separately, when “Remember my visits” is on in Settings ▸ What Purser knows about you — you can switch it off there at any time, and nothing is recorded unless and until your browser grants this site location access, a prompt that is yours to accept or refuse — your browser also works out which of that day’s stops you reached and saves that conclusion — the stop, whether you reached it or went past it, and when. The working out happens on your device; we never receive the coordinate, and we deliberately do not store how far you were from anything, because distances from several known places would add up to a position. Only you can see these; the people you travel with cannot. Switch it off and nothing new is recorded; use Forget my visit history to erase what already is.
• Invites. When you join from a friend’s link or trip invite, we record who invited you so we can credit them if you go Pro. Your inviter sees your first name, whether you went Pro, and whether that payment was refunded or disputed, never your email, trips, bookings or payment details.
• Notifications. If you turn on push notifications, we keep your device’s push address, its keys and your browser type so we can send them. Each push goes through your browser’s or phone’s push service (Google, Apple or Mozilla), which delivers it to your device. The emails we send, such as trip alerts and reminders, go through Resend. Every email carries a link to turn off that kind of email.
• Your calendar feed. If you switch on calendar sync, we make a private web address that your calendar app reads. It lists your trips’ flights, stays, cars and events with their dates and places, and never a booking reference, price or barcode. Your calendar app reads it without signing in, so anyone who has the address can see that list. You can replace the address (the old one stops working) or pause it, and we keep a record of when it is read.
• Partner links. Some links take you to a travel partner, such as a flight, hotel or activity site (for example Travelpayouts, Stay22, Kiwi.com and the sites they send you on to). Nothing is sent until you tap. When you do, your browser goes to the partner with the details of what you were looking at, such as the city or route, dates, number of travellers and currency, together with your IP address and any cookies that site already has. We do not put your name, email or account in the link. Each partner then uses that information under its own privacy policy, and we may earn a commission if you book.

How we use it

• To read your booking confirmations and file them into the right trip, automatically.
• To show, cost, time-line and map your trips, and to power optional AI trip planning.
• To run the optional Public Trips feature — if (and only if) you publish a trip, we show an anonymised version (places, a rough budget band and, only if you add them, your one-line “What I’d do again” and your pace and spend ratings; never your identity or exact prices) so others can discover it and copy it into their own draft.
• To keep the service secure, working and improving.

Our legal reasons for using your data

UK data protection law says we need a legal reason for each way we use your data. These are ours, in plain words. Where the reason is “legitimate interests”, you can object, and where there is a switch for it in Settings we say so. Where it is consent, you can withdraw it at any time; that doesn’t affect what we did before.

• It’s needed to give you the service you signed up for (UK GDPR Article 6(1)(b), contract): your account and trips, reading and filing the booking emails you send us, Purser answering the question you asked, the web checks it runs to answer you, your own saved passport, your calendar feed once you switch it on, the service emails and notifications that carry your trip facts, and the Companions marketplace matching you signed up for.
• Our legitimate interests (Article 6(1)(f)): using your trips and history, what you’ve asked Purser to remember (ordinary items), your travel party, and passports you hold for people you travel with, so answers fit you and your party (switches: Use my trips to personalise AI plans and Remember what I tell you); the Helping Purser improve records described above (switch: Help improve Purser); product analytics; keeping the service secure and fixing faults, including request logs; the one alert we get when someone signs up; the one email we send if your account has no trips after a day or two, and the weekly digest (each has an unsubscribe link); and showing you a partner’s price when you tap a partner link.
• Your explicit consent (Article 6(1)(a) and, for special-category data, Article 9(2)(a)): anything about your health, an allergy, an accessibility need or your beliefs that you tap Save on; a travel-party needs line; your residence status; the intent options and gender on a Companions profile (the “romance” option reveals something about your sex life); and publishing a trip.

Companions marketplace

The Companions marketplace lets members list a trip, or apply to join someone else’s, and message each other. It is for people 18 or older. Many members will be strangers to each other, so please read this before you join.

• What we collect for it: your date of birth (to check you are 18 or older; you type it in and we don’t check it against a document); your gender; your photos; a short bio; your languages and interests; your intent options (friends, adventure or romance); the trips you list and what you say about them; applications and the messages members send each other; anyone you block; and any report you make about a member.
• Who sees what: other members see your age range (never your date of birth), gender, photos, bio, languages, interests and intent on your profile card, as the marketplace shows it to them. Photos are stored privately and shown only through the marketplace. A member you block can no longer see you, and you can no longer see them. Our team can see reports and verification requests.
• Your consent for gender and intent. Your gender and your intent options, including “romance”, are shown to other members only after you give explicit consent on your profile, and we record when you did. Without it your profile isn’t visible to other members. Deleting your account deletes your profile and your messages.
• Reports and verification. You can report a member. A report is reviewed by our team and is kept even if the member or the person reporting later deletes their account, so that a report about someone isn’t lost. You can ask for your profile to be verified; our team reviews the request.
• Your safety. Meeting someone you’ve met online carries risk. Don’t send money to someone you haven’t met, and report anyone who asks. Our team’s review of a verification request is not a guarantee of who someone is.

Automated processing & AI

To read a confirmation we can’t parse ourselves, and to generate the AI trip plans you ask for, we send the relevant content to Google’s Gemini API. That is the text of a booking, and — where you use those features — the booking screenshots and receipt photos you upload. We send only what the task needs, and we don’t keep the images afterwards. When you dictate a question to Ask AI, the recording is sent to Gemini to turn it into text; we keep only the words you then send, never the recording.

We use Gemini on a paid plan, and under Google’s terms for paid use your content and Gemini’s responses are not used to train or improve Google’s models. Google retains them for a limited period only, to detect abuse of its own service. Unlike the rest of our processing, this step is not confined to the EU — Google may process or cache the content in any country where it operates facilities.

What Purser sends with a question. Every question you ask Purser goes to Gemini, with the earlier messages of that conversation. While Use my trips to personalise AI plans is on, we also send your record, so Purser can answer from it: for each trip that is under way or coming up, its dates and route, your flights, your stays (their name, town and street address, check-in and check-out times, and cancellation terms), hire cars, booked tables, tours and other reservations, the day-by-day plan and what is not booked yet; one line about each past trip; the things you’ve asked Purser to remember; your passport country and where you live, as codes; and your travel party’s details on questions where who is travelling matters. We take booking references (which Purser shows only as a link to your Wallet), email addresses, phone numbers and document numbers out of that text first, and passport numbers are never sent. Turn the switch off and we stop sending the rest of your record; a question you ask from inside a trip still carries that trip’s details.

Results may occasionally be imperfect, so always check important details against your original booking.

Helping Purser improve. When a check-in Purser runs for you stops, when you take over or correct something it filled, when you rate an answer down, or when you move, change or remove a booking we filed from your email or upload, or fix, re-check, file or dismiss an email waiting in your Inbox, we keep a short record of what went wrong: which step failed and a masked copy of what happened. We keep the same kind of record when our systems can tell an answer missed, a restaurant table was never confirmed, or a booking email is still unfiled. We also keep a short record when a job went right (a boarding pass filed after a check-in, a table confirmed, an answer you added to your trip, or a yes from you), and when we last asked you for feedback and whether you answered, so we ask no more than once a day. Names, booking references, numbers, contact details and passport data are removed first, and any of your own words are kept only after the same masking. Once a day we group these records by kind of problem and send a few masked examples to Google Gemini, which suggests a cause and a fix; a person on our team reviews every fix before anything changes. We do this because we have a legitimate interest in making Purser work reliably for everyone. We keep each record for 90 days, or less if you delete the trip, conversation or account it is about. You can object at any time: turn off Help improve Purser in Settings ▸ What Purser knows about you. We then stop keeping these records about you and delete the ones we hold.

Personalised recommendations

Reveldays tries to suggest trips, plans and places that actually suit you. To do that we use only your own first-party data: your answers to the travel-taste questions (how you like to travel, what draws you and who you usually travel with), the trips you track, save, copy or review here, the creators you follow, and — if you fill them in — the interests on your companion profile. Those signals are combined into a private taste profile that shapes what we recommend to you: the “For you” shelf, the starting points in the AI planner, and suggestions we show inside your own account.

There is one further signal, and it has both its own switch and its own permission gate: the stops you actually reached on a trip. With Remember my visits on (Settings ▸ What Purser knows about you), your browser works out on your own device which of a day’s planned stops you got to, and saves that conclusion — the stop, reached or passed, and when. Never the coordinate, never how far away you were. It marks those stops as done on your day and, in time, helps us suggest places that suit how you really travel rather than how you said you would. It is private to you: the people you travel with cannot see it. Turn it off and nothing new is recorded; use Forget my visit history, in the same place, to erase every visit we hold — your trips are untouched.

Things you tell us about yourself. If you tell Purser something lasting about yourself or the way you travel — “no red-eye flights”, “I’m BA Silver”, “my passport expires next March”, “tell me if anything about my Rome trip needs me” — we save it during that conversation and say so under the answer (“Remembered”, with Undo, which deletes it at once). Nothing is saved without that line. What we keep is the sentence you typed, or, for a date such as a passport expiry, a short label of ours with the date, never a guess about you; we never keep a child’s name or date of birth, card, loyalty or booking numbers, or contact details in it. Something personal — your health, an allergy, an accessibility need, your beliefs — is special-category data: we save it only when you tap Save on it, which is your explicit consent, we record when you gave it, and we never use it for offers, counts or web searches. When you tell us something newer on the same subject, it replaces the older one; the replaced value is kept, unused, for 30 days (so an Undo can restore it) and then deleted. A time-bound item carries its date, and Purser checks with you rather than trusting an old value. Everything is shown under Settings ▸ What Purser knows about you, where you can edit, pause or forget any item (forgetting one also deletes the values it replaced), turn the whole thing off with Remember what I tell you, or use “Forget everything you’ve learned about me” to erase it all at once. We use these items in every answer while Use my trips to personalise AI plans is on. We keep them until you delete them or your account; when you undo or forget something, or delete your account, it is removed from our live systems at once and from our backups within 8 days. They are included in your data download and never shown to travel companions. To shape an answer they are sent to Google’s Gemini API as part of the context for that answer, on the same terms as the rest of your AI use (see Automated processing & AI above).

Your travel party. You can keep a list of the people you travel with, so plans fit everyone. For each person we store only what you give us: who they are to you (partner, child, parent and so on), optionally their first name, and optionally their birth month and year — never a day of birth, and we never store an age: it is worked out from the month and year when it is needed. A person is added only when you type them in under Settings ▸ Profile & people or tap Save to your travel party on a suggestion Ask AI makes from what you wrote; nothing is saved from a conversation without that tap, and the suggestion appears only while Remember what I tell you is on. You may also add a short needs line for someone (for example “step-free access”). Because that can say something about a person’s health, it is special-category data: we store it only with your explicit consent, given when you save it on that screen, and we record when you gave it; Ask AI never offers to save one. Your travel party is private to you — the people you travel with, including anyone you share a trip with, cannot see it — and it is never written onto a trip: when we plan a trip’s days, the planner is told only who is coming and children’s age groups, never names or needs. Names, ages and needs are sent to Google’s Gemini API only inside your own Ask AI conversation, on questions where who travels matters. They are never used for analytics or advertising. You can edit or remove anyone at any time; “Forget everything you’ve learned about me” also erases the whole party; it is included in your data download and deleted with your account. You are giving us these details about other people, so please only add what they would be happy for you to share.

Three of these are on unless you switch them off, and every part has its own switch. Using your own trips, your travel-taste answers and the things you tell us about how you travel to personalise what we suggest is enabled when you create an account, so the product is useful from your first trip; each has its own switch in Settings ▸ What Purser knows about you and each takes effect immediately. Remembering the stops you reach is different: it needs your browser’s location permission before it can record anything at all, and it needs you to tell us once, in the app, that you want it — until you do, nothing is recorded. We never sell or share any of this data, and we never use it to advertise to you. With one exception, described below, none of it is shown to another traveller.

You can turn taste personalisation off at any time in Settings ▸ What Purser knows about you ▸ Travel style. With it off we stop building the profile and stop using it — nothing is deleted, so turning it back on picks up where you left off; if you’d rather erase it, use Delete my taste profile in the same place, which removes the profile outright and switches taste personalisation off, so nothing new is built (your trips are untouched). If you switch it back on, a new profile is built from your activity the next time a trip, booking, save or follow is added, including a booking filed from your connected Gmail.

None of this is shown to other travellers. Your taste profile, your recommendations and the signals behind them are private to your account. The one optional feature that shows anything taste-related to another person — “travellers like you”, which can display a shared interest such as food or mountains — requires you to have completed the taste questions and to have separately switched on the public opt-ins for it (a public profile and personalisation), on both sides. Turn either off and you disappear from it.

Who processes data for us (sub-processors)

• Supabase — our database, authentication and storage, hosted in the European Union.
• Cloudflare (Turnstile) — when you sign in with your email address, a quick check from Cloudflare confirms that a person, not a program, is asking for the sign-in email. Your browser sends Cloudflare your IP address and your browser’s technical details for this check; it is needed to keep the service secure, and Cloudflare uses it only to run the check. It is not used when you sign in with Google or Apple. Cloudflare is a US company.
• Google — Google sign-in (OAuth) and the Gemini API used for booking extraction and AI plans. Gemini runs on a paid plan: your content is not used to train Google’s models, and it may be processed outside the EU.
• Google Firebase App Hosting — runs the Reveldays app (European region).
• Google Cloud Logging — our hosting records each request to the app, and error messages, here for 30 days. See Request logs below.
• Postmark — receives every booking email you forward to your import address, so we can read it. It receives the whole email, including its attachments. Postmark is a US company.
• Push services (Google, Apple, Mozilla) — if you turn on push notifications, each notification is delivered by the push service your browser or phone uses. It handles the notification on its way to your device, so it sees your device’s push address.
• Travel partners — Travelpayouts, Stay22 (which can send you on to Booking.com and other hotel sites), Kiwi.com, Aviasales, Klook and similar. They receive data only when you tap one of their links, and from your browser, not from us: see Partner links above. Each is responsible for its own use of it.
• Your calendar app — if you switch on calendar sync, your calendar provider (for example Apple or Google) reads your private calendar address and keeps its own copy of your trips’ flights, stays, cars and events.
• Google Maps Platform — the maps in Reveldays are Google Maps. When a map comes on screen, your browser loads it from Google, so Google receives your IP address, your browser’s details and the area of the map you are looking at. It sees that the map is on our site, never which page of it. When you search for a place — a destination, a stop in your plan, a hotel, a station, a car-hire desk, or the town or village you set as your home base — the text you type is sent to Google to find matching places; for a stop or a booking we also send the coordinates of where you will be that day (or of the trip), so the results are near you. When a booking email arrives with a map link or a venue name and town, we send that address or name to Google to place the booking’s pin — never the email itself, your name, your booking reference or your account. The places the AI planner suggests are looked up on Google the same way, by their names and the trip’s area. When you ask Ask AI to find somewhere — “a ramen place near the hotel” — it sends Google a short search term (“ramen”) and the point where you will be that day, rounded to about 100 metres (or the name of the town you asked about); when you then ask about opening hours, it sends Google’s own identifier for a place that search just found; when it offers to start a draft trip, it sends the place’s name (“Seville”) to find where it is. It never sends your question, your name, your account or which trip you are on. When you pick a place, we keep its name as you saw it and Google’s identifier for it; its position on the map is kept for at most 30 days at a time, as Google’s terms require, and fetched again from Google when you next open the trip. For a home base we ask for a town or village, never a street address, and never your device’s location. Beyond the map area and these searches, we send Google nothing about you or your trip — not your name, your account or your bookings. Google handles this under its own privacy policy.
• ipwho.is — when you first sign in, we send your IP address to ipwho.is to estimate your country, so we can set your default currency and units. We don’t save that address ourselves (our hosting’s request logs do record it: see Request logs below).
• Google Search (through the Gemini API) — for a handful of questions that nothing in your Reveldays account can answer, and only those: whether there is a strike or a closure, what a country’s entry or visa rules are, an airline’s own published rules, opening times the map does not list, what is on somewhere. When that happens we run one web search. The search words follow a short template (a place, sometimes a date, and a few words about the subject), but our AI writes the subject and the place. So a search can contain a place, a date, an airline’s name and, if you asked about entry or visa rules, your nationality (for example “Italy visa Ukrainian passport”). If you ask for something near your stay, it can also contain the stay’s street address or area. We refuse any search that carries your name, a travel companion’s name, a booking reference, a flight number, a run of three or more digits (other than the digits of a stay address in your record) or your residence status. We don’t send your question as you wrote it, your name or your account. Google keeps the search data for a limited period. The sources we used are shown under the answer, along with Google’s own search suggestions, which Google’s terms require us to display with the result and to keep unchanged; those are stored on that message so they are still there when you re-open the conversation, and they go when you delete it.
• Ticketmaster — when you ask what is on, we can look up ticketed events (music, sport, theatre) near where you will be. We send a rounded location — an area of roughly a few kilometres, never a precise point — and a date range. We never send who you are or which trip you are on. This is not switched on yet.
• Resend — sends the emails we send, such as invitations, trip reminders and confirmations of an address you link. It receives the recipient’s address and the email’s content, and nothing else about you.
• Stripe — payments, only if you subscribe to Reveldays Pro. Stripe collects your card details and billing address directly on its own checkout pages (we never see your full card number) and takes your payments. We store only your subscription’s status, dates and Stripe’s identifiers for it, never the card. Deleting your account cancels the subscription and deletes your customer record at Stripe; Stripe keeps the invoices it is legally required to keep as a payment institution. To give each person one free trial, when a trial starts we keep a scrambled code made from your email address and from your card’s Stripe identifier — never the email or card itself. We keep it for 24 months after your last trial, including after you delete your account, because we have a legitimate interest in preventing abuse of free trials. Ask privacy@reveldays.com about it.
• PostHog (EU cloud) — product analytics. We send our own minimal, first-party usage events (never email content, prices, booking codes, names, your IP address or location) from our servers to PostHog’s EU region so we can see funnels and feature usage. Your browser never connects to PostHog. Deleting your account deletes the events linked to your account there too.

Sending data outside the UK and EU

Our database and app servers are in the EU. Several providers above, including Google (Gemini, Search, Maps, sign-in, push and logging), Cloudflare, Postmark, Resend, Apple and Mozilla’s push services and ipwho.is, may handle your data outside the UK and EU, including in the United States. UK law lets us do that only with a safeguard in place, such as the UK–US data bridge for certified companies or the UK’s standard transfer terms. We are still confirming which safeguard applies to each provider. Ask privacy@reveldays.com for the current position.

Request logs

When you use Reveldays, our hosting records each request in Google Cloud Logging: your IP address, the web address that was asked for (including anything after a “?”, which can include the private address of a calendar feed or an invite link), the time, and any error. We keep these for 30 days, to keep the service secure and to fix faults. These logs are separate from the analytics events above.

Cookies

We use the essential cookies needed to keep you signed in. If you open a friend’s invite link, we also set one cookie that remembers which link brought you, for up to 30 days, so we can credit your friend if you create an account; it is used for nothing else. We do not use advertising or cross-site tracking cookies.

Keeping & deleting your data

We keep your data for as long as your account is active. You are in control at any time from Settings:

• Delete email data — removes your imported emails and the data derived from them.
• Delete account — permanently removes your account and associated data.

You can also ask us to access, correct or export your personal data by emailing privacy@reveldays.com. If you’re in the UK or EU you have rights under the UK GDPR / GDPR, including the right to complain to your local data protection authority.

Children

Reveldays isn’t intended for children under 16, and we don’t knowingly collect their data. Signing in with Google doesn’t tell us your age, so we rely on you to meet that limit. The Companions marketplace is for people 18 or older, and the date of birth a member enters there is not checked against a document. If you add a child to your travel party, you are telling us about them on their behalf; see Your travel party above.

Changes

We’ll update this page if our practices change and revise the “last updated” date above. Questions? privacy@reveldays.com.