← Back to the legal notice
Version française
Privacy Policy
Last updated: 13 October 2026 (follow without installing the app, Polarsteps import, 3D flyover, recap, badges, evening reminders)
This Privacy Policy describes how the Vezoria app (“Vezoria”) handles your information. The App is free, ad-free, account-free and non-profit. It is available on the web and on Google Play.
- Your trips, notes, expenses and photos are encrypted on your phone before anything is sent. Neither the publisher nor the hosting provider can read them.
- No advertising, no cookies, no advertising trackers, no third-party analytics tool (Google Analytics, Firebase…). Only anonymous counters (number of installs, space used on the server) are used to run the service.
- Permissions (location, photos) are only requested when you use the feature concerned, and you can refuse them.
- You choose where your trips go (☁️ Cloud button): your whole notebook in the cloud, trip by trip, or no cloud (everything stays on your phone; to share, you send encrypted packages yourself).
- You can erase everything: on your phone in one tap, on the server from the app or on simple request.
1. Data controller
2. Data processed
| Data | Where | Why |
| First name and profile colour, trips, stops, bookings, expenses, notes, checklist, memories and photos | On your device. If you choose the cloud (whole notebook, or only the trips you put there): also on the server, encrypted | To run the notebook and share it with the members of the group |
| Fingerprint (hash) of the notebook code (the code itself is never sent) | Server | To store each notebook’s data separately |
| Date of the last erasure of a notebook or shared trip, stored with its anonymous fingerprint | Server | To tell the other members that the trip was emptied from the server and offer to put it back online with what their phone kept |
| Travel documents (type, expiry date; optional number and note) and photographed receipts, reimbursement method entered in a profile (optional), poll votes, shopping lists, tickets and documents attached to records, positions saved with “I’m here” (only when you tap the button) | Like the other records: on your device, and on the server if sync is enabled | Expiry alerts before departure, expense sharing |
| Trip tracking (off by default): positions recorded roughly every 300 m (every 50 m in “journey mode”, which you start yourself), only while the app is open and only during an ongoing trip. Positions already stored in your memory photos may complete the route shown on your device | On your device, and for the members of the shared trip (encrypted) | Draw your route on the map and in the trip film |
| Followers (only if you publish a trip): non-private memories (photos as thumbnails, titles, places, stories); your route, only if you turn it on (rounded to about 100 m); on the follower side: the chosen first name (optional), ❤️ and comments. A follower can follow the trip in their browser without installing the app: what they see is kept in that browser’s storage | Server, encrypted with the follower code: anyone who received the follower link or code can read them | Let your loved ones follow the trip and react |
| Install counter: a randomly generated identifier (unrelated to you or your trips), the device type (iPhone, Android, computer) and the date, sent only once | Server | Knowing how many times the app has been installed |
| Overall server statistics: total space used by photos, number of notebooks and records (aggregate figures, no content or identity) | Server; viewed by the publisher | Monitor storage and stay within the service limits |
| Notifications (off by default, only if you turn them on): the subscription address provided by your phone (Apple, Google or Mozilla), a random identifier for this device, the categories you chose (expenses, bookings, memories, polls, shopping, reminders, evenings while travelling and “one year ago” memories), your time zone and the “do not disturb at night” option. The text of notifications and scheduled reminders is encrypted by the phones: the server cannot read it | Server, stored with the fingerprint of the notebook or trip concerned | Let trip members know what was added, and send you your reminders on time |
| IP address, date and size of uploads | Server and the hosting provider’s technical logs | To route the data, security, protection against abuse |
Legal bases: performance of the requested service (Art. 6(1)(b) GDPR) and legitimate interest in securing the service (Art. 6(1)(f)).
The demo trip stays only on your device: it is never sent to the server.
3. End-to-end encryption
Before anything is sent, your device encrypts the data with AES-256-GCM, using a key derived from your notebook code (PBKDF2, 200,000 iterations). The server only receives a fingerprint of this code, which cannot be used to decrypt. Photo names are also replaced by encrypted identifiers.
To show the text of notifications, each trip’s key is kept in the app on your phone (on iPhone, in a form the app’s “notifications” part can read). It never leaves your device.
Lost code = notebook unrecoverable from the server. Nobody, not even the publisher, can retrieve it. Keep your code in a safe place and export regularly.
4. Hosting and processor
Synced data is hosted by Cloudflare, Inc. (Pages, D1 and R2 services), acting as processor. As Cloudflare is a US company, data may be stored outside the European Union. This transfer is governed by Cloudflare’s data processing agreement (European Commission standard contractual clauses) and by its certification under the EU–US Data Privacy Framework.
Since content is encrypted on your device, Cloudflare cannot read it. To learn more: Cloudflare’s privacy policy.
5. Third-party services contacted by your device
Some features contact third-party services directly. These then receive your IP address and standard technical information (browser type, language), as with any Internet request, but no content from your notebook:
- Map, routes and “What to see?”: the search for places around a stop goes through the app’s server, which queries Overpass (OpenStreetMap) with the city’s coordinates only; otherwise your phone contacts OpenStreetMap directly (Nominatim, Overpass), Photon (Komoot) and Wikipedia (search for places around a stop, photos and summaries of places) receive the name of the place searched for.
- Import of your Polarsteps trips: you choose the data file Polarsteps sent you (or a trip.json file). It is read on your phone (zip.js library included in the app) and never sent, neither to the publisher nor to Polarsteps. Steps, places, stories and photos (3 per step unless you ask for all) become memories, stored like the others: they only go to the server if you chose the cloud for that trip. Vezoria is not affiliated with Polarsteps.
- 3D flyover, shareable recap, badges, expense analysis: calculated and built on your phone from your journal. The video or image is sent nowhere unless you share it yourself. The flyover uses the 3D world map described below.
- Smart packing: the weather for your stops’ cities is requested from Open-Meteo (city position and dates), as for stop weather; the ideas are calculated on your phone.
- Trip tools (called directly by your phone, without your name or the notebook’s content): exchange rates (open.er-api.com, otherwise Frankfurter / ECB), weather at stops (Open-Meteo, which receives the city’s location), automatic receipt reading (the Tesseract.js tool is loaded from jsDelivr; the receipt photo is analysed on the phone and never sent).
- Maps and routes: the base map is loaded from OpenStreetMap (tile.openstreetmap.org) and walking routes along streets are calculated by the public service routing.openstreetmap.de (FOSSGIS). They receive the displayed coordinates and your IP address, without your name or the notebook’s content. The PDF is generated on your phone (pdf-lib library, included in the app). The route and film maps also use Esri base maps (server.arcgisonline.com), which receives the displayed area and your IP address.
- “Sort my photos”: the dates and GPS positions stored in your photos are read on your phone; only the coordinates are sent to OpenStreetMap (Nominatim) to find the place name. The photos themselves are not sent to this service.
- 3D world map: the MapLibre library is included in the app; images of the Earth come from NASA (Blue Marble, GIBS service), close-zoom maps from OpenStreetMap, country and city names from OpenFreeMap (OpenStreetMap data) and the outlines of visited countries from Natural Earth (public domain, loaded from jsDelivr). They receive the displayed area and your IP address, without your name or the notebook’s content.
- Booking import: PDFs are read on your phone (pdf.js library included in the app); screenshots are read by Tesseract.js, loaded from jsDelivr. The document is never sent elsewhere; it is attached to the record as a ticket.
- Install counter: the first time the installed app is opened, a randomly generated identifier and the device type (iPhone, Android, computer) are sent once to the app’s server, to count installations. No personal data, no link with your trips.
- Trip ideas: to complete the suggestions, the app queries Open-Meteo (weather at a destination), Wikidata, Wikipedia and Wikivoyage (nearby cities, places, photos and descriptions). They receive neither your name nor your notebook’s content. No flight prices are requested from any commercial service.
- “I’m here”: when you tap this button, your position is sent to OpenStreetMap (Nominatim) to find the name of the city and country. No position is collected in the background.
- Trip tracking and shared route: if you turn tracking on, your phone records your position only while the app is open (never in the background, phone in your pocket) and stores it in your notebook, encrypted. It is shown to your followers only if you tap “Show your route to followers”: each traveller decides for themselves and can stop at any time.
- Notifications: to reach your phone, a notification goes through your system’s service (Apple Push for iPhone, Google’s Firebase Cloud Messaging for Android and Chrome, Mozilla for Firefox). These services receive the subscription address and a message encrypted twice (by the Web Push standard, and with the trip’s key): they cannot read its content.
- Offline maps: map pieces are downloaded from OpenFreeMap (tiles.openfreemap.org, OpenStreetMap data) and kept on your phone. OpenFreeMap receives the requested areas and your IP address, without your name or your notebook’s content.
- Exploring a city: the city name is sent to OpenStreetMap (location and country), Wikivoyage, Wikipedia and Wikidata/Wikimedia Commons (guide, descriptions and photos) and Open-Meteo (weather and local time). None of these services receives your name or your notebook’s content; a city’s guide is then kept on your phone so it opens offline.
- Place cards: the place name and city are sent to OpenStreetMap (Nominatim) and Wikipedia to find opening hours, website, photo and summary. The (public) information found is stored in the place’s record.
- Serverless packages: if you choose this mode, your data is encrypted (AES-256) with your group’s passphrase into a file that you send yourself (messaging, AirDrop…). The publisher does not receive these files; how long they are kept depends on the service you use to send them.
- External links (airlines, Booking, Google Maps, Trainline…): these are plain links, with no affiliation or payment. By opening them, you leave the App and those sites’ rules apply.
These services are independent of the publisher, who receives no information about this.
6. Permissions, local storage, cookies and audience measurement
Permissions requested by the app (always when you use the feature, never at launch; you can refuse them or withdraw them in your phone settings):
- Location: for “I’m here”, for trip tracking if you turn it on, and to show where you are on the offline map. Only while the app is open, never in the background. In “journey mode”, the app keeps the screen on until you stop it.
- Notifications: only if you turn them on in Settings → Notifications. You choose the categories and can turn them off at any time, in the app or in the phone settings.
- Photos and files: when you add a photo, a receipt, a PDF ticket or a backup, you choose the file (or take the photo) yourself; the app has no access to the rest of your gallery.
- Clipboard and sharing: to copy or send an invitation, a file or the trip film, only when you tap the button.
- Persistent storage: the app asks the browser not to erase your trips when space runs low.
The app does not request access to the microphone or contacts, and sends no advertising notifications.
Local storage: the App uses your browser’s storage (LocalStorage, IndexedDB) to work, including offline. This storage is strictly necessary for the service and requires no consent. The App uses no cookies.
Audience measurement: there are no advertising trackers, no third-party analytics tools and no profiling. Only anonymous measurements strictly necessary to run the service are used: the install counter and the overall server statistics described in section 2, plus the technical traffic statistics provided by the host Cloudflare (number of visits and requests, countries, errors), without cookies and without cross-site tracking. No data is sold, rented or used for advertising.
7. Retention period
- On your device: until you erase the notebook or the browser data.
- On the server: as long as the notebook is in use. A notebook with no activity for 24 months is automatically deleted from the server (its data remains on your devices). A photo removed from a memory, or a deleted memory or trip, is erased from the server.
- Notifications: a device’s subscription is erased from the server as soon as you turn notifications off, when the phone no longer accepts it, or when the notebook is erased. A scheduled reminder is erased as soon as it is sent (at the latest 2 days after its scheduled time).
- Erasure date of a notebook or shared trip: at most 24 months.
- Reports: when a report is made, the publisher keeps a log (date, anonymous fingerprint of the notebook, action taken, reason given by the reporter) for as long as needed to handle it and for any legal follow-up, at most 3 years.
- Abuse protection: to limit automated uploads, the server counts uploads per connection. It does not keep the IP address, only a fingerprint that cannot be read back, erased after 2 hours.
- Hosting provider’s technical logs: according to Cloudflare’s policy, generally a few days.
8. Your rights
You have the right of access, rectification, erasure, restriction, objection and portability of your data:
- Access and portability: More → Sharing & profiles → Export (readable .json file).
- Rectification: edit your records and your profile directly in the App.
- Erasure on the device: More → Sharing & profiles → “Erase this phone”.
- Erasure on the server: ☁️ Cloud button at the top of the screen, or More → Sharing & profiles → “🗑 Delete my data from the server”: the records, photos and notification subscriptions of the chosen notebook are erased immediately from the server, for all its members. The other members of a shared trip keep what their phone already holds and can put it back online. When leaving the cloud, you can also cut your followers’ access. You can also write to the contact address above. See also the Delete my data page.
If you believe your rights are not being respected, you can lodge a complaint with the CNIL (French data protection authority): cnil.fr/fr/plaintes. If you live outside France, you can also contact your local data protection authority.
9. Minors
The App is intended for adults and families. A child may appear in a family notebook under the responsibility of their parents. A minor under 15 should not publish a trip for followers or comment without their parents’ consent.
10. Changes to this policy
This policy may change as the App evolves. Any change is published on this page, with its update date.
11. Contact
← Back to the legal notice