1. Privacy-first document work
Fileza is designed to keep PDF work simple and privacy-minded. Many tools process files directly in your browser. This means those files do not need to be uploaded to our servers for everyday tasks such as editing, merging, splitting, compressing, signing, or watermarking.
2. High-fidelity conversion services
Some Office-to-PDF workflows require a dedicated conversion worker to preserve layout, images, tables, fonts, and document structure. When such a service is enabled, the file is sent only for the requested conversion task and should be handled according to the server configuration you deploy for Fileza.
3. Information we may collect
We may collect basic website information such as device/browser type, page visits, tool usage events, contact form submissions, support requests, consent choices, and payment or subscription information if paid features are enabled later.
4. Information we do not need for normal browser tools
For browser-side tools, we do not need to view or store your document contents. File processing happens locally where supported by the selected tool.
5. Cookies, ads, and monetization
Fileza may include consent-controlled features such as advertising, affiliate links, analytics, pricing pages, or future account features. Where required, you will be given choices before optional tracking or advertising features are enabled.
6. Local storage
The website may use browser storage for preferences such as dark mode, temporary file handoff, recent review data, consent choices, and tool settings. You can clear this data from your browser settings.
7. Security
We use reasonable technical and organizational measures to protect the website and support workflows. You should still avoid uploading or sharing documents unless you are comfortable processing them with the selected tool.
8. API access, saved files, and provider processing
If you use API access, paid plans, saved file history, browser-rendered HTML-to-PDF capture, or high-fidelity provider routing, Fileza may process request metadata, job identifiers, tool names, billing status, credit usage, and temporary output links needed to complete the selected workflow. Provider secrets, API keys, OAuth secrets, raw session cookie values, and signed download URLs should never be exposed in public frontend assets or logs.
10. Contact
Privacy questions, API processing questions, billing requests, and provider-processing concerns can be submitted through the Support Center.