In short
- The toolkit is run by its two authors, with one operator. There is no support team behind it.
- It holds governance records, not customer or patient data, and it does not store your evidence files.
- It has no SOC 2 or ISO/IEC 27001 certification today. Nothing on this page says otherwise.
- Sign-in is an emailed single-use link. Single sign-on and a second factor are not available yet.
- Evidence exports carry checksums. They are not signed or certified.
Where it runs and who processes data
- Application and database
- Cloudflare. The application runs on Cloudflare Workers and the database on Cloudflare D1, in its Asia-Pacific region. Every record is stored against a licence and every query is limited to it.
- Resend sends sign-in links, reminders and notices from noreply@mail.terencekok.com. It sees the recipient address and the message.
- AI provider
- Three features send text to a third-party AI provider through a relay we run on Cloudflare: the question assistant, regulatory redlines and the tailoring assistant (off unless you ask). Processing may take place outside Singapore, including in the United States. Your registers and evidence are not sent. The exact text each feature sends is set out on the data privacy page.
- Everything else
- No analytics, advertising or social scripts load in the toolkit. There are no other sub-processors for licensee records.
Controls in place
- Sign-in
- An emailed link that works once and expires after 15 minutes. Only a hash of each link is stored. The session is a signed cookie that lasts 14 days.
- Separation between licensees
- Records are keyed to the licence. A suspended or revoked licence loses access on the next request, because the licence is re-read on every request.
- Evidence sign-off
- Evidence against a control needs a second person to sign it off, and the sign-off is recorded with who and when.
- Roles
- Owner, maker, checker and reader. A maker edits records but cannot approve. A checker signs off evidence and decides onboarding gates and risk acceptances but cannot edit. A reader can only view. Role changes are logged, and a licence always keeps an owner. People start as owners until an owner assigns roles.
- Change history
- Changes to systems, control scores, risk scores and risk acceptances are kept with who made them and when.
- Evidence bundle
- The audit bundle is a dated ZIP. Its manifest lists every file with a SHA-256 checksum, and the checksum of the manifest is logged when the bundle is made. The checksums show the files are unchanged since they were generated. They do not prove the content is right, and the bundle is not signed, certified or an audit opinion.
- Administration
- The authors use a separate administration console with individual passwords and an eight-hour session. Administrator actions such as granting access are logged. Administrators can technically reach stored records and open them only to help you at your request or to fix a fault.
- Browser protections
- Cross-site form posts are refused, cookies are SameSite and the toolkit pages are not indexed by search engines.
What is not there yet
If your policy requires any of these, treat it as a gap and decide whether the toolkit is right for that use.
- Independent assurance
- No SOC 2 report, no ISO/IEC 27001 certificate and no independent penetration-test report is available today.
- Identity
- No single sign-on and no second factor. Roles limit who can change and approve records, but everyone on a licence can still see all of that licence's records, and there is no read-only auditor seat yet.
- Vendor access log
- Administrator access to your records is not yet shown to you in a log of your own.
- Tamper evidence
- History is kept in the database we operate. It is not hash-chained and not independently time-stamped.
- Service levels
- No contractual uptime, recovery time or recovery point is offered. Because the service has one operator, you should hold your own copy of anything you rely on. Export it as CSV or take an evidence bundle at each review.
- Retention
- There is no fixed retention schedule or legal hold. Records are kept while the licence is active and deleted on request, with a confirmation by email.
Leaving
You can export the registers, control assessment, evidence list, gap register, training sign-offs and risk records as CSV at any time. The files you downloaded are yours to keep. When a licence ends, we delete its records on request and confirm by email. The toolkit does not store your evidence files, only a description and the location you give, so nothing needs to be retrieved from it.
Questions from your risk team
Standard answers to common third-party risk questions are on the questionnaire page, with a CSV you can attach to your own process. Send anything else through the contact page. We answer security and sub-processor questions in writing and we will say plainly when the answer is no.
The toolkit is operated by Terence Kok Wai Chuen, Singapore, with Michael Low as co-author.