PRIVACY POLICY

1. OUR PRIVACY COMMITMENT

Bleep That Sh*t! is designed with privacy as a core principle. In browser mode, transcription and censor rendering run on your device, and the media file is not uploaded for those operations. Studio is a separate upload-based workflow. This policy explains what data we collect, how we use it, and your rights.

2. DATA WE COLLECT

Account Information

When you create an account, we collect your email address through Supabase authentication. This is used for account management, password resets, and service notifications.

After email ownership is verified, we normalize the address by trimming surrounding whitespace and converting it to lowercase. We use an environment-specific secret key to create a versioned keyed fingerprint that records whether that verified email has claimed a Free Studio allowance. This pseudonymous record is not anonymous, cannot be read by browser users, and never stores the raw email, account ID, provider identity, IP address, or device identifier.

Payment Information

Payment processing is handled entirely by Stripe. We do not store your credit card number, bank account details, or other payment credentials. Stripe provides us with a customer ID and subscription status.

Usage Analytics

We use PostHog for product analytics and Google Analytics 4 for aggregate traffic, acquisition, and product improvement analytics. This includes page views, feature usage events, conversion events, and general interaction patterns. Analytics may use pseudonymous internal account, project, and job identifiers to connect product stages. It does not include the content of your media files, transcripts, selected words, file names, signed URLs, storage paths, or raw error messages.

For the call-recording privacy checker demonstration, analytics may include whether the synthetic walkthrough started, aggregate candidate-count bucket, candidate categories, confirm or reject action, demo-report export, signup CTA context, selected recording-platform category, coarse monthly-minute range, and selected server-workflow interests. If you continue through the static call-privacy signup intent, analytics may also record that an identified account reached Studio; the static intent is then removed from the URL and a content-free per-session de-duplication marker may remain. The page does not accept a visitor recording or transcript, and analytics do not include candidate values or masked context.

Error Reporting

We use Sentry for error monitoring. When an error occurs, technical details about the error (stack traces, browser info, and a pseudonymous account identifier) may be sent to Sentry to help us fix bugs. Before transmission, we filter authentication and analytics cookies, request query strings, signed URLs, storage paths, and internal project/job identifiers from structured request and diagnostic metadata. Exception messages and stack traces remain available for diagnosis. We do not intentionally attach media file content to error reports.

3. CLIENT-SIDE PROCESSING

When you use browser mode, transcription and censor rendering run locally using WebAssembly and Web Workers. The media file is not uploaded for those operations. The AI transcription model runs directly on your device. This mode requires no account.

The call-recording privacy checker demonstration runs locally over a controlled synthetic transcript. Its review decisions remain in the current tab's memory and are not stored as a Bleep project. The synthetic findings report is created locally and saved only when you request it. The page does not accept or process your recording.

4. CLOUD PROCESSING

When you opt into cloud transcription (available to registered users), the following occurs:

• Your audio file is uploaded to AWS S3 storage in the us-east-1 region.
• If you choose a file from Google Drive or Dropbox, we copy only the selected file into your project storage. We do not sync your drive, import other files, or store a persistent provider connection.
• Audio is split into chunks and processed by AWS Lambda functions using the Groq Whisper API for transcription.
• Audio chunks in temporary storage are deleted within 24 hours of processing.
• Transcription results (text and timestamps) are stored in your project record for the duration of your project's retention period.
• If you open the optional Tears of Steel sample, its licensed 15-second source and precomputed transcript are shared application assets. Your sample project, selections, and generated output remain tied to your account. The generated output uses the same retention period as your regular projects; the reusable sample record remains until you delete it or your account.

5. COOKIES AND LOCAL STORAGE

• Authentication cookies: Supabase sets cookies to manage your login session. These are essential for account functionality.
• Analytics cookies: PostHog and Google Analytics may set cookies for analytics when analytics consent is granted. If you are shown the cookie consent banner, you can decline analytics cookies there.
• IndexedDB: The browser-based processing mode uses IndexedDB (via Dexie) to cache transcription models locally for faster subsequent loads. Users can remove that cache by clearing the site's browser data. The call-recording checker does not persist recording, transcript, candidate, or review contents to IndexedDB or localStorage.

6. DATA RETENTION

• Free tier projects: Retained for 30 days from first successful transcription; unprocessed drafts are retained for 30 days from creation.
• Paid tier projects: Available while paid access is effective. When paid access ends, every surviving project and generated output is retained for at least 30 additional days from the effective end date. A later retention transition will not shorten a deadline already promised.
• Account data: Retained until you request account deletion. The deletion workflow removes account-owned application records and attempts to delete stored project media and the authentication identity from the services that hold them, subject to the limited eligibility record described below.
• Studio eligibility: The restricted versioned keyed email fingerprint is retained while the Free allowance eligibility program remains active, reviewed for necessity at least annually, and deleted if the program is retired. It survives account deletion solely to prevent repeat introductory-access claims.
• Cloud audio chunks: Deleted within 24 hours of processing.
• Feedback: GitHub reports and their screenshots, attachments, and logs do not follow Studio project expiry and are not automatically removed when you delete your Bleep account. They require separate removal from GitHub, including stored files and relevant history where applicable. Use Email privacy team to request access to or deletion of feedback and associated support records.
• Sample project output: The generated file follows your normal project retention period. The licensed source is part of the application, and the account-specific sample record remains until deleted.
• Inactive accounts: Balances are zeroed after 12 months of inactivity.

7. YOUR RIGHTS

You have the right to:

• Access your data: View your account information and projects through the dashboard.
• Delete your account: Request deletion from Settings at /studio/settings. The deletion workflow removes account-owned application records and attempts to delete stored project media and the authentication identity from the services that hold them. The restricted eligibility fingerprint described above is retained.
• Export your data: Download your processed files and transcriptions from your projects.
• Opt out of analytics: Contact us to opt out of PostHog analytics tracking, or decline analytics cookies through the cookie consent banner when it is shown in your region.
• Make a privacy-rights request: Use Email privacy team to ask about access, objection, restriction, or deletion rights for feedback, associated support records, or the retained eligibility record. Requests are evaluated under applicable law and, for the eligibility record, the documented abuse-prevention purpose.

8. THIRD-PARTY SERVICES

We use the following third-party services, each with their own privacy policies:

• Supabase — Authentication, database, and file storage
• Stripe — Payment processing
• AWS — Cloud transcription processing (S3, Lambda, Step Functions)
• Groq — Whisper transcription API (processes audio chunks only)
• Sentry — Error monitoring
• BugDrop (Bleep-operated) — Feedback collection and delivery through our own Cloudflare Workers deployment, as described above
• Cloudflare — Hosting and network/security processing for our BugDrop service. Cloudflare privacy policy
• GitHub — Private feedback Issue and attachment storage. GitHub privacy statement
• PostHog — Product analytics
• Google Analytics 4 — Aggregate traffic, acquisition, and product improvement analytics
• Google Drive and Google Picker — Optional file selection when you import a chosen Drive file into Studio
• Dropbox Chooser — Optional file selection when you import a chosen Dropbox file into Studio
• Resend — Transactional email delivery

9. CHILDREN'S PRIVACY

The Service is not intended for children 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 so we can take appropriate action.

10. CHANGES TO THIS POLICY

We may update this Privacy Policy from time to time. We will notify registered users of material changes via email. Continued use of the Service after changes constitutes acceptance of the revised policy.

11. CONTACT

Questions about this privacy policy? Email privacy team.