Privacy Policy

Drive Music is a personal, independently-run web app that plays audio files straight from your own Google Drive, with optional offline caching in your browser. This page explains what it accesses, what it stores, and where — in plain terms, matching what the code actually does.

What Drive Music accesses via Google Sign-In

Signing in with Google grants Drive Music exactly two things:

• Your basic profile (name, email address, profile picture) — used only to show who's signed in and to key your own data (see below).
• Read-only access to your Google Drive (the drive.readonly scope). Drive Music can list folders and download audio files you choose to open — it cannot create, edit, move, or delete anything in your Drive, and it never requests access to files you haven't browsed to.

Limited Use of Google user data

Drive Music's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically, data obtained from your Google account is used only to provide and improve the features described here — never for advertising, never sold or transferred to others (except as needed to provide the app, to comply with the law, or as part of a merger or acquisition), and never read by humans, unless you explicitly ask for support, the law requires it, or it is needed for security purposes.

Where your data actually lives

Drive Music doesn't have a database of its own. Almost everything it keeps is stored locally, in your browser:

• Downloaded tracks, playlists, favorites, listening history, and your personal recommendation model — stored in your browser's IndexedDB, on your device only. None of this is ever uploaded anywhere.
• Your sign-in session — a token that lets Drive Music call the Google Drive API on your behalf, held in an encrypted session cookie in your browser.
• "Listen together" sync — if you turn this on, a small real-time message (which track, play/pause, playback position) is relayed between your own devices signed into the same Google account, through a private, token-gated room. It exists only for the live connection and isn't written to any database; other people can't see or join your room.
• Anonymous performance metrics — page-load timing via Vercel Speed Insights, which doesn't identify you personally.

What Drive Music does not do

• Doesn't sell, rent, or share your data with third parties.
• Doesn't run ads or ad-tracking of any kind.
• Doesn't read, modify, or delete files in your Drive beyond playing audio you open.
• Doesn't keep a copy of your files on any server it controls.

Deleting your data

Settings → Clear all data wipes everything Drive Music has stored in your browser — downloads, playlists, listening history, and your recommendation model — instantly and permanently.

Signing out ends your local session but doesn't revoke Drive access on Google's side. To fully revoke Drive Music's access to your Google account, remove it from your Google Account permissions.

Third-party services involved

Drive Music runs on Vercel (hosting), uses Google's APIs for sign-in and Drive access, and Cloudflare/PartyKit for the optional real-time sync described above. Each is bound by its own privacy policy for the infrastructure it provides.

Children's privacy

Drive Music isn't directed at children under 13, and doesn't knowingly collect data from them.

Changes to this policy

If what Drive Music accesses or stores changes, this page will be updated and the date above will change accordingly.

Contact

Drive Music is an open-source personal project — the code is public at github.com/ChakkritGit/drive-music. Questions or concerns about this policy can be raised via GitHub Issues.