Privacy policy
SplashCut is a video editor that runs in your browser. Your footage is yours; this page says exactly where it goes, which is almost nowhere.
Last updated: November 2026 · Applies to SplashCut
The short version
Projects, recordings and exports are written to your browser’s own storage. Nothing is uploaded, and there is no account. The only features that send anything anywhere are Google Drive sync, which you switch on yourself, live transcription, which is disclosed below, and the Google AdSense ad that can appear in the export gate. There is no analytics SDK and no SplashCut cross-site tracking.
1. What is stored on your device
- Projects and media — timeline data, uploaded clips, recordings and generated audio, kept in IndexedDB in this browser.
- Preferences — theme, language, panel layout and onboarding state, kept in localStorage.
- Cached engine — the FFmpeg WASM build, kept in the browser Cache API so the editor does not re-download it.
None of this reaches us. It does mean the browser can clear it — under storage pressure or when you clear site data — so keep your own copy of anything you cannot lose. The editor can export a portable .evp project file for exactly that reason.
2. Google Drive (optional)
If you sign in, projects are saved to your own Google Drive under My Drive / AddToCut. The app requests three scopes: drive.file (only files this app creates — it cannot see the rest of your Drive), plus your basic profile and email so the interface can show who is signed in. The access token is held in memory only, never written to storage, and expires with the session. You can revoke access at any time from your Google account’s security settings, and signing out clears the session immediately.
If you publish a share link, the project file and its media are made readable by anyone with that link, in your Drive. “Stop sharing” removes that permission, and the link stops working.
3. Live transcription (the one feature that leaves your device)
Captions can be generated with your browser’s speech recognition. In Chrome and Edge that means recorded audio is sent to Google to be transcribed. We never receive or store it; the finished captions are written into your project locally. Firefox does not offer the API, so captions there are typed by hand. Nothing is recorded or sent until you start the feature.
4. Third parties the app actually uses
| Service | Why | What it receives |
|---|---|---|
| Cloudflare | Hosting, CDN, TLS | Standard request logs (IP, user agent) |
| Sign-in, Drive, speech recognition, optional fonts | Only what each feature above describes | |
| Google AdSense | The optional export ad gate | Ad-request data (IP, user agent, ad-page URL); may set advertising cookies |
| Pexels, Unsplash, Openverse, Jamendo, GIPHY, KLIPY | Stock media search | Your search query, via our proxy — never your files |
| jsDelivr / unpkg | FFmpeg engine fallback | Standard request logs |
| formsubmit.co | The report-issue form | The message you type |
5. Analytics, ads and cookies
There is no analytics SDK, no advertising identifier and no SplashCut cross-site tracking. The editor itself contains no ads. When you start a video export, a same-origin popup loads Google AdSense so the export can stay free. Google may set advertising cookies and receive standard ad-request data (IP address, user agent and the ad page URL) when that ad is requested. You can manage ad personalization in Google’s Ads Settings.
If an ad blocker prevents the ad from loading, the gate shows a support link (Buy me a coffee or PayPal) and still lets you export. The only cookies this app itself relies on are the ones Google sets when you choose to sign in. The export ad page is excluded from search indexing and is never loaded inside the editor document.
6. Children
This app is not directed at children under 13, and no personal data is collected from anyone.
7. Changes and contact
Material changes will be reflected in the date at the top of this page. Questions, corrections or data requests: [email protected].