Privacy policy

open-dj · last updated Friday 28 August 2026

Short version: open-dj runs on your own computer. If you sign in with Google, your name, email address and profile picture are stored locally on that computer so the app knows who you are. Nothing is sent to us, because there is no server to send it to.

Who runs this

open-dj is a personal project by Alex Foster. Questions or requests: agdfoster@gmail.com.

What signing in with Google collects

Signing in is optional. open-dj requests only the three standard identity scopes, openid, email and profile. It asks for no access to Gmail, Drive, contacts, calendar or any other Google service.

When you sign in, the following are stored on your own computer:

These live in the application's local database file on your machine, alongside your music library data. They are not transmitted anywhere. The application listens on 127.0.0.1, meaning it is reachable only from your own computer.

What we do not do

Optional cloud sync

open-dj can optionally back up and synchronise your own library data between your own machines using cloud storage that you own and configure, using your own credentials. If you enable this, your data is stored with that provider under your account and subject to their terms. It is off unless you turn it on, and it never routes through us.

Deleting your data

Signing out from within the app deletes the stored session. Because everything is held locally, deleting the application's data directory removes all stored account information permanently. You can also revoke open-dj's access at any time from your Google account permissions page, which invalidates the stored tokens.

Children

open-dj is not directed at children under 13 and does not knowingly collect their data.

Changes

If this policy changes materially, the date at the top of this page changes with it. Given the app collects nothing centrally, changes are expected to be rare.