1. Controller and contact
LocalFileLab is a product of Crimson Anchor Interactive.
Address: August-Metz-Weg 1, 64297 Darmstadt. Contact: contact@crimsonanchorinteractive.com.
2. File processing in the browser
When you select, drop or open content through a project file, the website receives browser access to those specific files. Conversion, compression, inspection and document, data, image or audio editing run in the current tab through JavaScript, WebAssembly and available browser APIs. The file and its contents are not sent to a LocalFileLab processing server.
Previews and outputs are held in memory or exposed through temporary object URLs until removed, reloaded or the tab is closed. An intentional download or saved project file is stored at the location you choose.
3. Hosting and security logs
The hosting provider processes connection data required to deliver and secure the site, typically including IP address, time, requested URL, referrer, browser identifier and status code. Retention depends on the deployment's hosting configuration. Where applicable, the legal basis is legitimate interest in secure and reliable operation.
Cloudflare Web Analytics collects anonymous, aggregated performance and usage metrics without file contents, user accounts or a first-party cross-site profile. These metrics help assess availability and technical performance.
4. Local preferences
LocalFileLab stores language and color-scheme choices in browser localStorage. These entries contain no file contents and are not automatically sent to LocalFileLab. You can remove them in browser site settings. LocalFileLab does not store permission for a download folder; supported browsers ask for the save location again on every download.
5. External runtime components
Some media features download FFmpeg/WebAssembly files from jsDelivr. OCR may download Tesseract worker files and language models. Those providers receive normal connection data such as IP address and user agent, but not your selected file.
6. Google AdSense
LocalFileLab embeds Google AdSense. Google may process IP address, browser and device data, visited page, approximate location and cookie or advertising identifiers. Depending on consent and region, ads may be personalized, non-personalized or limited. Selected file contents are not shared with Google.
Where consent is required, it must be collected through a Google-certified consent management platform and can be withdrawn for the future.
Google and, where applicable, other advertising partners may use cookies or similar identifiers to select ads based on earlier visits to this or other websites. Personalized advertising can be controlled or disabled through the privacy settings and Google Ads Settings.
7. No accounts or file analytics
No registration.
Cloudflare Web Analytics collects anonymous, aggregated performance and usage metrics without file contents, user accounts or a first-party cross-site profile. These metrics help assess availability and technical performance.
8. Recipients and international transfers
Recipients of technical data may include the hosting provider, runtime-resource providers and, when ads are active, Google and its advertising partners. They may process data outside the EEA under their applicable transfer safeguards.
9. Your rights
- Access and correction.
- Deletion or restriction where the conditions apply.
- Data portability where applicable.
- Objection to processing based on legitimate interests.
- Withdrawal of consent for the future.
- Complaint to a competent data protection authority.
10. Changes
LocalFileLab is a product of Crimson Anchor Interactive.
Local file processing protects file contents, but does not replace disclosures for hosting, external resources and advertising.