Security and responsible disclosure

Version 1.0 · Last updated

If you have found a vulnerability in HelpMeJPG, thank you for telling us. This page explains where to send it, what we do next and the promise we make to researchers who act in good faith.

How to report

Email support@helpmejpg.com with a clear description of the issue, the page or endpoint affected, steps to reproduce, and the impact you believe it has. Proof-of-concept code or a screenshot is welcome; please do not send someone else's personal data as evidence.

Encrypted reports. We have not yet published an OpenPGP key for the security mailbox. If your report is sensitive, send a short email first and we will agree an encrypted channel before you share details.

What to expect from us

  • Acknowledgement within 3 business days of receiving your report.
  • Triage and a first assessment within 7 days, including whether we can reproduce it and how severe we think it is.
  • A fix within 90 days for confirmed issues, usually much sooner for anything that could expose data; we will tell you when it ships and credit you in the changelog if you wish.
  • We do not run a paid bug bounty. We do say thank you, publicly if you like.

Scope

In scope:

  • helpmejpg.com – the website and every tool, guide and account page on it, including the /api/ routes.
  • The content system that serves blog articles and images on its own sub-domain, as far as it is reachable publicly.
  • The client-side processing itself: for example an image or PDF crafted so that a tool sends data somewhere, executes embedded script, or breaks the sanitisation of SVG or Markdown content.

Out of scope (please do not test these):

  • Denial-of-service, volumetric or brute-force testing against the live site, and automated scanning at high request rates.
  • Social engineering, phishing or physical attacks on people who work on the site.
  • Third-party services we do not operate (Google, the email delivery provider, the hosting company's infrastructure) – report those to the provider.
  • Findings that need an already-compromised device or browser, missing best-practice headers with no demonstrated impact, and version disclosure on its own.

Safe harbour

We will not take or support legal action against you, and we will not report you to the authorities, for security research that is done in good faith and within this policy: you avoid privacy violations, data destruction and service disruption; you only access the minimum data needed to show the issue and do not keep or share it; you do not exploit a finding beyond that demonstration; and you give us a reasonable time to fix the problem before making it public. If a third party starts legal action against you for research that followed this policy, we will make it known that you acted with our authorisation.

Public disclosure

We ask for coordinated disclosure: please wait until a fix has shipped, or 90 days have passed since your report, whichever comes first, before publishing details. We will agree a date with you and publish our own note in the changelog. We never ask researchers to sign anything or to keep an issue secret indefinitely.

How the site is protected

The main defence is architectural: most files are processed in your browser, and the few that use the conversion server (convert.helpmejpg.com) are handled in memory and deleted right after, so there is no store of user files to breach. On top of that the site is served over HTTPS with HSTS, applies a strict Content Security Policy (connect-src 'self' https://convert.helpmejpg.com, no third-party scripts unless you consent to one), isolates image codecs and PDF engines in Web Workers, validates and limits every file before processing, sanitises SVG and Markdown, never executes scripts embedded in PDFs, and keeps account sessions in an HttpOnly, Secure, __Host--prefixed cookie. Details of what we store are in the privacy policy; you can watch the network yourself by following how it works.