omiREADER

Omi Reader

Privacy Policy

Effective 9 September 2026 · Published by Udara Labs Limited

What's switched on today. This policy describes Omi Reader with every feature enabled, so it stays accurate as features ship. In the current release, cloud voices and subscriptions are disabled: sections 5 and 6 don't apply yet, and no text leaves your device. Update this paragraph — and only this paragraph — when that changes.

1 Who this covers

This policy applies to the Omi Reader iOS app, its Safari extension and its share extension, and to the voice service that supports them. The data controller is Udara Labs Limited, a company registered in England and Wales (number 16231683).

It doesn't cover the websites you read. Those have their own policies and we have no relationship with them.

2 The short version

WhatWhere it goesWhy
Articles and PDFs you saveYour device onlySo the app can read them back
Where you stoppedYour device onlyTo resume in the right place
Sentence text, when using Omi voicesOur server, then the speech providerTo turn it into audio
An install identifierOur serverTo count usage against your allowance
Your App Store transactionOur serverTo check the subscription is live
Provider API keys, if you add oneYour device's KeychainNever sent to us
Personal VoiceYour device onlyNever transmitted, by anyone

We don't ask for your name, email address or Apple ID, and there is no account to create.

3 What stays on your device

Pages, PDFs and shared text you bring into Omi Reader are stored in the app's own container on your device, along with your position in each one and your settings. None of it is uploaded to us, and none of it is readable by us.

What happens to it when you delete the app is covered in section 10.

4 The Safari extension

The extension only runs on sites you have granted it permission for, and only when you tap it. When you do, it reads the article text of the page you're on and hands it to the app on the same device.

It doesn't watch your browsing, record the pages you visit, or run in the background. Nothing it reads is sent anywhere by the extension itself.

5 Cloud voices

Omi Reader can read using voices on your device, which involves no network at all, or using a cloud voice. There are two kinds of cloud voice and they are meaningfully different for your privacy.

Your own provider key. If you supply an API key for OpenAI, Azure or ElevenLabs, your device contacts that provider directly. The text goes from your phone to them; it does not pass through us, and we cannot see it. Your key is held in your device's Keychain and is never transmitted to us. That provider's own privacy policy governs what they do with it.

Omi voices. If you use the voices we host, your device sends the sentence being read to our server, which forwards it to a speech provider under our account and returns the audio. In that request we receive:

  • the sentence text, and the voice you chose;
  • an install identifier — a random value created on your device, which identifies the installation and nothing about you;
  • your signed App Store transaction, if you subscribe (see section 6);
  • your IP address, as any web request necessarily reveals.

Worth knowing: synthesised audio is cached on our server and keyed by a hash of the text and voice, which means audio produced for one reader can be reused for another reading the same passage. The cache holds audio and that hash. It is not linked to who requested it, and it cannot be searched by person — but it does mean a sentence you had read may be served to someone else who reads the same article.

We do not use the text you send for training, and neither, under our agreements, do the providers we use for it. We don't build a profile of what you read.

6 Subscriptions and payment

Subscriptions are sold and processed by Apple. We never see your card, your billing address or your Apple ID.

What we receive is the signed transaction Apple issues, which we verify to confirm the subscription is live. It contains an identifier for the purchase, the product bought and its expiry date. We store that identifier so the monthly allowance follows your subscription rather than your device.

7 Diagnostics and usage

We may collect limited, aggregated information about how the app is used — for example how often a feature is opened, whether a step failed, how long synthesis took — to find faults and decide what to build next.

Where we do, it is tied to the install identifier described above rather than to you, and it never includes the content of anything you read. We will not use it for advertising, and we will not sell it. If we introduce anything beyond this, we will say so here before it starts, and offer a way to turn it off where the law requires one.

8 Personal Voice

Personal Voice is Apple's feature. Your recordings and the resulting voice are created and stored by iOS on your device. Omi Reader asks iOS for permission to speak with it and nothing more: we never receive the voice, the recordings, or anything derived from them, and they are never uploaded to us.

9 How long we keep things

  • On your device: until you delete the article or the app.
  • Usage counters: per calendar month, retained for up to 13 months so allowances and billing can be reconciled.
  • Cached audio: until it is evicted to make room, which is driven by space rather than time.
  • Server logs: up to 30 days, then deleted.

10 Deleting the app, and backups

Deleting Omi Reader removes the articles, PDFs, reading positions and settings it stored. Those are gone from the device at that point.

Two things deliberately survive deletion, because iOS keeps Keychain items after an app is removed:

  • the install identifier, so that reinstalling doesn't hand out a fresh monthly allowance — it identifies the installation, not you;
  • any provider API key you saved, so you don't have to paste it again.

Neither is created unless you use a cloud voice, so on a device that has only ever used the built-in voices there is nothing of either kind to keep. Both are removed when you erase the device. If you want the identifier reset without doing that, write to [email protected].

On backups: the app's stored articles, and those two Keychain items, are included in your iPhone's backup if you have backups switched on, and restore with it — including onto a new device. That is Apple's mechanism rather than ours, and the backup is held by Apple or your computer, not by us.

11 Who else sees it

Only the parties needed to make the app work: the speech provider that synthesises audio, our hosting provider, and Apple for payments. Each is bound by contract to process data only on our instructions.

We may disclose information if the law requires it. We do not sell personal information, and we do not share it for cross-context behavioural advertising — terms that carry specific meanings under US state privacy laws, and which we mean here in those senses.

Our providers may process data outside your country. Where that involves transfers out of the UK or EEA, they are covered by the standard contractual clauses or an equivalent safeguard.

12 Your rights

Depending on where you live, you may have the right to access, correct, export or delete the personal information we hold, to object to or restrict how we use it, and to complain to a regulator.

Most of what Omi Reader holds is on your device, where you already control it — see section 10 for exactly what deletion does and doesn't remove. For anything held on our server, write to [email protected]. Because the install identifier is all that connects a request to a person, we may need you to send it from the app so we can find the right records — and we may be unable to help without it, which is a consequence of not knowing who you are rather than an unwillingness.

Our lawful basis, where UK or EU law applies, is performance of our contract with you for the parts needed to deliver the app, and our legitimate interests in keeping the service working and free from abuse for the rest.

13 Children

Omi Reader is not directed at children under 13, and we do not knowingly collect information from them. If you believe a child has provided us with personal information, write to us and we will delete it.

14 Changes

If we change this policy we will update the date at the top. Where a change materially affects how we handle your information, we will say so in the app before it takes effect.

15 Contact

Udara Labs Limited, 86–90 Paul Street, London EC2A 4NE, England · [email protected]