What stays on this phone, and what doesn't.

The short version

Your photo files stay on your phone during trip detection. A first pass that notices whether you travelled at all runs entirely on your iPhone. If you then use the AI photo flow, Mapliva sends structured photo evidence — including timestamps, GPS coordinates, photo counts, and related travel clues — through our Firebase backend to OpenAI so it can group possible trips. This can happen before you approve a suggested trip. Candidate evidence and local photo identifiers can also sync to your private Firebase account. Approved trips, goals, and stamps sync so they survive a new phone. Share cards and flyover videos are composed on your device. We also use Firebase for product-usage analytics, crash reports, performance monitoring, and a simple daily record that the app was opened, as described below. If Mapliva's paid edition, Voyager, becomes available and you subscribe, we process Apple's purchase identifiers so the right account gets access — we never see your card details. Nothing is used to train a model. We share only with the named service providers below, and only as needed to run the app.

This website (the marketing pages and the in-browser Stamp Game) uses Google Analytics 4 with analytics storage denied by default. If you accept website analytics, GA4 can set cookies to count visits, understand which pages and main buttons people use, and measure aggregate Stamp Game progress and sharing actions. We do not send your exact city selections to GA4. You can decline or change your choice at any time.

If anything in this policy is unclear, write to team@otrip.app and a human will reply.

Who we are

Mapliva ("Mapliva", "we", "our") is a personal travel journal for iPhone. For the purposes of the EU and UK General Data Protection Regulation, the Mapliva team is the data controller of the personal data processed through the app and this website (together, the "Service"). Contact details are at the bottom of this page.

What Mapliva accesses on your device

Mapliva works inside the iOS sandbox, which means we can only see what you explicitly grant through system permissions or what you type into the app. Specifically:

• Photos (optional). When you grant Photos access through iOS, Mapliva uses Apple's PhotoKit framework to read the capture date, capture location (latitude/longitude, when present), and local identifier of each photo. The image and video files themselves are not uploaded for trip detection. An index is held in Mapliva's on-device database. If you start the AI photo flow, timestamp and coordinate rows, photo counts, duration and airport hints, and optional home references are sent through Firebase Cloud Functions to OpenAI before you review the resulting suggestions. Local photo identifiers are not sent to OpenAI, but they and the resulting candidate evidence can sync to Cloud Firestore under your private Firebase user ID so the review can continue across devices. You can revoke Photos access at any time in iOS Settings → Privacy & Security → Photos → Mapliva.
• Location History (optional, one-time imports). If you choose to import your iOS or Google location history, the app reads the file you provide and indexes it locally on the device. Mapliva does not use Core Location, does not request background location, and does not record any new location data on its own. Nothing about where you are right now is ever observed.
• Sign-in providers. When you choose to create an account, Mapliva uses Sign in with Apple, Sign in with Google, or an email address you provide. The chosen provider returns an authentication token that we exchange for a Firebase user identity. We do not see your provider password.
• On-device trip gate. Before any AI call, Mapliva checks the on-device photo index locally to see whether the dates no scan has covered yet contain a real block of time away from your usual base. This check never leaves the device and never produces a trip on its own; it only decides whether it is worth asking the AI flow at all.
• Purchases (optional). If you buy or restore a Voyager subscription, Apple's StoreKit returns a signed transaction to the app. Mapliva sends that signed transaction to our backend for verification. Payment is handled entirely by Apple — we never receive your card number, billing address, or Apple ID password.
• Push notifications (optional). If you opt in, we use Apple Push Notification service to deliver reminders and milestone alerts you've enabled. Notification payloads are not used for advertising.

Information we collect

Account information

• A Firebase anonymous user identifier may be created when you start as a guest. It is not linked to an email address or name unless you later connect a sign-in method.
• Your email address (from your sign-in provider or as you enter it for email sign-in).
• The name of the sign-in provider you used (Apple, Google, or email) and the user identifier returned by that provider.
• An optional display name, country code, language preference, and home base if you add them.

Travel content you create

• Before approval, photo-based trip candidates may sync to your private Firebase account. Candidate records can include local photo identifiers, timestamps, GPS coordinates, inferred stays and movement hints, city and country labels, and scan-session evidence. They do not include the photo image or video files.
• The trips, visits, goals, stamps, notes, and tags you save in Mapliva — including destination labels, dates, optional photos you attach to a trip, transport modes, and free-text notes.
• Any artifacts you generate inside the app such as trip postcards or year-in-review videos. These are composed on your device. They are only uploaded if you choose to share them through a system Share Sheet that requires server-side processing.

Subscription and purchase information

• If you subscribe to Voyager, we store Apple's verified purchase identifiers — the originalTransactionId, the latest transaction identifier, the product identifier, the store environment, the renewal/expiry dates Apple reports, and a random UUID (appAccountToken) we generate to attribute the purchase to your Mapliva session.
• We store a resulting entitlement record for your Firebase user ID: the tier, the status (trial, subscribed, grace period, billing retry, expired, revoked, or a complimentary grant), the reason it changed, and audit identifiers for the update.
• Apple sends us App Store Server Notifications about renewals, cancellations, billing problems, refunds, and revocations for purchases attached to Mapliva. We use them only to keep the entitlement record correct.
• We count AI work that is subject to an allowance — for example how many valid conversational trip drafts you have requested and whether the free saved trip has been used. Counters are numbers tied to your user ID; they do not contain the content of your drafts.
• We never receive your payment card, bank details, or Apple ID credentials. Apple is the merchant of record for App Store purchases.

Account activity

• When you open the app, Mapliva records a single timestamp for your account — the day it was last opened. We use it to identify dormant accounts whose cloud data can eventually be cleaned up, and to keep an account that is in use from ever being considered dormant. It is not a location, not a session log, and not a per-screen history.

Device and usage information

• Basic technical information such as iPhone model class, iOS version, app version, time zone, locale, and a Firebase-issued install identifier. This is used to render the right UI and to debug crashes.
• Coarse, IP-derived country for the request, used for routing and abuse prevention. We do not store your IP address with your travel content.
• Product-usage events through Firebase Analytics, including screen views, onboarding completion, photo-permission and scan outcomes, counts of suggested trips or GPS-tagged photos, trip and goal actions, sign-in method, and error context. Some events include internal user, trip, or goal identifiers. They do not include photo files, photo metadata, trip notes, or location coordinates.

Diagnostics

• Crash reports and non-fatal error events via Firebase Crashlytics. Each report includes stack traces, the screen you were on, and anonymised device characteristics — no trip content, no notes, no photo metadata.
• Performance traces via Firebase Performance Monitoring (request latency, startup time). Aggregated, not tied to individual users.
• Server-side request logs in our Cloud Functions backend (timestamp, function name, status, latency, derived country). Retained for up to 30 days for debugging and abuse prevention.

How we use information

We use the information described above to:

• Provide the core features of the app — creating an account, saving trips, syncing your record, restoring it on a new device.
• Suggest possible trips when you ask Mapliva to scan your photo library or run the AI trip-detection flow.
• Compose share artifacts (postcards, videos) on your device when you ask for one.
• Keep the Service reliable and secure — diagnosing crashes, monitoring performance, detecting abuse.
• Verify purchases with Apple, grant and revoke Voyager access on the correct account, apply free allowances, restore access you already paid for, and support you when billing goes wrong.
• Identify accounts that have been dormant for a long time so their cloud data does not sit on our servers indefinitely (see Retention and deletion).
• Respond to your account or support requests.
• Comply with applicable law and respond to lawful requests.

Under the GDPR, the legal bases we rely on are contract (to provide the Service you asked for, including handling a subscription you bought), consent (for optional features such as Photos access or Location History import — withdrawable at any time), legitimate interest (to keep the Service stable, secure, and abuse-free, balanced against your interests), and legal obligation where the law requires us to process certain data.

Website analytics (this site only)

The pages on mapliva.app — the marketing site, the in-browser Stamp Game demo, and these legal pages — load Google Analytics 4 (GA4) with analytics storage denied by default. Before you accept, GA4 cannot set or read analytics cookies; Google's advanced consent mode may still receive a cookieless ping containing consent state and basic page measurement. If you accept, we use GA4 to see visit counts, which pages are read, which main site buttons are used, aggregate Stamp Game stages and counts, sharing methods, and roughly where in the world traffic comes from. This website measurement is separate from the native Firebase Analytics events collected by the Mapliva iPhone app and described under “Device and usage information” above.

After you accept, what GA4 receives: the page URL you visited, page title, your referrer (the previous page or search engine), device type and screen size, browser language, an IP-derived approximate location (city / region level, with the full IP discarded), main-button event details, and Stamp Game events such as whether play started, aggregate numbers of stamps/countries/continents, results tabs viewed, restart, and sharing method. We do not send the particular cities or countries you selected. GA4 also receives a randomly-generated cookie identifier so a return visit can be counted as the same browser. What it does not receive: your name, email, account information, photos, exact Stamp Game selections, trip data, or anything you've entered into the app.

If you accept, GA4 can set first-party cookies named _ga and _ga_DNLYM84X3S on this site. They expire after 2 years. We rely on your consent for cookie-based website analytics. If you decline, analytics storage stays denied and Mapliva does not send custom main-button events. You can:

• Use the choice below to accept, decline, or change website analytics at any time.
• Block GA requests entirely with a browser tracking blocker.
• Install Google's own Google Analytics Opt-out Browser Add-on to opt out across every GA-using site at once.
• Clear the _ga cookies in your browser settings; declining through our control also asks the browser to remove Mapliva's GA cookies.

Sharing a Stamp Game atlas. Playing the game keeps your city selections in your browser. If you choose to share your atlas — the share link, or the poster shared with its link — those city selections travel inside the link (for example mapliva.app/a?s=par,tyo), because anyone opening it has to be able to see the same atlas. Opening such a link asks our Firebase backend to draw the preview card for it, so the city list appears in our server request logs, which we keep for up to 30 days. Nothing else about you is attached, and a game you never share is never sent to us.

We do not run advertising on this website, we do not use GA's advertising or remarketing features, and we have not enabled Google Signals (cross-device tracking via signed-in Google accounts).

AI features and what we send to OpenAI

Mapliva uses AI to help draft trips from your photos, run the assistant, and compose year-in-review summaries. These features call OpenAI through a backend we host on Firebase Cloud Functions.

What is sent to OpenAI: when you start the AI photo flow, Mapliva can send structured evidence before you approve a suggested trip. That evidence can include photo timestamps, GPS coordinates, grouped photo counts and durations, airport hints, and optional home-city or home-airport references. Other AI features can send dates, destination labels, airport and country codes, and text you submit to the assistant or trip-building flow. What is not sent to OpenAI: photo image or video files, local PhotoKit identifiers, sign-in credentials, or push tokens.

We use OpenAI's API with the default setting that prompts and outputs are not used to train OpenAI's models. OpenAI may retain inputs and outputs for up to 30 days for abuse and safety monitoring, after which they are deleted, in line with their API data-handling commitments.

AI suggestions are probabilistic. They can be incomplete or wrong. You decide what is saved to your travel record. You can avoid AI features entirely by using the manual entry flow (Type it in) instead of the photo-flow or assistant.

Service providers we share data with

We do not sell your personal information and we do not share it for cross-context behavioural advertising. We share data with the providers below ("subprocessors") only as needed to operate the Service. Each acts under a written agreement that restricts how they may use your data and requires them to apply appropriate security measures.

We may add or change subprocessors as the Service evolves. When we do, we'll update this list and, for material additions, surface a notice in the app or this page before the change takes effect.

Beyond subprocessors, we may also disclose information when required by law, to enforce our Terms, to protect the rights, property, or safety of Mapliva, our users, or others, or in connection with a merger, acquisition, or sale of assets (in which case we will use reasonable efforts to notify you in advance).

International data transfers

Mapliva is built on cloud infrastructure that may store and process your data in countries other than your own, including the United States. Where personal data is transferred from the European Economic Area, the United Kingdom, or Switzerland to a country that is not the subject of an adequacy decision, we rely on the Standard Contractual Clauses approved by the European Commission and, where applicable, the UK International Data Transfer Addendum, together with supplementary measures (encryption in transit and at rest, scoped access controls, audit logging).

You can request a copy of the safeguards in place by writing to team@otrip.app.

Retention and deletion

We keep your information for as long as your account is active and only as long as we need it.

• Account and travel content. Kept until you delete the relevant item or your account. When you delete your account in Settings → Account → Delete account, your trips, goals, stamps, profile, and settings are removed from our active systems within 30 days. Encrypted backups may persist for up to a further 60 days before they are overwritten on rotation.
• Photo index and candidate evidence. The primary photo index lives on your iPhone and is removed when you delete the app or revoke Photos access. The subset of local photo identifiers and evidence attached to synced trip candidates remains in your private Firebase account until you delete the candidate or account, subject to backup rotation.
• Crashlytics & Performance traces. Retained by Firebase for up to 90 days, then aggregated or deleted.
• Cloud Functions request logs. Retained for up to 30 days for debugging and abuse prevention.
• AI request logs at OpenAI. Up to 30 days, then deleted in line with the OpenAI API agreement we operate under.
• Subscription and entitlement records. Kept while the subscription is active and afterwards for as long as we need them to honour restores, handle refunds and chargebacks, and meet tax and accounting duties. Deleting your Mapliva account removes the entitlement, usage, and activity records tied to your user ID, but does not cancel an Apple subscription — cancel that in your Apple ID settings — and Apple's own record of the transaction remains with Apple.
• Account activity timestamp. Kept while the account exists and deleted with it. We are building a dormancy policy under which a long-inactive account's cloud data would be deleted after at least 6 months of inactivity for an unregistered guest account, or 12 months for a registered one, with advance notice and a grace period before anything is removed. No account is deleted on this basis today; the policy runs in report-only mode, and we will update this page and notify you in the app before that changes. An active subscription or complimentary grant protects an archive from dormancy cleanup.
• Legal & tax records. Retained for the period required by applicable law (typically up to 7 years for invoicing and tax).

Security

We use technical and organisational measures designed to protect your data, including TLS encryption in transit, encryption at rest in Firebase's managed services, Firestore security rules that enforce per-user authorisation on every read and write, scoped service-account access, audit logging, and least-privilege principles for internal access. Authentication is handled by Firebase Authentication; we do not store passwords for email sign-in ourselves.

No system is perfectly secure. If we become aware of a security incident that affects your personal data, we will notify you and the appropriate regulators where required by law.

Your privacy rights

Subject to local law, you have the following rights in relation to your personal data, and many of them you can exercise directly in the app:

• Access. Ask for a copy of the personal data we hold about you. Most of it is visible in the app; for the rest, write to us.
• Rectification. Correct inaccurate data — for trip and profile data, you can do this directly in the app.
• Erasure. Delete trips and goals from inside the app at any time. Delete your account (which deletes everything associated with it) from Settings → Account → Delete account.
• Restriction. Ask us to limit how we use your data in certain circumstances.
• Portability. Export your trips and goals as a structured JSON file from Settings → Export trips.
• Objection. Object to processing we carry out on the basis of our legitimate interests.
• Withdraw consent. Revoke Photos access in iOS Settings, disable push notifications, or stop using AI features at any time.
• Lodge a complaint. If you are in the EEA, UK, or Switzerland, you may complain to your local data-protection authority — we would appreciate the chance to address your concerns first.

If you are a California resident, the California Consumer Privacy Act (as amended by the California Privacy Rights Act) gives you the right to know what personal information we have collected, the right to delete it, the right to correct it, the right to opt out of the sale or sharing of personal information (we do neither), the right to limit use of sensitive personal information, and the right not to be discriminated against for exercising these rights. Residents of Colorado, Connecticut, Virginia, Utah, and other US states with comparable laws have similar rights and may exercise them through the same contact channel.

To exercise any of these rights, write to team@otrip.app. We may need to verify your identity before responding and will reply within the timeframe required by applicable law (one month under GDPR, extendable by two further months for complex requests).

Children

Mapliva is not directed to children under 13, or the equivalent minimum digital-consent age in your jurisdiction (for example, 16 in parts of the EEA, 14 in some EU member states). We do not knowingly collect personal information from children below that age. If you believe a child has provided us with personal information without parental consent, please write to us and we will delete it.

Changes to this policy

We may update this Privacy Policy from time to time to reflect changes to our practices, the Service, or applicable law. When we make material changes we will surface a notice inside the app and update the "Effective" date at the top of this page before the changes take effect. Continued use of the Service after that date means you accept the updated policy.