Privacy policy

Last updated 17 October 2026 · section 5 (Google user data) and the “Published trips” and “View-only links” rows in section 2 added 18 October 2026 · the “My documents” row in section 2, and the matching lines in sections 6 and 8, added 19 October 2026

miotripz helps a group plan and run a trip together: itinerary, expenses, photos, notes and a live stream. This page explains in plain words what we keep about you, why, who helps us run it, and what you can do about it.

1. Who we are

miotripz is run by its operator (“we”). For privacy questions or requests, write to [email protected].

Two kinds of people use miotripz. Organisers create trips and keep an address book of friends. Crew are the friends invited on a trip. When an organiser adds you to a trip, the organiser decides what trip details go in; we look after the data on their behalf and for the running of the service.

2. What we collect

What	Details
Sign-in	Your email address and your name, from Google sign-in or the 6-digit code we email you. We never see your Google password.
Your profile	Only what you or your organiser enter: name, photo, mobile number, home country and city, passport country, birthday, dietary needs, emergency contact, and the payment IDs you want friends to pay you back with. Every field except your name and email is optional, and you can edit all of it under My profile.
My documents (only if you add them)	Files you choose to add to your profile, such as a passport, visa, insurance or ticket (PDF or photo), with the name you give them and an optional expiry date. They are private to you: only you can open them. Each file is encrypted before it is stored on our own storage, and the key is held only on our servers. A trip organiser can open one of them only after you choose to share it with that trip, and you can stop sharing at any time. Opening a shared file is recorded in the activity log. They are never shown on view-only links, in published trips or in exports of a trip.
Trip content	Itineraries, flights, hotels, bookings, documents, expenses and who paid what, settlements, notes, photos, videos and reels that organisers and crew add.
Activity	A log of who added, changed or removed things (for example an expense), sign-ins to a trip, and the network address of requests, used for security and to show the crew who logged what.
View-only links	An organiser can make a link that shows part of a trip to someone who is not on it. We count how often a link was opened and when it was last opened (a number and a date, nothing about the visitor). A link’s own password is stored only as a one-way hash.
Published trips (only if an organiser chooses to publish)	A cleaned, public copy of the trip plan, shared on the miotripz trip library and visible to anyone without signing in, including search engines. It leaves out who is on the trip, flights and bookings, budget and expenses, documents, photos, notes and e-mail addresses, and replaces names of crew in the text with “a friend”. We count views and copies (numbers only, no visitor identity). If someone reports a trip we store the reason, their note and a one-way fingerprint of their network address to stop abuse. When another person copies a published trip, the copy becomes that person’s own trip.
Device storage	Your sign-in and a copy of the trip you are allowed to see are kept in your browser (local storage and a cache) so the app works offline. We do not use advertising or tracking cookies.
Errors	If the app crashes, a technical error report (page, browser type, error text) may be sent to our error monitor.

3. Why we use it

• To run the trip: show the plan to the crew, split expenses, settle up, share photos, send sign-in codes and invitations.
• To keep the service secure and fix faults: access checks, abuse limits, error reports, backups.
• To let organisers use optional AI help: if an organiser asks for suggestions, the text they typed (and any file they attach) is sent to an AI service to produce ideas. We do not use your trip data to train AI models.

We do not sell your data and we do not show advertising.

4. Who helps us run miotripz

We use these services, and share with them only what each needs:

• Hosting and network: a virtual server host and Cloudflare (traffic passes through Cloudflare).
• Sign-in: Google (Google sign-in). The emailed sign-in code is made and checked on our own server.
• Email: Amazon Web Services (Amazon SES) (sign-in codes and invitations, and a message from your trip organiser when they choose to email it to the crew - one separate email per person, no one sees anyone else's address).
• Error monitoring: Sentry.
• AI suggestions: Anthropic (only when an organiser requests suggestions).
• Files: photos, videos and documents are stored in the trip organiser's own cloud storage (Google Drive, OneDrive or pCloud) that they connect, and in our Cloudflare R2 store for covers and previews.
• Trip information feeds: weather (Open-Meteo), exchange rates (Frankfurter), flight status (AeroDataBox), maps (OpenStreetMap / CARTO) and background pictures (Wikipedia). These receive place names, dates or flight numbers, not your identity.
• Backups: encrypted copies of the database, kept in pCloud (Europe) for 30 days.

Other people on the same trip can see what the organiser puts in it: names, the itinerary, expenses and photos. Your mobile number and payment details are shown only to signed-in crew of that trip. People who only have a trip link see just the cover (name, dates, route and who is going) until they sign in or use a share link the organiser made.

5. Google user data

If you sign in with Google, or an organiser connects their own Google Drive, this is exactly what miotripz receives from Google and what it does with it:

• Signing in (everyone who chooses Google): your name, email address and profile picture (the basic openid / email / profile details). Used to sign you in, to match you to the trips you were added to, and to show your name and picture to the crew of those trips. We never receive your Google password and cannot see anything else in your Google account (no Gmail, contacts or calendar).
• Google Drive (optional, trip organisers only): if an organiser connects their own Google Drive to keep the trip's photos, videos and documents, miotripz is given the drive.file permission. It lets miotripz see and manage only the folders and files that miotripz itself creates in that organiser's Drive - not their other files. It is used only to save and show the trip's files, and can be disconnected in miotripz (My storage) or at myaccount.google.com/permissions.

We use Google user data only to provide these features. We do not sell it, we do not use it for advertising or for building advertising profiles, we do not use it to train AI models, and no person at miotripz reads your Google data except where needed for security, to follow the law, or because you asked us for help. It is shared only as described in section 4. You can see, download or erase your data under My profile (section 7).

miotripz'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.

6. How long we keep it

• A published trip stays public until its organiser unpublishes it (it disappears at once) or we hide it; copies other people already made are theirs and stay with them. Reports about a trip are kept while needed to deal with it.
• Trip content stays until the organiser deletes the trip; a deleted trip and its files are purged after a short grace period.
• Your documents stay until you delete them or erase your account; deleting a document removes the file and every share at once.
• Your profile stays until you ask us to erase it. A Google permission you granted is removed when you disconnect it or erase your account.
• A trip sign-in on a device expires after 30 days without use.
• Backups are deleted after 30 days.
• When you erase your account we keep one scrambled, one-way fingerprint of your sign-up address (it cannot be turned back into the address). It is used only so the free starter credits are given once per person, not again if the same person signs up anew.
• Activity logs are kept while needed for security and for the crew's expense history.

7. Your choices and rights

• See and download your data: sign in, open My profile and choose Download my data. You get one file with your account, profile, address-book entries about you, trips, what you added and the activity log.
• Correct it: edit your details in My profile, or ask us.
• Erase it: sign in, open My profile and choose Erase my account and data. This removes your account, profile, sign-in, saved ideas and connected storage, and wipes your details (email, mobile, birthday, photo, payment information) from every trip you were on. Access we were given to your own Google Drive or pCloud is cancelled with the provider at the same time; for Microsoft OneDrive only you can cancel it – remove miotripz at account.microsoft.com/privacy. In those trips your name becomes “Former traveller” so the other travellers’ shared expenses still add up. If you still organise a trip you need to delete it first. Photos and documents inside an organiser’s own cloud storage stay with that trip, free text an organiser wrote about you in an itinerary stays with the organiser, and backups age out within 30 days. If you cannot sign in, email us from your sign-in address and we will do it for you.
• Object or ask a question: write to us at the address above. We reply within 30 days.

If you are not happy with our answer you can complain to your local data-protection authority.

8. Security

Traffic is encrypted. Access to each trip is checked on our servers on every request, uploaded files cannot run as web pages, credentials for connected storage are stored encrypted, the documents you add to your profile are encrypted file by file, and backups are encrypted. No system is perfectly secure; if a breach affects you we will tell you promptly.

9. Children

miotripz is not meant for children under 13, and we do not knowingly collect their data. If you believe a child has been added, tell us and we will remove the record.

10. Changes

If we change this policy in a way that matters, we will update the date above and, for big changes, tell you in the app.