AnonShortsGo to the app

Privacy Policy

Last updated: 2026-11-15Effective: [TO_BE_FILLED_BY_OWNER: effective date]Version: 2.0.0

This policy explains what personal data AnonShorts collects, why, who we share it with, how long we keep it and what rights you have. It applies to the website at anonshorts.com and the app at app.anonshorts.com (together, the "Service").

1. Who we are

The Service is run by [TO_BE_FILLED_BY_OWNER: company legal name] ("AnonShorts", "we", "us"), of [TO_BE_FILLED_BY_OWNER: company registered address].

For the data described below, we are the "controller" (GDPR) or "data fiduciary" (India DPDP Act). Paddle acts as an independent controller for payment data.

2. Data we collect

Account data. Your email address, your name, and a password hash (we never store your password in readable form). If you sign in with Google we receive your Google name, email address and profile picture.

YouTube and Google data (only if you connect a channel). When you connect YouTube we ask Google for the permissions (scopes) listed in section 5. We then receive and store your channel ID, channel name, handle, thumbnail and subscriber count, your channel's video list and metadata, and your channel and video analytics (for example views, watch time and retention). If you use calendar scheduling we can read and write events on your Google Calendar. Google gives us OAuth access and refresh tokens, which we store encrypted.

Content you create. Topics, prompts, scripts, voiceovers, captions, storyboards, rendered videos and thumbnails, drafts, research reports, your channel settings and "channel brain" (the saved style, topics and learnings for your channel), autopilot settings and queue, calendar schedules, and any music or caption assets you upload.

Support data. Messages you send to support, and up to three attachments of up to 5 MB each per message. If you choose to include diagnostic context with a ticket, that context is included too.

Billing data. Payments are handled by Paddle, our Merchant of Record. Paddle collects your card or wallet details, billing name, address and tax details. We never see or store your full card number. We store the plan you bought, transaction, subscription and invoice references, amounts, currency, billing country, status, your credit balance and credit ledger, and any refund records. We also store a record of the legal documents version you accepted, with the time, your IP address and browser user agent.

Technical data. IP address, browser user agent and request identifiers in our server logs and for rate limiting and abuse prevention; login session records (we keep only a hash of your refresh token); and your cookie consent choice (see the Cookie Policy).

Notifications. If you turn on push notifications, we store a device token with Google Firebase Cloud Messaging so we can tell you when a video finishes rendering. We send transactional email (for example password resets) through Resend. If you opted in at sign-up, we also send product updates by email.

We do not use advertising trackers or sell personal data.

3. Why we use your data

PurposeDataLegal basis (GDPR)
Create and secure your account, sign you inAccount data, session recordsContract
Generate scripts, voiceovers, captions and videos for youContent you createContract
Connect to YouTube, publish approved videos, show your analytics, schedule on Google CalendarYouTube and Google dataContract and your consent to the Google permissions
Take payment and manage subscriptions and creditsBilling dataContract and legal obligation (tax, accounting)
SupportSupport dataContract and legitimate interests
Prevent abuse, secure and debug the ServiceTechnical dataLegitimate interests
Prove which terms and cookie choices you acceptedAcceptance and consent recordsLegal obligation and legitimate interests
Product update emailsEmail addressConsent (you can withdraw any time)

4. How content is processed

Text generation (topic ideas, scripts, storyboards) is done by Cloudflare Workers AI. Voiceovers and captions are generated by default on our own servers. Stock footage is searched on Pexels using keywords from your script, not your account details. Videos are rendered on servers we run at Hetzner in Germany. We do not use your content to train AI models. Your account has an AI-training preference which defaults to opted out.

Nothing is published to your YouTube channel until you approve it, or until you turn on an autopilot mode that publishes on your behalf. You can pause autopilot at any time.

5. Google and YouTube data and Limited Use

AnonShorts's use and transfer of information received from Google APIs to any other app will adhere to Google API Services User Data Policy, including the Limited Use requirements.

In practice:

Scopes we request:

ScopeWhat it is used for
openid, userinfo.email, userinfo.profileSign in with Google, and show your name, email and picture
youtube.readonlyRead your channel details and list of videos so you can pick a channel and see its content
youtube.uploadUpload and set the title, description and settings of videos you approve
yt-analytics.readonlyRead channel and video analytics to show performance and guide topic suggestions
calendar.events, calendar.readonlyCreate, update and delete publishing events on your Google Calendar and read your calendar list. Requested only if you use calendar scheduling

AnonShorts is not affiliated with or endorsed by YouTube or Google. YouTube is a trademark of Google LLC. Use of YouTube is also subject to the YouTube Terms of Service and the Google Privacy Policy.

6. Who we share data with (sub-processors)

ProviderWhat forDataLocation
Hetzner Online GmbHCloud servers that run the API, background jobs and video renderingAll data the Service processesGermany
MongoDB AtlasMain databaseAccount, content metadata, billing recordsFrankfurt, Germany
CloudflareWebsite and app hosting (Pages), Workers, R2 file storage for videos and backups, Workers AI text generation, network tunnel and CDNContent you create, files, traffic dataGlobal network
PaddleMerchant of Record: payments, taxes, invoices, receiptsBilling dataSee Paddle's policy
ResendTransactional and update emailEmail address, name, messageSee Resend's policy
GoogleSign in, YouTube Data and Analytics APIs, Calendar, Firebase push notificationsAs in section 5Global
PexelsStock footage searchSearch keywordsSee Pexels's policy

We will update this list before adding a provider that handles your content or personal data. We may also disclose data if the law requires it or to protect rights and safety.

7. International transfers

Our main servers and database are in Germany. Some providers (Cloudflare, Google, Paddle, Resend, Pexels) may process data outside your country, including in the United States and India. Where the law requires it we rely on safeguards such as the European Commission's Standard Contractual Clauses or the provider's data protection terms.

8. How long we keep data

DataRetention
Account and profile dataUntil you delete your account
Rendered videos and thumbnails in storageAutomatically deleted 30 days after creation. Your published YouTube videos are not affected
Draft and unpublished mediaRemoved after 30 days
Videos you deletePermanently removed after 30 days
Temporary render filesDeleted within 24 hours
Login sessionsExpire automatically (refresh sessions last 7 days) and records are purged 30 days after expiry
YouTube tokens and cached YouTube dataDeleted within 7 days after you disconnect the channel or delete your account
Database backupsTaken nightly and kept for up to 30 days, then automatically deleted
Billing records, invoices, credit ledger, refunds, and records of accepted termsKept after account deletion for as long as tax, accounting and legal rules require, and to handle disputes
Support ticketsKept while needed to help you and to handle disputes. Ask us to delete them

What account deletion does

When your account is deleted we: revoke our Google access tokens at Google; delete your profile, login sessions, channels and connections, videos, scripts, drafts, jobs, publishing queue and history, analytics, channel brain and memory, research, caption and music assets, notifications and push tokens; and delete stored video files we hold. Video files in cloud storage are removed by the 30-day expiry above. We keep the billing and legal records listed in the table. Deleted data can remain in backups until they expire (up to 30 days) and is not restored except to recover from a failure.

9. Your rights

Depending on where you live you may have the right to access your data and get a copy in a portable format, correct it, delete it, restrict or object to some processing, withdraw consent at any time (for example for product emails or the Google permissions), and complain to your data protection authority. In India you may also nominate someone to exercise your rights and use our grievance process.

To use these rights, email [TO_BE_FILLED_BY_OWNER: privacy contact email]. We will verify it is you and reply within 30 days. Product emails can be turned off with the unsubscribe link in them. Cookie choices can be changed as described in the Cookie Policy. Withdrawing consent does not affect processing before you withdrew it.

10. Security

We use encrypted connections (HTTPS) between you and the Service. Passwords are stored as bcrypt hashes. Google access tokens are stored encrypted. Login uses short-lived access tokens and rotating refresh tokens that we store only as hashes. Access to the database and servers is restricted, and we rate-limit login and registration. Our database is backed up nightly. No system is perfectly secure, and we cannot guarantee absolute security. If a breach affects you we will notify you and the authorities as the law requires.

11. Children

The Service is not for anyone under 18, and we do not knowingly collect data from children. If you think a child has registered, contact us and we will delete the account.

12. Cookies and local storage

We use browser storage that is strictly needed to keep you signed in and remember your choices. Details are in the Cookie Policy.

13. Changes to this policy

We may update this policy. For material changes we will give notice in the app or by email. The date at the top shows the current version. Older versions are available on request.

14. Contact and complaints

Contact: [TO_BE_FILLED_BY_OWNER: privacy contact email], [TO_BE_FILLED_BY_OWNER: company registered address].

Grievance officer (India): [TO_BE_FILLED_BY_OWNER: grievance officer name and email].