Skip to main content

InSkillSecContact

Contact

Email is the only channel, and it is answered by a person. Pick the address that matches your subject and you will get a faster answer.

Last updated: 2026-08-10

General enquiries

Questions about a course, its content, access to your account, an error you spotted, or a partnership.

contact@inskillsec.com

Privacy and your data

Access, correction, deletion or portability of your personal data, and any question about the privacy policy.

privacy@inskillsec.com

Security

A vulnerability on this site or on the platform. Reported in good faith, it will never be answered with a lawyer.

security@inskillsec.com

How long we take

  • General enquiries: within two business days.
  • Data protection requests: within thirty days, as the law requires, usually much sooner.
  • Security reports: acknowledged within two business days, with an assessment to follow.

Haythem Rehouma runs this site personally, from Québec, Canada. There is no phone line and no live chat, and no one will ever call you about your account.

What to include

For anything involving your account, write from the email address of that account and include the exact URL of the page concerned. That alone removes one round trip. For a technical problem, add your browser and what you expected to happen.

Never send us a password, a sign-in code, or an API key. We never ask for them, and no message from us will ever ask you to confirm your password. A message that does is not from us.

Verifying a certificate

Employers do not need to write to us: any certificate can be checked directly, without an account, from the verification page. It confirms the holder’s name, the course, and the issue date. Write to us only if a number does not resolve.

Reporting a vulnerability

Send a description precise enough to reproduce the issue, and give us a reasonable window to fix it before publishing. Please stay away from anything that would degrade the service for other people: no denial of service, no automated scanning at volume, no attempt to read another user’s data, no social engineering of anyone. We keep a machine-readable version of this at /.well-known/security.txt.

Verify a certificate