FileFiddler
PRIVACY

Privacy at FileFiddler

FileFiddler is designed to keep file processing local whenever practical. This page also explains the cookies and identifiers that may be used when Google advertising is present.

Last updated: October 5, 2026

Browser processing

Most FileFiddler tools process selected files directly in your browser. For those tools, FileFiddler does not intentionally upload the original selected file to FileFiddler servers.

Passport & ID Photo Maker: the selected portrait is processed in the browser for face landmarks, portrait matting, background replacement, resizing and print-layout generation. The tool downloads browser AI/runtime files such as MODNet, MediaPipe and ONNX Runtime components, but this workflow does not intentionally upload the original selected portrait to FileFiddler servers.

Protected reconstruction tools

Some tools use the protected FileFiddler processing service at api.filefiddler.com for reconstruction logic while keeping the original file local.

JPG → Excel: image reading and OCR run in your browser. The protected service receives OCR text boxes and lightweight line geometry needed to reconstruct the spreadsheet. The original image is not sent by this workflow.

PDF → Excel: PDF text extraction runs in your browser. The protected service receives extracted text and page coordinates used to infer rows and columns. The original PDF is not sent by this workflow.

Split PDF by Category: page text is extracted locally and sent to the protected service to detect and assign category labels. The actual PDF splitting and downloadable output are produced locally in your browser.

Advertising, cookies and identifiers

FileFiddler uses third-party Adsterra advertising scripts to display banner and native advertisements on pages where ad placements are present. These third-party scripts may process technical information such as IP address, browser/device details, page URL and advertising identifiers, and may use cookies or similar technologies for ad delivery, measurement and fraud prevention. Google AdSense publisher verification metadata remains present, but Google AdSense ad serving is separate and is currently disabled.

If advertising is enabled, third-party vendors, including Google, may use cookies to serve ads based on a visitor's previous visits to FileFiddler or other websites. Google's advertising cookies allow Google and its partners to show ads that may be personalized using browsing activity, subject to the visitor's choices and applicable regional requirements.

Advertising services may also use technologies such as cookies, web beacons, IP addresses or other identifiers to deliver, measure and limit advertising. A page can contact advertising services when an advertising tag is loaded even if an ad is not ultimately displayed.

Visitors can manage or opt out of personalized Google advertising in Google Ads Settings. More information about how Google uses information from partner sites is available at Google's partner-sites privacy information.

Google AdSense may also make advertising inventory available to Google-certified ad networks and ad technology partners. Information about Google's current ad technology partners and the controls available to publishers is available in Google's ad technology partner information. Where an advertising or consent interface identifies a third-party vendor, users can follow the vendor information provided there or use applicable industry opt-out choices.

Before enabling advertising that requires consent, FileFiddler must configure the applicable consent controls. Personalized advertising for visitors in the EEA, UK and Switzerland requires a Google-certified consent management platform integrated with the IAB Transparency and Consent Framework. Advertising remains disabled while that configuration is unverified.

Advertisement