Privacy Policy

Last updated: 15 November 2026

1. Who is responsible and how to contact us

Barbara Bondani, an individual in Italy who runs Daysaway, is the controller responsible for the processing described in this notice. Contact support@daysaway.ai for privacy questions or rights requests.

This notice concerns our website, accounts and associated features. External booking sites and applications you connect have their own privacy notices. Their separate responsibilities do not remove our responsibility for disclosures we initiate.

2. Information we receive and its sources

We receive information directly from you, from people who invite you or collaborate with you, from a sign-in provider you choose, and through operation of the website.

CategoryExamples and source
Account and profileEmail, name, handle, profile photo, password hash for email sign-in, language, distance units, notification preferences; from you, or from Google or Apple when you sign in with them
Waiting listEmail address, the language of the page and the date of the sign-up; from you, before accounts open
Trip and world-map contentDestinations, dates, a cover image you choose among those Daysaway offers, places, notes, lists, checklist entries, tags, trip preferences, travel marks and associated history; from you and authorised collaborators
Reservations and budgetBooking references, dates, expenses, estimates, payer and group shares entered by users; no travel payment is collected by Daysaway
Imported plansThe text of a file you import (CSV, Excel, Word, PDF), of a text you paste or of a Google Doc or Sheet whose link you give, the places of a Google Maps list you export, and the title, chapters and transcript of a YouTube video whose link you give; from you (section 5). The file itself is not kept
Booking emails you forwardThe emails you forward to our address (their sender, subject, text and PDF attachments) and the other email addresses you link to your account to send them; from you (section 5)
Pages you add with the browser extensionThe address of the page and what it says of itself (its title, its type, its position) when you add it to a trip; from you (section 5)
Clicks on booking linksWhich partner link you opened, when, from which trip and item, on the site or in the app; recorded when you click (section 7)
Purchases of AI creditsThe pack, its price, the date, the state of the payment, the refunds and the link to Stripe's receipt; from you and from Stripe. Your card details go to Stripe only: we never receive them
Social and public activityFriend requests, invitations, membership, ratings, comments, reports, the authors you block, likes of blog articles and publication information; from users and their actions
Your ratings of the assistantThe thumbs up or down you give an answer of the assistant; from you
AI and connected applicationsMessages, answers, tool results and changes, model/turn metadata, approval decisions and authorisations; from your interaction and supported integrations
Support and communicationRequest title, type, text, contact details and replies; from you and the support process
Technical, security and usage recordsRequests, IP/network and browser information where processed, sessions, audit events, access restrictions, error reports, view counts and resource/cost records; generated during use
Product analytics (PostHog, with your permission)Pages opened, feature events, timings and errors, device and browser type, a random browser identifier and, when signed in, the account's internal identifier; never email, names or the text of trips
Experience analysis, or session replay (PostHog, with your separate permission)On the pages where it is used: clicks, scrolling, pointer movement and the structure of the page, with what you type and the content of your trips masked before they leave your device (section 8)

Core account fields are required to create and secure an account. Other fields depend on the feature you use; without the information needed for a feature, it may not work. Daysaway does not store travel documents, nor the files you import. Enter only information relevant to your trip, and keep identity-document numbers, credentials, payment-card details and unnecessary sensitive information out of notes and chats.

Signing in with Google

If you sign in with Google, we receive your email address, whether Google has verified it, your name and your profile picture, and nothing else: we do not ask for access to your mail, contacts, calendar or files. Google learns that you signed in to Daysaway. You can remove Daysaway's access in your Google account at any time; your Daysaway account stays, and you can sign in by setting a password from "Forgot password?" on the sign-in page.

Signing in with Apple

If you sign in with Apple, we receive your email address and, only the first time, the name you let Apple share. Apple may give us a private address of its own, which forwards our emails to you, instead of your real one. We do not receive anything else, and Apple learns that you signed in to Daysaway. You can stop using Sign in with Apple for Daysaway in your Apple account settings; your Daysaway account stays, and you can sign in by setting a password from "Forgot password?".

People without an account

A user can type your email address to invite you to a trip or to send you a friend request. We use that address to send you that message, keep it with the pending invitation or request until it is accepted, declined, cancelled or expires (30 days), and limit how many such emails an address can receive. We do not create an account or a profile for you. The email says who invited you; write to support@daysaway.ai to stop further invitations to your address or to have it removed. Users may also write about fellow travellers in their trips: see section 14.

We also read public posts on Reddit about travel planning, to find questions we can answer. We keep them for a few weeks at most and never link them to a Daysaway account.

The mobile app

This notice covers the website and the Daysaway app for Android and iOS alike: the same account, the same data and the same choices. What changes in the app:

  • Usage statistics. The app asks for your permission on a screen of its own, the first time you open it, instead of the cookie banner; you can change your choice in the app's Settings › Privacy. One choice holds for the site and the app (section 8). The screens you open are also counted without any identifier, and without storing anything on the phone, as visits to the website are.
  • Your position. "Show where I am" reads your position on the phone, in the app and on the website opened on a phone, only when you press it, to show it on the map. It is not sent to us or kept.
  • Voice. When you speak to the assistant, your phone's own speech recognition, provided by Google or Apple under their terms, turns your voice into text. We receive only the text you send.
  • Notifications. If you allow push notifications, we keep the phone's notification token and send notifications through Google's or Apple's notification service (section 6). You can turn them off in the app's settings or the phone's.
  • Trips offline. A trip you make available offline is stored on your phone until you delete it from the app, sign out, delete your account or remove the app.
  • Testing the app. If you ask to test the app before it is in the stores, we give your email address to Apple or Google, whose test services deliver the app, to send you the invitation, under their terms.
  • Crash reports. If the app crashes, it sends us a report of the error without your name, your account or your trips.

The app has no advertising identifier and does not read your contacts or your photo library. You can delete your account from inside the app.

3. Why we use information

We use information to operate accounts; save and display trips; provide collaboration and the sharing options you select; answer AI requests; deliver service emails; handle support and reports; prevent abuse; maintain reliability; understand use of the service; and monitor operating costs and feature allowances. Where applicable, we retain records for identified legal obligations and the establishment or defence of claims.

Where the GDPR applies, we rely on these grounds:

PurposeGround
Running your account, saving and showing your trips, collaboration, the AI assistant, importing a plan and supportPerforming our contract with you (the Terms)
Selling you packs of AI credits and handling their payments and refundsPerforming our contract with you; keeping the accounting records the law requires is a legal obligation
Security, rate limits, investigating incidents and moderating reported contentOur legitimate interest in a safe service; a legal obligation where one applies
Publishing a trip or a guide and showing your public profilePerforming our contract with you: it is a feature you choose, and you can unpublish at any time
Recording what the service costs to run and applying fair-use allowancesOur contract with you for the allowances; our legitimate interest in keeping account of our costs
Product analyticsYour consent
Experience analysis (session replay)Your separate consent
Facts our servers record and send to analyticsOur legitimate interest in understanding how the service is used; you can object with the switch in Settings > Privacy
The team reading what you enter, to answer your requests, find and fix problems and enforce the TermsOur legitimate interest in a service that works and is used lawfully; you can object (section 13)
Affiliate links and the record of their clicksOur legitimate interest in funding a free service and knowing which trips lead to a booking; the link carries nothing about you, and the partner's tracking starts when you click it
Waiting listYour consent, given by signing up to it; you can withdraw from a link in every message
Invitations and friend requests to people without an accountThe legitimate interest of the person inviting, and ours, in delivering the one message asked for
Promotional emails, if we ever send anyYour separate consent

Accepting Terms or reading this notice is not blanket consent. Where consent is required, we ask separately and provide a way to withdraw it without affecting the lawfulness of earlier processing.

4. Who can see trips and public content

Trip members can access content according to their role. Friends sharing and public publication are distinct choices. When you publish, the public page shows the permitted itinerary/guide content and author information. It shows the version you published: later changes become public only when you publish an update. The address of a public trip or guide, and of one shared with friends, includes your handle and its destination. Authors see how many times their public content was viewed each day, never by whom. It may be indexed by search engines and copied through import/save features.

Structured booking details, budget/cost information and the trip preferences are excluded from the public read model. This does not remove personal information you place in a title, note, checklist, image or comment. Check the publication preview and warnings before publishing.

Anyone, also without an account, can report a public trip or guide, with a reason and, if they want, a note. We keep the report, with the account of who made it or, for a visitor, a short-lived record of the network address used to limit abuse, and the team reviews it in our support desk, on our servers. If we make the content private, its author sees the reason in Daysaway, but not who reported it. You can also block an author: their public trips and guides no longer appear for you, and they are not told.

Unpublishing cannot automatically recall third-party downloads or previously imported copies. If personal information should be removed from an authorised copy or search result, contact us to assess the applicable request and recipients.

5. AI assistance and external applications

When you use the in-app AI assistant, we send the messages and relevant trip context, conversation history and tool results needed to generate an answer to OpenAI (OpenAI Ireland Ltd, Ireland), which processes them on our behalf under a data processing agreement. Context can include dates, itinerary notes, budget and the trip preferences, including children's ages entered for family planning. Tool calls may read or change trip content within the user's permissions.

OpenAI does not use this information to train its models. It keeps it in its abuse-monitoring records for up to 30 days, unless the law requires longer, and then deletes it; we do not ask it to keep the conversations. OpenAI may process the information in the United States (section 10).

Importing a plan

Where the feature is available, you can bring into the assistant a plan you already have: a file (CSV, Excel, Word or a PDF with text), a text you paste, the link of a Google Doc or Sheet you shared with "anyone with the link", a list you exported from Google Maps, or the link of a YouTube video.

  • Files. Our server reads the file, takes out its text and forgets the file at once: it is not saved anywhere, and its content is not written in our logs.
  • Google Docs and Sheets. Our server downloads the document from Google's public export of the link, without access to your Google account, takes out its text and does not keep the document. A document that is not shared with "anyone with the link" cannot be read.
  • YouTube videos. Our server asks fetchtranscript.com for the title, channel, chapters and transcript of the video. It sends only the identifier of the video, never anything about you.
  • Google Maps lists. The places of the file are looked up in our own catalogue and written as a new list of your trip, without the AI. Nothing of the file is kept but the places and notes added to the trip.

For the other ways in, the text is sent to OpenAI with your message, like anything you write to the assistant, to prepare the plan, and it is kept with that message in the conversation until you delete the conversation or your account. The places and notes the assistant writes into your trip stay in the trip. A file can contain more than a plan, such as booking codes, document numbers or the names of the people you travel with: remove what is not needed before importing it.

Forwarded booking emails

You can forward the confirmation of a booking to the address shown in Settings. Cloudflare receives the email for us; our server reads its subject, its text and its PDF attachments, and the assistant of your trip writes the booking into it, in a new chat of that trip, sending the text to OpenAI like any message to the assistant. We accept emails only from your account's address or from other addresses you confirm, each linked to one account only. The email itself is not stored: one we cannot yet place in a trip waits at most 30 days, then it is deleted; its text stays in the chat until you delete the chat or your account. A confirmation can hold other people's names and booking codes: forward only what the trip needs.

Browser extension

With the Daysaway browser extension you can add the page you are looking at to a trip. It reads a page only when you click its icon: the address of the page and what the page says of itself for other programs, such as its title, its type and its position; on Google Maps only the address. It is signed in to your Daysaway account and sends what it read to our server, nothing else of your browsing.

We store conversation history and operational turn records in Daysaway. You can delete your own conversation using the chat controls. Information copied into the itinerary is separate from that conversation and is not necessarily removed when the chat is deleted.

When you authorise an external application such as ChatGPT or Claude, it can receive trip information under the granted permissions. Revoking its authorisation stops future access through that grant; it does not recall information already received or undo earlier changes. Its own provider conditions govern its separate processing.

6. Recipients and external resources

We disclose information needed for the relevant purpose to contracted providers, authorised recipients and, when lawfully required, competent authorities. The people who run Daysaway access your content only as described in section 9.

RecipientWhat it does and what it receives
Hetzner (Germany)Hosts our servers: the database and everything the service stores
Cloudflare (United States; files stored in the EU)Delivers the site, protects it from abuse with a challenge on the sign-in forms and on the reports of visitors, receives the booking emails you forward to us and stores the images Daysaway offers, such as trip covers; it sees the network requests and keeps a record of them, with the IP address, for up to 31 days
Google, for sign-inOnly if you sign in with Google: the sign-in exchange (section 2)
Google, for mapsWe ask Google for the identifier of a place, never anything about you; "Open in Google Maps" takes you to Google
Brevo (France)Delivers our emails: the recipient's address and the content of the email
OpenAI (OpenAI Ireland Ltd, Ireland; it may process in the United States)Answers the in-app assistant: your messages and the trip context; no training, up to 30 days in its abuse-monitoring records (section 5)
Anthropic (Anthropic Ireland, Limited; it may process in the United States)AI tools the team uses to develop the service and investigate problems: never names or email addresses, no training (section 9)
Applications you connect, such as ChatGPT or ClaudeThe trips you authorise them to read or change; they act for you, under their own terms
Google (Firebase Cloud Messaging) and Apple, for app notificationsOnly if you allow push notifications in the app: the phone's notification token and the notification itself
GetYourGuide (Germany), Stay22 (Canada), Booking.com (Netherlands) and Expedia (United States)What an affiliate link carries, when you click it (section 7)
Stripe (Stripe Payments Europe Ltd, Ireland; it may process in the United States)Only if you buy AI credits: takes the payment on its own page, with your email address, the pack and its price; you give your card details to Stripe, not to us. Stripe sends the receipt and uses the payment data also for its own legal duties, such as fraud prevention
OpenFreeMap, Wikimedia Commons, Pexels, PixabayYour browser or the app loads map tiles and photos directly from them, which shows them your IP address and the type of browser or device
Tools we run on our own serversPostHog (analytics and, with your separate consent, session recordings), Plausible (visit statistics without cookies), error tracking, the support desk and logs: no recipient outside our hosting

7. Affiliations and external bookings

Our affiliate links go to GetYourGuide (Germany), where activities and tours are booked: "Book on GetYourGuide" opens its search with the words of the activity and our partner reference. The link carries no identifier of you or of your Daysaway account. Once you are there, GetYourGuide processes browser and network information and applies its own cookies and privacy choices, including the cookie that tells it you came from Daysaway; if you book, we receive a commission. There is no partner script or widget on our pages; if we add one, processing may start before a click: we will describe that flow and obtain consent where required.

"Search stays on Booking.com" and "Find a place to stay" open Booking.com's search of stays through Stay22 (Montréal, Canada), an affiliate network, with our partner reference. The link carries the place to search, the dates, the number of adults, the ages of any children in the trip preferences and the language of the page, so that Booking.com shows the right search; it carries no identifier of you or of your account. When you click it, your browser passes through Stay22, which records the click, then reaches Booking.com; both apply their own cookies and privacy notices. If you book, Booking.com pays a commission through Stay22. For each booking, Stay22 shows us the site and the kind of booking, the place and the dates of the stay, the number of rooms or people, the date of the booking, the country and the type of device of the traveller, a booking reference and our commission. It does not give us your name, your email or any other contact detail, and we cannot link a booking to your Daysaway account.

"Search cars on Expedia" and "Rent a car for this trip" open Expedia's search of rental cars (Expedia, United States) with where and when the car is picked up and returned and our partner reference, nothing about you. Expedia applies its own cookies and privacy notice.

When you click a booking link, our server records the click: which partner, when, from which trip and item, and whether on the site or in the app. We use it to count the clicks and to understand which trips lead to a booking; the partner receives nothing of it.

Travel bookings and payments are completed outside Daysaway. We do not receive travel card details merely because you keep a booking record in your itinerary. For each booking made through our links, GetYourGuide shows us the activity, its city, the booking and travel dates, the number of participants, the country the traveller comes from, its booking reference and our commission. It does not give us your name, your email or any other contact detail, and we cannot link a booking to your Daysaway account.

Daysaway shows no third-party advertising, and we do not sell your personal data to advertisers or data brokers. There is no third-party tracking on our pages: the tracking of an affiliate link starts when you click it.

8. Cookies, local storage, product analytics and session replay

Cookies. We use the technical cookies the service needs to work: they keep you signed in and protect your session, remember your language and your answer about cookies, and complete a sign-in with Google or Apple. They last one year at most and are not used to follow you. Your browser also keeps some settings you choose, such as the theme or how the map is shown, until you clear them. We use statistics cookies only if you agree, as described below. You can change your choice at any time from "Cookie preferences", at the bottom of every page, or in Settings › Privacy; in the mobile app, in its settings. One choice holds for the site and the app.

We count visits to the public site, and the screens opened in the mobile app, with Plausible, which runs on our own servers, stores nothing in your browser or on your phone and does not identify you.

With your permission, we also use PostHog, an analytics tool that runs on our own server in Germany, to understand how Daysaway's features are used: pages opened, actions such as creating a trip, how long they take and the errors you meet. Events are linked to a random identifier stored in your browser and, when you are signed in, to a random code created for your account, which is not your email, your name or your public identifier and is stored nowhere else. We do not send the text of your trips, and we do not pass your IP address on. Without your permission nothing is sent to PostHog from your browser. You can refuse without losing any feature, and change your choice at any time as described above.

When you are signed in, our servers also record that certain things happened in your account, such as a trip created, an invitation accepted or an answer of the assistant ended, without their content, and send those facts to PostHog under the same key. We do this on the ground of our legitimate interest in understanding how the service is used. You can turn it off at any time in Settings > Privacy: it stops both the sending to PostHog and that record in our database.

Session replay

With your separate permission ("Experience analysis" in the cookie settings), we use PostHog, on our own servers in Germany, to record how the world map and the trip editor are used, to understand usability problems and diagnose errors. What you type and the content of your trips are masked before they leave your device. Recordings are not linked to your account, are kept for at most 12 months and can be watched only by the people who run Daysaway, for those purposes.

You can refuse without losing access to Daysaway, and withdraw your permission at any time in Cookie settings or in Settings > Privacy, which stops further recording; to have earlier recordings deleted before the 12 months, write to support@daysaway.ai. This permission is separate from accepting the Terms and from any marketing choice.

9. Security, logs and operating costs

We use technical and organisational measures appropriate to the processing, including account access controls and restricted handling of credentials. Passwords are stored as hashes. Technical records help prevent abuse, diagnose incidents and enforce resource allowances. No system can guarantee absolute security.

The cost ledger records provider, operation, resource units, cost, time and user/trip/application references to monitor service costs and AI allowances. It is distinct from a travel payment record. Security events can include hashed IP/browser values. Error reporting is designed to redact credentials and URL query/fragment data, but paths and other metadata may still identify a user or trip.

Improving the product: what we keep and read

To improve Daysaway we keep, in our own database: a record of what happened in each account over time, for example that a trip was created or changed and by which means, without its content, kept for 12 months and then deleted; the text of place searches that found nothing, kept for 12 months to fix the catalogue of places, after which only a count remains, not linked to any account; and your conversations with the assistant, for as long as you keep them. The four people who run Daysaway can access everything you enter, such as trips, dates, places, notes, lists, failed searches and assistant conversations, each bound to confidentiality; they look at it only to answer a request of yours, to find and fix problems and to enforce the Terms, and what they read is never used for advertising or to train AI models. To develop the service and investigate problems they may use AI tools, such as Claude by Anthropic: these tools may see information such as the content of a trip or the internal identifier of an account, but never your name or email address, and the information is not used to train their models. You can object by writing to support@daysaway.ai.

10. International processing

Our servers are in Germany. Some of the services we use are in other countries:

WhoWhereSafeguard
Hetzner (servers), GetYourGuide (affiliate links)GermanyNo transfer outside the EU
Stripe (payments of AI credits)Ireland (Stripe Payments Europe Ltd); processing also in the United StatesStandard contractual clauses
Expedia (car rental links)United States: your browser goes there when you click the linkNot a transfer we make
Stay22 (affiliate links to Booking.com)Canada: your browser passes through it when you click the linkNot a transfer we make; Canada has an adequacy decision of the European Commission
Brevo (emails)France; some of its own providers in the United StatesEU-U.S. Data Privacy Framework and standard contractual clauses, in Brevo's agreement
Cloudflare (site delivery; files kept in the EU)United StatesEU-U.S. Data Privacy Framework and standard contractual clauses
OpenAI (AI assistant)Ireland; processing also in the United StatesStandard contractual clauses
Google (sign-in, profile photo, Android notifications)Ireland (Google Ireland Limited); processing also in the United StatesEU-U.S. Data Privacy Framework, to which Google LLC is certified, and standard contractual clauses
Apple (sign-in, iPhone notifications)Ireland (Apple Distribution International); processing also in the United StatesStandard contractual clauses
OpenFreeMap (map tiles), Pexels and Pixabay (photos), Wikimedia Commons (photos)Hungary, Germany and the United States: your browser contacts them directly when it loads the map and the imagesNot a transfer we make: your browser asks them for the file

The AI assistant is the main transfer today: OpenAI Ireland Ltd may have the information processed by OpenAI in the United States, under the standard contractual clauses approved by the European Commission or an adequacy decision where one applies.

Where legally required, transfers use a valid mechanism such as an applicable adequacy decision or appropriate contractual safeguards and additional measures. Contact support@daysaway.ai to request information or an available copy of relevant safeguards, subject to necessary redactions.

11. How long we retain information

We retain information for the period needed for its stated purpose and any specifically applicable legal retention requirement. Data in live systems, external providers and backups may follow different deletion cycles. Copies and backups of the analytics events follow the same 12 months.

After an account is deleted, we may keep some information for as long as needed to comply with the law, to resolve disputes or to establish, exercise or defend legal claims, and for at most 24 months; when a claim or a request of an authority is pending, we keep the data it concerns until it ends.

InformationHow long we keep it
Waiting listUntil we open to everyone, and at the latest until 1 October 2027; at once if you unsubscribe
Account, profile and tripsWhile you have the account; we do not delete accounts for inactivity
AI conversations, with the text of what you importedUntil you delete them or your account
Files you importNot kept: read and forgotten at once
Booking emails you forwardNot kept once read; one waiting for its trip at most 30 days
Clicks on booking links24 months, then only as totals, without any link to you or your trips
Addresses whose emails bounced or were reported as spamIn coded form, until the emails are turned on again or the account is deleted
Public Reddit posts we readA few weeks at most: texts erased 30 days after we look at them, the others dropped after 14 days
Reports of public content12 months after the report is handled
Purchases of AI credits10 years from the purchase, as Italian accounting law requires, also after the account is deleted; the credits of a pack expire 12 months after they were added
What the AI assistant sends to OpenAIUp to 30 days in OpenAI's abuse-monitoring records, then deleted
Trip versions and change historyUp to 100 versions per trip; the record of changes for 30 days or the latest 2,000 changes. A text you remove from a trip stays in its earlier versions until they are replaced by newer ones or the trip is deleted
Invitations30 days, then deleted
Sessions and authorisations of connected applicationsA session on the site lasts 7 days and is renewed while you use it; an authorisation of ChatGPT or Claude lasts 30 days, renewed while it is used, and ends when you revoke it; a revoked one is kept 30 days as a record, then deleted
Security and audit records24 months
Records of usage and cost24 months, then kept only as totals, without any link to you or your trips
Support requests24 months after the last message; deleted with your account
Analytics events12 months
Record of what happened in your account12 months, then deleted
Text of place searches that found nothing12 months, then only a count without any link to you
Session recordings12 months
Backups30 days: data you delete, or a deleted account, stays in them until they expire, and we never restore a deleted account from them. Technical logs: 14 days

12. Deletion, sharing and remaining copies

You can delete your account through the account process, with identity verification. It revokes sessions and connected-app grants and removes owned trips/guides, so their members also lose access. Your AI conversations, comments, ratings and certain other account data are removed through that process, together with the record of what happened in your account and your profile in our analytics. The usage events already collected by our analytics stay, without your profile, under a random code that is erased from your account at that moment, so they are no longer linked to you; they are kept for at most 12 months.

Deleting an account does not necessarily remove every contribution to someone else's trip, every imported copy, every support exchange or every legally retained operational record. Group expenses on other people's trips remain with payer/member links cleared. Imported copies remain; the recorded source-author name is cleared by the account deletion service, but personal information embedded in copied text is not automatically removed. Your account record stays without your name, email or profile, so that what other people's trips still show remains consistent.

13. Your choices and rights

You can manage relevant profile/settings, trip access, publication, chat deletion and connected applications in the product. Your choices about email are under "Emails we send" below.

Depending on applicable law, you may request access and information, correction, erasure, restriction, portability and objection to relevant processing, and withdraw consent where it is the basis. Rights have conditions and exceptions; we will explain any restriction and applicable complaint route. You may object to direct marketing where applicable. Contact support@daysaway.ai; we may request proportionate identity verification, without routinely requiring a passport.

You may complain to the competent data-protection authority without first contacting us. In Italy it is the Garante per la protezione dei dati personali (garanteprivacy.it); you can also contact the authority of the country where you live.

Emails we send

Service emails, such as address verification, password reset, security notices, invitations and important changes to the service, the Terms or this notice, are sent while you have an account. Notification emails (a friend request, a new comment on your trip) can be turned off in Settings > Notifications or with the one-click link in each of them; they never contain the text of the comment. We send no newsletter or promotional email without your separate consent. Emails are delivered by Brevo, in France. They carry a counter that tells us, as totals only, how many are opened and how many links are followed: we do not know who opens them. If an email to you bounces or you mark it as spam, Brevo tells us and we stop the emails you can turn off, keeping your address in coded form; you can turn them on again in Settings > Notifications.

14. Adults, family trips and sensitive information

Accounts are intended for people who are at least 18 and have reached the age of majority where they live. Adults may plan family trips, including ages of children in the preferences. This is not the same as offering accounts to children. If we have reason to believe that an account belongs to a person under 18, we may suspend or delete it.

If you add information about fellow travellers, consider their privacy and provide only what is needed and lawfully shared. Health, accessibility needs, dietary requirements or documents may disclose sensitive information even if Daysaway does not request it. Contact us if information about a child or another person has been added improperly.

Files and images

You can import a plan from a file, which we read and do not keep (section 5); you cannot otherwise upload files: trip covers are chosen among the images Daysaway offers. Your profile photo is the one of your Google account, if you sign in with Google: your browser loads it from Google, and we do not keep a copy. You can replace it with one of the Daysaway avatars in Settings > Profile.

Notes, checklists, reservation fields, the trip preferences and chat messages are free text, so they can still hold sensitive information about you or fellow travellers, such as health, dietary or accessibility needs. We do not ask for it, and we suggest you leave it out unless the trip needs it. If you enter it, we use it only for the feature you asked for, such as an itinerary that suits a dietary need, and the team reads chats only as described in section 9. Contact support@daysaway.ai to have such information removed if you cannot remove it yourself.

15. Personalisation and automated decisions

Trip preferences and the request you make can influence AI suggestions. We take no decision based solely on automated processing that has legal or similarly significant effects on you. A few automatic rules keep the service running: usage limits, such as the weekly free AI of the assistant; the refusal of disposable email addresses at sign-up; and comments hidden after three reports, which a person in the team reviews on request. Blocking an account is always decided by a person.

16. Changes to this notice

We will identify the version and effective date of the published notice and communicate material processing changes appropriately. If a new purpose needs consent or another prerequisite, we will satisfy it before processing. Updating this notice or continued use is not a substitute for obtaining required consent.

Changes to AI providers, hosting, analytics, payment tools, partners or sharing features require review of the affected data flows and wording. Not every supplier change requires consent, but applicable notification, objection and contractual duties must be considered.