Privacy & advertising

Draft version: October 19, 2026. This notice describes the current converter implementation. The verified operator/controller identity and privacy contact remain pending.

Your file contents stay on your device

The converter reads selected files into your browser and creates results locally. The app has no file-upload API and does not send file contents, names or conversion results to advertisers, analytics services or an AI service. It does not persist your files in an app database or browser storage. Clear the queue or close the page to release the app’s references; browser or operating-system caches and files you downloaded may remain under your device’s control.

Hosting and access data

The hosting service receives ordinary page and network requests, which may include IP address, browser information, timestamps and requested URLs. This public site does not require visitors to sign in. The hosting platform may process authentication information when an owner signs in to manage access. Local file processing does not mean the website or hosting platform processes no personal information.

The operator must confirm hosting/security providers, data locations, retention periods, subprocessors and any international-transfer safeguards before publishing a final notice. Those details are not verified by this draft.

Cookies, storage and advertising

The converter does not set cookies, use local storage, fingerprint visitors or load third-party analytics or advertising networks. It offers optional first-party aggregate usage reporting, off by default. Two labeled sponsor placements are currently unbooked placeholders. The direct-sponsor renderer supports site-served text and an external sponsor link, without advertiser scripts, pixels or impression/click tracking. The hosting/access platform may use its own necessary authentication or security technologies.

If you choose to visit a sponsor, its separate website receives the visit and its own privacy terms apply. Sponsor links open a new tab without sending the page referrer. The converter does not append file information or tracking query parameters.

No advertiser receives your uploaded files. Before any advertising or analytics launch, this notice must identify the actual practices and providers, and any legally required consent or opt-out controls must work before those technologies activate. An ad-free plan will not remove essential security or account processing.

Optional usage reporting

You can choose to share usage counts with the unchecked checkbox in the converter. The choice lasts only for the current page, can be switched off at any time, and is not saved in cookies or browser storage. Conversion works without reporting. Reporting stays off when the browser signals Do Not Track or Global Privacy Control.

When enabled, the browser sends only an opt-in page-visit event, batch-start/finish events, and conversion attempts categorized by fixed input/output formats, success/failure and elapsed milliseconds (capped at ten minutes). No filenames, file bytes, previews, file sizes, download links, visitor IDs, location or browser/device profiles are included. Requests still expose normal network information to the hosting infrastructure.

The application immediately increments daily aggregate counters and total durations in its hosted database. It does not store individual event records, IP addresses, user agents, precise event timestamps or account identifiers in that database. Reports are restricted to the signed-in site owner. Totals older than 90 days are excluded from the dashboard and deleted when the next report is received; infrastructure logs/backups follow the hosting provider’s separate retention practices, which remain to be confirmed.

Opting out stops new events; existing anonymous aggregate totals cannot be linked back to an individual. Counts are incomplete and do not identify unique people. There is no advertiser access to these counts through the app.

Accounts, billing and support

The converter does not currently collect account registrations, payment details or support submissions. Future account and checkout information must be described before collection, including purposes, legal grounds where needed, recipients, retention and deletion rules. Payment-card details should be handled by a hosted payment provider, not the converter. Do not send sensitive files or payment credentials in support messages.

Your choices and rights

You control which files the browser processes and what you download. Depending on your location and the data processed, rights may include access, correction, deletion, objection, portability, consent withdrawal and complaints to a regulator. Mandatory rights are not waived. Requests concerning future operator-held data will need a monitored contact and a secure verification process before launch. We cannot delete copies you downloaded from your device.

Children, security and changes

The service is not designed for children under 13; account age and parental-permission requirements must be finalized for supported markets before signup launches. We do not knowingly collect children’s information through the converter. No system can guarantee absolute security. Security concerns need a monitored reporting channel before public launch. Material changes to data practices require an updated notice and any further notice or permission required by law.