Privacy Policy
Last updated: October 10, 2026
1. Who We Are
Mara (withmara.app) is responsible for the personal information it handles. Our Privacy Officer, the person in charge of the protection of personal information under Quebec's Law 25, can be reached at [email protected]. That address is also where to send any question or request described in this policy.
2. What We Collect
- Account: your name, email address, hashed password, and optional profile photo. If you sign in with Google, Facebook, or Apple, we store the sign-in tokens that provider issues.
- Trackers & trips: the destinations, dates, traveler counts, and budget thresholds you set, plus the names and notes you give them, and the places you add to a trip itinerary. If you tap Locate me on a trip map, your approximate location is used to centre the map and is never stored.
- Journal: the stamps you make (a place name, dates, the memory you write, and its illustration), what you write for each Day, where you say you were each Day, and the photos and videos you add, with their captions. Before we store a photo we re-encode it, which removes its embedded metadata; we keep the date and time it was taken, to place it on the right Day. Where a photo or video was taken is kept only if you choose it for that stamp: your device then reads the location saved in the file before uploading and sends us only that point, rounded to about 100 metres. If you don't, the location never leaves your device, and our servers never read one from your files. A video is re-encoded the same way, on our servers: we keep our own copy (at most 720p, with its sound), the date and time it was shot and, if you chose it, that rounded point, and we delete the file you uploaded once that copy is made, or within a day if it can't be. You can also place a photo on its stamp's map yourself, and remove one photo's place, or every place read from your photos, at any time. Photos and videos are stored privately: you see them, and so does anyone who opens a share link you create. If you make a trip reel, we make a video from your stamp's photos, videos and words on our servers and keep it until you make another or delete the stamp. Deleting a photo or video it shows deletes the reel too. A reel is only ever yours to download: it is never shared, and nothing in it is sent to Google, an AI provider or anyone else. To put a stamp on your Journal map, or a Day on a stamp's map, we look up the place name you type in our own list of the world's places, on our servers, and keep the spot it matches; nothing is sent to Google or any other map service to do it. Once a stamp's map has loaded, the box for a Day's place also suggests places from Google as you type, as a trip itinerary does, so what you type there goes to Google. If you pick one of its suggestions, we keep its name, its spot and Google's ID for it, and when a share link shows that spot we look it up again from Google at least every 30 days. If you place a stamp on the map yourself, we keep that spot with the stamp, to about a kilometre.
- Ask Mara: your chat messages and conversation history. If you use voice input, the short audio clip you record is sent for transcription and then discarded; only the text stays in your chat. In hands-free voice mode, your microphone stays open only while the voice screen is open; your device detects when you speak, and each phrase is sent as a short clip for transcription and then discarded the same way. Voice mode can also show a live caption while you speak using your browser's built-in speech recognition (Chrome and Safari); depending on your browser, that may send audio to the browser vendor (for example, Google) under its own privacy policy. The caption is cosmetic: Mara only acts on the transcript from our transcription provider.
- Calendar (optional): if you connect Google Calendar, we store the connection's access tokens (encrypted) and only your free/busy times (never event names, details, locations, or guests), and use them solely to fit travel-date suggestions around your schedule. This use of Google user data complies with the Google API Services User Data Policy, including its Limited Use requirements. Disconnecting (in Settings) deletes the stored times and tokens immediately, and deleting your account removes them with it. See Google User Data below for the full detail.
- Security metadata: when you sign in we record your IP address (IPv6 addresses are truncated to their network prefix) and browser user-agent string, both visible to you in your session settings. Short-lived abuse-prevention records are keyed by IP.
- Support requests: your name, email, account ID, and message, delivered to our support mailbox.
- Payment method (optional): if you save one, we store the cardholder name, card brand, last four digits, and expiry date, never the full card number. No payment processor is integrated yet; one will be named in this policy before paid billing launches.
- Demo: trying Ask Mara without an account creates a temporary anonymous identity with the same security metadata, protected by a Cloudflare bot check.
3. How We Use It
We collect publicly available pricing data from third-party travel providers for the searches you set up, and we use your information to:
- Run your trackers and send price alerts by email and in-app notification
- Power Ask Mara, a chat assistant that answers questions grounded in your own tracked price data, including voice transcription and read-aloud audio if you use them
- Keep your Journal: store your stamps, photos and videos, place your stamps on your Journal map, and draw a stamp's illustration when you ask Mara to
- Keep accounts secure and prevent abuse
- Send transactional email such as password resets
- Improve the service and communicate service updates and changes
We also derive anonymous market statistics (typical package prices by destination and month) from tracked prices across users. They are blurred to the month, rounded to the nearest $25, suppressed when too few users contribute, and never identify you or your searches.
4. Service Providers
We share data with a small number of processors, only as needed to run the service:
- AI model providers: your Ask Mara messages and the tracked data needed to answer them are processed by the third-party AI model provider we use to run Ask Mara. If you have connected Google Calendar, the busy dates Mara looks up to suggest travel dates are sent along with your messages. Voice clips go to a speech-to-text provider for transcription (dictation and hands-free voice mode alike), and read-aloud audio is generated by a text-to-speech provider. If you use voice mode's optional live caption, your browser's own speech service (not us) may process that audio under the browser vendor's terms. When you ask Mara to draw a stamp's illustration, the memory you write and the stamp's place name go to an AI model provider, which writes a short brief, draws the illustration, and checks it, under paid terms that do not permit the provider to train on that content. Your photos and videos are never sent to an AI provider. Stamp illustrations are made with AI. We do not use your content to train AI models, and our default providers' API terms do not permit them to train on your content either; if we route chat to another provider, it processes chat only under its own API terms.
- Resend: delivers transactional and alert email (underlying carrier: Amazon SES).
- Cloudflare: network security and delivery, the demo bot check, the country-level region lookup behind our consent rules, profile-photo storage, and private storage for your Journal photos, videos and drawings.
- Google Maps Platform: draws the trip map and the map previews on your trip list, serves the photos in a place's details, and resolves places you add to an itinerary or pick for a Day on a stamp. The map, the previews and the photos load in your browser straight from Google, and only when your cookie choices allow maps or you click to show them. Loading them shares your IP address with Google, which may set its own cookie. Accepting all cookies includes maps, and until you choose, maps may be on by default in the United States and in Canada outside Quebec; everywhere else it stays off until you allow it. You can turn maps off anytime in your cookie preferences or in Settings → Privacy → Maps. Your use of the map is subject to Google's Privacy Policy at policies.google.com/privacy.
- Sign-in providers: Google, Facebook, or Apple, only if you choose social sign-in.
- Hosting: our hosting provider stores the service's data on our behalf.
We do not sell your personal information.
5. Where Your Data Goes
Some of these providers process personal information in the United States and other countries. While your information is outside Canada, it is subject to the laws of those countries and may be accessible to their courts, law enforcement, and national-security authorities. We use contractual safeguards with every provider, but no safeguard overrides foreign law.
7. Share Links
If you create a share link, what it shows becomes visible to anyone who has the URL. Share links are excluded from search-engine indexing and do not expire; you can revoke one at any time from the app, which makes the URL stop working.
When you share a trip, the link shows the itinerary and its Stops only (never notes, costs, or reservations); its map, and a cover photo of where you stay, load from Google Maps under Google's Privacy Policy only when the viewer's cookie choices allow maps or they click Show map. Turning the link's travel dates off, or revoking it, takes effect on the next visit.
When you share a stamp, the link shows the stamp, what you wrote, your photos and videos (with their sound) and their captions, and your first name; never your Trip's plan, the exact time a photo was taken, or your account details. Your Journal map and where your stamps sit on it are never shared. A photo on a Day with a date shows that date. The page stays current: what you add to the stamp later appears there too. Revoking the link stops the page and its photos at once.
A shared stamp also shows its map unless you turn that off in its share settings: each Day's place and roughly where its photos and videos were taken, rounded to about a kilometre. Never for photos kept with the whole trip, and never places from your Trip's plan. That map loads from Google Maps only when the viewer's cookie choices allow maps or they click Show map.
8. How Long We Keep Things
Deleted data may also persist in encrypted backups for up to 30 days after deletion; such backups are excluded from any restore. If a shared page is reported, or the law requires us to preserve content, we may keep the Journal photos, videos and drawings of the account involved past these periods until the matter is resolved. If you sign up during a demo, the demo conversation and any draft trip plan move to your new account instead of being deleted.
9. Your Rights & Choices
You can access, update, or delete your personal data from your account settings, including deleting your account entirely. You can also email us for a full export of your data (Quebec residents may ask for computerized personal information in a structured, commonly used technological format) or for help with any request you cannot complete from settings. Cookie consent can be withdrawn at any time from the preference centre, and every price-alert email has an unsubscribe link (we do not send marketing email). If you are unhappy with our answer to a privacy request, you can complain to the Office of the Privacy Commissioner of Canada, the Commission d'accès à l'information du Québec, or the Office of the Information and Privacy Commissioner of Alberta.
10. Security
We implement industry-standard security measures including encrypted connections (TLS), hashed passwords, and secure session management to protect your data.
11. Children
Mara is not directed to children. You must be at least 16 years old to create an account, and we do not knowingly collect personal information from children; if we learn that we have, we will delete it.
12. Google User Data
This section describes how Mara accesses, uses, stores, shares, and protects the information it receives from Google when you sign in with Google or connect Google Calendar.
- What we access: if you sign in with Google, we receive your name, email address, profile photo, and Google account ID (Google's openid, email, and profile permissions). If you connect Google Calendar, which is optional and separate from sign-in, we receive the email address and account ID of the Google account you connect and your free/busy times (the calendar.freebusy permission). Free/busy times say only when you are busy: we never receive event titles, descriptions, locations, guests, or any other calendar content. We do not request any other Google data.
- How we use it: sign-in data is used to create your Mara account, sign you in, and show your name and photo in your account; we do not call Google with it after you sign in. Free/busy times are used only so Ask Mara can suggest travel dates that fit around your schedule, and only while “Use calendar for date suggestions” is on in Settings.
- What we never do: we do not sell Google user data or use it for advertising of any kind, including personalized, retargeted, or interest-based ads, and we do not use it to determine creditworthiness or for lending. We do not use it to develop, improve, or train generalized or non-personalized AI or machine-learning models, and we do not transfer it to anyone else to do so. No one at Mara reads it unless you ask us to (for example, in a support request), it is needed for security (such as investigating abuse), the law requires it, or it has been aggregated and anonymized for internal operations.
- Who we share it with: when Ask Mara checks your calendar, the busy dates it finds are sent to the AI model provider answering your chat (see Service Providers), only to answer you and under API terms that do not permit training on it. Our hosting provider stores the data on our behalf, and our email provider (Resend) delivers account and alert email to your address. We share Google user data with no one else, except where the law requires it.
- How we store and protect it: Google user data is stored in our database on our hosting provider's servers and travels only over encrypted connections (TLS). Google Calendar access tokens are encrypted at rest, and calendar data is only ever read for the account that connected it.
- How long we keep it and how to delete it: sign-in data is kept while your account exists. Disconnecting Google under Settings → Connected accounts removes the Google sign-in and its tokens, and deleting your account removes everything within 30 days. For Google Calendar we keep the connection's tokens and only the most recent free/busy times we fetched, replaced on each check, until you disconnect; disconnecting in Settings deletes them immediately and revokes Mara's access at Google. You can also remove Mara's access at any time from your Google Account at myaccount.google.com/permissions.
Mara's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
13. Changes & Contact
Material changes to this policy will be announced by email or in-app notification before they take effect, and the date above will be updated. For privacy questions or requests, contact our Privacy Officer at [email protected].