Tripfam

Privacy policy

Last updated 23 Oct 2026

Tripfam is where you and your friends plan a trip together, so most of what we store is there because someone in your group put it there. This page says exactly what that is and what you can do about it.

Who we are

Tripfam is a small project run by Anton Stasyuk, an individual. There is no registered company behind it yet, so one person, not a business, is responsible for your data and answers your requests. If a company is formed later, it takes over this service and these commitments, and we will tell you by email before that happens.

For anything in this policy, write to [email protected]. A real person reads it.

The operator lives in Spain, so the GDPR and Spanish data protection law apply to everything Tripfam does, wherever you live. We are the data controller for your account and for the trips stored here.

What we collect

Account details:

  • Your name and email address
  • Your password, stored only as a hash we cannot reverse
  • If you sign in with Google: the name, email address and profile picture Google shares with us, and the sign-in tokens Google issues

Trip content that you and the other members add:

  • Trip name, destinations, dates and currency
  • Who is a member, who invited whom, and the email address of anyone invited by email
  • Ideas, votes, polls and plans, with their times, places, notes, links and booking references
  • Who is going to each plan
  • Packing and to-do lists, who an item is assigned to and when it was ticked
  • Expenses: amounts, currencies, exchange rates, who paid, how it was split, and settlements
  • Files you upload, such as tickets, boarding passes and vouchers

Technical records created by using the site:

  • Session records, each with an IP address, browser user agent and timestamps
  • A copy of each email we send you, and whether it was delivered
  • Server logs kept by our hosting provider

We do not buy data about you from anyone, and we do not build a profile of you from other sites.

Sensitive details

We do not ask for passport numbers, health details or any other sensitive data, and the app has no field for them.

Notes and files are free-form, though, and a boarding pass or a booking confirmation can carry more than you expect. Everything in a trip is visible to every member of it, so upload only what the group needs.

Why we use it, and our legal basis

  • To run your account and the trips you belong to. Legal basis: performing our contract with you.
  • To send email you need, such as password resets and trip invitations. Legal basis: performing our contract with you.
  • To store the email address of someone a member invites, so the invitation can reach them. Legal basis: our legitimate interest, and that of the member, in letting friends invite each other.
  • To keep the service secure, stop abuse and fix faults. Legal basis: our legitimate interest in a working, safe service.
  • To meet a legal obligation, if one ever applies to us. Legal basis: legal obligation.

We do not use your data to train machine learning models, and we do not use it for advertising.

Who can see it

A trip is private to its members. Every member sees everything in it: the plans, lists, files and expenses, and the name and email address of every other member.

Anyone holding a valid invite link can join the trip it belongs to. Links expire after 14 days, and the trip owner can revoke them earlier.

The operator can access data in the database when needed to run the service, investigate a fault or answer your request. Nobody else has an account that can browse your data.

Companies that process data for us

We use as few outside services as we can. These ones handle personal data for us:

  • Railway: application hosting, the Postgres database and the storage holding your files, in the European Union.
  • Cloudflare: the tripfam.app domain and the network in front of the site, so every request passes through it, including your IP address.
  • Resend: sending email such as invitations and password resets.
  • Google: sign-in, if you choose it. The site also loads its fonts from Google, so Google sees the IP address of your browser when a page loads.
  • OpenFreeMap: map tiles, loaded by your browser, so it sees your IP address when a map is shown.

Some features look things up for you. For these, our server sends only the words or codes being searched, never who you are:

  • Place search: Photon by komoot and OpenStreetMap Nominatim.
  • Place descriptions: Wikidata and Wikipedia.
  • Flight details: AeroDataBox, through RapidAPI, which receives the flight number and day.

We do not sell your data, we do not share it with advertisers, and we do not use data brokers.

Some of these providers may process data outside the European Union, including in the United States. Where the GDPR applies, those transfers rely on the European Commission's standard contractual clauses in their terms.

Cookies and browser storage

  • A session cookie that keeps you signed in. The site cannot work without it.
  • Your language choice, kept in a cookie so the site opens in that language next time.
  • Your theme choice, light or dark, kept in your browser's local storage.
  • If you install Tripfam as an app, your browser keeps a copy of its code so it opens faster. It holds none of your trip data.

We run no analytics, no advertising pixels and no third-party trackers, which is why you are not being asked to accept cookies.

How long we keep it

  • Account data: while your account exists.
  • Trip content: while the trip exists. When the owner deletes a trip, everything in it is deleted.
  • Leaving a trip or deleting your account: your memberships, votes and shares go with you. Plans, expenses and files you added stay with the trip, because the group relies on them, and show as added by a former member.
  • Invitations: kept with the trip, including the email address an invitation was sent to.
  • Session records: until the session expires or you sign out.
  • Emails we send you, such as invitations, confirmations and password resets: a copy and whether it arrived, for up to 12 months, so we can look into mail that goes missing.
  • Backups: deleted data can survive in database backups until they rotate out.

Your rights over your data

Under the GDPR you can ask us to do any of the following, free of charge:

  • See what we hold about you.
  • Get a copy in a portable, machine-readable format.
  • Correct anything that is wrong.
  • Delete your account.
  • Restrict or object to a use you disagree with.

Some of this you can do yourself, right now: change your name in Settings, leave a trip, or delete a trip you own.

For everything else, including deleting your account or getting a copy of your data, email [email protected]. We answer within 30 days.

If you think we have handled your data badly, please tell us first so we can fix it. You can also complain to the Spanish data protection authority, the Agencia Española de Protección de Datos (aepd.es), or to the authority in the country where you live or work.

How we protect it

  • Passwords are stored as salted hashes, never in readable form.
  • Everything travels over HTTPS.
  • Files sit in private storage and are served through the app only to members of their trip.
  • Database and storage credentials are held by the operator alone.

No service is perfectly secure, and a small project should not pretend otherwise. If a breach ever affects your data, we will email you without undue delay and notify the relevant supervisory authority within 72 hours where the law requires it.

Age

You need to be 16 or older to create an account. If we learn that an account belongs to someone younger, we delete it.

Changes to this policy

As Tripfam grows, this policy will change. The date at the top always shows the current version. If a change materially affects your rights or how we use your data, we will email you before it takes effect.

Contact

Privacy questions, data requests and complaints: [email protected].

Flight data by AeroDataBox. Map data © OpenStreetMap contributors.