1. Controller and contact
LocalFileLab is a source-available project by WiSie98. The operator of each deployment is responsible for personal data processed by that website. Technical project requests can be submitted through GitHub. Do not publish sensitive personal data or confidential files there.
2. Local file processing
When you select a file, the website receives browser access to that specific file. Conversion, compression, PDF processing and OCR run in the current tab using JavaScript, WebAssembly, browser codecs and, where available, WebCodecs. The file is not sent to a LocalFileLab conversion server.
Outputs are temporary object URLs that remain until removed, reloaded or the tab is closed. Downloads are 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.
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.
7. No accounts or file analytics
LocalFileLab has no user accounts or server-side file history. File names and contents are not sent to LocalFileLab for analytics, training or profiling. The site currently uses no first-party web analytics system.
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
This policy changes when features, providers or legal requirements change. A public deployment should add the operator's full legal name, service address and a private privacy contact channel.
Local file processing protects file contents, but does not replace disclosures for hosting, external resources and advertising.