Privacy policy

MyConvert converts files you choose to upload. This page describes what the service stores, how long it keeps it, and who else may process it. It is written for the public site and is not a contract for a separate business product.

Files you upload

When you convert a file, the bytes are stored on our server long enough to run the job and let you download the result. A guest download stays available for 30 minutes after the job finishes, then the file is deleted. If you sign in, results are kept for 24 hours. Failed guest uploads are removed promptly. We do not offer a library of your old files beyond that window.

The upload is tied to an essential session cookie so the same browser can check the job and download the result. Do not use the service for files you are not allowed to send to a third party.

Accounts

If you create an account we store your email address and a password hash, plus the time the account was created. Google or Apple sign-in, when configured, stores the provider's account link and the email that provider returns. You can sign out from the sign-in page. While signed in, the account page can delete conversion files and keep the sign-in, or delete the files and the account together. Security records of rejected uploads stay so the service can defend itself.

Cookies and similar storage

The cookie fac_guest is essential. It is HttpOnly, lasts about 30 days, and identifies the browser session that owns an upload. We do not use it as an advertising identifier. Your advertising choice is stored in this browser under the localStorage key fac.consent. That choice is not a cookie. Details are on the cookie policy.

Advertising

The product is free and may show ads. Ad scripts are not added to the page until you choose Allow ads. Until then you only see an empty reserved space, and only when ads are switched on for the site. Members see the same advertising treatment as guests. There is no paid plan to remove ads.

Product events

The site records a short event when you view a tool, upload, start a job, finish a job, download, or use sign-in. Each row stores the event name, the tool name when there is one, the page path, the time, and the session or account id. It does not store the file itself. These rows help us see whether the tools work. They are kept in our database.

Security records

If an upload is rejected, looks like an executable, or is part of abuse, we keep a security log with the reason, time, network address, and a file hash where we have one. Those records are for operating and defending the service.

Where processing happens

File conversion for this site runs in EU. Uploaded bytes and the result stay on that processing path until the retention window deletes them.

A future setting, App:Storage:EuOnly, can require object storage to stay in the EU. It is off in this deployment and does not change where files are stored yet.

Processors

Conversion runs on servers we operate, with PostgreSQL for the application data. A Redis instance may count rate limits. If you use Google or Apple sign-in, those companies process the sign-in. If you allow ads and an advertising script is configured, that provider processes the ad request under its own policy. We do not sell your files.

Contact

Privacy questions go to [email protected]. Include a support reference if the question is about a specific job.