Privacy Policy
DjAI · Last updated:
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, SoundCloud, Amazon Music, Last.fm)
- 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
Purchase Data
- Subscription and in-app purchase status: plan, product, and purchase, renewal and expiry dates
- The store you purchased from (App Store or Google Play) and its country
Payments are processed by Apple or Google. DjAI never receives your card or bank details.
Device Data
- Device model, operating system version, app version and language
- An identifier the app creates for your installation; on Android, a one-way hash of the device's Android ID; on iOS, Apple's DeviceCheck signal
- The device's advertising identifier, where permitted: on iOS only if you allow tracking, and in the EEA, UK and Switzerland only with your consent
- If notifications are on for DjAI: a push token for your device, your app language, your time zone and your country, so notifications reach you in your language, at sensible local times, for your country's chart and season
We use device identifiers to recognise your device — so a guest account can be found again after a reinstall, and only once you confirm it is yours — and to prevent abuse of the free tier.
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
- Provide subscriptions and purchases, and find your account when you contact support
- Measure which channels bring people to DjAI, where you have allowed it
- Send the notifications that are on for you: when a set you asked for is ready, weekly trends, and set suggestions for the listening moments you picked (at most one scheduled notification a day, none between 22:00 and 08:00 your time)
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.
- SoundCloud — DjAI reads your SoundCloud likes and playlists while it builds a set, and can create a private playlist in your SoundCloud account when you export a set there. Audio is never downloaded or stored. A set you save keeps only song information (title, artist and SoundCloud ID). SoundCloud content is not sent to AI services, is not used for your Music DNA, and is not used to train models.
- Amazon Music — after you sign in with Login with Amazon, DjAI reads your Amazon Music playlists to build sets and can create a playlist in your Amazon Music account when you export a set there.
- Last.fm — if you connect Last.fm, DjAI reads your recent and top tracks and top artists to personalize your sets and Music DNA. DjAI does not post anything to your Last.fm account.
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)
- Subscription management provider (RevenueCat) — your DjAI account ID, purchase and subscription status, device and app details and, for registered accounts, your email address and display name, so we can find your account when you ask for help. Guest accounts are sent without an email or name.
- App stores (Apple App Store, Google Play) — they process your payments and tell us the status of your purchases.
- Advertising attribution provider (Meta) — app events such as install, sign-up and purchase, with your device's advertising identifier only where permitted as described in Section 1.
- Push delivery services (Google Firebase Cloud Messaging and Apple Push Notification service) — a push token and the notification text, only to deliver notifications that are on for you.
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.
- SoundCloud likes and playlists are read for the set being built and are not kept; song information in a saved set stays until you delete the set or your account.
- 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.
- Purchase records are kept after account deletion where needed for accounting, legal or fraud-prevention purposes; the rest of your account data is deleted.
- Push tokens are deleted when you delete your account or when the push service reports them invalid; a record of which scheduled notification you got on which day is kept for 30 days to enforce the limits above.
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
- Turn each notification type on or off in Settings → Notifications, or turn off DjAI notifications in your phone's settings
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.
11. Our Website
On playdjai.com we use only the storage the site needs to work and to remember your cookie choice, unless you allow more in the cookie banner. Your choice is kept in your browser, and you can change or withdraw it at any time with Cookie settings at the bottom of every page.
- Measurement (Google Analytics 4): if you allow it, Google records how the site is used, such as pages viewed, device and browser type and approximate location derived from your IP address. Google Analytics 4 does not log or store IP addresses.
- Marketing (Meta Pixel): if you allow it, Meta records page views so we can see whether our ads bring visitors. Meta may link this to your Meta account under Meta's own privacy policy.
If you decline, neither runs. The website does not use these tools for anything inside the DjAI app.
12. Contact
Questions about this policy or your data can be sent to support@playdjai.com.
This policy may be updated as DjAI's features evolve. Material changes will be reflected here with an updated date.