VidWhale Terms of Service →

Privacy Policy

Effective date: 28 August 2026
This version replaces the policy dated 21 August 2026.

The short version: Some of what you create is stored on our servers so it can work across sessions and devices — your audit reports, saved drafts, and generated narration. Your reel videos are assembled in your browser, and any API keys you bring are stored only in your browser and never saved by us. We never sell your data. Questions: hello@vidwhale.com.

1. Who we are

VidWhale ("VidWhale", "we", "us") is a pre-publish content intelligence tool for video creators, operated from Dubai, United Arab Emirates. This policy explains what information we handle when you use vidwhale.com and the VidWhale application (the "Service").

2. Your account and sign-in

Most features that use our AI services require a free account. You sign in with Google; we request your basic profile (name, email address, and profile picture) and nothing else through sign-in. Signing in sets a session cookie (vw_session) that keeps you signed in for up to 30 days. This cookie identifies your account and is required for the Service to work; we do not use advertising or cross-site tracking cookies.

3. What we store on our servers

When you use the following features, the associated data is stored in our cloud infrastructure (Google Cloud, including Firestore and Cloud Storage), linked to your account:

Stored items have lifespans: finished reels are kept for 15 days and saved drafts for 45 days, after which they are automatically deleted. Audit reports stay in your Library until you delete them.

4. Analytics

We use Cloudflare Web Analytics to understand how many people visit the site and which pages they read. It does not use cookies, does not track you across other websites, and does not collect information that identifies you personally. Cloudflare processes this data on our behalf.

5. What stays on your device

Your reels are assembled inside your browser — the assembled video file is never uploaded to VidWhale. API keys you bring for third-party services (such as ElevenLabs, OpenAI, PlayHT, fal.ai, or video generation providers) are stored only in your browser's local storage; we never save them on our servers, and requests using them pass through only to the provider you chose.

6. AI processing

To produce results, the content you submit (such as scripts or frames) is processed by AI services acting on our behalf — Google's Gemini models and Microsoft Azure's text-to-speech — solely to fulfil your request.

7. YouTube account connection

You can optionally connect your YouTube channel. If you do, we request read-only access (youtube.readonly and yt-analytics.readonly) to show your channel statistics inside VidWhale. We store an encrypted refresh token so the connection persists; we can never post, upload, edit, or delete anything on your channel. You can disconnect at any time in the app or via your Google Account permissions page, which deletes the stored token. VidWhale's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

8. What we never do

We never sell your data. We never use your content to advertise to you. We never see or store the API keys you bring.

9. Deletion

You can request deletion of your account and stored data at any time — see our data deletion page or email hello@vidwhale.com.

10. Where your data lives and how long logs are kept

Our servers and storage run on Google Cloud in the us-central1 region (United States). Server logs are retained for up to 30 days for security and troubleshooting.

11. Your rights

Depending on where you live (including under the EU GDPR and the UAE Personal Data Protection Law), you may have rights to access, correct, export, or delete your personal data, and to object to or restrict certain processing. To exercise any of these, email hello@vidwhale.com and we'll respond as the law requires.

12. Children

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

13. Changes

We'll update this page when our practices change, with the effective date above.