Privacy Policy

Last updated: April 28, 2026

Callback is a tool that turns show recordings into short social-media clips. This policy explains what we collect, how we use it, and the choices you have. It applies to the Callback web app at callback.show.

Short version: We store the videos you upload, the transcripts and clips we generate from them, and the minimum personal information needed to log you in. We don't sell your data. We don't train AI models on your videos. We delete uploads 30 days after you stop working on a project.

Who we are

Callback is operated by Whittleworks LLC, a North Carolina limited liability company based in Charlotte, NC. In this policy "we", "us", and "Callback" refer to Whittleworks LLC. Questions or data requests: callback.show@gmail.com.

What we collect

When you sign in with Google, we receive and store:

Your Google account email, display name, and profile picture URL.
A Google-issued unique user ID so we can associate your projects with your account.

When you use the app, we store:

The video files you upload, import from Google Drive, or import from YouTube.
Derived artifacts from your videos: audio tracks, transcripts, laughter-detection data, AI-generated clip suggestions, and thumbnail images.
Edits you make to clips: boundaries, zoom keyframes, bleeps, captions, and render settings.
Project metadata like filenames, timestamps, and which team (if any) the project is owned by or shared with.
For team-owned projects: which YouTube channel (if any) is connected for auto-import, when its subscription renews, and which team members initiated the connection.

If you create or join a Callback team:

Your team membership, role (Owner / Editor / Viewer), and invite history.
For teams with a paid plan: the team's monthly minute quota, minutes used this cycle, billing cycle anchor, retention overrides (if any), and Stripe customer ID for invoicing.

If you subscribe to a paid plan:

Your Stripe customer ID and the active subscription tier. We do not store credit card numbers — Stripe handles payment data.
A history of usage events (analyses, top-ups, refunds) tied to your account.

Automatic usage data we collect:

Anonymous product analytics via Google Analytics and Microsoft Clarity — page views, button clicks, and session-level diagnostics like browser and device type. Clarity may record session replays of your interactions with the app.
Server logs from our backend that include your user ID, project ID, timestamps, and error details. Logs are retained for 30 days.

How we use your data

To run the Callback service: process your videos, generate clip suggestions, render exports, and show you your projects across sessions.
To debug problems and improve the product.
To communicate with you about your account if we need to (for example, about a service outage).

We do not sell your data. We do not use your videos, transcripts, or edits to train machine-learning models.

Who we share it with

We share the minimum necessary data with the following service providers, each bound by their own privacy commitments:

Google Cloud Platform — hosts our backend (Cloud Run), stores your uploaded videos and derived artifacts (Cloud Storage), stores project metadata (Firestore), and authenticates users (Firebase Auth).
Google Gemini API — receives transcripts and audio data to generate clip suggestions. Google states that paid Gemini API data is not used to train their models.
Groq — receives your audio to produce transcripts via Whisper.
Apify — receives YouTube video URLs you import (manually or via auto-import) to extract the underlying video file. Apify only sees the URL; we do not share your Google account info.
Resend — sends transactional email from us to you (project-expiration warnings, team auto-import digests). Receives your email address and the project names referenced in the email.
Stripe — handles payments for paid plans. Receives your name, email, and payment method. Stripe is the source of truth for credit-card data; Callback never sees it.
Vercel — hosts the frontend web app you're using right now.
Google Analytics and Microsoft Clarity — receive anonymous usage analytics.

If you share a project with a Callback "team," other members of that team can see your project. Team-owned projects are automatically visible to every team member based on their role. You control sharing and team membership in the app.

Google Drive integration

If you choose to import a video from Google Drive, Callback requests the drive.file OAuth scope. This scope is narrow: it only allows access to files you explicitly pick via Google's file picker. Callback cannot read, list, or modify any other file in your Drive. We read the file you pick once to copy its contents to our storage, and we do not retain your OAuth token after the import completes.

YouTube integration

Two optional features connect to your YouTube account, both using the narrow youtube.readonly OAuth scope:

Manual picker — when you create a project, the "Browse my YouTube uploads" affordance lists videos from your own channel so you can pick one to import. We call YouTube's API for your channel info, your uploads playlist, and per-video metadata (title, thumbnail, duration). The OAuth token is short-lived and is discarded when the picker closes.
Team auto-import — a team owner or editor can connect their YouTube channel so new uploads become team projects automatically. We store the channel's public ID, channel title, and a per-subscription secret used to verify webhook deliveries. We do not retain a long-lived OAuth refresh token: ownership is verified once at connect time, then we subscribe to YouTube's public PubSubHubbub feed for that channel. Disconnect at any time from the team panel.

For both features, the actual video file is extracted via Apify (see "Who we share it with" above). Callback does not modify or post anything to your YouTube account — the scope is read-only.

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

Email notifications

Callback sends two kinds of transactional email:

Expiration warnings — a heads-up a few days before a personal project's source video would be auto-deleted, so you can export anything you want to keep.
Team digests — for teams, a single digest to the team owner summarizing all projects entering the warning window. Individual editors don't get personal mail about team-owned projects.

Both kinds include a one-click unsubscribe link (RFC 8058) and respect the per-account preferences in your in-app Notification Settings.

How long we keep it

Uploaded source videos and derived artifacts: 30 days after the project's last modification, then automatically deleted. Teams on a paid plan may have an agreed-upon longer retention window — visible in the team's Billing panel.
Project metadata (name, timestamps, clip list): kept while your account is active.
YouTube auto-import subscriptions: kept while the team's connection is active. Disconnecting marks the subscription inactive immediately and removes the channel-to-team binding within 24 hours.
Server logs: 30 days.
Analytics data: per Google Analytics and Microsoft Clarity retention policies (typically 14–26 months).

If you delete a project, its videos and derived artifacts are deleted immediately; metadata records are removed within 7 days.

Your rights

You can:

Delete any project directly in the app — this removes the video and all derived data.
Request full account deletion by emailing callback.show@gmail.com. We'll delete your account and all associated projects within 30 days.
Request a copy of the data we hold about you by emailing the same address.
Revoke Callback's access to your Google account at myaccount.google.com/permissions.

Residents of the EU, UK, and California: you have additional rights under GDPR and CCPA, including the right to object to processing and the right to data portability. Email us to exercise these rights.

Security

Your data is stored in Google Cloud Platform under industry-standard security controls. Uploads and downloads happen over HTTPS. Access to the storage bucket is restricted to the Callback backend service account. We do not log or store your Google OAuth password — Google handles authentication.

Children

Callback is not directed at children under 13 and we do not knowingly collect data from them. If you believe a child has provided us with personal data, email us and we'll delete it.

Changes to this policy

We'll update this page if the policy changes. Material changes will be announced in-app. Continued use of Callback after a change means you accept the updated policy.

Contact

Questions, deletion requests, or other concerns: callback.show@gmail.com.