Skip to content
Omato
For readersFor learnersSupport
Download on the App Store

Privacy Policy

Last updated: 27 September 2026

Omato is developed by Lucas Mariani. This policy explains the information processed when you use the app, request word definitions or translations, and purchase a subscription. Contact [email protected] with questions or data requests.

Your reading and vocabulary

Omato recognizes text in book photos on your device. Photos are not uploaded to our backend or advertising services. Your saved vocabulary and study data are stored on your device and, when available, in your private iCloud storage.

When you request a definition, translation or conjugation, Omato sends the selected word, relevant surrounding text, and requested language or grammatical information through our Cloudflare-hosted backend to an AI provider. OpenAI is the current production provider. This information is used to generate the requested result. We do not add your installation identifier, subscription identifiers or device authentication key to the AI provider's request.

The backend does not save lookup text or generated definitions in its usage-measurement database or application diagnostic logs. We explicitly disable OpenAI response-history storage for new requests, including retries. This does not disable all provider retention: abuse-monitoring records may contain prompts and responses and are normally retained for up to 30 days, with exceptions described in OpenAI's data controls. Provider prompt caching is separate and may retain encrypted processing data for up to 24 hours. This change does not retroactively delete previously stored responses. We do not claim zero retention by the AI provider.

Operating and protecting the service

Omato uses Apple's App Attest to verify app requests. Our backend retains an app-installation/device key identifier, public verification key, registration and last-use times, security status and an assertion counter that prevents replayed authentication attempts. Separate short-lived request counters enforce usage limits. We no longer accumulate lifetime request totals or archive hourly per-device usage. These identifiers do not require an Omato login or reveal your Apple ID to us.

Cloudflare processes network information, including IP addresses, to deliver and protect requests. We disable the Workers invocation logs that retained request headers, client IP addresses and IP-derived geographic metadata. Our retained application diagnostics contain a restricted set of operational fields, such as route, status, error category, request timing and provider/model; they exclude client IP, location, authentication keys, reading content, photos and definitions. Disabling these logs does not prevent Cloudflare from processing network information needed to operate and secure its infrastructure.

Subscriptions and app activity

Apple handles subscription purchases and billing. Omato uses StoreKit on your device to verify purchases, update access and restore subscriptions. We do not receive payment-card details.

Omato no longer sends installation-linked marketing activity or subscription transactions to our backend. Collection of the former activity events and Apple subscription notifications is disabled. The app does not use Meta or Firebase analytics SDKs, collect AdServices attribution tokens, or create a marketing installation identifier. Necessary authentication and service request counters are described above.

Advertising for Omato

Omato uses Apple’s privacy-preserving SKAdNetwork and AdAttributionKit mechanisms to help measure app installs from advertising. When the app launches or returns to the foreground, it asks Apple’s system to register a fixed launch-only signal. Omato supplies no user or installation identifier, reading content, activity details, purchase information or revenue with that signal.

Apple manages attribution and sends delayed postbacks to eligible advertising networks, subject to privacy thresholds. Omato does not request App Tracking Transparency permission, access IDFA, or track people across other companies’ apps and websites. The app does not display advertisements.

How long information is kept

The activity, installation/attribution and subscription-measurement records listed below are historical data collected before measurement was disabled. No new records are accepted through those measurement endpoints. Updating the app did not immediately erase previously collected records; they remain subject to these deletion schedules.

  • Activity events: scheduled cleanup removes backend measurement events more than 90 days after receipt.
  • Installation and attribution records: scheduled cleanup removes them more than 400 days after first enrollment.
  • Subscription measurement: transaction, notification and renewal-state records are removed more than 400 days after their applicable signed update. Ownership associations remain while related retained transaction records exist.
  • Device-security records: active keys are deleted after more than 400 days without use, once no retained acquisition installation depends on the key. Disabled/revoked keys are retained to enforce security decisions. Active authentication records remain necessary while used.
  • Request counters and authentication challenges: completed hourly/daily quota windows and consumed/expired authentication challenges are removed at the next hourly cleanup. Current quota windows remain enforced. The old hourly archive and lifetime totals are cleared rather than retained as usage history.
  • Operational logs: standard Cloudflare Workers Logs retention is up to seven days. These logs are separate from database records.
  • Provider-held information: OpenAI applies its own retention rules. Information previously sent to Meta remains subject to Meta’s policy; the current app sends no Meta events. Deleting Omato does not automatically delete information already held by providers.

Scheduled deletion can take until the next cleanup run. Infrastructure backup/recovery copies may persist according to the hosting provider's recovery retention after active records are deleted.

Your choices and requests

You can manage or export vocabulary in the app and manage its iCloud storage through Apple settings. Deleting the app does not immediately delete our server records or cancel a subscription. Manage or cancel subscriptions through your Apple account's subscription settings.

Contact [email protected] to ask about access, correction or deletion of information we hold. Because our records use pseudonymous identifiers, we may need information that lets us locate the relevant records and verify the request. Do not send passwords, payment-card details or book photos. If you email us, we use your message and contact information to respond and handle the request.

Service providers may process information in countries other than your own. Applicable privacy rights depend on your location. We will update this policy when our data practices change.

Website analytics and preferences

The Omato website records page views, App Store link clicks and language changes through our own Cloudflare endpoint. Records include the page path/type, language, clicked link destination and placement, language selection, host/referrer-host information, campaign parameters (UTM source, medium, campaign and content), timestamp, network-derived country and Cloudflare data-center code. Our analytics code does not set tracking cookies, assign a persistent visitor ID or write the visitor IP address to the analytics dataset. Cloudflare still processes network information to serve and protect the site. Website analytics retention is governed by Cloudflare Analytics Engine, separately from the app's database cleanup periods.

The website stores your selected language locally in your browser. This preference is separate from analytics. Links to the App Store and other external services are subject to those services' privacy policies.

Omato
Follow the step-by-step guidePrivacySupportTerms