Draft. The highlighted details in square brackets are still to be filled in, so this page isn't final yet.
Privacy policy
Effective 4 November 2026. This policy covers the Globora mobile app and the website at europe.shaperk.com.
The short version.
- We keep what you put in Globora so that the app can work, and we don't use it for anything else.
- There are no ads, no tracking and no analytics, and we don't sell your data.
- Most of your traveller profile is optional, including your passport and health details.
- Everyone on a trip can see that trip's plans, bookings, tickets and expenses.
- You can delete your account. It's deleted 30 days after you ask, and we email you when you ask and when it's done.
Who we are
Globora is run by [LEGAL ENTITY NAME], [REGISTERED ADDRESS]. We are the data controller for your information, which means we decide how it's used and we're responsible for it.
To contact us about privacy, email support@shaperk.com.
What we collect
| What | Details | Do you have to give it? |
|---|---|---|
| Your account | Name, email address and password. We store the password hashed, not as you typed it. We also keep whether your email is verified and which trip emails you want. | Yes |
| Your trips | Trip names, dates, currency and colour, starting point, stops and their map coordinates, activities, notes, packing lists and to-dos. | Only what you want to plan |
| Bookings and tickets | Provider, booking codes, times, places, cost, who's travelling, and the PDF or photo files you upload. | No |
| Money records | Expenses, how they're split, budgets, balances and settlements between travellers. We don't collect card or bank details, and no money moves through Globora. | No |
| About you | Legal name, date of birth, gender, nationality, phone, home city and country, profile photo, seat and meal preferences, loyalty programme numbers. | No |
| Passport and visas | Passport number, issuing country and expiry date. Visa country, number, category, entries and dates. Copies you upload. | No |
| Health and safety | Blood type, allergies, medical notes, insurer, policy number and insurer's phone. Emergency contacts' names, relationship and phone numbers. | No |
| Travel map | Countries you mark as visited, along with what your trips show. | No |
| Technical information | Your IP address, browser or app details, the time and the page or address requested, in our web server logs. The app sends its version number and a label for your device with its requests. Website sessions also store your IP address and browser details. | Sent automatically |
Information about other people. You can add other people's names and email addresses to a trip, and name your emergency contacts. Please only add someone if they would expect it. If your name or email is on a trip and you'd like it removed, ask the trip's owner or contact us.
What the app doesn't do. It doesn't read your location, your contacts or your calendar. It uses your camera or photos only when you choose to attach something. If you turn on the app lock, Face ID or your fingerprint is checked by your phone, and we never receive it.
Why we use it, and our legal basis
If you're in the European Economic Area or the UK, data protection law requires a legal basis for each use.
| Why | Legal basis |
|---|---|
| Running your account and showing your trips, bookings and balances to you and your travellers | Our contract with you (GDPR Article 6(1)(b)) |
| Sending account emails, such as verification and password reset, and the trip emails you've left on: reminders and changes made by others | Our contract with you. You can turn trip emails off at any time |
| Passport warnings and showing your loyalty numbers and preferences on bookings | Our contract with you |
| Health details, and any other sensitive details you enter. For example, a medical note could reveal a disability, and a halal or kosher meal preference could suggest your religion | Your explicit consent (Articles 6(1)(a) and 9(2)(a)). You give it by choosing to add these details, and you withdraw it by clearing them. Whether anyone else sees your emergency details is a separate choice |
| Keeping names on shared trips after someone leaves, so the group's balances still add up | Legitimate interests of the other travellers (Article 6(1)(f)) |
| Keeping the service safe and working: server logs, limiting repeated requests, backups | Our legitimate interests (Article 6(1)(f)) |
| Answering support requests | Our contract with you, or our legitimate interest in helping you |
| Meeting a legal duty, if we have one | Legal obligation (Article 6(1)(c)) |
We don't make decisions about you by automated means that have legal or similar effects. The trip check and passport warnings are simple date checks to help you.
Who can see your information
- Travellers on the same trip can see and change that trip's plan, bookings, tickets, booking codes, notes, checklists and expenses. They also see your name, your email address if it's on the trip, and your profile photo.
- Being added to a trip. If a trip's owner adds the email address of a verified Globora account, that person joins the trip straight away, with no invitation to accept. Only a trip's owner can remove a traveller. If you've been added to a trip you don't want to be on, contact the owner or us.
- Your emergency details (phone, emergency contacts, blood type, allergies, medical notes and insurance) are seen by people on your trips only if you turn on sharing in your profile. It's off by default, and it applies to all your trips. People with the app can hold a copy on their phone for offline use until it next updates.
- Your passport and visa details, date of birth and copies aren't shown to other travellers.
- Calendar links. A trip's calendar feed is a private link with no sign-in, because calendar apps can't sign in. Anyone who has the link can see that trip's times, places, booking codes, travellers' names and notes. Only share it with people you trust. The trip's owner can reset the link.
- People who run Globora. Sensitive details are encrypted, but we hold the key on our server so that the app can show them to you. Someone with administrator access could technically read them. We only do that if we have to, such as to fix a fault you've asked us to look into, or if the law requires it.
We don't sell your information or share it for advertising. We'd disclose it to others only if the law requires it, or as part of selling or reorganising the business, in which case we'd tell you first.
Companies that handle data for us
| Company | What for | What they receive |
|---|---|---|
| [HOSTING PROVIDER AND COUNTRY] | Hosts our server, database, uploaded files and backups | All the data described above, stored on their machines |
| Resend | Delivers our emails | Your name and email, and the email's content. Trip emails can include the trip's name and dates, flight times, the day's plan, to-dos, a passport expiry warning, and what you owe others. We leave booking codes and notes out of them |
Services your device or our server connects to
These independent services see your IP address, as any website you connect to would, along with what's listed. We don't send them your account details.
| Service | When | What it receives |
|---|---|---|
| Google Fonts | Loading any signed-in or sign-up page of the website | A font request |
| Tailwind CDN, jsDelivr, cdnjs (Cloudflare) | Loading the website's styles, scripts and world map | A file request |
| flagcdn | Showing country flags on the website | Which flag is requested |
| OpenStreetMap map tiles | Showing maps on the website | The map area being viewed |
| Nominatim (OpenStreetMap) | Searching for a place on the website | The text you search for |
| OSRM public routing server | Drawing road routes on the website | The coordinates of the two stops on that road leg |
| Frankfurter | Looking up an exchange rate on the website | The two currencies |
| OpenRailwayMap | Searching for a train station. Our server makes this request, so OpenRailwayMap sees our server, not you | The text you search for |
| Google Maps, Google Flights, Google Calendar | Only when you tap a directions, flight search or add-to-calendar link. These open outside Globora under Google's own terms | The place, route or calendar link in what you tapped |
| Your calendar service | If you subscribe to a trip's calendar feed | The trip's calendar details, fetched regularly from the private link |
The app has its flags and fonts built in, so it doesn't load them from those services. Apple and Google provide the app stores and the phone's operating system, under their own privacy policies.
Where your data is kept
Our server, including the database, uploaded files and backups, is with the hosting provider named above. Backups are kept on the same server. Your phone keeps its own encrypted copy of your trips, for offline use.
Some of the services above are based outside the EEA and the UK, including in the United States, so your information may be handled there. For Resend, we rely on the standard contractual clauses in its data processing terms. The services your device connects to directly work under their own terms. You can ask us for details of these safeguards.
How long we keep it
| What | How long |
|---|---|
| Your account, profile and trips | Until you remove them or delete your account. We don't delete past trips automatically |
| After you ask to delete your account | 30 days, so you can change your mind. Then the account is deleted as described on the delete account page |
| Backups of the database and files | About two weeks, then overwritten. Deleted data can stay in a backup until then |
| Web server logs | About 14 days |
| Changes waiting for a trip update email | Until the email goes out, usually within minutes |
| Records of which trip emails you've had | Until your account is deleted |
| Your name on someone else's shared trip, after you delete your account | Until the trip is deleted, for the group's balances. It's no longer linked to you, and your email address is removed |
| The app's copy on your phone | Until you sign out or uninstall the app |
| Support emails | As long as we need them to help you |
How we protect it
- All connections between your phone or browser and our server use HTTPS.
- On our server, these are encrypted with AES-256: date of birth, phone, passport number, visa details, loyalty numbers, emergency contacts, blood type, allergies, medical notes, insurance details, passport and visa copies, profile photos, and uploaded tickets.
- Your password is stored hashed. In the app, your sign-in token is kept in your phone's secure storage, and your offline copy is stored encrypted. You can also turn on a biometric app lock.
- Profile photos are redrawn when you upload them, which removes location data from the file.
- Sign-in attempts are limited, and app sign-ins expire after 90 days without use.
What isn't encrypted this way. Your account name and email, your legal name, nationality, gender, home city and country, passport issuing country and expiry date, and your seat and meal preferences are stored as normal database fields. So are your trip plans, bookings, booking codes, notes and expenses. Any ticket uploaded before we added ticket encryption stays an ordinary file in a private folder. All of these are protected by access controls, not by encryption of their own, and backups aren't separately encrypted. Please bear that in mind when you choose what to put in a note or attach as a ticket.
No system is perfectly secure, and we can't promise yours will never be affected. If a breach puts you at risk, we'll tell you and the authorities as the law requires.
Your rights
If you're in the EEA or the UK, you have the right to:
- see the information we hold about you, and get a copy;
- correct it, which you can do for most of it yourself;
- have it deleted, which you can do on the delete account page;
- get a copy in a portable format, to take elsewhere;
- limit or object to how we use it, where we rely on legitimate interests;
- withdraw consent at any time, by clearing the details or turning off sharing. This doesn't affect what happened before you withdrew.
To use these rights, email support@shaperk.com from the address on your account. We'll reply within one month. You can also complain to your local data protection authority.
You can turn trip emails off in your profile or with the link in any trip email.
Cookies
The website uses only the cookies it needs to keep you signed in and protect forms. There are no advertising or analytics cookies. The app doesn't use cookies for tracking.
Children
Globora isn't directed at anyone under 16, and you need to be at least 16 to create an account. If you think someone under 16 has given us their information, contact us and we'll delete it. Parents who are travelling with children can add a child's name to a trip for planning and splitting costs. Please don't add more about them than you need to.
Changes to this policy
If we change this policy, we'll update the date at the top. If a change matters, we'll also tell you by email or in the app before it takes effect.
Contact
[LEGAL ENTITY NAME], [REGISTERED ADDRESS]
Email: support@shaperk.com