Turbo Music Privacy Policy
A music player learns a lot about you — what you play, when, and how often. This page says exactly what Turbo Music keeps to itself, what it asks other services, and who else is involved.
- Last updated
- 14 October 2026
- Issued by
- Turbo Ventura, Dubai, United Arab Emirates
- Applies to
- Turbo Music: Offline Player for iPhone, iPad, Mac and Apple Watch
In short
- Your library and listening history stay on the device.
- No account and no sign-in. Our server knows this device by a random ID, never by name.
- Lyrics are made on the device; songs are never uploaded.
- Usage and crash events go to Firebase, with no titles or file names.
- Notifications and support replies come from our own server, which never receives your music or what you play.
- The free version carries advertising from AdMob and its mediation partners; Premium removes it.
- Sync runs through your own iCloud; purchases through Apple.
- A recovery code is mailed only when you ask, and only to you.
A summary, not the agreement. The sections below are what applies.
01 What this policy covers
This policy covers Turbo Music: Offline Player for iPhone, iPad, Mac and Apple Watch, published by Turbo Ventura of Dubai, United Arab Emirates. It is the policy referenced by the app’s App Store listing.
The company and this website are covered by our general privacy policy; where the two overlap, this page is the more specific and it governs the app.
For anything here, write to [email protected].
02 Your library stays on your device
Turbo Music plays files you bring in yourself, and it keeps what it knows about them on the device. There is no account to sign in to, and no server of ours ever receives your music. The following never reaches us; nothing in the app sends it, unless you choose to write it or attach it in a support conversation (section 11):
- Your music, videos, podcast downloads and anything else you import.
- File names, folders, tags, covers and the lyrics you save or edit.
- Your playlists, favourites, play counts, listening history and statistics.
- What you type into the app — searches, server addresses and passwords, and the Wi-Fi Transfer PIN.
The library is a database inside the app’s own container. Passwords and sign-in tokens are held in the iOS Keychain. Deleting the app removes the container and everything in it; the Files app folder of your music goes with it unless you moved it elsewhere.
03 Usage analytics and crash reports
To understand which parts of the app are used and where it fails, Turbo Music sends usage events through Google Analytics for Firebase, and crash diagnostics through Firebase Crashlytics. Google acts as our processor for both.
What is sent
- That the app was launched and that you came back to it, which screens are used, and feature events carrying only counts and kinds — that an import finished and how many files it brought, which source was used, that a sleep timer was set, and a coarse reason when something failed.
- Device model, OS version, app version, language and country, plus a pseudonymous app-instance identifier generated by Firebase.
- For a crash: the stack trace, the app state at that moment, and the same device fields.
Purchases are not reported to Firebase; what is reported, and where, is in section 5.
What is never sent
No song titles, artists, file names, folder paths, station or podcast names, addresses, or anything you have typed. We never call Firebase’s user-identifier API, so events cannot be tied to a person. There is no switch in the app to turn analytics or crash reports off.
04 Advertising in the free version
The free version can show advertising supplied by Google AdMob, and by the mediation partners AdMob may pass a request to when it does not fill an ad itself: AppLovin, Pangle, Liftoff Monetize, DT Exchange and InMobi. Each is an independent controller of the data it receives, under its own policy:
No ad plays over your music, none appears in the full-screen player, during setup or on the purchase screen, and Premium removes advertising entirely.
To request, show and measure an ad, these SDKs may process your device’s advertising identifier (IDFA, only if you allow it), the IDFV, IP address, device and operating-system information, a coarse location derived from that IP address, and your interaction with the ad. Nothing from your library is ever part of an ad request. If you allow tracking, the advertising identifier also goes to our own server with the installation record (section 10).
- App Tracking Transparency. The advertising identifier can be used only if you have allowed tracking when iOS asks; until then it is not available to the app or to the ad partners above. You can change the answer in Settings › Privacy & Security › Tracking.
- Consent in the EEA, the UK and Switzerland. Where the law requires consent for personalised advertising, the ads SDK follows the consent recorded through Google’s consent framework (UMP) and passes it to the partners above; without that consent, no personalised advertising is shown.
05 Purchases and subscriptions
Premium is sold through Apple’s In-App Purchase system using StoreKit. Apple takes the payment and holds the payment details; we never see your card, your billing address or your Apple Account credentials. The app keeps only the entitlement on the device, checked against Apple’s service. Refunds are handled by Apple at reportaproblem.apple.com.
When a purchase moves money — a new subscription or lifetime unlock, a free trial starting, a renewal, or a refund — the app reports it to our own server (section 10): the product, its price and currency, Apple’s transaction number, and whether it was a real or a test purchase, together with this installation’s device ID. Restoring a purchase, reinstalling and Family Sharing are not reported. A report waits, encrypted on the device, until the app is unlocked and online. It is how our records know an installation has Premium, and it carries nothing that names you.
06 App lock and recovery code by e-mail
If you lock the app, the passcode check is held in the iOS Keychain on the device and never leaves it. If you add a rescue e-mail address and then ask for your recovery code to be mailed, the app sends that address and the recovery code over HTTPS to our mail relay, which uses them only to deliver that one message. Nothing else about you or your library is sent. If you never ask for a mail, nothing is sent at all — adding an address only stores it on your device.
The link in that mail opens the app. The code travels in the part of the link a browser never sends to a server, so it does not reach this website either.
07 Services the app looks things up with
A few features need to ask a public service a question. Each request goes from your device straight to that service, carries only what the question needs, and is answered under that service’s own privacy policy. Like any request, it shows the service your IP address.
- Lyrics — LRCLIB is sent the title, artist, album and length of the song whose lyrics you open.
- Tags and covers — Apple’s iTunes Search, MusicBrainz and the Cover Art Archive are sent the title, artist and album you look up, only when you ask.
- Podcasts — Apple Podcasts, Podcast Index and fyyd are sent your search terms; the feeds you subscribe to are fetched from their publishers, who see the request like any podcast app’s.
- Radio — the radio-browser directory is sent your searches and filters; a station you play streams from its own server.
- The lyrics model is downloaded once, after you agree, from our content server; the request carries nothing about you or your music. The songs themselves are separated and recognised on the device, using Apple’s on-device speech recognition — audio is never sent to a server, and a language with no on-device model is refused rather than uploaded.
08 Accounts and servers you connect
In every case the connection goes from your device straight to the service you chose — it does not pass through us, and we receive no copy of anything.
- Cloud accounts (Google Drive, Dropbox, Yandex Disk): you sign in with the provider’s own screen, and the token it hands the app is stored in the Keychain.
- Your own server (SMB, WebDAV, Nextcloud, FTP, SFTP, S3) and media servers (Jellyfin, Emby, Plex): the address and credentials you enter are stored in the Keychain and used to talk to that server directly. SFTP remembers the server’s key and refuses a different one.
- DLNA / UPnP devices are discovered and reached on your local network only.
- Last.fm and ListenBrainz, if you connect them, receive the title, artist, album and time of the songs you play — that is what scrobbling is. Disconnect and nothing more is sent.
- iCloud sync of playlists, favourites, subscriptions and play counts is stored in your own private iCloud database. Apple holds it for you; we cannot read it.
- Wi-Fi Transfer and sending to a nearby device run only on your local network or directly between devices, and Wi-Fi Transfer is gated by a PIN.
09 MP3 Converter
When you choose an action MP3 Converter performs — trim, ringtone, convert, repair — the file is placed in a storage area shared only by our own apps on your device, and handed back the same way. Nothing leaves the device. If MP3 Converter is not installed, the App Store page is shown instead.
10 Our own server
Turbo Music talks to one server of ours, app.turbocloud.systems, for what a player cannot do alone: notifications, replies to a support conversation, messages inside the app, telling an old version that an update is needed, and recording a purchase. There is no account on it and nothing to sign in to. It never receives your music, file names, tags, lyrics, playlists, listening history or anything about what you play.
How the app is known to it
The app creates random identifiers on the device. None is derived from you or your device:
- a device ID, kept in the iOS Keychain. It stays the same if you delete and reinstall the app, and our other apps on the same device use the same one;
- an account ID, which iCloud Keychain, if you use it, carries to your other devices so they are recognised as one owner. It is not your Apple Account and says nothing about who you are;
- an installation ID, new with every install, and a secret that proves later requests come from this installation.
What is sent, and when
- An installation record, each time you open the app, when one of the values below changes, and otherwise at most once a day: the identifiers above; Apple’s identifier for vendor (IDFV); the advertising identifier (IDFA) only if you have allowed tracking, and whether you have; device model, iPhone or iPad, OS version, app version and build, the app’s language and your time zone; the notification token Apple issues for this device and whether notifications are allowed, declined or not yet asked; and, for our other apps that have run on this device, which ones, when each was first and last opened, its version and whether it is still installed.
- App settings — which version is current and which download addresses are blocked. This request carries the app version, language, OS version and device type, and no identifier.
- Messages inside the app — once each time you open it, the app asks whether we have one, sending the device ID, app version, language, OS version and device type. When one is shown, it reports that it was seen, which button you pressed, or that you closed it.
- Notification events — when you tap one of our notifications or one of its buttons, the app reports which. When one arrives, the notification extension reports that it was delivered.
- Purchases — see section 5. Support conversations — see section 11.
Like any server, ours sees the IP address a request comes from and works out from it the country the installation is in. The app never sends your name, e-mail address, phone number, contacts, location or Apple Account.
Notifications
We send two kinds: replies to your support conversations and occasional notices about the app. The app asks for permission only after you send a support message, never when it opens. If you decline, a reply still reaches you silently, as a badge on the app icon. A notification can carry a picture: the notification extension downloads it from the secure address in the notification, without cookies, and the server that hosts it sees your IP address. You can turn notifications off at any time in Settings › Notifications › Turbo Music.
When nothing is sent
- Until our server confirms that this version of the app is one we released and have left switched on. That first question carries only the app version.
- While the app lock is on. What was waiting is sent after you unlock; the only exception is the notification extension, which can report a notification as delivered while the app is locked.
- While you are looking at the demo library.
11 When you write to us
Contact Us opens a conversation inside the app. What you write — the topic you pick, a subject for the first message, your message, and any pictures you choose to attach — goes to our own server (section 10) over HTTPS, and our reply comes back to the same screen. Pictures are chosen with the system photo picker, which gives the app only the ones you pick, and each is re-encoded on the device so its location and other metadata are removed before it is sent. No e-mail address is asked for and the app adds nothing to your message; we read it alongside this installation’s record — device model, OS and app version, language — which is how a reply finds its way back. Opening a reply tells the server you have read it.
When the conversation cannot be offered — no connection the first time the app runs, or this version has been switched off — Contact Us opens your own mail app instead, with the topic and message you wrote, addressed to [email protected]. The app version, OS version, device model and language are added only if you leave that switch on. You send that mail yourself; we receive only what you send.
Nothing about your library is ever added by the app. What you write or attach is yours to choose.
12 Permissions the app asks for
Each request happens only when you use the feature that needs it, and declining one disables that feature and nothing else.
- Photos — to import the videos and audio you pick.
- Media & Apple Music — to read the songs in your Apple Music library and bring in the ones without copy protection. The library is read on the device and never sent anywhere; the app does not change it.
- Speech recognition — to write lyrics on the device.
- Local network — for Wi-Fi Transfer, SMB and DLNA on your own network.
- Bluetooth — to send a playlist to a nearby device.
- Notifications — offered after you send a support message, so a reply can reach you; our notices about the app use the same permission. The question appears only when you tap Turn On. Declining still lets replies arrive silently, as a badge.
- Face ID / Touch ID — only if you add them to the app lock; the match happens inside iOS.
- Tracking — see section 4.
Turbo Music never asks for your location, contacts, calendar, camera or microphone.
13 Retention and deletion
- Files and library data — on your device until you delete them or remove the app; items in the bin are removed after thirty days.
- iCloud sync data — in your iCloud account until you turn sync off and delete it there.
- Analytics and crash events — retained by Google for a bounded period (currently 14 months).
- Advertising data — retained by each ad partner under its own policy.
- Our server — the installation record and your support conversations are kept for as long as needed to provide these features, and purchase records for as long as accounting and tax law requires. Write to us, or use Contact Us, to have them deleted.
14 Children
Turbo Music is a general-purpose player and is not directed at children under 13, or the equivalent minimum age where you live. We do not knowingly collect personal data from them and hold no account data by which a child could be identified.
15 Your rights
Depending on where you live you may have the right to access, correct or delete personal data we hold about you, to restrict or object to its processing, to withdraw a consent you gave, and to complain to your supervisory authority — under the GDPR (EEA and UK), the KVKK (Türkiye), the CCPA/CPRA (California) and the UAE Personal Data Protection Law, among others.
We do not sell personal data. The installation record on our server (section 10) is used to deliver notifications and support replies, to choose who a notice goes to by app version, language or country, and to count installations.
To exercise a right, write to [email protected], or use Contact Us inside the app: a request sent there arrives attached to this installation’s record. By e-mail alone, with no account, we often cannot match a request to data we can identify as yours — that is a consequence of collecting so little, not a refusal.
16 International transfers
Our own server (section 10), and Google, Apple, the advertising partners in section 4 and the services named in sections 7 and 8, may process data outside your country. The outside services operate globally, including in the United States, under the transfer mechanisms set out in their own policies, such as the EU Standard Contractual Clauses.
17 Changes to this policy
When this policy changes materially — a new processor, a new category of data — the date at the top changes with it and the App Store privacy labels for Turbo Music are updated to match.
18 Contact
Privacy questions and data requests: [email protected]
Help with the app: [email protected]
Legal notices: [email protected]
Turbo Ventura
Dubai, United Arab Emirates