Last updated: 17 September 2026
Philipp Schröter
Lahmertstr. 25
12527 Berlin
Germany
info@visomea.com
TuneLink has no user account, shows no advertising and includes no analytics libraries. The app collects no personal data about you as a person.
What it does process is the music link you give it. To turn that into the matching link on your service, the link has to leave your device. That is the core of what the app does and cannot be avoided.
In a private settings file that no other program can read:
None of this is transmitted. The history can be cleared entry by entry or all at once; uninstalling the app removes everything.
Sent to the lookup proxy:
DE), so that regionally available links are foundThe proxy is a service run by the operator of this app at Cloudflare. From there it queries Odesli (Songlink) and, where needed, Musicfetch, and caches successful answers for up to 30 days so that the same link need not be requested again. The cache holds the link and the answer, nothing about the device.
No device characteristic, identifier or IP address is stored deliberately. As with any internet connection, the servers involved necessarily see the connection’s IP address.
TuneLink fetches the shared page directly in order to read title and artist from its Open Graph tags. This creates an ordinary connection from your device to the provider in question — Spotify, Apple Music, SoundCloud or YouTube, for instance. Those providers’ own privacy policies apply.
This connection happens even if you never open the link in the end.
Only if you explicitly tap “Report” on the card. Nothing happens in the background and nothing without your action.
Sent to the proxy in that case:
Likewise only on explicit input. Sent are the text you wrote, the contact address you optionally provided, and the app’s version number.
The text is free-form. Whatever you write into it is transmitted and stored, so do not put anything there that should not reach the developer.
Reports and requests are kept for up to 90 days and then deleted automatically. They serve solely to find errors in how recordings are matched and to answer requests. Where notifications are configured, the content is additionally sent to Telegram.
The subscription is purchased and billed through Google Play. Payment handling lies entirely with Google; the app receives neither payment details nor your identity. It merely asks Google Play whether a valid subscription exists for this device and checks that answer for authenticity. There is no account with us for this.
| Recipient | Purpose |
|---|---|
| Cloudflare, Inc. | Running the lookup proxy and this website |
| Odesli / Song.link | Matching recordings |
| Musicfetch | Matching recordings |
| Google Ireland Ltd. | Distribution and billing via Google Play |
| Telegram | Notification of reports and requests |
| The music service in question | Fetching the shared page |
Some of these providers process data outside the European Union.
The app requests two permissions:
No access to location, contacts, photos, microphone, camera or files. The app reads the icons of installed music apps in order to show them in the picker; no data is transmitted in doing so.
Processing the shared link serves the purpose you pursue by using the app — Art. 6(1)(b) GDPR. Reports and support requests happen on your explicit action and serve the legitimate interest in improving the app and answering your request — Art. 6(1)(f) GDPR.
Because no personal data is stored in a way that is linked to you as a person, individual requests generally cannot be attributed. You nonetheless have the rights to information, rectification, erasure, restriction, portability and objection under Art. 15 to 21 GDPR, as well as the right to lodge a complaint with a supervisory authority.
This site is hosted at Cloudflare. It sets no cookies, loads no third-party fonts or scripts and performs no analytics. Fetching it produces the technical connection data that any website request produces.
The app is not directed at children under 13 and does not knowingly collect data from them.
Changes to this policy are published here; the date above shows the current version.