DOZ — Privacy Policy
Last updated: November 2, 2026
This privacy policy (“Policy”) explains how DOZ, a mobile-first social music application published by SARL PAX, collects and processes personal data when users access and interact with the DOZ platform.
DOZ lets users connect one or more supported music-streaming accounts (currently Spotify, Apple Music and Deezer), share and discover music through a social feed, and compare their musical taste with other users. DOZ is designed to work across streaming providers: it is a social layer above them, not a replacement for them.
1. Definitions
- User: any person who creates a DOZ account and uses the platform to connect a music provider, share, browse, save or compare music.
- Visitor: any person browsing public content without an account.
- Platform: the DOZ mobile application (iOS and Android) and the DOZ website accessible at https://www.dozapp.com.
- Music Provider: a supported streaming service that a user connects to DOZ — currently Spotify, Apple Music and Deezer. Additional providers may be added over time.
- Provider Data: data retrieved through a Music Provider’s API, such as the provider account identifier, storefront (Apple Music), playlists, saved/favorite tracks, top tracks and artists, listening history, recently added items, and track metadata (title, artist, album, ISRC).
- Music Profile: the normalized collection and summary of a user’s musical taste built by DOZ from Provider Data (representative tracks, top artists, genres, average BPM and related indicators).
- Compatibility: the comparison DOZ computes between the Music Profiles of two users.
- Canonical Track: a provider-independent track record stored by DOZ. Canonical tracks and their audio metadata are reference data and are not, on their own, personal data.
- Personal Data: any information relating to an identified or identifiable individual, as defined by the GDPR.
- Controller: SARL PAX, registered in France at 41 avenue du maréchal Lyautey, 75016 Paris.
2. Data We Collect
DOZ may collect and process the following categories of data.
2.1 Account and identity data
- Username, name, email address, profile picture, bio.
- Phone number, required at sign-up and verified with a code sent by SMS.
- Account role and privacy setting (public/private), onboarding status.
- Email verification codes (used during the Apple Music sign-up flow).
2.2 Provider authentication data
- OAuth access tokens and refresh tokens for each connected Music Provider.
- Provider user identifier and, where applicable, storefront/country (Apple Music).
2.3 Provider music data and listening signals
Depending on the provider connected and the permissions granted, DOZ may collect:
- playlists and playlist tracks (including the date a track was added);
- saved/favorite tracks, favorite artists and favorite albums;
- top tracks and top artists;
- listening history and recently added items;
- track metadata (title, artist, album, duration, cover, release year, ISRC).
Not every provider exposes the same signals; DOZ collects only what the connected provider makes available and what the user has authorized.
2.4 Derived Music Profile data
From the above, DOZ builds and stores a Music Profile, which may include representative tracks, representative top artists, genres, average BPM, average release year, and per-signal source information used for taste analysis and Compatibility.
2.5 Audio-feature and genre enrichment data
For tracks identified by an ISRC, DOZ retrieves audio characteristics (such as tempo/BPM, energy, danceability and related features) from a third-party metadata provider (Soundcharts) in order to power the Compatibility feature. DOZ also sends artist names and metadata to Google Gemini to classify music genres. This enrichment relies only on reference data about tracks and artists: it is not keyed to individual users, and no user data is sent to these providers.
2.6 User-generated content
- Posts (“dozs”) including the selected track(s) and any comment.
- Comments and mentions of other users.
- Reactions (“buzz”) and redoz (reshares of a doz).
- Saved and pinned tracks.
- Collaborative multi-platform playlists (“collabs”), including the tracks added to them, their cover photos and the messages exchanged in them.
- Doz views (which dozs a user has viewed).
- Playlists a user chooses to make visible, relevant or set as a saving destination.
- Social-graph data: follows, follow requests, and follow-related notifications.
2.7 Contacts (optional)
If the user allows access to their contacts through the system permission, the app normalizes the phone numbers of their contacts on the device and sends DOZ only their SHA-256 hash. Contact names and phone numbers in clear text are never sent. DOZ’s servers keep only the matches with existing DOZ accounts and discard everything else. Each synchronization replaces the previous one.
These matches are used to suggest accounts to follow and to show which DOZ users are in the user’s contacts. The user can withdraw the permission at any time in their device settings: the next time the app is opened, it asks DOZ to delete the stored matches.
2.8 Photos and camera
Profile pictures and collab cover photos uploaded by users are stored on Amazon Web Services (S3). The camera is used to take a photo and to scan Compatibility QR codes.
2.9 Technical data
- IP address, device information, application version, browser type (web).
- Connection dates and times, diagnostic and error logs, including the search queries typed in the app (tracks, users, playlists).
- Usage analytics and crash reports from the mobile application (see section 8).
- Device signals collected by the mobile SDK of our phone-verification provider (Prelude) to prevent fraud.
- Push-notification token (mobile), where notifications are enabled.
3. Purposes and Legal Basis
| Data category | Purpose | Legal basis |
|---|---|---|
| Provider authentication | Purpose: Connect and authenticate the user to their chosen Music Provider(s) | Legal basis: Performance of a contract |
| Provider music data & listening signals | Purpose: Build the user’s Music Profile, display playlists, enable sharing and saving of tracks | Legal basis: Performance of a contract |
| Derived Music Profile & Compatibility | Purpose: Compute and display musical-taste compatibility between users, generate insights and suggested content | Legal basis: Performance of a contract / Consent (see 3.1) |
| Recommendations | Purpose: Suggest accounts to follow and “For you” dozs | Legal basis: Performance of a contract / Legitimate interest (see 3.1) |
| Audio-feature & genre enrichment (Soundcharts, Google Gemini) | Purpose: Enrich tracks with audio characteristics needed for Compatibility and classify music genres | Legal basis: Performance of a contract / Legitimate interest |
| Account & identity data | Purpose: Create and manage the user account and profile, send transactional emails (such as the Apple Music sign-up code) | Legal basis: Performance of a contract |
| Phone number & phone verification (Prelude) | Purpose: Verify the phone number, secure the account, prevent fraud and abuse, help users find their friends on DOZ | Legal basis: Performance of a contract / Legitimate interest |
| Contacts (SHA-256 hashes) | Purpose: Suggest accounts to follow and show which DOZ users are in the user’s contacts | Legal basis: Consent (system permission, which can be withdrawn at any time) |
| Photos & camera | Purpose: Display profile pictures and collab covers, take photos, scan Compatibility QR codes | Legal basis: Performance of a contract |
| User-generated content & social graph | Purpose: Enable community sharing, discovery, follow relationships and collabs | Legal basis: Performance of a contract |
| Usage analytics & crash reports (PostHog) | Purpose: Produce usage statistics, detect and fix crashes and errors | Legal basis: Legitimate interest |
| Technical data | Purpose: Diagnose issues, ensure security and prevent abuse | Legal basis: Legitimate interest |
| Push-notification token | Purpose: Send notifications the user has enabled | Legal basis: Consent |
3.1 Automated processing and profiling (Compatibility and recommendations)
The Compatibility feature analyses a user’s Music Profile and compares it with other users’ profiles to produce a compatibility score and related insights. This constitutes profiling within the meaning of the GDPR. It is used to power a core, user-initiated feature of the Platform and does not produce legal or similarly significant effects on users. Users can request that DOZ stop this processing by disconnecting a provider or deleting their account. Where required, DOZ relies on the user’s consent, given when they choose to run a compatibility comparison.
DOZ also suggests accounts to follow and “For you” dozs. These recommendations are computed from the accounts the user follows, their contacts (where the user has granted access, see 2.7) and their Music Profile. This also constitutes profiling within the meaning of the GDPR. It does not produce legal or similarly significant effects on users.
4. Data Recipients and Sub-processors
DOZ shares data only as necessary to operate the Platform:
- Music Providers (Spotify, Apple Music, Deezer): for the API calls required to authenticate the user and access their music data.
- Soundcharts: receives track identifiers (e.g. ISRC) to return audio-feature metadata.
- Google Gemini: receives artist names and metadata to classify music genres. No user data is sent.
- Prelude: verifies phone numbers by sending a code by SMS, and collects device signals through its mobile SDK to prevent fraud.
- Hostinger: hosting of DOZ servers, in Paris, France.
- Amazon Web Services (S3): storage of files, such as profile pictures and collab cover photos, in the Paris region (France).
- Vercel: hosting of the DOZ website.
- PostHog (hosted in the EU): usage analytics and crash reports from the mobile application. Users are identified there only by their internal DOZ identifier, their music service and their account role.
- Expo: push-notification service, which delivers notifications through Apple Push Notification service and Firebase Cloud Messaging (Google).
- Resend: sending of transactional emails (for example, the Apple Music sign-up code).
- App-distribution services (e.g. Apple App Store, Google Play) where applicable.
- Competent authorities: where disclosure is legally required.
DOZ does not sell or rent personal data to any third party.
5. Data Retention
- OAuth tokens: retained until the user revokes access or the token expires, and deleted when the connection or account is removed.
- Phone number: retained as long as the account exists.
- Contacts: only matches with existing DOZ accounts are kept, and each synchronization replaces the previous one; hashes that match no account are not kept. The matches are deleted when the user withdraws the permission or deletes their account.
- Photos: retained as long as the account exists, and deleted within 30 days after the account is deleted.
- Usage analytics and crash reports (PostHog): retained as long as the account exists, and deleted within 30 days after the account is deleted.
- Music Profile and listening signals: retained while the account is active and the provider remains connected; refreshed periodically and deleted when the user disconnects the provider or deletes their account.
- Canonical tracks and audio-feature cache: retained as anonymous reference data independent of any single user.
- Technical logs: retained for 6 months, then anonymized or deleted.
- User-generated content (dozs, comments): retained until the user deletes the content, their account, or requests erasure. See section 10 for content shared in collabs.
6. International Data Transfers
DOZ’s servers are hosted in Paris, France (Hostinger), and its files are stored in the Paris region of Amazon Web Services. Usage analytics and crash reports are hosted in the EU by PostHog.
Some data may be processed on servers located outside the European Union, in particular through certain Music Providers, enrichment providers and service providers (for example Apple, Soundcharts, Google, Expo, Resend, Prelude and Vercel). Where this is the case, DOZ ensures appropriate safeguards are in place, such as EU Standard Contractual Clauses or an adequacy decision.
7. Security Measures
- TLS encryption on all connections.
- Encrypted database backups.
- Secure storage of provider tokens; tokens are never exposed in logs or client responses.
- Access control with multi-factor authentication for internal teams.
- Regular security reviews.
9. Your Rights
Under the GDPR, you have the right to:
- access your data;
- correct or erase your data;
- restrict or object to its processing;
- data portability;
- withdraw consent at any time, where processing is based on consent;
- not be subject to a decision based solely on automated processing producing legal or similarly significant effects.
You can also delete your account at any time (see section 10).
To exercise your rights, contact us at hello@dozapp.com. You may also lodge a complaint with the CNIL (Commission Nationale de l’Informatique et des Libertés).
10. Account Deletion
You can delete your account directly in the app: open your profile, then Settings → Account → Delete my account, type DELETE and confirm with Delete permanently. Deletion is permanent.
- Deleted immediately: your profile (username, name, bio), phone number, email address, Music Provider connections and tokens, Music Profile and imported listening data, dozs, comments, reactions, redoz, saved and pinned tracks, follows and followers, playlists, Compatibility results, contact matches, notifications and sessions.
- Deleted within 30 days: the photos you uploaded and your usage analytics (PostHog).
- Technical logs: kept for 6 months at most, then deleted or anonymized (see section 5).
Collabs shared with other members are handled as follows:
- tracks you added to these collabs remain in them and are attributed to “A former member”;
- the text of your messages in collabs is erased and displayed as “Message deleted”;
- a collab you owned is handed over to another member, or deleted if no members remain.
If you cannot use the app, you can request the deletion of your account and its data by email at hello@dozapp.com. We process the request within 30 days.
For step-by-step instructions and the full list of what is deleted and kept, see dozapp.com/delete-account.
11. Children
DOZ is not intended for children under 16. Users must be at least 16 years old and hold a valid account with a supported Music Provider.
12. Changes to This Policy
We may update this Policy to reflect changes in our services or legal obligations. Users will be notified by email or on the Platform at least 15 days before significant updates take effect.