Privacy Policy

This Privacy Policy explains how the Ovessa application (“Ovessa”, “we”, “us”, “our”) handles information when you use it on your iPhone or iPad. We are Georgii Shilovskii, an individual developer registered in Mexico, contactable at support@ovessa.app.

If you do not agree with this Privacy Policy, please do not install or use Ovessa.

Summary

Ovessa does not collect your health data. There is no account, no cloud copy of your logs, no analytics, no advertising, and no third-party SDK. Your cycle, symptoms, supplements, weight, meals and settings live on your device and — if you choose — in your own Apple Health. Network requests happen only when you explicitly scan or look up food, or when Apple handles an App Store purchase: a meal photo and optional hint go to Ovessa’s stateless service for recognition; generic food words go to the same service, which matches them to the public USDA food database; and barcode digits go anonymously to Open Food Facts. Food-service requests also carry the selected app language and integrity proof, but no account identity. Photos are processed in memory and discarded — never stored or logged. We could not sell, share, or hand over your health data even if asked — we never have it. The only thing kept on a server is a standard technical log of requests to the food service, held by Google Cloud for 30 days to diagnose problems (§4).

Table of contents

1. What Ovessa stores on your device
2. Apple Health
3. Data we collect about you
4. Network connections, exactly
5. The camera and your photos
6. Your doctor report and exports
7. Permissions
8. Retention and deletion
9. Children
10. Third parties
11. Your privacy rights
12. Cookies and tracking technologies
13. Changes to this Privacy Policy
14. Contact us

1. What Ovessa stores on your device

All of the following lives only on your device, in the app’s local database or its settings. iCloud sync for this database is deliberately disabled.

Ovessa never stores a meal photo — not on the device and not anywhere else. None of the data above is uploaded, transmitted to a server we control, or shared with any third party. We cannot see it and we cannot recover it for you.

2. Apple Health

Connecting Apple Health is entirely optional and Ovessa works fully without it. If you connect it:

• Data you author in Ovessa — cycle days, the symptoms Apple Health has a type for, weight, water, and your meals’ calories, carbohydrate and protein — can be saved into your own Apple Health, so it lives with you and is available to your other apps.
• Data you already keep in Apple Health — cycle history, symptoms, weight, glucose from a CGM, sleep, steps, water — is read in place, on your device. Glucose, sleep and steps are read-only by design: Ovessa never writes them. Ovessa’s permission request also lists basal body temperature; the current version neither reads nor writes it.

Health data is never copied to any server, never synced to iCloud by Ovessa, and never sent to us. Apple’s own rules additionally forbid using HealthKit data for advertising or sharing it with third parties, and we do neither. You control access type by type in the Health app and can revoke it at any time. Note that iOS deliberately hides read authorization from apps, so Ovessa can only know that it asked for access, never which types you allowed it to read; its Apple Health status reflects the request, not what is actually shared.

Ovessa’s “Delete everything” erases its own local data but never purges Apple Health; manage Health data in the Health app.

3. Data we collect about you

Only technical diagnostics of the food service. We do not collect health data, anything you type or photograph, usage data, advertising identifiers, or analytics events. Ovessa contains no analytics, telemetry, or crash-reporting code and no third-party SDKs. The one thing kept on a server is the standard request log of Ovessa’s food service described in §4: diagnostics about how the service works, not about what you do in the app. There is no account to create, no profile on any server, and no App Tracking Transparency prompt because there is nothing to track.

4. Network connections, exactly

Ovessa opens a network connection in only four situations:

1. Meal-photo scan — only when you tap scan. The photo (downscaled to roughly 100–300 KB), your optional hint text, and the selected app language are sent over HTTPS to our own stateless service on Google Cloud Run, which forwards the image and hint to a vision model on Google’s Vertex AI — a paid tier, under terms that prohibit training on the data — and returns what food it sees in the app’s language. The service keeps nothing you send: it has no database, writes nothing you send to any log, and processes images in memory only; its own diagnostics carry status codes, never content. The request carries a cryptographic proof that it comes from a genuine, un-tampered copy of Ovessa (Apple App Attest), set up once through a short handshake with the same service, and an opaque per-install identifier. Daily limits on photo scans and nutrition lookups are counted against the attested key. None of this says anything about you: no account exists to link it to, and the rate-limit counters live in memory that evaporates rather than in any datastore. Like any internet service, Google Cloud keeps a standard request log for this service — the time, the address requested, the response code, the IP address and the device’s user agent (app and iOS version) — for 30 days, then deletes it. We use it only to diagnose problems with the service; it never contains your photos, your words or anything from your health records, and we do not use it to identify anyone.
2. Food nutrition lookup. Generic food words — “salmon”, “white rice” — and the input language when needed for translation are sent to the same stateless service. It uses the same Vertex AI model to translate them where needed and to pick the matching entry in the public USDA food database, and fetches the nutrition figures from that entry; only when nothing matches does the model estimate rough figures, which the app labels as approximate. No photo, and no identifiers beyond the same integrity proof and per-install identifier.
3. Barcode lookup, on the first scan of a product. The barcode digits are sent anonymously to Open Food Facts, a public open food database — with no cookies, no identifiers, and nothing about you. Products you have scanned before are cached on your device and work offline forever.
4. App Store purchases. Apple’s StoreKit handles the subscription; that traffic is Apple’s, governed by Apple’s Privacy Policy (opens in a new tab). We receive an entitlement signal (“subscription active”) and never your payment details or Apple Account.

Everything else — cycle, symptoms, supplements, weight, water, insights, the doctor report, CSV export — works entirely offline and makes no connection at all. The privacy, terms and support links inside the app open in your browser only when you tap them.

5. The camera and your photos

The camera is used for two things you invoke. Reading a barcode: the camera frames are processed on your device and only the barcode number is looked up. Photographing a meal: the photo is sent once for recognition as described in §4 — and Ovessa does not store it, on your device or anywhere else. Choosing an existing photo instead uses Apple’s out-of-process picker, so Ovessa sees only the single photo you pick and never your library.

6. Your doctor report and exports

The PDF doctor report and the CSV export are generated on your device and go only where you send them through the iOS share sheet. The patient name on the report is optional and exists only inside the PDF you choose to share — left blank, the report shows no name. Both are written to a temporary folder that is wiped and recreated on each export.

7. Permissions

Ovessa requests only what a feature you’re using needs, and asks in context rather than up front:

• Camera — to scan a barcode or photograph a meal. Declining leaves manual barcode entry, the photo library, and fully manual meal entry available.
• Apple Health, read and write — optional, granted type by type in the Health app, revocable at any time.
• Notifications — for local supplement reminders only. Nothing is sent anywhere; the notifications are scheduled on your device.

Ovessa never requests Location, Microphone, Contacts, or Local Network access, and the photo library is reached through Apple’s out-of-process picker.

8. Retention and deletion

Apart from the 30-day request log described in §4, we retain nothing, because we hold nothing. On your device, data persists until you delete it:

• Edit or delete any individual entry in-app at any time.
• Settings → Privacy centre → What’s stored & where shows live counts of exactly what is on your device.
• Settings → Privacy centre → Delete everything erases every cycle day, symptom, supplement, weight entry, meal, scanned product, and your allergy and diet profile. It is immediate and permanent — we can’t recover it because we never had it.
• Deleting the app removes all of its local data.
• Data you exported, shared, or saved into Apple Health remains wherever you put it. Apple Health data is managed in the Health app; Ovessa never purges it.

9. Children

Ovessa is a health tracker intended for users aged 13 and over. It is not directed to children under 13, and it collects nothing from anyone of any age.

10. Third parties

• Apple Inc. — App Store distribution, StoreKit purchases, HealthKit (on-device), and App Attest, under Apple’s Privacy Policy (opens in a new tab).
• Google Cloud (Cloud Run, Vertex AI) — infrastructure for meal-photo recognition and generic food nutrition lookups, acting as a processor of ephemeral requests. No training on your data; nothing stored by us apart from the 30-day request log in §4.
• Open Food Facts — anonymous barcode lookups against a public database, available under the Open Database License (ODbL); attribution is shown in-app on every product card.
• No other third party receives anything. Ovessa bundles no third-party SDKs.

11. Your privacy rights

Because your health data never reaches us, the rights typically granted under the GDPR, CCPA/CPRA, and similar privacy laws — access, correction, deletion, and portability — are exercised by you, on the device:

• Access. Everything is visible in-app, with live per-category counts under Settings → Privacy centre → What’s stored & where.
• Correction. Every entry, and your allergy and diet profile, is editable in-app.
• Deletion. Delete any entry, or use Delete everything, or delete the app.
• Portability. Export a CSV bundle (eleven files and a readme), or, with Premium, a PDF doctor report, from inside the app.
• Withdrawal of consent. Revoke camera, notification, or Apple Health access in iOS Settings, or delete the app.

We do not sell or share personal information, and we do not process personal data for advertising or profiling — there is none to process. If you nonetheless have questions about your rights, contact us at support@ovessa.app. We hold no data about you beyond the request log in §4, which is not linked to any name, email address, or account, so we cannot look it up by person; it is deleted after 30 days.

12. Cookies and tracking technologies

Ovessa is a native iOS application. It does not use cookies, web beacons, pixels, or any other web-tracking technology, and it performs no online tracking. Barcode lookups are made without cookies. Do-Not-Track signals are therefore not applicable — there is nothing for us to track.

13. Changes to this Privacy Policy

If we materially change this Privacy Policy, we will update the Last updated date above and, where required by law, notify you the next time you open the app or update through the App Store. We encourage you to review this Privacy Policy periodically.

14. Contact us

Questions about this Privacy Policy, or about how Ovessa handles data on your iPhone, please contact us:

Developer: Georgii Shilovskii, Mexico

Email: support@ovessa.app