Privacy Policy

1. The short version

For nearly everything on this site, your file never leaves your device. There is no upload. We do not sell personal data, we do not run advertising trackers, and we do not train any model on your files.

The two things that do reach us are described in sections 3 and 4, and we would rather you read them than take the headline on trust.

2. Conversion happens in your browser

Almost every EMconvert tool runs entirely inside your browser. Your file is read from your own disk by the page, converted by code already downloaded to your device, and handed back to you as a download — the bytes never travel to us, because the app has no endpoint that accepts them.

The converters are ordinary open-source libraries running as JavaScript and WebAssembly on your device:

• PDF tools (merge, split, rotate, compress, images to PDF, text to PDF) — pdf-lib.
• PDF to JPG and PDF to Word — pdf.js reads the pages, and the text it finds is written into a new file locally.
• Image tools (convert, compress, resize, crop, rotate, upscale, HEIC to JPG) — the browser's own canvas, plus heic2any for iPhone photos.
• Audio and video tools — ffmpeg.wasm, a WebAssembly build of ffmpeg that runs in a worker on your device.
• Multi-file results are zipped locally with JSZip.
• Your download is produced from memory (a blob: URL). Nothing you convert is written to the site's storage in your browser, and it is gone when you close the tab.

3. What our server does receive

When you run a conversion, the page writes a job RECORD to our API so that your history and your plan limits mean something. The record is metadata, not content:

• The tool you used and the category it belongs to.
• For each file: its NAME, its source format, its size, and the output format you chose. The file name is the one piece of your own text in the record — if a file name is sensitive, rename it before converting.
• A session identifier stored in your browser (the "emconvert_session" key), so your history and credit wallet follow you between visits.
• A HASHED IP address for rate limiting and abuse detection. We store a keyed hash, not the address.
• Ordinary request logs: path, status, timing, response size and interface language, against the same hashed session and hashed IP.
• Account data if you create one: email address, plan, credit balance and ledger entries.

4. AI features send text to us

This is the one place where content you provide leaves your device, so it gets its own section.

When you ask a question in an AI panel, the text you typed is sent to our servers over HTTPS, together with your session identifier, and a record of the call (which tool, how many credits, when) is written to your history. There is no document upload in the AI panel today: it answers questions about a built-in sample contract that ships with the site, so no file of yours is involved.

Answers are currently pre-written responses about that sample, generated without a live model. When live model inference is switched on, the text you send will additionally be processed by the third-party model provider that produces the answer, and we will say so here before that happens.

Do not paste anything into an AI panel that you would not send to us in an email.

5. What your browser downloads from us

The site's code, fonts and icons come from emconvert.com. Audio and video tools additionally fetch the ffmpeg engine — about 31 MB, once per browser — from cdn.emconvert.com, which is our own storage bucket, not a third-party CDN. That fetch is an ordinary HTTPS file request: it reveals your IP address and browser to that host the same way any download does, and it carries nothing about the file you are converting.

The site loads no third-party fonts, scripts or images. Our content-security policy names only our own hosts and the analytics beacon in section 6, which is enforced by your browser, not just promised here.

6. Analytics

Our edge provider serves a small, privacy-preserving analytics beacon on each page. It counts page views and performance timings, sets no cookies, stores nothing in your browser, and does not follow you to other sites. Product analytics are aggregate counters keyed to a hashed session, never to a person.

We do not use advertising analytics, cross-site trackers, session recording, or heat-mapping.

7. How long we keep things

There are no converted files on our servers to keep or delete — for the in-browser tools we never had them. What has a retention window is the metadata:

• Job records (metadata only, including the file name): kept while your account exists, or up to 90 days for an anonymous session, whichever is shorter.
• AI request text: kept only as long as needed to produce and deliver the answer, plus the call record described in section 4.
• Hashed IP and abuse signals: 30 days.
• Request logs: 30 days.
• Billing and ledger records: kept as long as tax and accounting law requires.

8. Who processes data for us

We use infrastructure and payment providers acting as processors under contract: an edge/CDN provider for delivery, storage and bot protection, a database host for job records and wallets, and — once paid plans are live — a payment provider for checkout and invoices. Card numbers do not reach our servers. Processors act only on our instructions, and we do not sell or share personal data for advertising.

9. Your rights

Depending on where you live, you may have the right to access, correct, export or delete your personal data, and to object to certain processing. Write to [email protected] and we will respond within 30 days. If you have an account, deleting it removes your profile, wallet and job history. To clear an anonymous history, clearing this site's data in your browser discards the session identifier that links it to you.

10. Children

The service is not directed at children under 13 (or the minimum age in your country), and we do not knowingly collect their personal data.

11. Changes

If we make a material change — in particular, if any tool starts sending your file content to a server — we will update the "last updated" date, say so plainly in this document, and email account holders before the change takes effect. This English version governs.