Privacy Policy
Journeyfy for iPhone and Android · Last updated 29 October 2026
Journeyfy helps a group plan a trip together: the plan, the places, bookings, shared expenses, polls, checklists, a chat and photos. This page explains what the app keeps, where, who sees it, how long it's kept and how to remove it.
In short
- Your trips are stored with Supabase in the European Union (Ireland).
- Only the people in a trip see it, unless its organizer shares it in Discover after it ends.
- Journeyfy is free, shows no ads, sells nothing about you, has no analytics and doesn't track you across apps or websites.
- You can delete your account at any time: here's how.
Who we are
Journeyfy is made by Francisco Chávez Romero, Carrer de Torns 37, 1-1, 08028 Barcelona, Spain ("we"), who decides how your data is used and is responsible for it (the data controller). You can reach us at frandeveloper4@gmail.com. Using Journeyfy is also subject to our Terms of Use.
What we keep and why
- Your account: your email address and password (stored only as a secure hash), or, if you use Sign in with Apple (iPhone), the identifier Apple gives us and the email address Apple shares, which can be a private relay address. The name you choose, and a profile photo if you add one. To sign you in and to show your group who's who.
- What you add to a trip: the trip itself (name, description, destination and dates), the day-by-day plan, places on the map, bookings (including confirmation codes and any ticket or document you attach), expenses and who owes what, polls and votes, checklists, chat messages, reactions and stickers, and photos and videos. To share them with the trip's members.
- Payment usernames you choose to add (a PayPal.me or Revolut username), so the people you travel with can pay you back. Journeyfy handles no money and never asks for card or bank details.
- Reports and blocks: what you report (the message or trip, and who posted it) and the people you block. To keep the community safe.
- A notification token for your phone if you allow notifications, with the kind of phone, the app version and your language. To tell you about your trips, in your language.
- Flight lookups: when you fill in a flight from its number, our server asks for that flight and keeps the answer for about six hours, so the rest of your group gets it without asking again. We also count how many flights each account looks up per day, to keep this free service working for everyone.
- Sign-in sessions: while you're signed in, our sign-in service keeps your session with the IP address and type of device it started from. To keep your account secure.
- Technical logs: like any online service, our hosting provider logs each request (time, IP address, what was asked for) to run and protect the service.
Photos are re-saved by the app before they're uploaded, and videos are made smaller without their details, which leaves out the location your camera may have stored in them. A receipt you photograph to fill in an expense is read on your phone and never uploaded or kept. (On Android, videos can be watched but not added yet.)
The app doesn't collect your location. On iPhone and Android it can show where you are on the trip map if you allow it; that stays on your phone. Places you pin on a trip are saved with their position, as part of the trip.
Journeyfy has no analytics, advertising or tracking code. Apple and Google may show us crash reports and download statistics from people who chose to share them with app developers in their phone's settings; these don't tell us who you are.
Legal basis
If you're in the EU, the UK or another country with similar laws, we use your data on these grounds:
- Our agreement with you (Art. 6(1)(b) GDPR): your account and everything the app does for you and your group.
- Our legitimate interests (Art. 6(1)(f)): keeping Journeyfy safe and working (reports, blocks, the daily flight-lookup limit, sign-in sessions, logs and backups), and moving trips from the iCloud version so groups keep them. You can object to these at any time (see Your rights).
- Your consent (Art. 6(1)(a)): notifications, which you can turn off in your phone's settings, and showing a trip in Discover, which its organizer chooses and can undo.
- A legal obligation (Art. 6(1)(c)), when the law requires us to keep or hand over data.
Who sees it
- The members of each trip see that trip's content, and the name, profile photo and payment usernames of the people in it. The database itself enforces this: nobody outside a trip can read it.
- People with an invite link can join that trip, and then see it. Share links only with people you mean to invite; they expire after 30 days at most.
- Public trips: if a trip's organizer makes it public, once the trip has ended other Journeyfy users can see in Discover its destination, description, length and month (never the exact dates), the day-by-day plan, the places and the photos nobody made private, with the organizer's name and profile photo. They can copy its plan and places into a trip of their own. Its chat, expenses, polls, bookings and members are never shown.
- The services that run Journeyfy for us (below), only to provide it.
- Authorities, only when the law requires us to.
Nobody else. We don't sell or rent personal data, and we don't use it for advertising.
Where it lives, and who helps
Your data is stored with Supabase (database, sign-in, file storage and our server functions) in the European Union (Ireland). These services process data for us, only to run the app:
| Service | What for | What it gets |
|---|---|---|
| Supabase | Database, sign-in, file storage, our server functions | Everything above, stored in the EU (Ireland) |
| Brevo (Sendinblue SAS) | Sending sign-up confirmations and password-reset codes | Your email address and the email we send you |
| GitHub | Nightly backups of the database; hosting this website and the invite page | Each night, a copy of the database, sent over an encrypted connection to a GitHub machine that encrypts it there and keeps only the encrypted copy, for 14 days; your IP address when you open these pages |
| Apple | Sign in with Apple, notifications to iPhones, the map and place search on iPhone | Your Apple sign-in, your phone's notification token and the notifications we send, what you search for on the map |
| Google (Firebase Cloud Messaging) | Notifications to Android phones | Your phone's notification token and the notifications we send |
| AeroDataBox (through RapidAPI) | Filling in a flight from its number | The flight number and date only, sent by our server, never who you are |
| Photon (komoot), with OpenStreetMap data | Place search, destination suggestions and addresses on Android | What you type, the area of the trip or the place's position, and your IP address |
| OpenFreeMap | The map on Android | Requests for the part of the map you're looking at, and your IP address |
| Frankfurter (European Central Bank rates) | Converting expenses between currencies | The two currencies, and your IP address |
| Open-Meteo | The weather forecast on each day of a trip's plan | The trip's destination, its position and your IP address, never who you are |
Links that take you out of the app (directions in Apple Maps or Google Maps, PayPal.me, Revolut, the App Store, Google Play) open those services, under their own privacy policies.
Transfers outside the EU
Your data is stored in the EU. Supabase, GitHub, Apple and Google are based in the United States (Brevo, which sends our emails, is in France, in the EU); they may reach or process data from there, for example for support or security. The free map, place-search and exchange-rate services may answer from servers outside the EU; they only see your request and your IP address.
When personal data leaves the European Economic Area, it's protected by a European Commission adequacy decision (such as the EU–US Data Privacy Framework, for companies certified under it) or by the Commission's Standard Contractual Clauses in our agreement with the provider (Art. 46 GDPR). You can ask us for a copy of these safeguards at frandeveloper4@gmail.com.
On your phone
To keep your trips readable without a connection, the app saves a copy of them on your phone, and on iPhone the Home Screen widget keeps a small copy of your next trip. Both are removed when you sign out or delete your account, and the copy isn't included in phone backups. The people you block, and trip reminders such as "your trip starts tomorrow", are also kept on the phone itself.
How long we keep it
- Your account and profile: until you delete your account.
- A trip and everything in it: while the trip exists. When its organizer deletes it, its content, photos, videos and tickets are deleted too.
- Flight answers: about six hours. They hold no personal data.
- Reports: as long as needed to deal with them and with repeated abuse, and at most 12 months.
- Technical logs kept by Supabase: about a day.
- Backups: the database is backed up every night, encrypted, and each backup is kept for 14 days. Something deleted, including a deleted account, disappears from the backups within 14 days. Photos, videos and tickets are copied separately, about once a week, into an encrypted archive we keep offline; each copy is kept for up to 4 weeks, so a deleted photo is gone from them within 4 weeks.
Delete your Journeyfy account
This is how to delete your account in Journeyfy, the group trip planner by Francisco Chávez Romero on the App Store and Google Play, and what happens to your data.
In the app (iPhone or Android)
- Open Journeyfy and sign in.
- Go to the Settings tab.
- Tap Delete Account, then Delete to confirm.
If you signed in with Apple, your iPhone may ask you to confirm with Apple once more, so that Journeyfy's access to your Apple ID is withdrawn too. Deleting the app from your phone doesn't delete your account.
Without the app
Email frandeveloper4@gmail.com with the subject "Delete my Journeyfy account", from the email address you sign in with. If you used Sign in with Apple with Hide My Email, include the address shown for Journeyfy under Sign in with Apple in your Apple ID settings. We may ask you to confirm by replying from that address. We delete the account within 30 days, usually much sooner, and tell you when it's done.
What is deleted
- Your account: email address, password, and the link to your Apple ID.
- Your profile: name, profile photo and payment usernames.
- Your membership of every trip.
- The trips you organize that nobody else is in, with everything in them, including their photos, videos and tickets.
- Your notification tokens, sign-in sessions, the people you blocked and the trips you saved in Discover.
Trips you organize with other people aren't deleted. Each one passes to the co-organizer who joined it first or, if it has none, to the member who joined first, who becomes its organizer. A public trip stays in Discover under its new organizer's name.
What is kept, and for how long
- What you added to trips shared with others stays in those trips, so the group's trip still makes sense and its balances still add up: your messages and reactions, photos and videos, places, plan items, bookings and their tickets, checklists, polls and votes, and expenses, shown with the name you had. They stay as long as that trip exists. You can delete your own messages and photos in the app before you delete your account.
- Reports you sent, or that were made about you: at most 12 months.
- Other people's block lists keep your name, so their blocks keep working.
- Backups: up to 14 days for the database, up to 4 weeks for photos, videos and tickets. Technical logs: about a day.
- If you used the iCloud version (1.0.9 or earlier): the old copy of your data in iCloud, until 9 February 2027, or sooner if you ask us (see below).
Moving from the iCloud version
Until version 1.0.9, Journeyfy kept trips in Apple's iCloud, in the app's own CloudKit database, which we managed, rather than in your personal iCloud storage. From version 1.1.0, Journeyfy keeps them with Supabase in the EU, so that friends without an iPhone can join your trips too.
- One copy, in November 2026, on the day version 1.1.0 is released: we copy the trips from the old version to the new servers once: the trips, their members' names and photos, and everything in them (plans, places, bookings, expenses, polls, chat, photos and videos). That includes what you wrote in your groups' trips, so your group keeps its history even if you haven't updated yet. Anything added in the old version after that day isn't copied.
- Linking your old trips to your account: the first time you sign in to the new version on an iPhone signed in to the same iCloud account, the app asks iCloud to confirm who you were in the old version. Apple tells our server only your old iCloud user identifier for Journeyfy, never your Apple ID password. We then link your old trips to your new account, and keep a coded identifier derived from that old identifier so the link can be made only once, and only by you.
- The old copy: once the move is done, we delete the old data from iCloud on 9 February 2027. If you'd rather your old data weren't moved, or want it deleted sooner, write to us.
Your rights
You can see and change most of your data in the app, and delete your account (see above). You can also ask us for a copy of your data, including in a format another service can read, or ask us to correct it, delete it, or limit how we use it, and you can object to uses based on our legitimate interests or withdraw your consent. Write to frandeveloper4@gmail.com; we answer within one month. You can also complain to your data protection authority (in Spain, the AEPD).
Content safety
Objectionable content isn't allowed (see the Terms of Use). You can report any message or public trip and block anyone; reported content is hidden for you at once and reviewed within 24 hours, and offending content and accounts are removed.
Minimum age
Journeyfy is for people aged 13 and over. Where the law of your country sets a higher age for using a service like this without a parent's consent (in the EU it can be up to 16; in Spain it is 14), you need to be that age or have your parent's or guardian's consent. If you think a child under 13 is using Journeyfy, tell us and we'll delete the account.
Security
Data travels encrypted (HTTPS), the database checks who may read or change each piece of data on every request, passwords are stored only as hashes, and backups are encrypted before they're stored.
Changes
If this policy changes, we'll update this page and its date, and for important changes we'll tell you in the app before they apply.
Contact
Francisco Chávez Romero · Carrer de Torns 37, 1-1, 08028 Barcelona, Spain · frandeveloper4@gmail.com