Privacy, in plain language.
OpenFileTools' released file-processing tools are designed to process selected files locally in the browser unless a page explicitly says otherwise. Files, visible signatures, decoded messages, generated documents, and other processing inputs stay on the device for browser-local workflows and are not uploaded to an OpenFileTools processing API.
Information we may collect
Our hosting provider may receive ordinary service information such as requested pages, approximate region, device type, security events, and referral source. We do not intentionally collect the contents of files processed by browser-only tools.
Clipboard access
Clipboard image data is read only when you explicitly paste an image with Ctrl+V / Cmd+V while a compatible OpenFileTools tool is focused. OpenFileTools does not continuously monitor your clipboard and does not upload pasted image data.
Loading an image from a URL
When you use a supported URL-loading control, your browser requests the image directly from the address you enter without sending user credentials. The remote website may receive ordinary request information such as your IP address and browser details. OpenFileTools does not receive or store the entered URL or image.
Trade reference data
Some Trade Studio workflows request public reference data through bounded OpenFileTools same-origin endpoints—for example UN Comtrade HS descriptions and first-pass partner-country trade data. Those requests retrieve public classification or market-reference records; they do not upload selected local files. The upstream public provider can receive ordinary server-to-server request information. Trade Studio labels the source and keeps important customs, tariff, policy, buyer, supplier, and regulatory decisions as verification steps rather than treating a reference lookup as a final ruling.
Cookies and device storage
Most tool inputs and results live only in browser memory. Smart File can temporarily place a selected file in this site's browser-local IndexedDB so an existing OpenFileTools tool can reuse the same file after navigation; that handoff is removed after the destination reads it and expired handoffs are rejected.
Community posts and abuse protection
If the Community feature is enabled and you choose to post, the display name, title, text, related tool, votes, comments, and timestamps you submit are stored so the discussion can be shown publicly. OpenFileTools does not require an email address for the initial Community experience. To limit automated abuse without storing raw IP addresses in the Community database, the service can derive a one-way rate-limit key from connection information and a private server secret. Do not post private files, passwords, account numbers, or other confidential or personal information.
Advertising review
OpenFileTools currently uses the AdSense publisher meta tag and ads.txt record to identify the site during Google AdSense account review. The current approval build does not load the AdSense advertising runtime and does not render Google display-ad units, so browser-local file contents are not sent to Google for advertising.
If advertising is enabled after approval, this policy will be updated before runtime ad code is activated. Private-communication workspaces such as the WhatsApp Chat Export Viewer and Email Archive Viewer are designated as non-monetized surfaces, and future ad placements will be restricted to eligible publisher-content pages. Applicable consent requirements will be implemented before advertising storage or personalized advertising is enabled where required.
Analytics
Google Analytics is not enabled in this release. A future analytics integration would be documented here before activation and must not transmit filenames, file contents, decoded messages, metadata values, or generated output.
Server-backed feature boundary
Community actions, deal/provider requests, and bounded Trade Studio reference lookups are server-backed features. They are separate from browser-local file processing. OpenFileTools does not silently switch a local file workflow into server conversion.
Questions
Privacy questions can be sent to contact@openfiletools.com.