Privacy

dhoom-dj is a private service run by two people for a handful of DJs. It is not a product, it sells nothing, and nobody is being measured.

What signing in tells us

Signing in with Google gives this service your email address and the name on your Google account, and nothing else. The permissions asked for are openid, email and profile — there is no access to your mail, your files, your contacts or your calendar, and asking for any of those would show on the consent screen.

Google never gives us your password, and this service could not ask for it.

What is kept

Sign-in sessions and API keys are stored as one-way hashes, so the stored copy cannot be turned back into a working credential. Share links are the one exception and are kept readable on purpose — otherwise “what was that link again?” could not be answered, and every asking would leave another live link behind.

Cookies

Two, both doing a job and neither watching anybody:

There is no analytics, no tracking, no advertising and no third-party script on any page here.

Who else sees it

Nobody. Nothing is sold, shared or sent anywhere. The database sits on a machine in a house.

Two exceptions worth naming rather than hiding. The people who administer this library can see the list of who has signed in. And if you connect an assistant — Claude, or anything else that speaks MCP — that assistant acts as you against this library, which is what you are agreeing to on the page that asks.

Getting rid of it

Ask, and the row is deleted. There is no form, because there are not enough people here to need one.

You can also disconnect an assistant yourself at any time from your account page, which ends every token it holds for you at once.

Music

The recordings in this library came from YouTube. They are here so a set can be listened to before it is performed, and they are not offered for download or sold. A link you are sent plays one set and nothing else, and can be revoked.