Your files stay yours.
FileUp24 is designed so supported file-processing tools can run directly in your browser, with no need to upload your files to a FileUp24 server.
What stays local
PDF operations use pdf-lib and a Web Worker; page rendering uses pdf.js; image workflows use browser APIs; HEIC conversion is loaded only when needed. These tools do not require a FileUp24 upload endpoint.
Verify with DevTools
Open DevTools → Network and run a local tool. Look for network requests and confirm that no FileUp24 upload endpoint is carrying your file bytes. For a stronger check, load the tool first and then disable the network before processing a small local file.
Real browser limits
Browser memory is finite, so very large jobs can fail. Unlock PDF requires the password and supports the encryption formats listed on its tool page. The Sign PDF feature creates a drawn signature image rather than a cryptographic digital signature.
Optional accounts and preferences
Sign-in and account requests are handled through Supabase Auth. Favorites, recent tools and saved workflows are stored in this browser; they are not currently synchronized between devices. An account is not required to use the local file tools.
Site analytics
Google Analytics loads only after you allow analytics. You can decline or withdraw using Analytics preferences at the bottom of any page; all tools work without analytics. We remember your choice for 30 days in this browser. We measure known public page visits, using fixed page names and addresses without fragments or arbitrary query strings. We do not send document contents, filenames, form entries or account-page visits through this integration. For Merge PDF, Split PDF and the homepage sample, we also count processing starts, successful results, failures and download requests using fixed labels. Built-in samples are counted separately. Files selected in the Merge or Split picker are labeled user-selected; carried or unclassified files are counted separately and are not assumed to be customer documents. A download request does not prove that a file was saved. No raw error messages or file details enter these events. Previous analytics grants require a fresh choice before measuring this expanded set of tools; previous declines remain declined. Advertising measurement is a separate, optional choice: Allow analytics alone never enables it, including for existing analytics choices. If you explicitly choose Allow analytics and ad measurement, Google Analytics can share successful user-selected Merge PDF and Split PDF events with our linked Google Ads accounts to measure ad results. The landing address may then include only Google Ads click identifiers (gclid, gbraid or wbraid), and Google can use measurement cookies to associate tool use with an ad click. Personalized advertising and remarketing remain off. Choose Allow analytics to withdraw only ad measurement, or Use without analytics to withdraw both; advertising measurement cookies are cleared when it is withdrawn. Both choices expire after 30 days. If you allow analytics, Google receives technical connection and browser data and uses analytics cookies; these requests are separate from local file processing. A Global Privacy Control signal keeps analytics off. Hosting and account-service logs are separate from this optional analytics choice.
Remote MCP integration
MCP clients send file bytes to the FileUp24 server for processing and receive results in the response. The endpoint processes those requests in memory and does not implement file storage. Server and hosting logs have separate behavior; the browser-local processing statement does not apply to remote MCP requests.