⚡
Quick Beat Drops
  • Overview
  • Terms
  • Privacy
  • Licensing
  • Launch Studio →
Document Contents
  • 1. Privacy Overview
  • 2. Information We Collect
  • 3. Isolated API Security Vault
  • 4. Google & YouTube User Data
  • 5. How We Use Data
  • 6. Data Retention & Deletion
  • 7. Cookies & Local Storage
  • 8. Your Privacy Rights
DATA PROTECTION Effective Date: October 17, 2026 • GDPR & CCPA Compliant

Privacy Policy & Data Security

At Quick Beat Drops, we treat user isolation, credential protection, and API privacy as foundational principles. This policy outlines how your private keys, account details, and media assets are safeguarded within our multi-tenant infrastructure.

01. Privacy Overview

Quick Beat Drops is designed for music producers and curators who require automated workflows without risking sensitive credentials. Every account operates inside an isolated sandbox—your Suno tokens, YouTube OAuth refresh keys, Gemini configurations, and produced beats are never exposed to other platform users.

02. Information We Collect

We collect only the minimum information required to execute your automated pipelines:

  • Account Information: Username, email address, password hash (salted using cryptographic scrypt).
  • API Credentials (Stored in Your Private Vault): Suno session tokens, Google OAuth client credentials & refresh tokens, Gemini API keys.
  • Production Metadata: Track titles, genre choices, custom prompts, visualizer settings, and scheduled drop times.
  • Rendered Media: Temporary audio files (WAV/MP3), 1080p MP4 visualizer videos, 9:16 Shorts clips, and generated album artwork.

03. Isolated API Security Vault

Tenant Credential Isolation

Each user's API keys and tokens are stored in a dedicated record in the server database. Tokens are never passed to the client frontend after initial configuration. Pipeline tasks read only the executing user's credentials in isolated server memory.

We enforce strict TLS 1.3 encryption for all data in transit across HTTPS, backed by Let's Encrypt certificates and HSTS policy headers.

04. Google & YouTube User Data Handling

Quick Beat Drops' use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

  • Scope Requested: We request only https://www.googleapis.com/auth/youtube.upload and youtube.readonly solely to inspect your channel ID/title and publish your finished renders.
  • No Selling of Data: We do NOT sell, rent, or monetize your Google or YouTube channel data.
  • No Third-Party Sharing: Your YouTube tokens are never shared with advertisers, data brokers, or external AI model trainers.

05. How We Use Data

Your data is used strictly to provide automated services:

  • Synthesizing audio based on your chosen genres and prompts.
  • Rendering 1080p Ken Burns visualizers and 9:16 Shorts hook clips using FFmpeg.
  • Executing scheduled video publishing according to your peak-hour daemon settings.
  • Tracking daily YouTube API quota consumption (units used per 24 hours).

06. Data Retention & Automatic Cleanup

You have full control over your media vault. When you delete a track from your dashboard, Quick Beat Drops immediately removes the corresponding database record and permanently purges local audio files, 1080p video visualizers, and thumbnail assets from server storage.

07. Cookies & Local Storage

We use secure, HTTP-only cookies and local session tokens solely for authentication and session persistence (e.g. qbd_token). We do NOT use third-party tracking cookies or ad pixels.

08. Your Privacy Rights

Regardless of your jurisdiction, you have the right to inspect your stored data, update your API credentials, or request immediate account deletion. Contact our privacy officers at privacy@quickbeatdrops.com.

© 2026 Quick Beat Drops. All rights reserved.
  • Terms
  • Privacy
  • Licensing
  • System Status