Privacy Policy

Effective October 5, 2026

DJOPS is a desktop application for macOS that helps DJs prepare, edit and publish recordings of their DJ sets. This policy explains what data DJOPS accesses, how it is used and stored, and the choices you have. "We" and "us" mean the DJOPS team, based in Montréal, Canada.

1. YouTube API Services

DJOPS uses YouTube API Services to publish videos to YouTube channels you choose to connect. By connecting a YouTube channel to DJOPS, you agree to be bound by the YouTube Terms of Service. Google's handling of your data is described in the Google Privacy Policy.

When you connect a channel, you sign in with Google and grant DJOPS permission to act on that channel. DJOPS uses that permission only to do what you ask it to in the app:

• upload videos you have created and approved (full sets and short clips);
• set and update a video's title, description, chapters, tags, category, privacy status and scheduled publish time;
• set a custom thumbnail;
• read your channel's details, videos and playlists, so you can see your uploads and pick where to publish;
• create and update playlists, and add your videos to them;
• update your channel's details when you edit them in DJOPS;
• delete a video, only when you choose to remove it in DJOPS;
• read your channel's analytics (YouTube Analytics, read-only), so DJOPS can show which sets and clips performed well.

DJOPS also reads the name and email address of the Google account you sign in with, so you can tell your connected accounts apart.

Where YouTube data is stored, and for how long. YouTube channel data is stored only on your own computer. Every stored item (channel and analytics reads, Channel Doctor reports, channel snapshots, thumbnail undo copies and caches) is refreshed or deleted automatically once it is 30 days old. The cleanup runs when DJOPS starts and once a day while it is running. The only YouTube data kept longer is the IDs and links of videos DJOPS itself uploaded for you, so it does not upload the same video twice. Text you typed yourself is yours and is not affected.

DJOPS does not collect data about other channels or other creators. Channel analytics are aggregated statistics provided by YouTube; DJOPS never identifies individual viewers.

DJOPS's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

2. What data DJOPS accesses and where it is stored

• Google sign-in tokens. The access and refresh tokens Google issues when you connect a channel are stored only on your Mac and are never included in backups. They are used only to make the YouTube requests described above.
• Channel information and analytics. Your channel's name, ID, videos, playlists and analytics are stored locally so the app can show you where a video will go and how your content is doing. They are refreshed or deleted after 30 days, as described above.
• Backups, if you turn them on. DJOPS can back up its own data to your Google Drive. It only uses your Drive when you enable backups, and only for those backups.
• Your media and library. Recordings, audio files, your Rekordbox library and anything DJOPS produces from them (edits, thumbnails, clips, listings) stay on your Mac. They leave your computer only when you publish, and only to the platform you publish to.

We don't operate a server that receives or stores YouTube API data or your media.

3. How we use and share data

Data is used only to provide DJOPS's features to you. We do not sell YouTube data or any other data, share it with third parties, use it for advertising, or use it to train AI models.

If you connect other services, such as Spotify for playlists or Publer for scheduling posts to Instagram and TikTok, DJOPS sends them only what is needed for the action you choose (for example, a clip and its caption to Publer). Those services handle that data under their own terms. YouTube API data is never sent to them.

If you choose to connect your own AI provider (for example to help write a video description), the text you send for that task, such as a tracklist or a draft description, goes directly from your Mac to that provider under their terms. Google sign-in tokens are never sent to an AI provider.

4. Beta sign-ups, cookies and analytics

If you sign up for the beta, the form is hosted by Tally and your answers (such as your name, email, social handles and what you play) are stored with Tally and in our private spreadsheet. We use them only to contact you about the DJOPS beta and product updates. To have them deleted, email us.

This website itself does not use cookies or tracking. The DJOPS app does not currently collect analytics. If we add usage or crash reporting in the future, it will be opt-in, will never include YouTube API data or your media, and this policy will be updated before it ships.

5. Retention and deletion

• Disconnect in the app. You can disconnect a channel at any time in Settings → Connections. This revokes DJOPS's access at Google and deletes the stored sign-in from your Mac. Saved channel data is deleted automatically once it is 30 days old.
• Revoke from Google. You can revoke DJOPS's access at any time from your Google Account permissions page. DJOPS will no longer be able to act on your channel.
• Uninstall. Deleting DJOPS and its application data removes everything it stored locally.

Because we don't hold your YouTube data on our side, there is nothing for us to delete on a server. Videos you published stay on YouTube until you remove them there.

6. Security

Sign-in tokens are kept in DJOPS's private data folder on your Mac and are only ever sent to Google. Every request to YouTube uses an encrypted connection (HTTPS). Anyone with access to your Mac user account could read local app data, so keep your Mac protected with a password.

7. Children

DJOPS is not directed at children under 13 and we do not knowingly collect their data.

8. Changes

If we change this policy, we'll update the effective date above and, for significant changes, tell users in the app.

9. Contact

Questions or requests: [email protected]