Medlet

Privacy Policy

Last updated: November 4, 2026

The short version. Your medicine cabinet stays on your phone. Medlet needs no account (only the optional shared family cabinet asks you to sign in with Apple or Google) and has no ads, and it does not sell your data or track you across other apps. If you choose to read a pack with AI, the photo of the pack goes through our server in the EU to Google Gemini and is not kept by us. We collect pseudonymous usage analytics only if you agree (where the law requires consent) and crash reports to fix bugs. You can switch AI reading, analytics and crash reports off at any time: Settings → Privacy.

Who we are

Medlet (“the app”, “we”, “us”) is developed and published by Matvey Pirogov, the controller of the personal data described in this policy. Contact: medlet@pirog.app.

Data that stays on your device

Everything you create in the app is stored only on your phone, in the app’s local storage:

We do not receive this data. It is included in your device backups according to your backup settings (iCloud or a computer on iPhone, Google backup on Android). Deleting the app deletes it from your phone.

Data processed by services we use

ServiceWhat and whyYour choice
Apple (App Store) or Google (Google Play) Payments for Medlet Pro are handled by Apple or Google under their privacy policies. We never see your payment details. —
RevenueCat, Inc. (USA) Manages Pro subscriptions and purchases: a random app user ID, purchase and subscription records, app version and device type. Used to unlock Pro, restore purchases and count subscriptions. Needed to sell and restore Pro (contract).
Apple Ads attribution (Apple, via RevenueCat; iPhone only) If you install Medlet after tapping one of our ads on the App Store, the app gets an attribution token from Apple’s AdServices framework, and RevenueCat exchanges it with Apple for the campaign, ad group, keyword and country of that ad. No advertising identifier (IDFA) is used, and Apple does not treat this as tracking. Used only to see which of our ads pay off. Legitimate interest (measuring our own ads). You can object at any time: medlet@pirog.app.
AI reading of packs: Google Cloud Functions and Vertex AI with Google Gemini, both in the EU (Google Cloud) Only if you agree before your first AI scan. The photo of the pack (resized, without location or other photo metadata), the app language, the code read from the pack and a random installation ID go to our function in the EU (Belgium), which asks Google Gemini to read the name, strength, pack size, expiry date and what the medicine is used for. We don’t store the photo. Google reads it in the EU under the Google Cloud terms for Vertex AI: it does not use it to train models, keeps it in memory for no longer than 24 hours and may log it for a limited time only to detect abuse. The random installation ID and a count of scans are stored in the EU (Firestore) for 62 days to limit the number of scans. Your explicit consent. Off at any time: Settings → Privacy. Without it, the code on the pack and manual entry still work.
Google Firebase Analytics (Google LLC / Google Ireland) Pseudonymous usage events: screens opened, paywall shown or closed and which version of the Medlet Pro screen you get (to compare versions), purchase made, a one-time discount shown or declined, moving your data from the previous version, your answer about AI reading, the result and duration of an AI scan, adding a pack (how it was added and counts only — never medicine names, photos or dates), a shelf scan series (how many frames and packs it found, how long it took and whether each pack was shelved, skipped or left waiting for Pro — counts only), making a place private or shared again in the shared cabinet (that fact only — never the place’s name or contents) and marking a dose as taken (the remaining count only), plus device model, OS version, app version and approximate country. No advertising ID is collected and the data is not used for ads. In the EEA, the UK and Switzerland — only if you say yes during setup (consent). Elsewhere — on by default (legitimate interest). Off at any time: Settings → Privacy.
Google Firebase App Check with Apple App Attest or Google Play Integrity (Google LLC / Google Ireland; Apple) Protects pack reading and the shared cabinet from abuse: the app proves to our cloud functions that requests come from the genuine Medlet app on a real phone. Apple’s App Attest (iPhone) or Google Play Integrity (Android) issues a cryptographic attestation of the app, which Google checks. It contains no personal data and isn’t used to identify or track you. Always on — it only confirms the app is genuine (legitimate interest: keeping the service safe).
Google Firebase Crashlytics Crash reports: the error, the state of the app when it crashed, device model, OS and app version. Used only to find and fix bugs. On by default (legitimate interest). Off at any time: Settings → Privacy.

Reminders — expiry dates, course doses and “running out” — are local notifications that Medlet schedules on your phone. No push service is involved and nothing about them is sent to us. A reminder shows the medicine’s name; to hide it on the lock screen, turn off notification previews in your phone’s settings.

Shared family cabinet (optional)

If you turn on the shared cabinet (a Medlet Pro feature), Medlet copies your cabinet to Google Firebase Cloud Firestore in the EU (multi-region eur3) so that the people you invite see the same shelves: medicines and what they are for, packs with their stock, expiry dates and places, the family members you added, and course marks, plus small cut-out pictures of pack fronts (without the background, up to 256 pixels) so everyone sees the same shelf. Full photos of packs are not uploaded.

You choose which places to share. When you turn on or join a shared cabinet, you tick the places your family will see, and you can change it later on the Family screen. A private place stays only on your phone: the place, its packs, medicines that are only in private places, and their courses, marks and pictures are not uploaded. Making a place private removes its data from the shared cabinet in the cloud and from the other members’ phones; making it shared again uploads it.

Links to the App Store

Links to Medlet on our website and in our posts carry a campaign name, for example “launch-post”. Apple reports to us, in aggregate, how many people downloaded or subscribed after following each link.

What we don’t do

How long data is kept

On-device data stays until you delete it or the app. Photos sent for AI reading are not stored by us; the scan counter with the random installation ID is deleted after 62 days. Analytics data is kept for up to 14 months and crash reports for up to 90 days. Purchase records are kept by RevenueCat while needed to provide Pro and to meet legal accounting obligations. Shared cabinet data is kept while the shared cabinet has members and is deleted when the last member leaves or deletes their account.

International transfers

Our AI function, the Gemini model that reads the pack and the scan counter run in the EU. RevenueCat and Google (for analytics and crash reports) may process data in the United States. These transfers rely on the EU–US Data Privacy Framework and/or the European Commission’s Standard Contractual Clauses.

Your rights

Depending on where you live (for example under the GDPR or US state laws), you may have the right to access, correct or delete your data, to object to or restrict processing, to data portability and to withdraw consent at any time. Most data never leaves your device, so you control it directly. For analytics, crash or purchase data, write to medlet@pirog.app — include the approximate date of purchase if your request is about a subscription. You can also complain to your local data protection authority.

Children

Medlet is not directed at children under 16, and we do not knowingly collect data from them.

Changes

If this policy changes, we will update this page and the date above. Significant changes will also be noted in the app’s release notes.