Privacy policy
Version 1.2 · Last updated
Summary
- Your images and documents stay on your device by default. 49 of 52 tools run entirely on your device. 9 of them can also use our conversion server for higher quality, only when you choose it for a file. The other 3 – OCR PDF, Repair PDF and PDF to PDF/A – need our server; files sent to it are deleted right after the result is returned. By default your files stay on your device. Some tools and optional modes send a file to our conversion server (convert.helpmejpg.com) only when you choose them; it is processed for that one request and deleted as soon as the result has been sent. The conversion service does not keep, log or share file names or file contents.
- No account is required. An optional account stores only your name, email and saved settings – we never store files, file names, image contents, document text or the passwords you use on documents.
- Analytics is switched off on this site. If it is ever enabled, it will run only after you accept a consent prompt and will never receive file names or image data.
- Advertising is switched off on this site. If it is ever enabled, ads will load only after consent and will never have access to the images you process.
- Because neither analytics nor advertising is running, there is nothing to consent to and no consent prompt is shown.
Who we are
HelpMeJPG is operated by NexuxLabs, which is the controller of the limited personal data described in this policy (technical request data, your consent choice where a prompt exists, optional account data and, where enabled, analytics and advertising data).
- support@helpmejpg.com
- Website
- www.nexuxlabs.com
Representative in the EU or UK. We are established outside the EU and the UK and have not appointed an Article 27 representative at this time; if one is appointed, their name and contact details will be published here. In the meantime address every request directly to us using the details above.
How image processing works
When you add an image to a tool, your browser reads the file into memory and the tool uses the HTML Canvas API, Web Workers and, for some formats, WebAssembly codecs (libwebp, MozJPEG, OxiPNG) that are downloaded as static files from this site. Processing results are kept in your browser's memory as temporary object URLs until you download them, remove the file or leave the page. Nothing is written to our servers, and nothing is written to your browser's persistent storage except the items listed under cookies and local storage.
The SVG to PNG and Favicon Generator tools sanitise SVG files before rendering them and block external resource loading, which also means an SVG cannot cause your browser to contact any third-party server during conversion.
Metadata. Image tools remove embedded metadata – EXIF camera details, capture date, GPS location and colour profiles – from every file they produce, after rotating the pixels to match the EXIF orientation. The one exception is a JPG made from a JPG: tick “Keep EXIF” (off by default) and the original EXIF block, GPS coordinates included, is copied into the result. Check a processed file before sharing it publicly if you turned that option on.
How PDF processing works
The PDF tools use two open-source libraries that run inside your browser: a PDF manipulation library (merging, splitting, rotating, cropping, watermarking, compressing, encrypting and decrypting) that executes in a Web Worker, and the PDF.js rendering engine for page previews, image export and text extraction, with its own worker and codecs served as static files from this site. In these browser tools documents never leave your device, previews are discarded when you remove the file, and scripts or actions embedded in a PDF are never executed – the tools only warn you that they exist. Tools and modes that use our conversion server instead are described under server processing.
Passwords you enter to open or protect a document are used in memory for that operation only. They are not stored, logged or sent to analytics, and the site has no way to recover them. If you forget a password you set with the Protect PDF tool, we cannot help you recover the document.
Metadata. PDF tools keep a document’s own metadata (title, author, subject, keywords, dates and embedded XMP) unless you turn on “Remove metadata” in Compress PDF; tools that build a new document – merge, split, extract, rotate, reorder and images to PDF – carry over only the title and record HelpMeJPG as the producer.
Server processing (optional)
By default your files stay on your device. Some tools and optional modes send a file to our conversion server (convert.helpmejpg.com) only when you choose them; it is processed for that one request and deleted as soon as the result has been sent. The conversion service does not keep, log or share file names or file contents.
- Purpose. Some conversions (high-quality Office and PDF conversion, OCR, PDF repair and PDF/A) need native engines that cannot run in a browser. In those cases, and only when you tick the confirmation box and press the server button, the file you chose is sent to our conversion server to produce the result you asked for.
- Legal basis. Performing the service you request (GDPR Art. 6(1)(b)) and your explicit choice for that single conversion (Art. 6(1)(a)); the confirmation box is not remembered and is unticked for every file.
- Retention. None beyond the request. The file and its result are held in a private working folder created for that request and deleted as soon as the result has been sent, or straight away if the conversion fails. They are not backed up, logged or used to train anything.
- Processors and sub-processors. The conversion server runs on infrastructure rented from Hostinger International Ltd., which acts as our processor for the duration of the request and has no use for the content.
- Security. Transfers use TLS (HTTPS). The conversion service runs in its own container, separate from the website, and each request gets a private working folder that no other request can read. Browser requests are accepted only from this site’s origin, and rate limits protect the service from abuse.
- Logs. The conversion service writes one log line per request – a random request id, the operation, a size class, the duration and the result status – with no file name, file content or IP address; rate limiting uses a shortened, salted hash of your address that is kept in memory only. The web server in front of it may keep a standard access log (see server logs), which never contains file contents.
- International transfers. The conversion server is located in Mumbai, India. If that is outside your country, the file is transferred there for the length of the request only, under the hosting provider’s standard contractual safeguards.
- How to avoid it. Use the browser mode of the tool (the default), which keeps the file on your device. Tools that exist only in server mode are marked as such.
Data we do not collect
- Image files, thumbnails, pixel data or any derived fingerprint of your images.
- PDF documents, extracted text, rendered pages, metadata or passwords.
- File names, EXIF metadata, GPS coordinates or camera information.
- Payment details – there are no payments. (Optional account details are described in the accounts section.)
- Precise location, contacts, microphone or camera data – the site does not request these permissions.
- A file you send to the optional conversion server is processed for that one request and not kept; see server processing.
Data we do collect
| Data | Purpose | When |
|---|---|---|
| IP address, requested address, timestamp, status code, bytes sent, referrer and user-agent string (server access logs) | Delivering the site, security, abuse prevention and capacity planning | Every request |
| Anonymous usage events: tool name, success or failure, error category, size and time buckets | Understanding which tools are useful and fixing failures | Never on this site – analytics is switched off |
| Advertising identifiers, cookies, approximate location, page and device information (handled by Google) | Serving, measuring and limiting ads | Never on this site – advertising is switched off |
| Optional account: name, email, password hash, email-verification and two-step settings, plan, preferences, saved presets, tool-usage log (tool name and success only), security log (event, time, shortened IP, browser type) | Providing sign-in, saving your settings and securing the account | Only if you create an account |
| Messages you send us by email | Answering your question or bug report | Only if you contact us |
Optional accounts
You can use every tool without an account. If you choose to create one (with an email and password), we store: your name and email address; a salted password hash (we never see or store your password itself); whether and when your email address was verified; whether two-step sign-in is on; your plan (every account is on the free plan); the avatar colour, tool defaults and email preference you choose; the presets you save; a short activity log containing only the tool name, whether it succeeded and the time; technical session records (a hashed session token, browser and device type and IP address) so we can keep you signed in, show you where you are signed in and detect abuse; and a security log of sign-ins, failed attempts and account changes, with the IP address shortened (to its first three blocks for IPv4, or a /48 network for IPv6) and only a browser/operating-system summary such as “Firefox on Windows”.
- Never stored: your images, PDFs, file names, extracted text or document passwords. Accounts do not back up your files.
- Purpose: sign-in, saving your preferences and keeping the account secure. We do not use account data for advertising.
- Where it lives: in our own database on our servers, reached only by our site's back end; your browser holds just the session cookie and the signed-in marker listed under cookies and local storage.
- Emails and one-time codes: we email you a 6-digit code to verify your address, to finish signing in when two-step sign-in is on, and to confirm a new address; plus password reset links and notices when your password or email changes. We keep only a salted, keyed hash of each code, never the code itself; codes expire after 10 minutes and the records are deleted about a day later. These security emails are part of the service. Product news is sent only if you opt in (off by default, legal basis: consent) and you can opt out at any time in your account preferences. Emails are delivered through an email delivery provider that processes your address and the message only to deliver it.
- Plans: every account is on the free plan. We do not take payments, so we hold no payment details. The usage figure on your account page is the size of your saved settings – never files.
- Control: download everything we hold, edit your profile and preferences, change your password or email, turn two-step sign-in on or off, see and sign out individual devices, review recent security activity, or delete the account permanently from your account page – deletion removes the account and everything attached to it (presets, preferences, activity and security logs, sessions and pending codes).
- Retention: kept while the account exists. Automatically purged: sign-in attempt records after about 7 days, sessions when they expire, one-time codes and reset links about a day after they expire or are used, and security-log entries after one year (at most the latest 100 are kept). The activity log keeps your latest 200 entries.
Optional integrations
Optional integrations with other companies (such as cloud import or social sign-in) exist in the software but are switched on per deployment. When one is enabled it is listed on this page, together with what it receives; if nothing is listed, none is active.
Active on this site: none.
Why we process data (legal bases)
Where the GDPR, the UK GDPR or similar laws apply, we rely on: legitimate interests for server logs, security and delivering the site; contract (providing the account you asked for); consent for analytics, advertising cookies and similar technologies where they are enabled (you can withdraw it at any time, see your choices); and legitimate interests or consent, as applicable, for replying to messages you send us.
Analytics
Analytics is switched off on this site: no analytics script is loaded and no analytics cookie is set. The events the software can send if the operator ever enables it are documented on the analytics disclosure page; none of them include file names or image content, and enabling analytics would be announced in the changelog and this policy first.
Advertising
Advertising is switched off on this site: no ad script is loaded and no advertising cookie is set. The software is prepared for Google AdSense; if the operator enables it, ads will load only after consent, in sandboxed frames that have no access to processed images, and this policy and the changelog will be updated before that happens.
Cookies and local storage
The site sets no cookies unless you sign in to an optional account, in which case a strictly necessary session cookie and a signed-in marker are used. Because analytics and advertising are switched off, no consent prompt is shown and no consent choice is stored. If a provider is ever enabled, its cookies will be listed here before it goes live. The table below is the same inventory as the cookie policy; both pages are generated from one list.
| Name | Set by | Purpose | Lifetime | Type |
|---|---|---|---|---|
__Host-hmj_session (cookie)Previously itp_session; the old name is still accepted for one release and then removed. | This site | Keeps your optional account signed in. Holds an opaque session token, never your email or password. | Until you close the browser, or 30 days if you tick “keep me signed in”. | Strictly necessary |
hmj_signed_in (cookie) | This site | A marker (value “1”) that tells the page you are signed in, so it only asks the server about your account when there is one. Contains no identifier. | Same as the session cookie. | Strictly necessary |
helpmejpg.sign-pdf.signature (local storage) | This site | Stores a signature image you drew or typed in Sign PDF, when you choose “remember my signature”, so you can reuse it. | Until you remove it in the tool or clear site data. | Functional (set only when you ask for it) |
Our server sends no tracking cookies and we do not fingerprint your browser. Because the site is built to work without them, no tool needs cookies to function.
Third parties and international transfers
We do not sell your personal data. The only third parties that may receive data are the hosting provider that runs our servers, the email delivery provider that sends account emails. Google may process data in the United States and other countries; where required, such transfers rely on safeguards such as the EU–US Data Privacy Framework or Standard Contractual Clauses. Fonts, scripts and codecs used by the tools are served from this site, not from a third-party CDN.
How long we keep data
- Files and document content: never stored – they exist only in your browser's memory while a tool is running, or on the conversion server for the length of a request you chose to send it (see server processing).
- Server access logs: see server logs (full IP address, deleted or archived within 30 days).
- Account data: kept until you delete the account (you can do this yourself at any time); sign-in attempt logs are deleted after about 7 days, one-time codes about a day after they expire and security-log entries after one year.
- Emails you send us: kept only as long as needed to respond and to keep a record of the conversation.
Server logs
Our web servers record a standard access log for every request: the full IP address, the requested address, date and time, response status, bytes sent, the referring page and the browser’s user-agent string. Access logs record the request, never its body, so they cannot contain the contents of a file.
These access logs are not shortened or anonymised at the time of writing. They are rotated and deleted or archived within 30 days unless a specific entry is needed for a security investigation. The account security log described below is different: there we store a shortened IP address. Logs are not combined with any other data.
Blog and newsletter
Blog articles are written by our editors in a separate, access-controlled content system that we also operate. Visitors cannot log in, comment or submit data there. Article text is delivered from this site; article images are served from this site as well. We do not run a newsletter or collect email addresses for marketing. If that changes, we will ask for your explicit consent and update this policy first.
How we protect data
The best protection is not collecting your files at all. In addition, the site is served over HTTPS, applies a strict Content Security Policy and other hardening headers, restricts what third-party code can run, validates and limits every file in the browser before processing, and sanitises SVG and Markdown content. No system is perfectly secure; if you find a vulnerability, please follow our security and responsible-disclosure policy – we acknowledge reports within 3 business days and will not take legal action against good-faith research.
Your rights
Depending on where you live (for example under the GDPR, the UK GDPR, the California Consumer Privacy Act, Nepal's Privacy Act 2018 or similar laws) you may have the right to access, correct, delete or restrict the use of personal data we hold about you, to object to processing, to withdraw consent at any time, to data portability, and to lodge a complaint with your local data protection authority. Because we hold very little personal data and cannot identify you from it without extra information, we may ask you to supply details (such as an approximate time and your IP address) so we can find your records.
We do not sell or share personal information for cross-context behavioural advertising, and we do not make automated decisions that have legal effects on you. We honour the Global Privacy Control browser signal: when your browser sends it and you have not made a choice in the consent prompt, the site treats it as a decline of analytics and advertising (there is nothing to decline while both are switched off, but the code path is in place).
Children
The site is a general-audience utility and is not directed at children under 13 (or under 16 where local law sets a higher age). We do not knowingly collect personal data from children. If you believe a child has provided us data, contact us and we will delete it.
Links to other sites
Guides and articles may link to other websites. We are not responsible for their content or privacy practices, so please read their policies before sharing any information.
Your choices
- While analytics and advertising are switched off there is nothing to consent to and no prompt is shown. If either is enabled later, a prompt will appear and a “Cookie settings” link in the footer will let you change your answer at any time.
- Block or delete cookies in your browser settings, or use a private window; the tools keep working.
- Turn on Global Privacy Control in your browser; we treat it as a decline (see your rights above).
- Use the tools without JavaScript-based third parties: image and PDF processing works identically whether or not you consent.
- Contact us to exercise any of the rights above.
Changes to this policy
We will update this page whenever the way the site processes data changes, for example if analytics or advertising is enabled or if a server-side feature is introduced. The version and date at the top identify the current revision, and every change is recorded with a short description in the changelog. Material changes are also announced there before they take effect.
Contact
Questions, requests or concerns about privacy: support@helpmejpg.com (see the contact page for what to include and our response time). NexuxLabs operates this website. Please do not attach your files to messages – we never need them to answer a privacy question.