Privacy policy
This policy explains what personal data Dalinq processes when you use the Dalinq app (iOS and Android), open a Dalinq link, or visit dalinq.com, why we do that, and what you can do about it. We try to collect as little as possible. We do not sell personal data and we do not show ads.
1. Who is responsible
Dalinq is the trade name of Blackmountain Networks, registered with the Dutch Chamber of Commerce (KvK) under number 91253896 in the Netherlands ("Dalinq", "we").
Questions or requests about privacy: contact@dalinq.com. We have not appointed a data protection officer.
2. What we process, why, and on what basis
2.1 Using the app without an account (guest)
The first time you open the app, it creates a random device ID. Linked to that ID we store: the music app you chose as your main app, the display name you enter (optional), your app language and time zone, counters for how often you shared and opened links, and when your device first contacted us.
Why: to make the app work, remember your choices, and show you your own statistics. Legal basis: performance of our agreement with you (Art. 6(1)(b) GDPR).
2.2 Your account
An account is optional. If you create one, we store your name, username, e-mail address, a hashed password (we cannot read it), and, if you add them, a profile photo and a short bio. We also store your settings, such as whether your profile is private and which notifications you want.
If you sign in with Google or Apple, we receive your verified e-mail address and, if you allow it, your name from Google or Apple. We never see your Google or Apple password. With Apple's "Hide My Email" we only receive a relay address.
E-mails. When you register with an e-mail address, we send you a message to verify it. If you forget your password, we send a reset link to your e-mail address; the reset token expires after 60 minutes. We only send these service e-mails, no newsletters or marketing.
Who sees what. Your name, @username and profile photo are always visible on your profile and on your invite page, so others can add you. If your profile is set to private, then for people who are not your friends: your name or @username is not shown as "Shared by" on your Dalinq links, you do not appear in search results or when people find friends through their contacts, and your bio, statistics, achievements and friend count are hidden. You can still be found by your exact @username and through your invite link. Friends see your full profile.
Why: to give you a profile, friends, chat and achievements across devices. Legal basis: performance of our agreement (Art. 6(1)(b) GDPR).
2.3 Songs you share and Dalinq links
When you share a song, we store the original link (for example a Spotify link), the song details (title, artist, album, artwork, ISRC code), the matching links on the other music services, which device or account shared it, and when.
Dalinq link pages are public. Anyone who has the link can open the page. It shows the song and, if known, the name or @username of the person who shared it ("Shared by"), unless that person has a private profile: then no name is shown. Only share a link with people you want to see it.
Why: creating a working link is the core of the service. Legal basis: performance of our agreement (Art. 6(1)(b) GDPR).
2.4 Share and open statistics
Every share and every open of a Dalinq link is recorded as an event: the type (share or open), whether it happened in the app or on the web, the time, the song (ISRC), the source and destination music service, the channel where we can tell (for example WhatsApp, from the app's share sheet or the referring website), the link code, whether it worked, and two coarse location fields:
- Country: derived from the request IP address using a MaxMind GeoLite2 database that runs on our own server. The app's share and open event records do not contain IP addresses, and no IP address is sent to MaxMind. Our servers may use IP addresses briefly in security, session and access logs to prevent abuse and investigate problems.
- Language region: the region part of your browser's or device's language setting (for example "nl-NL" becomes NL). This is a language setting, not a location.
- A share is linked to the sharing device and, if signed in, the account. If you share a song you received earlier via a Dalinq link, we record which link that was (a "re-share"), and which link originally brought your device to Dalinq.
- An open in a web browser is not linked to the person opening it: we use no cookies or fingerprinting for that. It is linked to the link and its sharer, so the sharer can see that their link was opened.
- An open in the app is linked to that device and, if you are signed in, to your account.
- Recognizable link-preview bots (such as WhatsApp's) are excluded. Not every preview or automated request can be identified.
Why: to show you your statistics and achievements, and to understand and improve Dalinq (for example which services need better song matching and how songs spread). Legal basis: performance of our agreement for your own statistics (Art. 6(1)(b)), and our legitimate interest in measuring and improving the service (Art. 6(1)(f)). You can object, see section 7.
2.5 App use and how you found Dalinq
App opens. When the app comes to the foreground we record at most one event per device per 30 minutes: the device, your account if signed in, the platform (iOS or Android), the app version, the app language and the country derived from the request IP. The app-session record does not contain the IP address. We use this to count active users and how many keep using the app.
How your device found Dalinq. If you install or first open the app through a Dalinq link or an invite link, we record that once ("first touch"), only within 24 hours of your device's first contact with us: which link or invite it was, the device and account of the person who shared it, and when. On Android we read the Google Play Install Referrer for this, which tells us the Dalinq link you came from when you installed via the Play Store button on our pages. On iPhone we only know this if the app opens on that link. We do not use fingerprinting, IP matching or your clipboard for this. Self-referrals are ignored.
Why: to measure growth and which shared songs bring new people to Dalinq. Legal basis: our legitimate interest in measuring and improving the service (Art. 6(1)(f)). You can object, see section 7.
2.6 Friends and chat
If you have an account, you can add friends. We store friend requests, friendships, and how the connection was made (for example via search, an invite link or your contacts). Chat in Dalinq consists of shared songs: for each message we store the sender, the song (title, artist, artwork, link) and when it was read.
Legal basis: performance of our agreement (Art. 6(1)(b) GDPR).
2.7 Finding friends via your contacts (optional)
You can choose to add your own phone number so friends can find you. We store only a keyed hash of the number, made with a secret key held by our server, never the number itself.
If you choose to search your contacts, the app sends the phone numbers from your address book to our server over an encrypted connection. The server turns each number into the same kind of keyed hash, compares the hashes with those of other Dalinq users, and returns the matches. We do not store your address book; the numbers are discarded right after the comparison. Note that a hash of a phone number is pseudonymised data, not anonymous data.
Legal basis: your consent (Art. 6(1)(a) GDPR), given through the permission prompt. You can withdraw it at any time by removing your number in the app or revoking contacts access in your phone's settings.
2.8 Push notifications
If you allow notifications, we store a push token from Firebase Cloud Messaging for your device, and a record of which notifications we scheduled and sent (for example about a friend request, an achievement or a weekly challenge), so you don't get the same one twice.
Legal basis: your consent via your phone's permission prompt (Art. 6(1)(a)). You can switch notifications off in the app or in your phone's settings.
2.9 Achievements, streaks and challenges
Based on your activity we calculate achievements, levels, streaks and challenge progress, and compare them with your friends. Legal basis: performance of our agreement (Art. 6(1)(b)).
2.10 App analytics (Firebase Analytics)
The app uses Google Firebase Analytics to see how the app is used: for example which screens are opened, app version, device type, operating system and an app-instance identifier. Google derives an approximate location from your IP address but does not share the IP address with us. We do not use this for advertising.
Legal basis: our legitimate interest in understanding and improving the app (Art. 6(1)(f) GDPR).
2.11 Crash reports
When the release app encounters certain errors, it sends technical error information, device and operating-system details, and the app version to our self-hosted error-reporting system. Legal basis: our legitimate interest in maintaining and securing the app (Art. 6(1)(f) GDPR).
2.12 Website and cookies
dalinq.com uses no tracking or advertising cookies and no website analytics. We use functional cookies: a cookie that remembers your language choice (lang, up to one year) and session/security cookies used by the website. The session lifetime is up to two hours. Our servers may record IP addresses in security, session and access logs for a limited time to prevent abuse and investigate problems. Website fonts are served from our own server.
2.13 Contact with us
If you contact us by e-mail, through the contact form or through app feedback, we process your name and e-mail address (where provided), message, topic, and any image or screenshot you attach so we can respond and handle the request. App feedback can also include app version/build, platform, device model, operating system, language and time zone, screen/route, screen size, text scale, theme, network type, onboarding state, uptime, username/main music platform and up to 20 recent technical log lines. Website contact submissions may include your browser's User-Agent and language. We store support requests for as long as needed to handle and follow up on them. They are stored in our own support system; Mailgun sends e-mail replies. Legal basis: our legitimate interest in responding to and resolving support requests (Art. 6(1)(f) GDPR).
3. Music services
To find a song on other services, our server looks it up at Spotify, Apple Music, Tidal, Deezer and YouTube Music using song details (such as title, artist, platform IDs and ISRC), not your account or device identifiers. We also fetch catalogue details such as genre, release date and whether a song is explicit. These lookups are about the song, not about you. When you follow a link and use a music service, that service acts separately and processes data under its own privacy policy. We do not see or control what happens inside that service.
4. Who receives your data
We do not sell personal data. The following external providers receive or host data for the purposes listed:
| Provider | What for | Location |
|---|---|---|
| Netcup | VPS hosting for the app backend, database, avatars, support system and error-reporting system | Germany (EU) |
| Google (Firebase Cloud Messaging, Firebase Analytics, App Check, Google Sign-In and Google Play Install Referrer) | Push delivery, app analytics, app verification, sign-in and Android install attribution | EU and other regions, including the USA |
| Apple (Sign in with Apple and Apple Push Notification service) | Sign-in, push delivery on Apple devices and account-token revocation when requested | EU and other regions, including the USA |
| Mailgun (EU region) | Sending account/service e-mails and e-mail replies to support requests | EU region |
Our support and error-reporting tools run on our own Netcup-hosted server; Libredesk and Bugsink do not receive data as separate external providers. The country lookup uses a MaxMind GeoLite2 database file that we download and run locally; MaxMind receives no data about you.
We may also share data when the law requires it, for example with a court order.
5. Transfers outside the EU
Google and Apple may process data in the United States or other countries. Where personal data is transferred outside the EEA, we rely on an applicable adequacy decision or appropriate safeguards, such as the European Commission's Standard Contractual Clauses, as applicable.
6. How long we keep data
- Account data, friendships, song chats and achievements: until you delete your account, subject to limited records retained as described below.
- Guest device data: while needed to provide the app's sharing, link and statistics features. Guest device records are not automatically deleted after a fixed period.
- Dalinq links and song details: while needed for the link to keep working. Deleting an account removes the account link from associated records, but does not necessarily delete the link or its song details.
- Share, open, app-session and attribution records: while needed to provide statistics, operate and improve the service. After account deletion, account identifiers are removed from associated records where the deletion process does so; pseudonymous device and event records may remain.
- Phone-number hash: until you remove it or delete your account. We do not retain the contact list; numbers submitted for matching are processed for the match and discarded.
- Push token: while registered for the device; it can be removed when invalidated, replaced, or when the associated account/device is removed.
- Support records and crash reports: for as long as needed to respond to requests, diagnose errors and maintain service security, under our operational retention settings.
- Security logs: app-signature and app-verification logs are retained for up to 14 days. Other server/session logs are retained for the limited period needed for security and troubleshooting.
7. Your rights
Under the GDPR, subject to the conditions and exceptions in the law, you can request access to, correction or deletion of your personal data, restriction of processing, and data portability where applicable. You can object to processing based on our legitimate interest. Where we rely on consent, you can withdraw it at any time; this does not affect processing before withdrawal.
E-mail contact@dalinq.com. If you use the app without an account, include your device ID so we can find your data. We normally respond within one month. If a request is complex or numerous, the law allows an extension of up to two further months; we will tell you within the first month if that applies. We may ask you to confirm your identity.
You also have the right to complain to a data protection authority. In the Netherlands that is the Autoriteit Persoonsgegevens; you can also contact the authority in your own country.
8. Deleting your account
You can delete your account in the app under Settings. This deletes your account and associated profile, photo, friendships, chats, phone-number hash, achievements and notification history. The account's devices are detached and their push tokens are cleared. Links you shared may keep working, but are no longer linked to your account. Some pseudonymous device, link and event records may remain. Guest users can ask us to delete device data by e-mail; include the device ID if available. You can also contact us about account deletion.
9. Security
All traffic between the app, the website and our servers is encrypted (HTTPS). Passwords are stored hashed. Requests from the app are signed so that only the real app can use our API. Access to production data is limited to people who need it.
10. Children
Dalinq is intended for people aged 16 and over. If we learn that someone under 16 has provided personal data, contact us so we can review and delete it where appropriate.
11. Changes
We may update this policy when our processing changes. We will publish the current version here and give notice where required before materially different processing begins. The latest version is always at dalinq.com/en/privacy.
12. Contact
Dalinq · Blackmountain Networks · KvK 91253896 · contact@dalinq.com · Contact form