Last updated 1 October 2026
Privacy policy
This policy explains what 240fps collects, why, how long we keep it, who processes it, and the choices you have. The short version: your work stays in your browser unless you sign in, share a link, add a website or subscribe.
1. Who we are
240fps (240fps.com) is a browser-based editor for device mockups and product videos, operated by Shaheer Malik (“we”, “us”). We decide how and why the personal data described here is processed. You can reach us with Send feedback in the editor’s 240fps menu; include an email address if you’d like a reply.
2. What stays on your device
When you’re signed out, your screenshots, recordings, music, logos, drafts and exports are stored only in your browser (IndexedDB) and never uploaded. Clearing your browser’s site data removes them. Exports are made in your browser too.
3. 240fps for Mac
The Mac app keeps your screen recordings and their edits in a folder on your Mac (Library/Application Support/240fps-desktop/Recordings); they’re never uploaded. Captions are transcribed on your Mac, and exports are saved where you choose. The app talks to 240fps.com to sign you in, check your plan and look for updates.
4. What we collect, and how long we keep it
We only collect what the features you use need:
| What | Details | Kept for |
|---|---|---|
| Your account | Name, email address and profile picture from Google, or name and email (possibly a private relay address) from Apple; when you signed up and last signed in | Until you delete your account |
| Sign-in sessions | A hashed copy of your session cookie and when it expires | Up to 60 days, then deleted |
| Projects and brand kit (signed in) | Your projects, the images, videos, music and logos in them, thumbnails, up to 40 earlier versions, and your brand kit | Until you delete them or your account |
| Share links | The image or video you shared, its title and a view count | Until you delete the link or your account |
| Website capture | The address you entered, the time, the screen size, your account and a salted, daily-changing hash of your network address | 90 days, then deleted |
| Subscription | Your plan, status, renewal date and Polar customer number | While you're subscribed, then as long as needed for tax and accounting |
| Payment webhooks | Delivery receipts from Polar, so a payment event is never applied twice | 30 days |
| Feedback | Your message, and your email address if you give one | Up to 2 years |
| Usage counts | Anonymous daily totals (for example, “an image was exported”), with no account, device or identifier | Kept as statistics |
| Product analytics (240fps.com) | Which pages and features you use, clicks and scrolling, your browser, device type and approximate country, and, if you're signed in, your account number (not your email). Typed text is never recorded. No IP address is kept, nothing is stored in your browser, and none of it is collected when your browser sends Do Not Track or Global Privacy Control | Up to 1 year in PostHog |
We don’t use advertising or tracking pixels, and we don’t sell or share personal data. Product analytics run through PostHog (below), only on 240fps.com.
5. Why we use it (legal bases)
- To provide the service you ask for (performance of a contract): your account, synced projects, brand kit, share links, website capture and your purchase (Lifetime, or a Pro subscription).
- To keep it working and fair (legitimate interests): rate limits and abuse prevention for website capture, security, and anonymous usage counts and product analytics that tell us which features are used and where people get stuck.
- To meet legal obligations: keeping subscription and transaction records for tax and accounting.
- To answer you (legitimate interests): feedback you send.
6. Websites you add
When you add a website, its address goes to our server, where a browser (Cloudflare Browser Rendering) opens the public page and sends pictures of it back to you. Only add pages you’re allowed to show; pages that need a sign-in can’t be captured anyway. The pictures are kept in your browser, and in your account if you’re signed in.
7. Figma import
If you import a Figma frame, your Figma personal access token is saved in your browser only and sent straight to Figma, never to us. Figma renders the frame, and your browser downloads the image. If Figma’s image server doesn’t allow a direct download, the image passes through our server on its way to you without being stored.
8. Who processes it for us
- Cloudflare: hosting, database, file storage, and the browser that renders websites.
- Google and Apple: sign-in. Their own privacy policies cover your Google account and Apple Account.
- PostHog (US Cloud): product analytics on 240fps.com, as described above.
- Polar (polar.sh): sells 240fps Lifetime and bills Pro subscriptions as the merchant of record, handling card details, invoices and sales tax under its own privacy policy. We never see or store your card.
These providers may process data outside your country, including in the United States. Where data protection law requires it, transfers rely on the providers’ standard contractual clauses or equivalent safeguards.
10. Your rights
Depending on where you live, you can ask to access, correct, export or delete your personal data, or object to or restrict how it’s used. You can do most of this yourself:
- Delete projects, versions and share links in the editor.
- Delete your whole account from the 240fps menu (Delete account). This removes your account, sessions, projects, versions, brand kit and share links, with their files, straight away. Cancel an active Pro subscription first.
- Manage or cancel your subscription from Manage subscription in the 240fps menu.
For anything else, contact us through Send feedback. You can also complain to your local data protection authority.
11. Children
240fps isn’t meant for children under 16, and we don’t knowingly collect their data. If you think a child has an account, tell us and we’ll delete it.
12. Security
Everything is sent over HTTPS. Sign-in sessions are stored only as hashes, projects and files are private to your account, and payment details never reach us. No system is perfectly secure, but we’ll tell affected users promptly if something goes wrong.
13. Changes
We’ll update this page when what we collect or how we use it changes, and change the date at the top. For significant changes we’ll also say so in the editor. See also our terms.