Report a security weakness without putting anyone at risk.

Report safely

Send a credible report to security@how2revise.com. Use a plain description first. Do not attach live secrets, schoolwork or personal information unless an authorised responder asks for a protected transfer method.

For immediate danger to a person, call 999. For a privacy complaint rather than a technical weakness, use the privacy notice. For a child-safety concern, use safeguarding help.

What to include

• the affected public address or feature;
• a concise description of the weakness and expected security impact;
• safe, minimal reproduction steps using only an account and data you control;
• the browser, device or request conditions if relevant; and
• a safe way to reply.

Replace tokens, credentials, email addresses, names and pupil material with redacted or synthetic examples. Do not send a database copy, password, API key, full session cookie, payment-card data or an image of real schoolwork through ordinary email.

Do not

• access, change, download or retain another person's account or information;
• test with a real child, real pupil profile or real schoolwork;
• use phishing, credential stuffing, malware, denial of service, spam or physical attacks;
• defeat rate or cost limits at scale, disrupt availability or degrade another visitor's experience;
• contact a pupil, school, provider worker or unrelated third party;
• demand money, threaten disclosure or publish exploit details before a safe resolution; or
• assume this draft grants legal permission or immunity for conduct that would otherwise be unlawful.

Proposed handling

1. Restrict the report to authorised security responders and acknowledge it using a reference.
2. Preserve the minimum evidence, remove exposed secrets and protect any unexpectedly received personal information.
3. Triage impact without asking the reporter to retrieve more real data.
4. Contain, correct and verify the weakness, including provider notification where required.
5. Explain the outcome and coordinate any public disclosure only after affected people and systems are protected.

No response-time promise is published because a named monitored owner and continuity cover have not been verified. The final page must publish only a target the company can staff and must connect to a tested incident, breach-assessment and notification process.

Scope today

The current scope is the public content, manual Reset and guided Biology practice at www.how2revise.com. Accounts, paid profiles, checkout, real uploads and pupil-facing AI are closed, so no researcher should try to activate or simulate them in production. Provider dashboards, staff accounts, other ECOMMERCE ONLINE LTD products and third-party websites are outside this page.

No bounty or public-disclosure promise

How2Revise has not established a paid vulnerability programme. This candidate promises no reward, reimbursement, legal immunity, credit or publication timetable. A final coordinated- disclosure policy may recognise good-faith help only after qualified review and operational ownership are complete.

Machine-readable route

The site also publishes /.well-known/security.txt. It exposes a mailbox only when branded mailboxes are enabled; otherwise it points to this safe public route. The record is not evidence that a staffed response target or bounty exists.

Approval still required

Independent security review, named incident ownership, protected evidence transfer, breach response, provider escalation, record retention and legal safe-harbour wording remain unresolved. This candidate has no effective date.