How VoyaMate processes your travel data on Android.

2. Data processed and purposes

Journeys and settings

VoyaMate stores travel information that you enter, import or confirm. This may include destination and place name, country or territory, period, visit type, travel purpose, transport, airports, notes, deliberately saved coordinates, home country, home airport, nationality, and display or app settings. This data is used for maps, calendars, statistics, visa and stay calculations, yearly reviews, Travel Film and exports.

Location and automatic travel detection

If you enable automatic travel detection and grant the required permissions, VoyaMate uses Android LocationManager with passive, network-based or GPS-based location events. Background location may be required for detection while the app is closed.

Automatically received raw coordinates are checked against country boundaries bundled with the app and are not written to the VoyaMate database, backups or logs. VoyaMate permanently stores the derived country, detected period and the fact that the record was created automatically. Android and, where applicable, location components supplied by Google or the device manufacturer provide the location itself; their processing is governed by your device and account settings.

Photo library

When you voluntarily use photo import, VoyaMate reads capture date and, when available and permitted by Android, GPS metadata from selected photos or the local media library. Country and territory matching uses boundary data stored in the app. Visual image content is not analyzed to detect journeys and is not uploaded by VoyaMate.

Time, coordinates and a local media identifier are processed temporarily to form groups. If you import a suggestion, VoyaMate stores the detected period, country or territory, average coordinates, number of supporting photos and a non-reversible SHA-256 fingerprint of local identifiers. The images themselves are not copied into the travel database.

Map and place search

The map is rendered with MapLibre. The current style loads its style definition, vector tiles, symbols and fonts from demotiles.maplibre.org. The service therefore receives technical information including your IP address, time, HTTP request data and requested map resources or tile coordinates. These requests can reveal the displayed map area. VoyaMate does not transmit a VoyaMate account name and does not operate its own map server.

Optional place search and readable place names use the Android device's Geocoder. The provider depends on the device and its system services. Geocoder can process search terms or coordinates over the network. Once you choose a result, VoyaMate stores its name, country or territory and coordinates.

Travel expenses and documents

Expenses, currencies, categories, business or personal classification, reimbursement and settlement status, optional profile details for exports, and receipts, invoices, bookings, boarding passes or other documents that you import or capture are stored with their files in private app storage.

PDF, CSV and other data exports are generated only when you request them and written to the destination you choose through Android. Files that you then share or store externally are also subject to the terms of that destination.

Identity documents, camera and text recognition

VoyaMate can store document type, label, nationality, issuing country, expiry date and reminder settings locally. An optional document number is stored separately using AES-GCM with a key held by Android Keystore and is excluded from backups and exports.

During an optional scan, VoyaMate processes the camera capture with Google ML Kit on the device. ML Kit does not send the input image or recognition result to Google servers. It may occasionally contact Google servers for bug fixes, updated models or hardware-accelerator compatibility information. An identity-document capture is discarded after recognition and is not kept as a document copy. A receipt you deliberately capture can be stored as a travel document.

Notifications and app protection

If you enable reminders, Android schedules local notifications containing the document label and expiry date. If you enable app protection, Android performs biometric or device authentication; VoyaMate receives no biometric characteristics.

Google Play

Product information, checkout, payment processing, purchase status and restoration of one-time purchases are handled through Google Play Billing. VoyaMate reads Google Play's confirmed product identifiers and purchase state to unlock features. The developer does not receive payment-card details. Android purchases are not matched with Apple purchases.

3. Local storage, exports and Google Drive

Travel data is held in a local Room database; imported travel documents are kept in the app's private files area. VoyaMate disables general Android cloud backup and automatic device transfer for its databases, settings and app files. Cloud data is therefore created only through the VoyaMate backup features you deliberately use.

Encrypted local backup

At your request, VoyaMate creates a backup containing journeys, expenses, travel documents, daily expense reports, identity-document metadata, visa rules, saved places and visits, and app settings. Imported travel-document files can be included. Document numbers, saved passwords, Google access tokens and Google Play purchase data are excluded.

The backup is encrypted with an AES-256-GCM key derived from your password. A backup password saved in the app is itself protected through Android Keystore. A backup cannot be restored without the corresponding password.

Readable data export

VoyaMate can create a password-protected ZIP containing CSV tables, complete JSON data and imported travel documents. Identity-document metadata may be included; protected document numbers remain excluded. The export remains at the destination you select until you delete it there.

Optional Google Drive backup

If you connect Drive, VoyaMate requests only the Google OAuth scope drive.appdata. The encrypted backup is uploaded to your Google Drive hidden app-data folder. This area is accessible only to VoyaMate and is not shown in the regular Drive file interface. VoyaMate finds its backup file there and creates or replaces the current version.

Google processes Google Account, authorization, access, file and technical connection data under your Google Account terms. The developer does not operate a backup server and does not receive your backup password.

4. Legal bases

Where the GDPR applies, processing required for app features you use is based on Article 6(1)(b) GDPR. Optional access to location, photos, media location, camera, notifications and Google Drive is based, where required, on your consent under Article 6(1)(a) GDPR. Processing required for security and operation is based on Article 6(1)(f) GDPR. You can change Android system permissions at any time.

5. Retention and deletion

App data remains stored until you delete individual entries, clear the app's data in Android or uninstall VoyaMate. Deleting an identity document also removes its protected document number and scheduled reminder. Deleting an imported travel document removes its associated private file.

PDF, CSV, ZIP and backup files you export remain at the destination you choose until you delete them there. You manage the encrypted backup in Google Drive's app-data area through the connected apps and data settings of your Google Account. Uninstalling the Android app does not necessarily remove files you exported yourself or app data held in your Google Account.

6. Your rights

Subject to the applicable legal requirements, you have rights to access, correction, deletion, restriction, portability and objection. You may withdraw consent with future effect and lodge a complaint with a data protection authority.

Because the developer does not operate a server for your VoyaMate travel data and cannot access the local database or the contents of your encrypted backup, the developer cannot directly inspect or change those records for you. Your legal rights and ability to contact the controller remain unaffected.

7. Third parties and further information

• Google Privacy Policy
• Google Drive app-data folder
• Google ML Kit terms and privacy
• MapLibre Style Specification

8. Date and controller

Last updated: August 24, 2026. This policy will be updated if features, map services or data processing change materially.

Controller
Fabian Vocke
Am Autobahnzubringer 1
76709 Kronau
Germany

Email
privacy@mate.build