DriveBeatsDriveBeats

Privacy Policy

Last updated: October 23, 2026

What we do

DriveBeats lets you stream audio files (MP3, FLAC, WAV, AAC, OGG) stored in your Google Drive. It also lets you sync playlists and favorites between devices. It does not upload or re-host your audio files on our servers.

Google account access

We request Google Drive access through Google Picker and the drive.file scope. This limits DriveBeats to the folders and files you explicitly choose in the picker. In practice, that means DriveBeats can access your imported library, not your entire Drive. Your selected music files remain read-only: we never modify, delete or share them. You can revoke access at any time from your Google Account permissions.

We also require drive.appdata access. DriveBeats creates, reads and deletes its own hidden app-data files in your Google Drive to save playlists, favorites, Imported Folder and Standalone Track choices, and extracted title, artist and album tags. This backup uses your Google storage. App-folder approval is required to use DriveBeats. These writes never alter your music files.

We also request OpenID, email, and profile scopes so DriveBeats can identify which Google account is signed in and show your account name, email address, and avatar inside the app.

Cookies and local storage

We store secure HttpOnly cookies for authentication, including a refresh token cookie and a signed session cookie, so you can stay signed in for up to 30 days. No advertising or cross-site tracking cookies are used.

We also store an encrypted Google refresh token in our database, linked to your Google account ID, so future sign-ins can reuse the access you already approved. Logging out removes your browser session and preserves this connection. Deleting cloud data removes the saved connection. You can revoke access at any time in your Google Account permissions.

Recently played history, downloaded audio, download settings, active player state and the derived Library Search catalog stay on this device. Your Library choices, music tags, playlists and favorites are cached locally and backed up in hidden Google Drive app data. Saved unchanged tags restore on another browser before new tag extraction. Pending changes have not yet been acknowledged by Google and may be lost if this browser is cleared or closed before saving finishes.

Hidden app data passes through DriveBeats servers to validate and coordinate saves, restore and account deletion. Account identity, encrypted Google connection data and durable synchronization and deletion controls remain in our Neon-hosted Postgres database. Audio files are never saved to Neon or to the hidden backup.

Existing playlists and favorites move once from Neon to Google Drive after you approve app-folder access. Legacy Neon music tables are retained for a fixed 30-day window beginning with the verified production rollout. During that window the app shows the exact global cutoff in Europe/Berlin. Unmigrated playlists and favorites are permanently removed at that cutoff; later sign-ins start with empty collections. Account, authentication and synchronization controls remain.

Logging out clears local device data and preserves the remote backup and saved connection. Unsaved playlist, favorite, music tag and Library choice changes are lost when you log out; the confirmation warns you before clearing them. Removing downloads clears only this device. Delete account in Storage & data permanently deletes hidden DriveBeats data before removing account credentials and clearing this browser. Missing Google access requires reauthorization before DriveBeats can attempt cleanup. If an interrupted save has an unknown outcome, automatic account deletion may be blocked and need manual cleanup or support/provider verification. Your account and encrypted Google connection remain stored until cleanup is verified. Deleting hidden data through Google Drive Settings → Manage apps → DriveBeats → Options does not by itself prove all pending saves have stopped or complete account deletion. Revoking access alone does not delete hidden data. Your music files remain untouched.

Analytics

We use Vercel Analytics to measure page views, performance and WebMCP usage. WebMCP events include only the tool name, never tool inputs, results or Library content. No personal information is collected.

Data sharing

Your Google Drive files are requested directly from Google and stream to your browser. We don't sell your data, share it with data brokers, or use it for advertising.

Limited data is shared with service providers that operate the app, such as Google for authentication, Google Picker, and Drive access, Neon for account, encrypted connection and synchronization controls, and temporary legacy playlist and favorite storage, and Vercel for hosting and privacy-friendly analytics.

AI assistants and site tools

If you choose to use an AI assistant with DriveBeats, WebMCP site tools let it search your library, read your saved collections, control playback, and update playlists or favorites in the open page. Tool results are sent to the AI provider you use, such as OpenAI when using ChatGPT. These results can include track filenames and file IDs, playlist names and contents, favorite status, sign-in status, and playback information such as the current track and position.

The site tools do not return audio files, Google authentication tokens, or your account name and email address. Your Google Drive music files remain read-only. You can use DriveBeats without an AI assistant.

Contact

Questions? Contact Fabian Dietenberger at dietenberger.me.