MP3 Converter Privacy Policy
The app has no accounts and never asks who you are. This page says exactly what it sends, what it never sends, and who else is involved.
- Last updated
- 14 October 2026
- Issued by
- Turbo Ventura, Dubai, United Arab Emirates
- Applies to
- MP3 Converter for iPhone and iPad
In short
- Your files stay on the device. We never receive them.
- No account and no sign-in. The app registers a random device identifier with our own service, for notifications, support replies and Premium.
- Notifications come from the device and from us; if you decline them, nothing is shown.
- What you write to support, and any picture you attach, reaches us — nothing else you type does.
- Anonymous usage and crash events go to Firebase; no content is attached.
- The free version carries AdMob advertising; Premium removes it.
- Purchases run through Apple — we learn the plan and price, never payment details.
- Cloud and server sign-ins stay on the device, and are read-only.
A summary, not the agreement. The sections below are what applies.
01 What this policy covers
This policy covers MP3 Converter for iPhone and iPad, 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 What stays on your device
MP3 Converter opens, converts, edits and plays files that are already on your device, and all of that work happens on the device itself. We run no service you log in to, and nothing of ours ever receives your media. The following never reaches us, and there is no mechanism in the app by which it could:
- Your files — everything you import, convert, record or export.
- Your library: playlists, favourites, recents, playback positions, waveforms, artwork and the tags you edit.
- File names, folder paths and the metadata inside any of it.
- Anything you type in the app other than a message to support — the Wi-Fi Transfer passcode, and the address and password of any server you connect.
The one exception is deliberate: a message you write to support, and a picture you choose to attach to it, reach us because you sent them (section 5). What the app does send to our own service is set out in section 3.
Credentials of every kind — cloud tokens, server passwords, the transfer passcode — are held in the iOS Keychain, never in the app database and never in a log. What happens when you connect a service of your own is set out in section 9.
The library index is a database inside the app’s own container, encrypted with a key held in the device Keychain, and it is deliberately not exposed to other apps through the Files app. Deleting the app removes the container and everything in it — except the two random identifiers described in section 3, which iOS keeps in the Keychain.
03 What the app sends to us
The app talks to one service of ours, at app.turbocloud.systems, which every Turbo Ventura app shares. It is how notifications and support replies reach the app, how the app learns its settings and whether it must be updated, and how we know that Premium was bought. It receives no file, no file name and nothing from your library.
The device record
When the app is opened, and again when it comes back after half a minute or more away, it sends a record of this installation:
- A device identifier — a random number the app generates the first time it runs, derived from nothing about you or the hardware. It is kept in the iOS Keychain, so it survives deleting and reinstalling the app, and our other apps on the same device use the same one.
- An account identifier — a second random number, kept in iCloud Keychain, so it is the same on your other devices where iCloud Keychain is on. It tells us that two devices belong to the same person, never who that person is.
- An identifier for this installation, which changes each time the app is installed, and a secret the app generates so that only it can update its own record.
- Apple’s vendor identifier (IDFV) and, only if you allowed tracking when iOS asked, the advertising identifier (IDFA). Your answer to that question is sent either way.
- The device model (such as “iPhone15,2”), the iOS or iPadOS version, phone or tablet, the app version and build, the language the app is set to, and the time zone.
- The notification token Apple issues to the app, and whether you allowed notifications (section 4).
- Which of our other apps have been opened on this device, with their versions, when each was first and last seen, and whether each is still installed.
Like any server, ours sees the IP address a request comes from, and it works out from it the country the installation is in. It sends the country back, and the app keeps it for the footer of a support email.
The record never contains your name, email address or phone number, and not the name you gave the device — the app sends the model, never the name.
The other requests
- Whether this version may use the service — the app’s name, version and a release code, nothing about the device. Until it is answered, nothing else is sent.
- Settings — every few minutes while the app is in use: advertising placements, whether an update is required, sites the downloader must refuse, and which of our apps to suggest. The request carries the app version, language, iOS version and phone or tablet, and no identifier.
- In-app messages — once each time the app is opened, with the device identifier (section 4).
- Unread support replies — a count, checked when the app opens or comes back, with the device identifier.
- Support messages and purchase reports — sections 5 and 8.
What it is used for
The record is how we deliver notifications and support replies, choose who a notice goes to — people on a given version or language, people who have not opened the app for a while, people who do not already have the app a notice is about — count installations, and know which of them are Premium. The app does not attach these identifiers to the analytics events in section 6.
There is no switch for it inside the app: without it, notifications and support replies could not reach the device. These requests go out whatever you answered to the tracking and advertising-consent questions; those answers change only whether the advertising identifier is included.
04 Notifications and in-app messages
MP3 Converter shows two kinds of notification:
- From the device itself — that a conversion finished, or was paused, while you were in another app. Nothing about these leaves the device.
- From our service, through Apple’s push notification service — replies to your support conversations and occasional notices about the app. A notice may carry a picture, and buttons that open a screen in the app or a web page.
When you are asked
iOS asks for permission once, the first time you queue a conversion; the support conversation also offers to ask after your first message. The app never gives itself quiet delivery without asking. You can change your answer at any time in Settings › Notifications › MP3 Converter.
Whatever you answer, iOS gives the app a notification token, and the app includes it in the device record. If you declined, nothing is shown to you: the token is used only to tell the app, silently, that support has replied, so it can show the unread count the next time you open it.
What is reported back
When a notice arrives, a small extension of the app attaches its picture and tells us it was delivered. When you tap it, or one of its buttons, the app reports the tap. Swiping it away reports nothing. Each report carries the device identifier, the notice’s identifier and the time — nothing else.
The picture is downloaded from the address the notice names, over HTTPS, without cookies and with no identifier added; the server holding it sees an ordinary image request from your IP address.
In-app messages
Each time the app is opened it asks our service whether there is a message to show, sending the device identifier, app version, language, iOS version and phone or tablet. It shows at most one, and never over the app lock, a purchase screen, the player or an ad. How often each message has been shown is counted on the device. Seeing a message, tapping its button or closing it is reported to us in the same way as a notification tap.
05 Writing to support
Contact Us opens a conversation with us inside the app, and what you send there reaches our service:
- The topic you picked, a subject if you add one, and your message.
- Up to three pictures you choose to attach. You pick them in the system photo picker, which hands the app those pictures and nothing else — never access to your library. Each is re-encoded and reduced in size before it leaves, which removes its metadata, including the place it was taken.
The conversation is tied to the device identifier. That is how our reply finds its way back to this device, and how we see the details in section 3 — model, versions, language, country, whether Premium is active — without having to ask. The app does not ask for your email address.
If the conversation is not available — our service has not answered yet, or the device’s Keychain could not be read — the app opens an email to us in your own mail app instead. Its last lines carry the app version, iOS version, device model, app language, whether Premium is active and the country; you see them before you send, and the email arrives with your address, as any email does.
06 Usage analytics and crash reports
To understand which parts of the app are used and where people get stuck, MP3 Converter sends anonymous usage events through Google Analytics for Firebase, and crash diagnostics through Firebase Crashlytics. Google acts as our processor for both.
What is sent
- Screen views — which screens are opened, and in what order.
- Feature events — that a conversion started and whether it finished, which output format was chosen, that a Studio tool was used, that an import happened, and a coarse reason when something failed.
- Purchase events — which plan was bought or restored, and whether it succeeded.
- Device model, iOS version, app version, language and country, plus a pseudonymous app-instance identifier generated by Firebase on top of Apple’s vendor identifier (IDFV).
- For a crash: the stack trace, the app state at the moment it happened, and the same device fields.
What is never sent
No event carries content of any kind: no file names, no folder paths, no tags, no URLs, and nothing you have typed. We never call Firebase’s user-identifier API, so events cannot be tied to a person or to an account — because there is no account.
Google retains this event data for a bounded period (currently 14 months) and processes it under its own terms. It may derive an approximate location from the IP address of the request; we ask for country-level reporting only and never receive a precise location.
07 Advertising in the free version
The free version shows advertising supplied by Google AdMob, plus the mediation partners AdMob passes a request to when it does not fill an ad itself: AppLovin, Pangle, Liftoff Monetize, DT Exchange and InMobi. Each of these is an independent controller of the data it receives and has its own privacy policy:
This is the set of partners currently enabled in mediation. If one is added or removed, this section changes with it — that is what section 16 means by a new processor. Premium removes advertising entirely.
What advertising means here
- Nothing plays over your media. No ad interrupts playback or a conversion.
- Rewarded clips are opt-in — a video plays only after you tap to start it, to go past a free allowance.
- Ads appear in place, in the space reserved for them on the screen.
Data the ad partners may receive
To request, show and measure an ad, the ad 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. This may be used for ad selection, frequency capping, measurement and fraud prevention.
Your choices
- App Tracking Transparency. iOS asks your permission before the advertising identifier may be used to track you across apps and websites. Decline and ads still appear, but non-personalised. If you allow it, the identifier is also included in the device record the app sends to us (section 3). You can change the answer at any time in Settings › Privacy & Security › Tracking.
- Consent in the EEA, the UK and Switzerland. Where it is required, Google’s consent form (UMP) is shown before personalised advertising is enabled and your choice is passed to the partners above. It can be reopened from the app’s settings.
- Premium removes advertising on every device signed in to the Apple Account that bought it.
08 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.
When a purchase, a renewal or a refund happens, the app reports it to our service: which plan, the price and currency, Apple’s transaction number, and whether it was a real purchase or a test — tied to the device identifier in section 3. That is how our records know which installations are Premium. A restore, a repeat tap on a plan you already own and Family Sharing are not reported, because no money moved. The transaction number does not tell us who you are; only Apple can connect it to an Apple Account.
The app also keeps the entitlement on the device — which plan is active and when it renews — checked against Apple’s service, so a lost purchase is recovered with Restore purchases rather than by asking us.
Refunds are handled by Apple at reportaproblem.apple.com.
09 Services and sources you connect
The app can browse a cloud drive or a server of your own and copy files down from it. In every case the request goes from your device straight to that service — it does not pass through us, and we receive no copy of anything it returns.
- Cloud accounts (Google Drive, Dropbox, Box, Yandex Disk): you sign in with the provider’s own screen. It hands the app a token; we never see your password. The token is stored in the iOS Keychain, keyed to that account, and never in a log or on a download task.
- Read-only by design. We ask for the read-only scope wherever a service offers one, so the app can list and copy but has no permission to change, move or delete anything on your drive.
- Your own server (WebDAV, Nextcloud, ownCloud, SMB): the address, username and password you type are stored in the Keychain and used to talk to that server directly. No developer key and no third party is involved at all.
- What each service sees is the same thing it would see from any other client: your sign-in, the folders you open and the files you ask for, along with your IP address. What it does with that is governed by its own privacy policy.
A download task carries a description of the item — provider, account, file — rather than a link with a credential in it, and the link is re-resolved each time the transfer starts. Signing out removes the account and its token from this device; the files stay where they are, on the service.
10 Permissions the app asks for
iOS asks before the app may reach anything sensitive. Each request happens only when you use the feature that needs it, and declining one disables that feature and nothing else.
- Photos — only when you import a video or audio file from your library, or export one back to it. The app reads the item you picked and nothing else.
- Microphone — only while you are recording in Studio. Recordings are written straight into the app’s own storage.
- Notifications — asked the first time you queue a conversion, so the app can tell you it finished while you are in another app; support replies and notices from us arrive the same way. Declining means nothing is shown. See section 4.
- Local network — so Wi-Fi Transfer can be reached from a browser on your own network, and so an SMB share on that network can be found at all. Both stay between your own devices; nothing about them touches us.
- Tracking — see section 7. Declining does not reduce what the app can do.
MP3 Converter never asks for your location, contacts, calendar or camera.
11 Retention and deletion
- Files and library data — on your device until you delete them or remove the app.
- The device record, notification reports and support conversations — on our service, kept for as long as needed to provide these features.
- Purchase reports — kept for as long as accounting and tax law requires.
- Analytics and crash events — retained by Google for a bounded period, as described in section 6.
- Advertising data — retained by each partner under its own policy.
Deleting the app stops anything further being sent, but iOS keeps the device and account identifiers in the Keychain, so a reinstall — or another of our apps — is recognised as the same device.
Because analytics events are not linked to an identity, we cannot look up “your” events to delete them one by one; you can reset the advertising identifier in iOS settings. The device record is different: it is held against the device identifier, so we can find it. To have it and your support conversations deleted, write to [email protected] — or use Contact Us inside the app, where the request arrives already tied to the device.
12 Children
MP3 Converter is a general-purpose tool 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 the app asks no one for a name, an email address or an age.
13 Your rights
Depending on where you live you may have the right to access the personal data we hold about you, to have it corrected or deleted, 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. To exercise a right, write to [email protected] — or, for the device record and support conversations, use Contact Us in the app, so we know which device the request is about. An email alone gives us nothing to match it against, because there is no account.
14 International transfers
Our own server, Google and the advertising partners named in section 7 may process data outside your country. Google and the partners operate globally, including in the United States, under the transfer mechanisms set out in their own policies, such as the EU Standard Contractual Clauses.
15 Security
The strongest measure here is structural: we never receive your media, your library or your credentials, so we cannot leak them. What does reach our service — the device record, support conversations and purchase reports — travels over HTTPS, and each installation proves itself with a secret only it holds. The library database is encrypted with a key held in the Keychain, and the Wi-Fi Transfer server is passcode-gated, foreground-only, and grants destructive operations only when you enable them explicitly.
16 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 MP3 Converter are updated to match.
17 Contact
Privacy questions and data requests: [email protected]
Help with the app: [email protected]
Legal notices: [email protected]
Turbo Ventura
Dubai, United Arab Emirates