Suvenio · Legal
Privacy Policy
Effective date: 3 August 2026
Suvenio is built around a simple idea: your photos and where you took them are yours. This policy explains exactly what the app does with data, what stays on your device, and which third-party services are involved. Questions? Write to [email protected].
1. What Suvenio does on your device
Suvenio reads your photo library (with your permission) and extracts metadata from your photos and videos: location coordinates, timestamps, dimensions, file names and folder names. This metadata is stored in a local database on your device and is used to place your media on a map and to detect your trips.
Your photos and videos themselves are never copied, modified or uploaded by Suvenio. All indexing, trip detection, statistics and editing (trip names, notes, merges, splits, manual locations, hidden photos) happen entirely on your device.
Suvenio has no user accounts and operates no servers of its own.
2. Permissions Suvenio asks for
- Photo library — to index your photos and videos. On iOS you can grant access to selected photos only.
- Camera (optional) — only if you take a photo from inside Suvenio.
- Location (optional) — only used to tag photos you capture inside Suvenio with your current position, and — using the last known position, never a fresh request — to fill the "Photos around here" home-screen widget. Suvenio does not track your location in the background.
3. Data that leaves your device
Although Suvenio itself uploads nothing, some features rely on third-party services that necessarily receive limited data:
- Map tiles. The maps you see are loaded from a tile provider (currently CARTO, using OpenStreetMap data). When the map loads, the provider receives your IP address and the map areas you view, like any website you visit.
- Geocoding. Trip naming and place search use your device platform's geocoding service (Apple or Google). The coordinates being named, or the place name you search for, are sent to that service.
- Purchases. Subscriptions are processed by Apple's App Store or Google Play, and managed through RevenueCat. RevenueCat receives an anonymous app-generated identifier and your purchase state — never your photos, locations or trips.
- Crash reports. If the app crashes or hits an internal error, a technical report (the error, a stack trace, device model and OS version) is sent to Sentry so the bug can be found and fixed. Crash reports never include your photos, places, trips or files.
Suvenio shows no ads and sends no analytics.
4. Sharing and backups
Share cards (trip images, summaries, the scratch map) and backup files are created only when you explicitly ask for them, and are handed to the app you choose via the system share sheet. What happens to them after that is governed by the receiving app or service.
If the privacy zone setting is enabled (it is by default), photos and route points near your detected home area are excluded from share cards before they are drawn.
Backup files contain your trip edits, manual locations, hidden-photo flags and source preferences — not your photos.
5. Home-screen widgets and background processing
Widget content (a photo thumbnail and counts) is prepared on your device and stored in a private container shared only between Suvenio and its own widgets. If you enable background indexing, the same on-device scan runs periodically; nothing about it leaves your device.
6. Data retention and deletion
Everything Suvenio stores lives on your device. Deleting the app deletes the index, your trip edits and all settings. You can also revoke photo, camera or location permissions at any time in system settings.
7. Children
Suvenio is not directed at children under 13 and does not knowingly collect personal information from them.
8. Future features
If optional accounts or cloud features (such as Google Photos import) are added, they will be strictly opt-in, this policy will be updated first, and the app will ask for your consent before any data leaves your device beyond what is described above.
9. Changes and contact
We may update this policy as the app evolves; the effective date above always reflects the latest revision.
[email protected]