Privacy Policy for the Sonvel app

This policy applies to the Android app Sonvel by Entevion Labs. This website is covered by the website privacy policy.

Controller

The controller is the provider named in the legal notice. For privacy questions: contact@entevion.com

Your content stays on your device

Sonvel processes recordings, imported audio files and entered lyrics exclusively locally on your device. This content is not transferred to us or to third parties unless you share or export it yourself or send it to another phone via Wi-Fi (see "Sending songs to another phone via Wi-Fi"). We have no access to it at any time.

The processing itself also takes place entirely on the device: separating vocals from accompaniment, aligning the lyrics in time, the style analysis, the voice swap and the sound editing. Voice profiles that the app derives from your voice are also created and kept on the device. The same applies to the names of other players that you create in the app: they are only stored on your device and only appear outside it on a result image that you share yourself. If you share a mix, it may also contain the voices of other players. The data remains on the device until you delete it yourself; uninstalling the app also removes it. This does not apply to files you export from the app yourself — for example mixes that the app saves in your device's music folder; they remain there until you delete them. No transfer takes place as part of Android backup or when moving to a new device, as the app disables backup and excludes all of its data from it.

Microphone

The app needs access to the microphone for recordings. You grant this access yourself and can revoke it at any time in the Android settings. The microphone is only active while you are using a function that needs it and that you started yourself — for example a recording, an exercise or a measurement of your vocal range. Recordings are stored in the app's protected storage area.

Bluetooth audio devices

So that the app can set the right latency for Bluetooth headphones and speakers, it asks for permission to access paired Bluetooth devices — only once you switch on this function in the settings. With it, the app reads the type and name of paired audio devices. The device names are only stored on your device and are not transferred.

Model files: downloading and checking for new versions

To make processing on the device possible, the app downloads model files. It also checks whether newer versions of these models are available. Apart from the advertising SDK and the diagnostic reports of the Google Play billing library (both see below), these are the only cases in which the app connects to the internet on its own. In addition, at your request, it connects to another phone to transfer songs (see "Sending songs to another phone via Wi-Fi").

The check for new versions runs on its own at most once a day — in the background or when you open the settings or the model management; if it fails, the app tries again on the next of these occasions. In addition, it checks every time you start the check manually there or switch on the toggle. It fetches a small file that only contains information about the models — version numbers, sizes, checksums and download addresses; no content from the app is transmitted. A new model is never downloaded on its own — that is your decision. The check is switched on initially. You can switch it off in the app under "Settings → About → Storage & data → AI models" with the "Check for model updates" toggle; the app then remains fully usable and simply no longer learns about new model versions.

In both cases, the recipient and processor is Cloudflare, Inc., San Francisco, USA, via the Cloudflare R2 object storage. Only what is technically necessary to fetch a file is transmitted: your IP address, the time of the request, the name of the requested file and the technical information Android sends with every request (Android version, device model and system build ID). No content from the app is transmitted. The model files themselves are generally available models and contain no data about you.

Object-level access logs are disabled for this storage. Delivery takes place via Cloudflare's network, which keeps its own logs for operation and security. According to Cloudflare, how long it keeps these logs depends on the respective purpose and legal obligations; Cloudflare does not state a fixed period.

The legal basis is Article 6(1)(b) GDPR: providing the function for which you use the app. As Cloudflare is based in the USA, this constitutes a transfer to a third country. It takes place on the basis of the EU Standard Contractual Clauses included in the data processing agreement with Cloudflare.

Sending songs to another phone via Wi-Fi

You can send songs directly to another phone with Sonvel. The transfer is intended for the Wi-Fi network both phones are on and runs directly between the two phones — without servers of ours or of third parties. We receive nothing from it. It only takes place when you open sending or receiving yourself, and ends when you close or cancel it. Until then, sending also remains active in the background, indicated by a notification; if you close the app while a song is being transferred, that song is still sent to the end. The app does not need any permission that it asks you for.

What all devices on the Wi-Fi network see. While sending is open, the app makes your phone discoverable on the Wi-Fi network. All devices on the same network receive: your display name, the version of the transfer protocol, your phone's IP address in the local network and the number of the port on which it accepts connections, as well as a network device name that Android assigns itself. You choose the display name yourself before you send or receive for the first time and can change it later; if you skip this, "Sonvel user" appears. It is only stored on your device. The receiving phone searches the Wi-Fi network for sending phones while receiving is open and not yet connected; it does not make itself discoverable.

Joining with a PIN or QR code. Another phone can only connect with the four-digit PIN shown on the sending phone, and only one at a time. After five wrong attempts, the sending phone generates a new PIN and rejects every attempt for a while. Instead of entering the PIN, the receiver can scan a QR code on the sending phone. It contains the sender's IP address, port, PIN and display name; anyone who scans it can read the PIN in it. It is read by the camera app of the receiving phone, which then opens Sonvel; Sonvel itself does not use the camera. If you open such a join link or enter an address manually, the app connects to the address it contains and sends it your display name and the PIN. Only open join links from a phone that is in front of you.

What is transferred between the two phones. When connecting, the receiving phone sends its display name, the PIN and the version of its transfer protocol. If the PIN is wrong, the sending phone only rejects the attempt and neither shows nor stores any of it. If the PIN is correct, it replies with its display name and a list of the songs on offer — title, artist, size, where applicable the estimated size of a compact version, and whether a song is archived. The receiver then makes a selection. The selected songs are then sent to the other phone as they would be saved when exported to a file, including audio files — also self-recorded tracks and the original file names of imported audio files —, lyrics, timing, title, artist, genre, style analysis, pitch template and the song's exercises and playlists. Karaoke recordings, scores and voice profiles are not transferred. At the request of either side, a song can be sent compact: then only the tracks needed for singing, compressed and read-only on the receiving phone. The receiving phone creates the songs as its own songs and reports back for each song whether it was added or why it failed — for example due to lack of storage space or because the free slots of the free version are used up. This last report shows the sender that the receiver does not have Sonvel Premium.

No encryption. The transfer is not encrypted. It is protected by the PIN and intended for the local Wi-Fi network. Anyone on the same network who intercepts the traffic can see the PIN, display names, song titles and the songs themselves. Only send on a Wi-Fi network you trust.

The legal basis is Article 6(1)(b) GDPR: providing the transfer that you trigger yourself. What happens to the songs on the other phone is up to the person you send them to.

Advertising in the free version

The free version of Sonvel shows advertising. For this we use Google AdMob, a service of Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. Google is independently responsible for processing your data in connection with advertising. Google's privacy policy applies (policies.google.com/privacy); Google explains how it uses data from apps that use its services at policies.google.com/technologies/partner-sites.

Advertising appears only in these places: as a full-screen ad when opening the post-processing of a saved result, and as an optional rewarded ad with which you unlock the word editor for one song permanently, one run of the advanced separation of vocals and accompaniment, or switching to a Premium stage; each further song and each further switch to a Premium stage costs a separate ad. Which songs are unlocked for the word editor is only stored on your device. There are no banner ads. Without an internet connection, no advertising is shown; the word editor, post-processing and Premium stages then remain freely usable. The trial run of the advanced separation needs a connection because it is tied to an ad. In Sonvel Premium, the app shows no advertising. Once it knows about your purchase, it also does not ask for advertising consent and does not start the advertising SDK. After reinstalling the app or on a new device, it can happen on the first start that the app still shows the consent dialog and starts the advertising SDK before Google Play has confirmed the purchase; even then, it shows no advertising.

Consent. Where required by law, in particular in the European Economic Area, the United Kingdom and Switzerland, the app asks for your consent via Google's User Messaging Platform. To do so, the app queries the status of your advertising consent from Google every time it is opened; your decision is stored on your device. If you consent, Google can tailor advertising to you. If you decline, you receive non-personalized or limited advertising, and all functions remain usable. You can change or withdraw your decision at any time with effect for the future: in the app under "Settings → About → Ad consent". This setting appears where consent is required.

Which data goes to Google. Before your decision in the consent dialog, the app only asks Google whether such a dialog is needed and loads it; the advertising SDK itself only starts afterwards, and not once the app knows about your Premium purchase. Independently of advertising, the Google Play billing library generates technical diagnostic reports every time the app starts or is brought back to the foreground and sends them to Google, even before your decision and in Premium (see "Premium purchase via Google Play"). When advertising is loaded or shown, Google processes in particular your IP address, from which an approximate location can be derived, your device's advertising ID and app set ID, and where applicable identifiers of your signed-in Google account, information about your interactions with the advertising and the app, such as app launches, taps and video views, as well as diagnostic data on how the advertising service is working. Google uses this data to deliver and measure advertising, for analytics and to prevent fraud. The transfer is encrypted. Your recordings, audio files, lyrics and projects are not transmitted. You can reset or delete the advertising ID in the Android settings. How long Google stores this data depends on Google's privacy policy.

The legal basis for advertising that uses information on your device — personalized advertising as well as non-personalized advertising, for which Google uses identifiers to limit how often ads are shown and for aggregated reporting — is your consent under Article 6(1)(a) GDPR and § 25(1) TDDDG. If you decline, Google shows limited advertising without identifiers on your device; this is based on our legitimate interest in financing the free version through advertising, under Article 6(1)(f) GDPR.

Google may also transfer data to Google LLC in the USA. Google LLC is certified under the EU-US Data Privacy Framework, for which an adequacy decision of the European Commission exists; in addition, Google bases transfers on EU Standard Contractual Clauses.

No analytics, no crash reports

Apart from advertising and the diagnostic reports of the Google Play billing library, the app contains no analytics or tracking tools and no crash reporting. We ourselves do not create usage profiles.

Obtaining the app via Google Play

The app is obtained via Google Play. Google, not we, is responsible for the processing involved — for example your Google account, installation data and payment transactions. Google's privacy policy applies.

Premium purchase via Google Play

You buy Sonvel Premium as a one-time purchase via Google Play. Purchase and payment are handled exclusively by Google; Google is responsible for the processing involved, for example your payment details and the purchase history in your Google account. Sonvel has no account of its own and no server of its own for purchases. We do not receive your payment details. For your purchase, Google Play passes technical information such as the order number and purchase receipt to the app; the app only uses it to check and confirm the purchase, does not store it and does not pass it on to anyone other than Google Play.

The app asks Google Play whether you have bought Premium — every time you open it or bring it to the foreground. The query runs via the Google Play app on your device and relates to the Google account signed in there. This way, a purchase is available again after reinstalling the app or on a new device, provided the same account is signed in there. The app confirms a new purchase to Google Play. Of all this, the app only stores on your device whether Premium has been bought — yes or no; it does not store the order number, purchase receipt or payment details. The legal basis is Article 6(1)(b) GDPR: providing Premium.

As the provider, we can view the orders for Sonvel in Google's Play Console — with the order number, the email address of your Google account, the purchased item, price, taxes and fees, and the order history — and issue refunds there. We only use this information to handle requests about your purchase, such as a refund. The legal basis is Article 6(1)(b) GDPR.

Diagnostic reports from the billing library. For purchases, the app uses Google's Play Billing Library. This library logs its own operations — such as connecting to Google Play and the result of the purchase query. Such reports are generated every time the app starts or is brought back to the foreground, even before your decision in the consent dialog and also in Sonvel Premium. The library transmits them to Google in batches and with a delay (firebaselogging.googleapis.com), possibly also when the app has already been closed. The reports contain, among other things, the library version, the app's package name and version, your device's manufacturer, model and system identifier (build fingerprint), the Android version, country, language setting and time zone, the identifier of your mobile network operator (country and network code) and the type of network connection, the result of the purchase query with error code and error text, and a session number that is newly generated every time the app starts. Google determines exactly which information is included; this may change with new versions of the library. When the reports are transmitted, Google also sees your IP address. According to our review, the reports contain no advertising ID, no permanent device or account identifier and no content from the app. We have not yet been able to check whether they additionally contain information about a purchase when one is made. Until transmission, the library stores the reports on your device — without an internet connection for about a week at most, after which it deletes them. This cannot be switched off in the app.

According to Google, it uses the reports to improve the billing library and to provide better support for errors; Google is independently responsible for this. The legal basis is our legitimate interest under Article 6(1)(f) GDPR in offering purchases via the route Google provides, of which these reports are a fixed part. We base storing the reports on your device on § 25(2) no. 2 TDDDG, as the purchase function cannot be offered without this library. Here too, Google may transfer data to Google LLC in the USA; what is stated in the section on advertising applies. How long Google stores the reports depends on Google's privacy policy.

Your rights

You have the right of access, rectification, erasure and restriction of processing, the right to data portability, and the right to object to processing. To exercise these rights, contact contact@entevion.com.

Right to object. Insofar as we process data on the basis of our legitimate interest (Article 6(1)(f) GDPR), you can object to this at any time on grounds relating to your particular situation (Article 21 GDPR). To do so, contact contact@entevion.com.

As we do not receive any content from the app, we cannot provide information about it — it is stored exclusively on your device and remains under your control there.

For processing in connection with advertising and purchases via Google Play, you can also exercise your rights directly with Google.

You also have the right to lodge a complaint with a data protection supervisory authority. The authority responsible for us is the Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen (State Commissioner for Data Protection and Freedom of Information of North Rhine-Westphalia), Kavalleriestr. 2–4, 40213 Düsseldorf, Germany, poststelle@ldi.nrw.de, ldi.nrw.de.

You are under no legal or contractual obligation to provide us with data. We do not engage in automated decision-making, including profiling.

Last updated

Last updated: October 2026