Privacy notice

When you convert a file, the application stores the uploaded file in private application storage outside the public web directory. It records the original file name for display, the source and target formats, the file size, the job status, safe error codes, timestamps, and a random download token.

Conversion is performed by local open-source tools on the server. Files are not submitted to a paid conversion API or an external conversion service. The hosting provider still processes data as part of running the server and its network.

Files are not end-to-end encrypted while stored. Access is limited by server permissions and private storage paths, but the operator and hosting infrastructure can technically access stored data. Do not upload passwords, access keys, identity documents, financial records, medical records, or other highly sensitive files.

Source files are removed after processing. A completed result remains available through its temporary link for 1 hour(s). After that, the result is deleted automatically. Failed and expired jobs, stale queue records, and abandoned work directories are also cleaned up by the scheduled cleanup process.

You can delete the current job and its files from the result panel. The operator can also delete a job and its stored files from the protected admin area. The upload limit is 25 MB per file.

Deletion removes the application records and private files described here. It does not control independent copies that may exist temporarily in server backups, provider snapshots, or network logs. Backups and hosting logs follow the hosting provider’s retention policy.

Each job receives a high-entropy token. Anyone who possesses the token can read the status and download the result until the job expires or is deleted. Do not forward the result page or download link to people who should not have access. The current design does not provide user accounts, so there is no per-user ownership check beyond the token.

The contact form collects the name, email address, subject, and message you submit. The application also stores a one-way hash of the request IP address and a shortened user-agent string to help investigate abuse. The raw IP address is not stored in the contact message table.

Contact messages are not sent to a marketing platform or a third-party support service. They are stored in the application database and are visible to the operator in the protected admin area. Messages are kept until they are reviewed and deleted by the operator. Do not include sensitive files or credentials in a message.

The service uses an essential session cookie and a security token to keep forms working and to protect requests against cross-site request forgery. These are necessary for the service to function and are not used for advertising or cross-site tracking.

At present, this deployment does not use Google Analytics, advertising cookies, social media pixels, or other non-essential tracking cookies. It does not currently serve ads and does not load the Google advertising script.

If advertising is enabled in the future, Google AdSense and its partners may use cookies, web beacons, IP address, device and browser information, page interactions, and advertising identifiers to serve, measure, and limit ads. Google may use advertising cookies to serve ads based on a user’s prior visits to this and other websites. Non-personalized ads may still use cookies for frequency capping, aggregated reporting, and fraud prevention.

Advertising is disabled by default on this deployment. If it is enabled, Google and its advertising partners may process data as independent advertising providers. Their handling of data is governed by their own terms and privacy policies, not only by this notice.

You can learn how Google uses information from sites that use its services at policies.google.com/technologies/ads, review Google’s privacy policy at policies.google.com/privacy, and manage personalized advertising at adssettings.google.com.

If ads are enabled, this notice and the consent interface will be updated before the advertising script is loaded. The operator must not enable Google ads while this notice still says that advertising is disabled.

If the service targets visitors in the European Economic Area, the United Kingdom, or Switzerland, optional advertising and analytics technologies require an appropriate legal basis and, where required, prior consent. Essential cookies needed to deliver the page, session, and security protections are treated separately from optional advertising cookies.

Before enabling Google ads for those regions, the operator must integrate a Google-certified consent management platform (CMP), present a compliant consent choice, record consent, pass the consent signals to Google, and provide a way to withdraw or change consent later. The current deployment does not load an ad script, so no CMP is active. The application is configured so that Google ads remain disabled unless the operator explicitly sets both a valid AdSense client ID and the CMP readiness flag after testing the consent flow.

Where consent is required, personalized advertising and optional advertising cookies must not be used before consent is obtained. Withdrawing consent must be as easy as giving it. The CMP, not this static notice, is responsible for recording and communicating the visitor’s choices.

The application may record job status changes, safe error codes, durations, and request metadata such as IP address, user agent, and request time. It does not intentionally log document contents. Server and hosting logs may also record connection and error information under the hosting provider’s own retention policy.

No external conversion API is used. The main third party involved is the hosting provider that operates the server, network, and backups. If advertising or email delivery is enabled, Google, its advertising partners, or an email provider may process data in other countries under their own safeguards and terms. The operator must update this section before adding a new provider.

Measures include private storage, random download tokens, HTTPS, file-type and container checks, size and output limits, request rate limits, no macro execution, and restricted admin access. These measures reduce risk but do not make the service suitable for highly sensitive data, and no service can guarantee absolute security.

You can avoid uploading a file, delete a job from the result panel, wait for automatic expiry, or contact the operator about a specific message or conversion. Depending on where you live, you may also have rights to access, correct, delete, restrict, or object to processing, request portability, withdraw consent, or complain to a supervisory authority. Requests can be sent through the contact page.

Because jobs are not tied to accounts, the operator may be unable to identify a conversion without its private token or enough details to locate the record.

The service is not directed to children, and the operator does not knowingly collect personal information from children. If you believe a child submitted a file or message, contact the operator so it can be reviewed and removed.

This notice may change when the service, engines, retention period, hosting, advertising, or legal requirements change. The current version is the one shown on this page. Questions and privacy requests can be sent through the contact page. See also the terms of use and the FAQ.