Skip to main content
Search ExamKind
Reading options
Colours
Reading comfort
Background tint

Saved in a cookie on this device only.

Policies

Reporting a security problem

Version security-disclosure-2026-10.1Prepared 12 October 2026Last reviewed 12 October 2026

Draft for review

This describes ExamKind as it works today. It is being reviewed by our Data Protection Officer and our solicitors, and the wording may change before our public launch.

In short

ExamKind holds information about families, so we take security seriously. If you think you have found a security weakness, please email security@examkind.com. The short version:

  • Tell us privately and give us time to fix it before you tell anyone else.
  • Never access, change or keep anyone else's information, especially children's. Use only accounts you created.
  • Don't overload our services, trick our staff or try to get into our offices.
  • We reply within 3 working days and keep you updated until the problem is fixed.
  • If you follow this policy in good faith, we will not take legal action against you.

What this policy covers

  • examkind.com and its subdomains
  • ExamKind accounts and the sign-in and sign-up pages
  • Our public tools, data downloads and website widgets

Services run by other companies, such as our hosting provider or Google and Apple sign-in, are not covered. Please report problems with them to the company concerned. If you're not sure whether something is in scope, ask us first.

What not to do

  • Don't access, download, change or delete information that isn't yours. If you come across personal information, stop, don't keep a copy, and tell us what you saw.
  • Never try to see or contact children, or access a child's information.
  • Don't run denial-of-service attacks, or tests that slow ExamKind down for other people. Keep automated scanning gentle.
  • Don't use social engineering, such as phishing our staff or pretending to be someone else.
  • Don't try to get into our offices, data centres or devices.
  • Don't send spam through our forms or post test content in our community where other people can see it.
  • Don't use what you find for anything except reporting it to us.

How to report a problem

Email security@examkind.com with:

  • what the problem is and which page or address it affects;
  • the steps to reproduce it, with screenshots or a short video if that helps;
  • what someone could do with it, as far as you know;
  • how you would like to be credited, if at all.

Please write in English. Don't include anyone else's personal information in your report.

What we will do

  • Acknowledge your report within 3 working days.
  • Check it, decide how serious it is and tell you what we found.
  • Keep you updated until it is fixed, and tell you when it is.
  • Thank you publicly once it is fixed, if you would like us to.
How quickly we aim to fix a confirmed problem, by how serious it is
How seriousWe aim to fix it within
Critical, on a service anyone can reach on the internet48 hours
Critical, anywhere else7 days
High14 days
Medium30 days
Low90 days

Please give us reasonable time to fix a problem before you share any details publicly, and agree the timing with us. We don't offer payment for reports at the moment.

Our promise to researchers

If you act in good faith and follow this policy, we will treat your research as authorised, we will not take legal action against you, and we will not report you to the police for it. If someone else takes action against you for research that followed this policy, we will make it clear that it was authorised.

This promise does not cover anything that breaks the rules above, such as accessing other people's information, or anything we can't authorise, such as testing another company's services.

Changes to this policy

We review this policy at least once a year and whenever our services change.

Version history
VersionDateWhat changed
security-disclosure-2026-10.112 October 2026First version, for review by the founder and our solicitors before launch.

Spotted something wrong? Report an error on this page