Privacy Policy

This policy is issued by Turbo Ventura (“we”, “us”), a company established in Dubai, United Arab Emirates. It covers this website at turboventura.com and the correspondence you have with us.

Each app we publish has a policy of its own, because each one carries its own set of third-party components and changes on its own schedule:

• MP3 Converter — convert, edit and keep your own audio

The policy linked from an app’s App Store listing is the one that governs that app. For anything here, write to [email protected].

The detail belongs in each app’s own policy, but the shape is the same across all of them, and it is the reason the studio exists: the work happens on your device. We run no service you log into, we receive no files, and there is no account by which you could be identified to us. What an app does send — anonymous usage events, crash diagnostics, an advertising request in a free version — is named in full in its own policy, together with who receives it and how to switch it off.

The site is static files. There is no login, no form and no database, and nothing you do here is stored against you.

Like every web server, the host that serves it writes a standard access log entry per request: IP address, time, the address requested, the referring page and the browser’s user-agent string. Those logs exist so that faults and abuse can be investigated, they are kept for a short period by the host, and they are not used to profile a visitor. The lawful basis is our legitimate interest in running a site that stays up and is not attacked.

Nothing else is fetched from anybody: no third-party fonts, no embeds, no social pixels. The two typefaces are served from this domain for exactly that reason.

We use Google Analytics 4 to count visits — and only if you allow it. Until you press the button on the banner, nothing is requested from Google, no script of theirs runs, and no cookie of theirs exists. Declining is one press of the button beside it, and either answer is remembered for a year so you are not asked again.

When it is allowed, Google Analytics records the pages you open on this site, roughly where in the world the request came from, which site or search sent you, and what kind of device and browser you are using. It also records three things we ask it for, each of them a press and nothing more:

• which “Download on the App Store” button was pressed, and on which page;
• which email address was pressed, and from where;
• which question on a support or app page was opened.

None of it is tied to a name, an account or a profile, and advertising features are switched off — so this data cannot become an advertising audience.

The cookies involved

• tv_consent — your answer to the analytics question, and which version of the question it answered. Without it we would have to ask on every page. Set by us, kept for a year.
• _ga and _ga_* — set by Google Analytics, and only after you allow it. They give this browser a random identifier so that two visits can be counted as one visitor. Google sets these to expire after two years.
• __cf_bm and similar — a short-lived security cookie the network in front of the site may set to tell a browser from a bot. Strictly necessary, not ours to read, and described in section 5.

You can change your mind at any time: Analytics choice in the footer reopens the question. Deleting this site’s cookies in your browser has the same effect, and the question will be asked again on your next visit.

The site is served by a web host, and requests to it may pass through a content delivery network (currently Cloudflare) which sits in front of the origin to serve pages from a location near you and to absorb attacks. Both act as our processors.

To do that work the CDN sees the same request metadata the server does — your IP address, the address requested, the browser you are using — and it may set a strictly necessary security cookie such as __cf_bm to tell a browser apart from a bot. That cookie stores no identity, is never read for analytics or advertising, and under the ePrivacy rules it needs no consent because the site cannot be protected without it. It expires within the hour.

Nothing about it is under our control beyond switching it on; Cloudflare’s own privacy policy governs what it does with what it sees.

If you email us we receive what you chose to send: your address, your message, and whatever you attach — usually a version number and a description of what went wrong. We use it to answer you and to fix the thing you found, and for nothing else.

Correspondence is kept while the conversation is live and for a reasonable period after, in case the same question comes back. Ask us to delete it and we will.

This site and our apps are general-purpose and are not directed at children under 13, or the equivalent minimum age where you live. We do not knowingly collect personal data from them, and we hold no account data by which a child could be identified. If you believe a child has sent us personal information, write to [email protected] and we will delete it.

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. These rights arise under the GDPR in the EEA and the UK, the KVKK in Türkiye, the CCPA/CPRA in California, and the UAE Personal Data Protection Law (Federal Decree-Law No. 45 of 2021) where we are established.

We do not sell personal data and we build no profiles of individuals. To exercise a right, write to [email protected] and say which right you are exercising. Because there is no account, what we hold is usually nothing more than an email thread — that is a consequence of collecting so little, not a refusal.

We are established in Dubai, United Arab Emirates. Our web host, the CDN in front of it, our email provider and — where it is switched on — Google Analytics operate globally and may process data outside your country, including in the United States, under the transfer mechanisms set out in their own policies, such as the EU Standard Contractual Clauses.

The strongest measure here is structural: data we never receive cannot be leaked by us. Beyond that, this site is served over HTTPS and consists of static files — there is no database behind it to breach, and no account of yours inside one.

When this policy changes materially — a new processor, a new category of data — the date at the top changes with it. A change to what an app collects is announced in that app’s own policy, and its App Store privacy labels are updated to match.

Privacy questions and data requests: [email protected]
Legal notices and copyright matters: [email protected]
Help with an app: [email protected]

Turbo Ventura
Dubai, United Arab Emirates