Privacy Policy

When you register for a webinar, what is stored is the name you gave for the certificate, an email address, your account identity, the registration status and the time of registration.

The name on the registration form is the name that will be printed. It is asked for separately because the name on a platform profile is frequently a handle rather than a name fit to print on a document.

Attendance is recorded as a number of minutes, with a join and leave time where those are available. That record is what decides certificate eligibility, and only administrators can see or change it.

The verification page is open to anyone with no account. It shows the holder's name, the webinar title, the issuer's name, the attendance figure in minutes, the issue date, and the revocation status where there is one.

What it never shows: the email address, the account identity, the registration, the meeting link, and any revocation reason.

• Shown: holder's name, webinar title, issuer, minutes attended, issue date, revocation status.
• Not shown: email, account id, internal ids, meeting link, revocation reason.

A certificate code is random rather than sequential, so one person's code cannot be used to guess another's. A code that was never issued and a malformed one are answered in exactly the same way, so the verification page cannot be used to discover whose certificates exist.