Effective date: April 20, 2026 · Last updated: April 20, 2026
This Privacy Policy describes how ClipSpeedAI ("we", "us", "our", or "the Service"), operated from Florida, USA, collects, uses, stores, discloses, and protects personal information when you use clipspeed.ai or any related ClipSpeedAI products. It also describes your rights and how to contact us.
We wrote this in plain English on purpose. If anything here is unclear, email support@clipspeed.ai and we will explain.
1. Who we are
ClipSpeedAI is a web-based productivity tool that helps content creators convert their own long-form videos into short-form vertical clips for YouTube Shorts, TikTok, Instagram Reels, and similar platforms. The Service is owned and operated by ClipSpeedAI, founded by Kyle White.
Location: United States (data hosted in US regions on Supabase, Railway, and Cloudflare)
2. Information we collect
2.1 Information you provide
Account information — your name and email address, provided via "Sign in with Google" or email signup.
Billing information — processed by Stripe. We do not see or store your full card number, CVV, or bank details. We only see a charge confirmation, the last 4 digits of your card, and your Stripe customer ID.
Content you upload or link — URLs of YouTube videos you process through ClipSpeedAI, and any custom titles, captions, or hashtags you enter.
2.2 Information we receive from third-party platforms
When you connect your YouTube, TikTok, Instagram, X, or LinkedIn account via OAuth, we receive:
OAuth access token and refresh token (encrypted at rest — see Section 7)
Your channel/profile ID and username on that platform
Limited metadata about content you own on that platform (titles, captions, view counts) — only what the API methods listed in Section 4 return
We never request or receive passwords for any third-party account.
2.3 Information collected automatically
Usage logs — IP address, browser user-agent, pages visited, features used, timestamps. Retained for 30 days for debugging and security, then deleted.
Device information — screen size, timezone, language (for rendering the UI correctly).
Your social security number, government ID, or other high-sensitivity identifiers.
Your precise location (beyond country-level inference from IP).
Content from third-party platforms that you do not own or have not granted us access to.
Any data from YouTube about users other than yourself.
3. How we use your information
We use the information we collect to:
Provide the Service: generate short-form clips from videos you submit, show you analytics, publish clips you authorize to third-party platforms.
Maintain your account, process payments, and send you transactional emails (receipts, password resets, service notifications).
Send product updates or marketing emails only if you opt in. You can unsubscribe anytime from the footer of any email.
Detect and prevent abuse, fraud, and violations of our Terms of Service.
Improve the Service: we may review aggregate, anonymized usage statistics to decide which features to build next. We never review individual user content without explicit permission.
Comply with legal obligations (tax records, lawful requests from authorities).
When you connect your YouTube channel via "Sign in with Google", Google's consent screen will show every scope we request. The scopes are:
Scope
Why we need it
openid, email, profile
To create your ClipSpeedAI account and identify you.
https://www.googleapis.com/auth/youtube.readonly
To read captions on videos you own (for accurate transcripts) and to display view / like / comment counts for Shorts you posted through ClipSpeedAI.
https://www.googleapis.com/auth/youtube
Required by Google alongside upload scope for quota and channel metadata when posting.
https://www.googleapis.com/auth/youtube.upload
To upload short-form clips to your own YouTube channel — only when you explicitly click "Post to YouTube Shorts".
4.2 YouTube API methods we call
These are the only four YouTube Data API v3 methods our application is capable of calling. The scopes above do not permit any others.
Method
Purpose
When it runs
youtube.channels.list (mine=true)
Verify your OAuth connection is live and fetch your channel ID for ownership checks.
Once at sign-in.
youtube.captions.list
Retrieve caption tracks for videos you own, so we can use your own captions for more accurate transcripts.
When you process one of your own YouTube videos and opt in to native captions.
youtube.videos.list (part statistics,snippet)
Display view / like / comment counts for Shorts you posted through ClipSpeedAI. We only query video IDs we ourselves uploaded on your behalf.
When you open the Performance dashboard, rate-limited to once per 60 seconds per video.
youtube.videos.insert (resumable upload)
Upload generated short-form clips to your own YouTube channel.
Only when you explicitly click "Post to YouTube Shorts" or schedule a post to a time you choose.
4.3 What YouTube data we store
Data
Where
How long
OAuth access token + refresh token
Supabase — protected in transit by TLS 1.2+, at rest by row-level security and restricted production access controls; AES-256 encryption column rollout is phased
Until you disconnect YouTube or delete your account
Your YouTube channel ID + email
Supabase
Until account deletion
YouTube video IDs of content you processed
Supabase
Until you delete the project or account
Captions / transcripts derived from your own videos
Supabase
Until project deletion
View / like / comment counts from videos.list
Supabase (dashboard cache)
Refreshed on demand, deleted on account deletion
4.4 What we do NOT do with YouTube data
We do not access videos you do not own.
We do not search for, browse, or analyze other creators' content.
We do not read or post comments on any video.
We do not post to your channel without an explicit action from you.
We do not use YouTube data for serving or targeting advertisements.
We do not sell YouTube data to any third party.
We do not use YouTube data to train artificial intelligence or machine learning models that could be used outside of ClipSpeedAI's own clip-generation features for you.
4.5 How to revoke our access to your YouTube account
You can revoke ClipSpeedAI's access to your YouTube account at any time in three ways:
In ClipSpeedAI — go to Settings → Connections → "Disconnect YouTube". Our stored OAuth tokens are immediately deleted.
In your Google Account — visit myaccount.google.com/permissions, find ClipSpeedAI, and click "Remove Access". Our stored token becomes invalid on the next API call.
By deleting your ClipSpeedAI account — go to Settings → Account → Delete Account. This cascade-deletes your tokens along with every project, clip, transcript, and related file.
(a) We use YouTube API data only to provide user-facing features of ClipSpeedAI that are prominent in the user experience.
(b) We do not transfer YouTube API data to anyone other than the service processors required to deliver those features (Supabase, Railway, Cloudflare — acting as data processors under agreement).
(c) We do not use YouTube API data for advertising.
(d) We do not allow humans to read YouTube API data unless (i) we obtained your affirmative consent for specific data, (ii) it is necessary for security, (iii) it is necessary to comply with law, or (iv) the data is aggregated and used for internal operations per YouTube's policies.
5. TikTok, Instagram, and other connected platforms
When you connect TikTok, Instagram, X (Twitter), or LinkedIn, the same principles apply as with YouTube: we request the minimum scopes required for posting and analytics, we store tokens encrypted at rest, and we never post without your explicit action. Each platform's own terms and privacy policy additionally govern their data.
6. Payments (Stripe)
We use Stripe as our payment processor. When you subscribe to a paid plan, your card information is submitted directly to Stripe over TLS. ClipSpeedAI's servers never see your full card number, CVV, or bank credentials. We only see the Stripe customer ID, the last 4 digits of the card, the brand, and subscription status. Refer to Stripe's privacy policy for details on how Stripe handles payment data.
7. Storage, encryption, and security
Hosting: our application runs on Railway (US regions).
Database:Supabase (PostgreSQL, US regions). Row-level security ensures you can only read/write your own rows.
Object storage:Cloudflare R2 (S3-compatible) for generated video clips and thumbnails.
Encryption in transit: all traffic uses TLS 1.2+.
Encryption at rest: OAuth tokens are protected by multiple layers — TLS 1.2+ in transit, Supabase row-level security so only the owning user's row is accessible, and strict production-access controls. AES-256 encryption functions (pgcrypto-based) are provisioned in the database and being rolled out to active token columns in phases so live sessions are not disrupted.
Access controls: production database credentials are held only by the founder. There is no customer-support tooling that can read OAuth tokens in plaintext.
Breach notification: in the event of an unauthorized disclosure of personal information, we will notify affected users by email within 72 hours of discovery and take reasonable steps to mitigate the impact.
8. Sharing of information
We share personal information only in these specific cases:
Service processors (Supabase, Railway, Cloudflare, Stripe, Resend, AssemblyAI, Deepgram, OpenAI/Whisper, ElevenLabs) that operate on our behalf under data-processing agreements. Each processor receives only the minimum data necessary to perform their function.
Third-party platforms you explicitly connect, when you authorize us to publish content there (e.g., YouTube Shorts, TikTok).
Legal obligations — in response to valid legal process such as a subpoena, court order, or law enforcement request. We will push back on overbroad requests and notify affected users where legally permissible.
Business transfer — if ClipSpeedAI is acquired or merged with another company, your information may transfer as part of the transaction. You will be notified and can delete your account before the transfer completes.
We do not sell personal information. We do not share personal information with data brokers, ad networks, or tracking companies.
9. Data retention and deletion
9.1 How long we keep data
Account + billing data: as long as your account is active, plus up to 7 years after account deletion for tax and legal compliance (Stripe transactions only; no content).
Generated clips + transcripts: until you delete them or delete your account.
OAuth tokens: until you disconnect a platform or delete your account.
Usage logs: 30 days, then purged.
Email logs (transactional): 90 days.
9.2 Deleting your data
You can delete your data at three levels:
Delete a specific clip — from your dashboard. The MP4 file and database row are removed immediately.
Delete a project — removes the project and all its clips, transcripts, and thumbnails. Cascading delete.
Delete your entire account — Settings → Account → Delete Account. This triggers a cascade delete of every project, clip, transcript, OAuth token, and uploaded asset. Associated files in object storage are enqueued for deletion and purged within 30 days. Stripe subscription records remain for tax compliance but contain no content.
If you are unable to delete your account through the UI, email privacy@clipspeed.ai and we will action it within 30 days.
10. Your rights (GDPR / CCPA / global)
10.1 Rights we offer to everyone, regardless of where you live
Access — request a copy of the personal information we hold about you.
Rectification — correct inaccurate data.
Erasure — delete your account and all associated data.
Portability — receive your data in a portable format (JSON) so you can take it to another service.
Objection — object to specific processing activities (e.g., marketing emails).
To exercise any of these rights, email privacy@clipspeed.ai. We will respond within 30 days.
10.2 For European users (GDPR)
Our lawful bases for processing are: (a) contract — to provide the Service you signed up for; (b) legitimate interest — to prevent abuse and improve the Service; (c) consent — for marketing emails and for any optional data use you opt in to; (d) legal obligation — for tax and compliance records.
You have the right to lodge a complaint with your local data protection authority.
10.3 For California users (CCPA / CPRA)
California residents have the additional rights to know what categories of personal information we collect, the business purpose for collecting it, and to whom we disclose it; to request deletion; and to opt out of the "sale" of personal information. We do not sell personal information under CCPA's definition. To exercise your rights, email privacy@clipspeed.ai.
11. Cookies and tracking
We use a small number of cookies, in roughly these categories:
Essential — session cookie for authentication (so you stay logged in). Cannot be disabled without breaking the Service.
Functional — remember UI preferences like dark mode.
Analytics (if enabled) — we may use a privacy-respecting analytics tool (e.g., Plausible) that does not set third-party cookies and does not fingerprint users. No data is sent to Google Analytics or Meta.
We do not use advertising cookies or cross-site tracking pixels.
12. Children's privacy
ClipSpeedAI is not directed to children under 13 (or under 16 in some jurisdictions) and we do not knowingly collect personal information from children. If you believe we have inadvertently collected information from a child, email privacy@clipspeed.ai and we will delete it promptly.
13. International users
ClipSpeedAI is operated from the United States. By using the Service, you consent to the transfer of your information to the United States and the processing of your information in the United States, which may have different data protection laws than your country. For users in the European Economic Area or the United Kingdom, we rely on appropriate safeguards for such transfers, including Standard Contractual Clauses with our data processors where applicable.
14. Changes to this policy
We may update this Privacy Policy from time to time as the Service evolves or as laws change. When we make material changes, we will notify you by email (to the address on your account) and by posting a notice on clipspeed.ai at least 14 days before the changes take effect. The "Effective date" at the top of this page will always reflect the latest version.
15. Contact us
If you have any questions about this Privacy Policy or our handling of your personal information, reach out:
This Privacy Policy complies with Google API Services User Data Policy (including Limited Use), YouTube Developer Policies, GDPR, CCPA / CPRA, and Florida state privacy law. If any provision conflicts with applicable law, the applicable law governs.