Privacy Policy

Last updated: September 15, 2026

This page explains what data Loopipe ("we") collects when you use the service, how it's used, who it's shared with, and how long it's kept. Loopipe is currently in a demo / early-access phase — read the below with that in mind.

1. Data we collect

Data	Source	Purpose
Email address	Signup form / early-access form	Account login, onboarding email
Password	Signup form	Hashed with scrypt before storage — we never see or store your plaintext password
Your Groq / Pexels API keys	Account Settings	Stored encrypted (Fernet), used to generate scripts/visuals on your behalf
Your YouTube access token (OAuth)	Google's consent screen	Stored encrypted, used to upload videos and fetch stats on your behalf
Channel/video metadata	Your own input + the YouTube API	Showing your history and stats in the dashboard
Session cookie	Your browser	Remembering you're logged in — not a tracking/advertising cookie

2. YouTube/Google data — a specific note

When you connect your YouTube channel, we request the following scopes:

youtube.upload — to upload videos on your behalf
youtube.readonly — to read your channel's video list/history
yt-analytics.readonly — to read stats like views, retention, and subscriber counts

Your Google password never reaches us — the connection is made entirely through Google's own OAuth screen, and you can revoke access at any time from your Google account settings.

Google API Services User Data Policy Loopipe's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not use YouTube data for advertising, do not have humans read it, and do not sell it to third parties.

3. Who we share data with

Loopipe relies on the following subprocessors to function — each only sees the data it needs for its own job:

Google / YouTube — uploading videos, reading channel/stats (with your consent)
Groq — script/topic text generation (using your own API key; only the topic/prompt text you provide is sent)
Pexels — stock footage search (using your own API key; only search terms are sent)
Cloudflare R2 — temporary storage of generated video files
Neon (Postgres) — database hosting for account and dashboard data
Upstash (Redis) — running the video generation queue
Resend — sending onboarding/notification emails (your email address only)

We never sell or rent your data for advertising purposes.

4. How long we keep data

Generated video files: deleted from storage 24 hours after a successful YouTube upload — from that point, your copy on YouTube is the durable one. Videos left as an unpublished preview (dry run) are automatically deleted after 7 days.
Video thumbnails: kept indefinitely (a few KB each) so your history list keeps showing an image.
Account data (email, encrypted keys, video history metadata): kept until you delete your account.
Early-access email: kept until we've reached out / until you ask us to remove it.

5. Security

Passwords are hashed with scrypt (plaintext is never stored). Your API keys and YouTube token are stored encrypted (Fernet) in the database. All traffic is encrypted over HTTPS.

6. Your rights

You can remove your API keys from Account Settings at any time, and revoke the YouTube connection from your Google account. To have your account fully deleted, email us at the address below.

7. Changes

This policy may be updated during the demo phase — we'll notify you by email of any material change.

8. Contact

Questions: merhaba@loopipe.com