Privacy
This page explains what happens to your videos and what data LimitFix collects. It’s written to be read, not skimmed past.
Your videos
Normal use: compressed on your device
By default, LimitFix compresses videos inside your web browser using WebAssembly. The video is read from your device, processed there, and the result is saved back to your device. The video is not uploaded to us or to any third party. The compression engine (ffmpeg.wasm) is downloaded from our own servers; it doesn’t send your video anywhere.
Optional cloud processing (Pro)
If you switch on “Process in the cloud”, your video is uploaded to our server over an encrypted connection so it can be compressed there. The uploaded original is deleted as soon as compression finishes or fails. The compressed result is deleted shortly after you download it, and in any case within 30 minutes. Leftover temporary files are also removed automatically whenever the processing service restarts. We don’t look at, analyze or keep your videos.
The image tools work the same way: images are processed in your browser and never uploaded.
Metadata
Compressed files have hidden metadata removed, including GPS location, camera details and chapter information.
Data we collect
- Usage counters. To keep the free plan fair, we set a random identifier in a cookie (
lf_anon). It identifies this browser, not you, and it isn’t a fingerprint. We count free compressions per account, per browser identifier and per keyed hash of your IP address, and limit how many free accounts one browser can create. We never store your IP address itself. - Account data, if you create an account: your email address, your plan, credits and subscription status and — only if you chose one — a salted, hashed password (we can’t read it). If you sign in with Google or Apple, we also store the account identifier they give us, to recognize you next time. A session cookie (
lf_session) keeps you signed in. - Google and Apple sign-in: if you choose “Continue with Google” or “Continue with Apple”, you sign in on their page and they share your email address and an account identifier with us. We don’t receive your password or contacts. With Apple’s “Hide My Email” we receive a relay address that forwards to you. What happens on their side is covered by their own privacy policies.
- Rate limits: to stop abuse, such as repeated sign-in attempts, we briefly count requests per keyed hash of your IP address. Shared IP addresses are never blocked permanently.
- Basic technical logs kept by our hosting provider for security and reliability, such as request times and error reports.
- Sign-in codes: when you ask for one, your email address is passed to our email provider to deliver it. We store only a hash of the code, and it expires after 10 minutes.
We don’t collect file names, video contents or the length of your videos in analytics.
Analytics
Only if you allow analytics in the cookie banner, we count events such as “compression completed” or “download clicked” as daily totals, with coarse details like the destination you picked or a size range. These counters contain no identifiers or IP addresses. If enabled, we also use Plausible Analytics, which doesn’t use cookies and doesn’t collect personal data.
Advertising
On the free plan, pages may show ads served by Google AdSense — but only if you accept advertising cookies in the cookie banner. Otherwise no ads and no ad scripts are loaded. Once you accept, Google and its partners may use cookies or similar technologies to show and measure ads, and in some regions to personalize them. You can change your choice at any time from “Cookie preferences” at the bottom of every page. Learn more in how Google uses information from sites that use its services. Pro has no ads.
Payments
Payments are handled by Stripe. Card details go directly to Stripe and never reach our servers. We receive a customer reference, the product you bought and the status of your subscription. See Stripe’s privacy policy.
Cookies and local storage
lf_anon: random browser identifier for free daily limits and abuse prevention (necessary).lf_session: keeps you signed in, only if you have an account (necessary).lf_oauth: holds a random security value for a few minutes while you sign in with Google or Apple (necessary).lf_consent: remembers your cookie choice for about six months (necessary).lf-theme(local storage): remembers light or dark mode.lf-locale(local storage): remembers your language.- Advertising cookies set by Google on the free plan, only after you accept them.
How long we keep data
Account data is kept while your account exists and deleted when you ask us to close it; payment records may have to be kept longer where tax law requires it. Sign-in codes expire after 10 minutes, sessions after 30 days, daily usage counters after 48 hours (monthly Pro counters after 45 days), the record of accounts created in a browser after 30 days, rate-limit counters within a day, and the first-party analytics totals after 120 days.
Your rights
You can ask us for a copy of your account data, ask us to correct or delete it, or close your account at any time by writing to support@getlimitfix.com. Depending on where you live, you may also have the right to complain to a data protection authority.
Children
LimitFix isn’t directed at children under 13, and we don’t knowingly collect personal data from them.
Changes
If we change how we handle data, we’ll update this page and, for significant changes, tell account holders by email. Questions? Contact us.
LimitFix is operated by the LimitFix team.
