Privacy Policy

1. Introduction

Welcome to BeatOps ("we," "our," or "us"). BeatOps is a beat upload automation platform that helps music producers distribute their beats across multiple platforms including YouTube, BeatStars, and SoundCloud.

This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our service. Please read this policy carefully. By using BeatOps, you agree to the collection and use of information in accordance with this policy.

2. Information We Collect

2.1 Account Information

When you create an account, we may collect:

• Email address
• Producer/brand name
• Account preferences and settings

2.2 Beat and Content Data

When you use our service, we process:

• Beat metadata (titles, BPM, keys, artist references)
• Generated thumbnails and video files
• Template configurations and preferences
• Upload history and scheduling information

2.3 YouTube Account Data (via OAuth)

When you connect your YouTube account, we access:

• YouTube channel information (channel name, ID)
• Permission to upload videos on your behalf
• Permission to manage your playlists

2.4 Usage Data

We automatically collect certain information when you use our service:

• Features used and actions taken
• Error logs and performance data
• Device and browser information

3. YouTube API Services

3.1 What We Access

Through the YouTube API, BeatOps accesses:

• Your YouTube channel information to identify where videos will be uploaded
• Permission to upload videos to your channel on your behalf
• Permission to add uploaded videos to your playlists
• Video metadata (titles, descriptions, tags) that you configure

3.2 How We Use YouTube Data

We use YouTube API access solely to:

• Upload beat videos and YouTube Shorts to your channel as you request
• Set video titles, descriptions, and tags based on your templates
• Add videos to playlists you specify
• Display upload status and video URLs within the BeatOps interface

3.3 YouTube Data Storage

Regarding YouTube data:

• We store OAuth access tokens securely to maintain your connection
• We store YouTube video URLs and IDs for your uploaded content
• We do NOT store copies of your YouTube videos on our servers
• We do NOT access your YouTube viewing history or subscriptions

3.4 Revoking YouTube Access

You can revoke BeatOps' access to your YouTube account at any time:

• Via BeatOps: Use the "Disconnect" button in Settings. Your YouTube authorization data is deleted immediately.
• Via Google: Visit your Google Security Settings and remove BeatOps. Your YouTube authorization data is deleted immediately upon detection.

Upon revocation, we delete your stored OAuth tokens and YouTube channel information. Previously uploaded videos remain on your YouTube channel (we do not delete content from YouTube).

3.5 Sharing, Transfer, and Disclosure of Google User Data

BeatOps does not share, transfer, or disclose Google user data to any third parties, except in the following limited circumstances:

• YouTube (Google): We transmit video files and metadata (titles, descriptions, tags) to YouTube on your behalf when you initiate an upload. This is the core functionality of the service.
• Legal requirements: We may disclose data if required by law, legal process, or government request.

We do not:

• Sell or transfer Google user data to third parties for advertising, data brokering, or any other purpose
• Use Google user data to serve advertisements
• Use Google user data for credit assessment, lending, or any purpose unrelated to providing the BeatOps service

3.6 Google API Services User Data Policy

BeatOps' use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

In addition to this Privacy Policy, your use of YouTube features is also governed by the Google Privacy Policy.

3.7 Bring Your Own Key (BYOK) Credentials

BeatOps allows you to optionally provide your own YouTube API credentials (OAuth Client ID and Client Secret) from your Google Cloud Console project. This is called "Bring Your Own Key" (BYOK).

What We Store (BYOK Mode)

• Your OAuth credentials are stored locally on your computer in encrypted form
• Credentials are encrypted using Fernet symmetric encryption with a locally-generated key
• Stored at: ~/.beatops/credentials/youtube_client_config.json (encrypted)
• We do NOT transmit your credentials to our servers

Your Responsibilities (BYOK Mode)

When using BYOK, you are responsible for:

• Managing your own Google Cloud project and YouTube API quota
• Complying with YouTube API Terms of Service and Google Cloud policies
• Protecting your OAuth credentials from unauthorized access
• Monitoring your own API usage and quota consumption

Quota Tracking

When using BYOK, BeatOps tracks your YouTube API quota usage locally to help you monitor consumption. This data is stored in your local database and is never transmitted to our servers.

Deleting BYOK Credentials

You can remove your BYOK credentials at any time via Settings > YouTube API Credentials > Remove. This deletes the encrypted credential file from your computer. After removal, you will need to reconfigure your credentials to use YouTube features.

3.8 SoundCloud API Credentials (Required)

SoundCloud's Terms of Service require each application to use unique API credentials. SoundCloud requires each user to register their own application at soundcloud.com/you/apps.

What We Store (SoundCloud Credentials)

• Your OAuth credentials (Client ID and Client Secret) are stored locally on your computer in encrypted form
• Credentials are encrypted using Fernet symmetric encryption with a locally-generated key
• Stored at: ~/.beatops/credentials/soundcloud_client_config.json (encrypted)
• OAuth access and refresh tokens are also stored locally in encrypted form
• We do NOT transmit your credentials to our servers

Your Responsibilities (SoundCloud)

When using SoundCloud with BeatOps, you are responsible for:

• Registering your own SoundCloud application
• Complying with SoundCloud API Terms of Use
• Protecting your OAuth credentials from unauthorized access
• Understanding that your uploads go directly to your SoundCloud account

Deleting SoundCloud Credentials

You can remove your SoundCloud credentials at any time via Settings > SoundCloud API Credentials > Remove. This deletes both the encrypted credential file and your OAuth tokens from your computer. After removal, you will need to reconfigure credentials to use SoundCloud uploads again.

4. How We Use Your Information

We use the information we collect to:

• Provide, maintain, and improve our service
• Process your beat uploads and content generation requests
• Upload content to YouTube and other platforms on your behalf
• Send you service-related communications
• Respond to your inquiries and support requests
• Monitor and analyze usage patterns to improve user experience
• Detect and prevent technical issues or abuse

4.1 What We Do NOT Do With Your Data

• We do NOT sell your personal information to third parties
• We do NOT share your data with third parties for advertising purposes
• We do NOT use your YouTube data for any purpose other than providing the BeatOps service
• We do NOT serve advertisements within BeatOps

5. Third-Party Services

We use the following third-party services:

5.1 YouTube (Google)

For video uploads and playlist management. See Section 3 for details.

5.2 SerpAPI

For image search functionality. When you search for images, we send search queries to SerpAPI. SerpAPI's privacy policy is available at serpapi.com/privacy-policy.

5.3 Payment Processing (Stripe)

For subscription payments, we use Stripe as our payment processor. Stripe is PCI DSS Level 1 compliant, the highest level of certification available in the payments industry.

What we store:

• Your email address (for account identification and license delivery)
• Subscription status and tier (e.g., Growth, Scale)
• Subscription dates (start, renewal, cancellation)
• Whether you're an early adopter

What we do NOT store:

• Full credit card numbers
• CVV/security codes
• Complete card details

All payment card information is handled directly by Stripe and never touches our servers. For more information about how Stripe handles your payment data, see Stripe's Privacy Policy.

How we use your payment email:

• Sending your license key upon purchase
• Important subscription updates (payment issues, renewal reminders)
• Product updates and feature announcements (you can opt out)

We do not send marketing emails without your consent. You will never be subscribed to promotional emails without explicitly opting in.

5.4 Cloudflare

Our website is hosted on Cloudflare Pages for security and performance.

5.5 Error Reporting (Sentry)

To identify and fix software errors, BeatOps sends anonymous error reports to Sentry when errors occur in the desktop application.

What We Collect

Anonymous error reports including stack traces, application state, and action breadcrumbs. File paths, usernames, email addresses, beat names, API credentials, and IP addresses are automatically removed before transmission.

Default State and Opt-Out

Error reporting is enabled by default. You can disable it at any time in Settings. To disable error reporting, go to Settings and turn off the Error Reporting toggle. Changes take effect on the next application restart.

Data Retention

Error reports are retained for 90 days and then automatically deleted.

For more information, see Sentry's Privacy Policy.

5.6 Website Analytics (Umami)

To understand how visitors use our website, we use Umami Cloud, a privacy-focused analytics service.

Privacy-First Design

Umami does not use cookies, does not track users across websites, and does not collect personal information. Because Umami does not use cookies or collect personal data, no consent banner is required under GDPR for website analytics.

What We Collect

Anonymous pageview counts, referrer URLs, browser type, and country (derived from IP address, which is not stored).

Scope

Website analytics applies only to beatops.io. The BeatOps desktop application does not track website-style analytics.

6. Data Security

We implement appropriate security measures to protect your information:

• OAuth tokens are encrypted at rest
• All data transmission uses HTTPS encryption
• Access to user data is restricted to authorized personnel
• Regular security reviews and updates

However, no method of transmission over the Internet or electronic storage is 100% secure. While we strive to protect your information, we cannot guarantee absolute security.

7. Data Retention

• Account Data: Retained while your account is active and for a reasonable period afterward for legal and business purposes.
• Beat Data: Stored locally on your device. We do not retain copies of your audio files.
• OAuth Tokens: Retained until you disconnect your account or revoke access.
• Usage Logs: Retained for up to 90 days for operational purposes.

8. Your Rights

You have the right to:

• Access: Request a copy of the personal data we hold about you
• Correction: Request correction of inaccurate personal data
• Deletion: Request deletion of your personal data
• Portability: Request transfer of your data to another service
• Revoke Access: Disconnect YouTube and other third-party integrations at any time

8.1 How to Request Data Deletion

You can request deletion of your data in the following ways:

• YouTube data: Use the "Disconnect" button in BeatOps Settings, or revoke access via Google Security Settings
• Account data: Contact us at [email protected] with the subject "Data Deletion Request"

We will process deletion requests within 30 days and confirm completion via email.

9. Children's Privacy

BeatOps is not intended for users under 13 years of age. We do not knowingly collect personal information from children under 13. If you are a parent or guardian and believe your child has provided us with personal information, please contact us.

10. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page and updating the "Last updated" date. You are advised to review this Privacy Policy periodically for any changes.

11. Contact Us

If you have questions about this Privacy Policy or our data practices, please contact us at:

Email: [email protected]