Privacy Policy

1. Who this covers

This policy covers the OMS Player application for Android and iOS — also listed as OMS AI on the App Store — and the omsplayer.com website. It explains what information the app handles, what is sent off your device, and who receives it.

Using the app means you accept this policy. If you do not agree with it, do not use the app.

2. Your account and sign-in

OMS Player requires you to sign in before you can use it. On Android you sign in with Google; on iPhone and iPad you sign in with Apple. There is no password of ours — the store account you already have is what identifies you.

What we receive from that sign-in is your email address, and your display name when the provider supplies one. The email address is the key that ties together your licence, your subscription and your usage allowance — all three systems identify you by it. It is stored on your device and sent to the servers listed in the next section.

If you use Apple's Hide My Email, the relay address Apple gives us (@privaterelay.appleid.com) is the address we hold, and we never see your real one. Apple returns your email only on your very first sign-in; on later sign-ins the app reads it from the signed identity token Apple issues, so that it does not lose track of who you are.

The app also generates a device identifier so that a licence can be tied to one device. On Android this is the operating system's ANDROID_ID, which is unique to this app's signing key, resets on a factory reset, and is not tied to your hardware. On iOS it is Apple's vendor identifier, kept in the keychain so it survives deleting and reinstalling the app. Neither is a hardware serial number, a phone number, an advertising identifier or a MAC address — the app never reads any of those.

3. What stays on your device

All of the following is stored in the app's private storage on your device and is never uploaded to us:

• Your audio and video files, imported into the app
• Playlists and every per-track setting — volume, fades, trim, delay, loop, speed, colour tag
• Album artwork, whether you chose it or generated it
• Voice keyword rules, global and per-track
• App settings — theme, language, engine choice, show timer
• Your own AI provider API key, if you chose to enter one

A backup you create is a single file written to a location you choose. It is yours: we never receive it, and it goes wherever you put it.

4. What leaves the device, and when

The first two happen automatically every time you open the app. The rest happen only when you take the action that triggers them.

• Licence check — on every launch Sent to our licensing backend at cmx-ops.cobramagic.com/api What is sent: your email address, your access code, the device identifier, and which platform and app version you are running. What is stored: that record, plus when the code was activated, its plan and its validity period. Purpose: to confirm your licence is valid and to keep one code tied to one device.
• Access and credit check — on every launch Sent to our AI server at omsplayer.com/oms-ai/api.php What is sent: your email address, your access code or subscription identifier, and the device identifier. What comes back: whether you are on the free trial, subscribed or expired, how many days of the trial are left, and how much of your usage allowance you have spent. This is also what tells the app whether your trial has ended.
• AI requests — smart edit, album art, music generation Sent to our AI server, which forwards them to the provider omsplayer.com/oms-ai/api.php These do NOT go directly from your device to OpenAI or Anthropic. They go to our server, which holds the provider keys, checks your licence, meters your usage and then forwards the request on our account. What is sent: the instruction you typed and the playlist details needed to carry it out — track names and their settings — together with your email address, access code and device identifier. Our server sees the request; the provider receives the content but not your identity. The one exception: if you enter your own API key in Settings, that request bypasses our server entirely and goes straight to the provider.
• YouTube import Sent to our AI server, which forwards to a conversion service omsplayer.com/oms-ai/api.php · youtube.com · i.ytimg.com What is sent: the link you pasted, plus your identifying details as above. The conversion runs through a third-party service on our key, and the video title and thumbnail are fetched from YouTube. Only used when you paste a link.
• Voice transcription, when the Cloud engine is selected Sent to our AI server, which forwards it to OpenAI omsplayer.com/oms-ai/api.php · api.openai.com A short audio clip of what you said is transmitted for transcription, together with your email address, access code and device identifier. See the microphone section below — this applies to one engine only, and only on Android.
• Usage events Sent to our licensing backend at cmx-ops.cobramagic.com/api/activity Described in full in the Usage logging section below.
• App configuration and updates omsplayer.com · huggingface.co The app downloads its own settings files, the knowledge text that lets the assistant answer questions about the app, and web updates that arrive without a store release. On Android, choosing an offline voice engine downloads its speech model once. These are downloads only — no information about you is sent with them.

Like any web server, our hosts record standard technical log entries such as an IP address and a timestamp when your device contacts them. These logs are used for security and troubleshooting only.

5. Microphone and voice recognition

The microphone is used for one purpose only: to run the voice commands you defined, and only while voice control is actively listening. It pauses by itself when you leave the app and resumes when you come back. Audio is never recorded to a file and is never stored after it has been processed.

On iPhone and iPad

Voice recognition uses Apple's own recogniser, built into iOS — the same engine behind dictation. Nothing is sent to us. What Apple does with the audio is governed by Apple's privacy policy and by your device settings.

On Android — it depends on the engine you pick

• Fast and Accurate are offline engines. They run a speech model downloaded once to your device, and the audio is processed entirely on the device. Nothing is transmitted.
• Cloud transmits. A short audio clip of what you said is sent to OpenAI's transcription service — through our server, which attaches your email address, access code and device identifier in order to meter the request. This is the most accurate engine, and it is the one selected by default.

If you want voice control that transmits nothing at all, choose Fast or Accurate in Settings. Note that this changes the default behaviour.

6. Usage logging

The app reports what you do inside it to our licensing backend, so that support can see what happened on an account when something goes wrong, and so we can tell which features are actually used. This is our own logging — nothing in it is shared with advertisers or data brokers. The one third-party measurement service we use, for install attribution only, is described at the end of this section.

What is reported:

• Which screens you opened, and the visible label of any button or link you tapped.
• When playback started, and which track was played.
• When you change a track's settings: the track's name, together with the values you set — volume, loop, auto play, delay, trim and fades.
• When you sign in, and the sign-in method used.
• A contact email address, if you type one in Settings — so that support can reach you when your sign-in address is an Apple relay.
• The text of questions you type to the AI assistant, truncated to 200 characters. The assistant's answers are never stored. This is used to turn the most common requests into the suggested question chips shown in the app.

Each event carries your email address, access code, device identifier, platform and app version. Nothing is reported until there is an email address or an access code to attribute it to.

What is not reported: the contents of your audio or video files, your artwork, your voice rules, or your playlists as such. Track names reach us only through the playback and track-settings events listed above.

Campaign measurement. To know which campaign brought an install, the app uses AppsFlyer, a third-party measurement provider. AppsFlyer receives a device identifier, broad usage events — opening the app, importing tracks, starting a show, purchasing a subscription — and where the install came from. It does not receive track names, your content or your email address. On iOS the app does not ask for tracking permission (ATT), so there is no tracking across other apps. AppsFlyer holds this data under its own privacy policy: appsflyer.com/legal/privacy-policy

7. Payments and subscription

Subscriptions are purchased and billed through Google Play or the Apple App Store. Those stores handle the entire transaction. We never see or store your card number or billing details.

Subscription status is managed for us by RevenueCat, a third-party subscription service. So that a subscription follows you rather than a handset, the app identifies you to RevenueCat by your email address, and also sends your display name. Our server then asks RevenueCat directly whether your subscription is active — which is why a subscription cannot be faked by a modified app. RevenueCat holds this data under its own privacy policy.

During the free trial, and on any plan with a usage allowance, our server keeps a running total of what your account has spent on AI features, counted against your email address and your device identifier. That total is what the credit meter in the app shows.

9. Retention and deletion

Your account record — the email address, the access code, the device identifier and the dates — is kept for as long as the account is in use, and for a reasonable period afterwards for support and abuse prevention. Usage events and the credit ledger are kept for the same purposes. You can ask us to delete all of it at any time using the contact address below.

Everything else is on your device, so you control it directly: deleting the app removes your playlists, audio, video, artwork, rules and settings from that device. Keep a backup first if you want to keep them.

10. Your rights

You may ask what information we hold about your account, ask for it to be corrected, ask for a copy of it, or ask for it to be deleted. Write to us from the email address you signed in with, so that we can locate the record and be sure it is yours.

Deleting your account data ends your licence and your usage history. A subscription bought through Google Play or the App Store is cancelled in that store, not by us.

For data that reaches Google, Apple, RevenueCat, OpenAI, Anthropic or YouTube, those companies are the ones holding it, and their own policies and processes apply.

11. Children

OMS Player is a professional tool for live performance and is not directed at children. We do not knowingly collect information from children.

12. Changes and contact

If this policy changes, the date at the top of the page changes with it. Material changes will be announced on this page.

Questions about privacy, or to request your data: support@omsplayer.com