Cookies & Cache Policy
Last updated: June 1, 2025
This policy explains the cookies, browser storage and caching used by ClipForge AI.
1. Cookies we use
| Name | Purpose | Type | Duration |
|---|---|---|---|
| cf_session | Keeps you signed in (signed token, httpOnly, SameSite=Lax, Secure over HTTPS). | Strictly necessary, first-party | Up to 14 days, or until you sign out |
We do not use advertising, tracking or analytics cookies, so no cookie consent banner is shown. Strictly necessary cookies do not require consent under the ePrivacy rules; if we add non-essential cookies in future we will ask for your consent first.
2. Local storage
The app does not store personal data in localStorage or sessionStorage. Your browser may keep ordinary technical data (for example media buffers while previewing a video).
3. Caching
- Private data is not cached. API responses, video previews, downloads and signed-in pages are sent with
Cache-Control: no-store/privateso they are not kept by shared caches or proxies. - Static assets (scripts, styles, images, fonts) are cached by your browser and any CDN to make the app faster. They contain no personal data.
- Public pages such as this policy may be cached.
- Server-side temporary files created during processing are deleted when a job finishes; stored videos and clips are deleted per our retention schedule.
4. Managing cookies and cache
You can block or delete cookies in your browser settings, but the Service will not work without the session cookie. Signing out removes it immediately. To clear cached files, use your browser's "Clear browsing data" option.
5. Third-party content
YouTube thumbnails shown for projects are loaded from YouTube/Google image servers (for example i.ytimg.com), which can receive your IP address and browser information when the image is requested.