Legal
Privacy policy
What KG Partners Limited collects, why, and what you can do about it.
Last updated
This policy explains what personal data we hold when you use CPD, why we hold it, and where it goes. We have tried to describe what the system actually does rather than write something broad enough to cover anything we might ever do.
Who is responsible
KG Partners Limited, a company incorporated in Hong Kong, is the data user for the purposes of the Personal Data (Privacy) Ordinance (Cap. 486).
What we collect
When you create an account
- Your name, as it will appear on certificates
- Your email address, which is how you sign in
- Optionally your phone number and organisation
- Your password, stored only as a bcrypt hash. We cannot read it, and we cannot tell you what it is
When you take a course
- Which courses you enrol in, and when
- How much of each recording you have watched, and where you stopped, so playback resumes where you stopped and so we hold an honest record of how much of a course was actually watched
- Your assessment answers, scores, and whether you passed
- The certificates issued to you
When you pay
Card payments are processed by Stripe. Your card details go directly to Stripe and never reach our servers. We keep a payment reference and the amount, so we can identify your purchase, answer a question about it, and issue a refund in the circumstances our terms describe.
When you sign in with Google
If you choose Google rather than a password, Google tells us your name, email address, profile picture, and the identifier Google uses for your account. We store those and use them for the same purposes as the details you would have typed yourself. We never receive your Google password. Google's own privacy policy governs what Google does with the fact that you signed in.
If an account already exists with that email address and a password, we will not join the two together automatically — you are asked to sign in with your password instead. Linking on a matching email address would let someone who registered an address they do not own take over the real owner's account when they later arrive through Google, and that account holds certificates in a person's name.
When you use the iPhone or Android app
- A sign-in token for the device, so you are not asked to sign in every time. We store only a hash of it; the token itself stays on your device, in the iOS keychain or Android's encrypted storage, and is deleted when you sign out
- The device name and platform you signed in from, and when the token was last used, so a session can be recognised and ended
The apps collect nothing else. There is no analytics SDK, no advertising identifier, and no crash reporter that sends us your data.
When you contact us
What you put in an enquiry form — name, email, organisation, and your message — so we can reply.
What we don't do
We run no analytics, no advertising pixels, and no third-party trackers. We do not sell or rent personal data, and we do not send marketing email you did not ask for.
Certificates are public
This is the part worth reading twice
Every certificate we issue has a reference that resolves to a public page on this site. That page shows the holder's name, the course title, the CPD hours, and the date of issue. Anyone with the reference can view it, without an account.
This is deliberate — a certificate nobody can independently check is worth very little. But it does mean that completing a course results in your name appearing on a publicly accessible page. Nothing else about you is shown: not your email, phone, organisation, assessment answers, or which other courses you have taken.
Where your data is processed
We are based in Hong Kong, but some of the infrastructure is not. Specifically:
- The application runs on Google Cloud Run in Singapore
- The database is hosted by Neon in Singapore, and holds your account, enrolments, progress, assessment results, and certificates
- Course recordings and course artwork sit in Google Cloud Storage in Hong Kong. These contain no personal data
- Payments are handled by Stripe, which processes data internationally
- Password reset emails are sent through Resend, in Tokyo. Only your email address and the reset link pass through it
- If you sign in with Google, that exchange happens with Google, which processes data internationally
So your personal data is transferred outside Hong Kong — principally to Singapore, and to Japan when we email you. We use established providers with their own security and data protection commitments, and we hold no personal data on servers we run ourselves.
Cookies
- A session cookie that keeps you signed in. It is essential — you cannot use an account without it — and it is removed when you log out
- A cookie recording your chosen interface language, so the site stays in it between visits
We set no advertising or analytics cookies. Your light or dark theme preference is stored in your browser's local storage, not a cookie, and never sent to us.
The apps use no cookies. They keep a sign-in token in the device's own secure storage, which is removed when you sign out.
How long we keep it
- Account and progress — while your account is open
- Certificate records — indefinitely, including after an account is closed. A certificate that stops verifying is worse than useless: an employer checking a genuine record years later would be told it does not exist. Certificate records hold your name, the course, the hours, and the date — nothing more
- Payment records — as long as tax and accounting law requires
- Enquiries — up to two years, then deleted
Your rights
Under the Personal Data (Privacy) Ordinance you may ask what personal data we hold about you, ask for a copy, and ask us to correct anything inaccurate. Contact us through https://hkcpd.com/contact and we will respond within the statutory period.
You can delete your account yourself, without asking us — on the site under Account, and in the app under Account. It takes effect immediately. As above, issued certificate records are retained so verification continues to work — if that is not acceptable to you, tell us and we will discuss it rather than apply a blanket rule.
Security
Passwords are hashed with bcrypt and never stored in readable form. The site is served over HTTPS. Course recordings sit in a private bucket that is not publicly readable, and are served through short-lived signed links issued only after we have confirmed your enrolment. Credentials are held in a managed secret store, not in our code.
Changes
If we change how we handle personal data, we will update this page and the date at the top. Material changes will be notified before they take effect.
Contact
Questions, or a request about your data: Contact.