DjAI is a personal AI DJ app that helps you create music sets from the streaming services you connect and the local songs you choose. This policy explains what we collect, why, and the controls you have.
1. Data We Collect
Account Data
- Email address
- Display name
- Authentication provider (e.g. Google, Apple, email/password)
Music Source Data
- Which source type you connect (Spotify, Apple Music, YouTube)
- Authorization/connection status
- Library and playlist metadata, where the source permits
- Track metadata (title, artist, duration, genre), where permitted
- Source sync status
Local Music Data
- Metadata for local files you explicitly select (title, artist, duration, format)
- Optional audio-feature metadata (e.g. tempo/energy) if analyzed on-device to build sets
Usage Data
- App screens viewed and navigation actions
- Set generation actions
- Playback interactions (play, pause, skip, completion)
- Likes, favorites, and saves
- Crash and diagnostic data
Prompt and Search Data
Raw prompts and raw search queries you type are not sent to analytics. Where a prompt is processed to generate a set, it is used only for that request and is not stored for advertising or shared with third parties for marketing purposes.
Optional Demographic Data
You may optionally provide an age range, gender, city, country, and language preferences to improve set personalization. All of these fields are optional, gender includes a "prefer not to say" option, and we do not request precise location or exact date of birth.
Music DNA & Listening Behavior
If you use DjAI's personalization features, we build a "Music DNA" profile from: connected-source metadata, local file metadata, your stated preferences, likes/favorites/saves, and playback behavior signals (skip/completion, replay, set completion). This profile is used to personalize recommendations and is never shown to other users in raw form.
2. How We Use Data
- Create personalized, AI-assisted music sets
- Manage your connected music sources
- Improve recommendations and set quality
- Maintain security and prevent abuse
- Debug and improve app performance
AI and Model Development
We use third-party AI services to interpret the requests you type and to generate sets. We may also use usage data, stated preferences, and non-Google catalog and metadata — in aggregated or de-identified form — to evaluate, improve, and develop our recommendation systems and models. Information obtained through YouTube API Services or other Google APIs is never used for this purpose; see YouTube API Services.
3. What We Do Not Do
- We do not host or stream commercial provider audio ourselves — playback happens through the provider you connected, subject to their own terms.
- We do not sell your personal data.
- We do not use provider access tokens for advertising targeting.
- We do not use information obtained from YouTube API Services or other Google APIs to train, fine-tune, or develop machine-learning or AI models.
- We do not claim an official partnership with any music service unless explicitly authorized by that service.
4. Connected Music Services
Each source you connect has its own permission scope, explained at the point of connection. You can disconnect any source at any time from Profile → Privacy in the app.
- Spotify — DjAI reads permitted profile/library/playlist metadata to help build sets. Playback and availability depend on your own Spotify account, device, region, and subscription plan.
- Apple Music — DjAI uses Apple Music access to find permitted library or catalog content and build sets from music you can play.
- YouTube — see YouTube API Services below.
5. YouTube API Services
DjAI uses YouTube API Services. Your use of the YouTube integration is also subject to the YouTube Terms of Service. Google's handling of information received through its APIs is described in the Google Privacy Policy.
What DjAI accesses
When you connect YouTube and grant the youtube.force-ssl permission, DjAI accesses:
- your YouTube playlists and their contents;
- your liked music videos;
- your channel ID (used only to confirm the connection).
What DjAI does with it
Only to carry out actions you start in the app:
- create private playlists in your YouTube account and add tracks to them (“Export to YouTube”);
- remove tracks from, or delete, playlists you created through DjAI;
- remove a “like” from a music video when you ask it to;
- display your playlists and liked music inside DjAI.
How DjAI protects it
- OAuth access and refresh tokens are encrypted at rest with AES-256-GCM before they are stored; the encryption key is held separately from the database.
- All requests to Google are made over TLS.
- Stored tokens are accessible only to DjAI’s backend services and authorized personnel.
- Tokens are deleted the moment you disconnect YouTube (Profile → Privacy) or delete your account.
Limited Use
DjAI’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Information obtained through YouTube API Services is used only to provide and improve the features above; it is not sold, is not used for advertising, and is not used to train, fine-tune, or develop machine-learning or AI models. No human reads this data except where you give consent, where it is needed for security or to comply with law, or in aggregated / de-identified form for internal operations.
Revoking access
You can disconnect YouTube at any time from Profile → Privacy in the app, which deletes DjAI’s stored tokens. You can also review or revoke DjAI’s access from your Google Account permissions page.
6. Local Files
DjAI only accesses local files you explicitly select. Removing a file from DjAI removes it from DjAI's index only — it does not delete the original file from your device.
7. Data Sharing
We work with a small number of service providers to operate DjAI, which may process data on our behalf:
- Cloud hosting provider
- Analytics / crash-reporting provider
- Authentication provider
- AI processing provider (for intent parsing, not for storing your raw prompts)
We do not sell personal data to third parties.
8. Retention
- Account data is retained while your account is active.
- Source access tokens are deleted immediately on disconnect or account deletion.
- Music metadata derived from connected sources (including YouTube) and used for sets or personalization is retained under the controls in Section 9 and removed when you reset your Music DNA, delete your personalization data, or delete your account.
- Analytics data is retained according to our analytics provider's standard retention window.
- Local file metadata is deleted when you remove it from your library index or delete your account.
9. Your Rights & Controls
From Profile → Privacy in the app, you can:
- Toggle use of listening activity for personalization
- Toggle use of connected-source metadata for personalization
- Toggle use of local file metadata for personalization
- Reset your Music DNA profile
- Delete your personalization data
- Disconnect any connected source
- Delete your account and associated data entirely
Account deletion is permanent and removes your account data, source tokens, personalization/Music DNA data, and saved sets you own.
10. Children
DjAI is not directed to children and should not be used by anyone under the minimum age required by their country's data protection laws.
Questions about this policy or your data can be sent to support@playdjai.com.