Last updated: September 3, 2026
voyagee is an app for trip planning and packing lists. We collect as little as possible, and we'd rather explain it in plain language than legal boilerplate.
Data controller: Aleksandr Khonin, self-employed (Russia). For any questions about your data, write to khoninwork@gmail.com.
If you clear your browser data or uninstall the app without ever signing in, your trips and lists are gone for good. If you'd rather not risk that, sign in with Google.
Signing in with Google syncs the following to the cloud:
The attached files themselves (ticket scans, booking confirmations) are stored only locally on your device and are never uploaded to the cloud.
Syncing isn't continuous: it runs when you sign in, and periodically while you're using the app (for example, when you switch back to the tab after being away). If the same item is edited on two devices, the most recent change wins.
If you're not signed in, none of this ever leaves your device.
When you fill out a profile — your own or a fellow traveler's, including children and pets — you can enter: name, gender, date of birth, habits (smoking, vegetarian diet), a list of medications (name, a note on dosage, expiry date), home city and home airport.
This data never syncs to the cloud — it stays only on your device, even if you're signed in.
For children and pets, this data is entered by the parent or owner — we don't collect data from children directly.
When you sign in, we receive from Google: your email, name, and profile photo. We never see or store your Google password — Google handles that entirely.
We use Firebase Analytics (Google Analytics 4) to understand which screens and features are used. This is a standard Google service — see their privacy policy for details. If your local law requires an analytics opt-out, write to us and we'll handle it manually until the app has a built-in toggle.
When you send feedback, a bug report, or an idea through the in-app form, we receive: the message text, its type, the page it was sent from, the last ~10 browser console messages (to help diagnose the bug), your browser and device type, an anonymous install ID, and your user ID if you're signed in.
To show a forecast, we send the destination's coordinates and trip dates to Open-Meteo — anonymously, with no personal or account data attached.
We use one functional cookie — tp-lang, which remembers your chosen interface language. Google Analytics may set its own technical cookies — see their policy for details.
We don't sell or share your data with advertisers.
Our cloud providers (Google/Firebase, Vercel) may process and store data on servers outside Russia, potentially in other countries. Google provides safeguards for cross-border data transfers (such as the EU Standard Contractual Clauses). The exact storage region for our Firestore database is still being confirmed — we'll update this section with specifics once we have them.
You can ask us to show you what data we hold about you, correct it, delete it entirely, or provide a copy in a machine-readable format. Just write to khoninwork@gmail.com.
If you're in the European Union, this is handled under GDPR: the legal basis for processing is your consent (account, analytics) and necessity for the feature to work (e.g., coordinates for weather).
The app isn't intended for unsupervised use by children. If a traveler profile belongs to a child, that data is entered by a parent or guardian, who is responsible for it.
There are no paid features in the app right now. Once a subscription payment system launches, we'll update this policy with a payments section.
If we make a meaningful change to how we handle data, we'll update this page and change the date at the top.
Write to khoninwork@gmail.com — a real person will answer.