Privacy Policy
Last updated October 29, 2026
Tripanation is operated by Maxim Zvarici. Contact zvarichmaxim2020@gmail.com about support, privacy or removal of shared data.
Your iPhone memories
Photos you select, trip details and notes are stored in the app’s local storage. We read dates and location information from selected photos to suggest stops. You can choose locations manually. Original photos in your library are never edited or deleted. The release does not record your live GPS route or use background location.
Maps and place search
Place names, searches and map coordinates are sent to Apple’s map services on iPhone under the Apple Privacy Policy. Web maps use OpenFreeMap and OpenStreetMap data. The map provider receives map requests and your IP address. See the OpenFreeMap privacy policy.
Publishing a story
Only when you choose Publish story, a separate copy of that trip and resized photo copies are uploaded to Supabase. Anyone with the resulting link can view it without an account, and may forward the link or save what they see. Before publishing you can exclude notes and companion names. Captions and photo dates are included. Original photo GPS metadata and library identifiers are excluded; map stops are rounded to approximate coordinates and saved places are excluded.
The service stores a random share token and a hash of a separate secret management key. Your iPhone keeps the key in its keychain. It authorizes updating or revoking your story; viewers do not receive it. No personal account is created by the iPhone sharing feature. Requests are subject to abuse limits using salted hashes of IP addresses, not stored raw IP addresses in our application quota table.
Retention and deletion
Local memories remain until you delete them or the app. System backups may also contain app data according to your iPhone settings. Deleting a local trip does not delete its published copy. Revoke its link in Share trip or Settings → Manage published stories to make it unavailable and request removal of its uploaded photos. A small token/hash record remains to prevent a revoked link from being taken over; it contains no trip story. Previously downloaded copies cannot be recalled.
Failed publication uploads are cleaned up on request failure; interrupted server processes or failed storage deletion may leave inaccessible photo objects pending operator cleanup. Email support to request removal or help with a lost management key. Verification may be needed to prevent someone else deleting your story.
Backups
Exported backups contain trip data, photo copies and sharing management keys. You choose where to store them. Keep them private. Restoring adds trips and restores link management.
Website accounts
Some website deployments may enable optional email-link accounts for the web editor. When enabled, Supabase stores your email address and account trip data; session cookies keep you signed in. The iPhone MVP does not use these accounts. The public shared-story site works without sign-in. Contact support for deletion of a website account and its data.
Service providers
Supabase stores published data in the project’s EU region; Vercel serves this website. These providers process IP addresses and technical request logs for delivery and security under their retention policies. See Supabase privacy and Vercel privacy. We do not add advertising, analytics or cross-app tracking.
Changes
We update this page when our handling of your data changes. Material new uses will be explained before you use the affected feature.
Help and contact