THE HSWAGATA BUDDHA TOOTH RELIC PRESERVATION PRIVATE MUSEUM
FOR INTERNAL USE ONLY
Template No.: TK-054 (E/C)
Template Title: Website Page Used to Spread False Claim — Web Logs & Web Publishing Controls
Related Research Case IDs / Cluster: Cluster E (Science/Testing/Misinformation) + Cluster C (Institution-Building / Responsibility & MoUs)
Linked Templates / Policies:
TK-042 Lay Complaint & Rumour Intake Record
TK-045 Public Science Claim Pre-Release Review
TK-050 Testing Results Leaked Early — Confidentiality Control
TK-051 No-Fast-Claims Policy
TK-055 “Science Talk” Misuse Risk Assessment
Institutional Policies for Relic Stewardship (HSWAGATA)
Date of form: ____ / ____ / ______
Prepared by / Role: _______________________
Office / Unit: ____________________________
Country / Location: _______________________
Confidentiality Level:
Internal only [ ] Restricted [ ] Sacred-Restricted / Sensitive [ ]
Use of this form (tick):
New case / action [ ] Follow-up [ ] Annual review [ ] Archive only [ ]
TK-054 — Purpose
Use this template when a HSWAGATA website page (or a partner site page) is used to spread:
a false claim about testing, authenticity, approvals, or “proof,” or
misleading lab language, edited images, or fake documents.
This template helps staff:
contain harm quickly,
collect web logs and evidence,
correct or remove the content safely, and
strengthen web publishing controls.
A. Incident Intake (What Happened)
Page URL / web address (record internally): ____________________________
Page title (as shown): _____________________________________________
Date/time discovered: ____ / ____ / ______ ________
Discovered by (name/role): _________________________________________
Source of report: ☐ Visitor ☐ Donor ☐ Staff ☐ Media ☐ Other: ___________
False claim type (tick all that apply)
☐ “Scientifically proven authentic”
☐ “Lab confirmed Buddha tooth relic”
☐ “DNA / Carbon-14 confirms”
☐ “Official government / palace letter confirms”
☐ Edited image used as proof
☐ Fake certificate / fake stamp / fake logo
☐ Other: ______________________________________________
Exact false wording (copy exact sentence):
Risk level: ☐ Low ☐ Medium ☐ High
(High if fundraising, conflict, threats, or major media spread)
Assigned lead officer: ____________________ Date: //____
B. Immediate Containment (Do First)
Tick what is done now:
☐ Take screenshots of the page (top, claim text, images, footer, date)
☐ Save page as PDF (internal evidence)
☐ Record URL + time + browser used
☐ Turn page to “draft/unpublished” OR add emergency banner note
☐ Stop sharing (remove from homepage / remove from social links)
☐ Notify Compliance & Risk + Executive lead
☐ If fundraising involved: notify Finance/Donations unit
Containment notes (short):
C. Web Log & Change Evidence Collection
C1. Server / CMS logs to collect (tick)
☐ CMS edit history (who edited, what changed, when)
☐ Login logins (admin/editor access list)
☐ IP addresses (if available)
☐ Publish/unpublish log
☐ File upload log (images/PDFs)
☐ Web access logs (traffic spikes)
C2. Key details to record
CMS platform: ☐ WordPress ☐ Wix ☐ Squarespace ☐ Custom ☐ Other: ________
Page ID / post ID (if available): _________________________________
Last modified date shown in CMS: ____ / ____ / ______
Who last edited (username): _________________________________
Any unknown login? ☐ Yes ☐ No ☐ Unclear
Notes: ________________________________________________________
C3. Attachments on the page
List all files/images used for the claim:
File name/URL: __________________________ Type: ☐ Image ☐ PDF ☐ Video
File name/URL: __________________________ Type: ☐ Image ☐ PDF ☐ Video
(Continue if needed)
D. Root Cause Check (Do Not Blame Without Evidence)
Select likely cause(s):
☐ Staff mistake (draft published too early)
☐ Poor review controls (no approval step)
☐ Unauthorized editor access (shared password)
☐ Account compromise / hacking suspected
☐ External partner supplied false text/images
☐ Old content reused without update
☐ Other: _______________________
Evidence (facts only):
E. Correction Action (Choose One Main Path)
E1. Remove
☐ Page removed/unpublished
Reason: _____________________________________________
E2. Correct
☐ Page corrected with approved wording
☐ Misleading text deleted
☐ Images replaced/labelled “Illustration / Not proof”
☐ Add date-stamped correction note at top
E3. Replace with a safe official statement
☐ Replace page with short official clarification (no details that fuel drama)
Suggested safe statement:
“An earlier version of this page contained incorrect or unclear wording. HSWAGATA does not make fast authenticity claims and does not treat partial materials as proof. Verified information is shared only through official channels.”
Action completed by: ____________________ Date: //____
F. Web Publishing Controls (Mandatory Controls Checklist)
Implement and tick when done:
F1. Roles and permissions
☐ Separate roles: Admin / Editor / Author
☐ Remove unused accounts
☐ No shared accounts
☐ Strong passwords + password manager
☐ Two-factor authentication (2FA) enabled for admin/editor
F2. Publishing workflow
☐ Draft → Review → Approval → Publish (no direct publish)
☐ Two-person rule for pages that mention “science/testing/authenticity”
☐ Required use of TK-045 (pre-release review) before publishing claims
☐ “Approved wording list” used (safe phrases only)
F3. Technical controls
☐ Auto backups enabled (daily/weekly)
☐ Change log retained for ___ months
☐ Security plugin/firewall enabled (if possible)
☐ Limit file uploads to approved types
☐ Watermark/label policy for relic images
F4. Monitoring
☐ Weekly check of high-risk pages
☐ Alerts for login from new device/location
☐ Alerts for sudden traffic spikes
☐ Monitor for copied pages or screenshots spreading elsewhere
Assigned to (name/role): __________________ Due date: //____
G. Public Communication (If Needed)
Choose:
☐ No public response (quiet fix)
☐ Short correction notice on site only
☐ Social media correction (official channel only)
☐ Direct message to key stakeholders (donors, monks, partners)
Spokesperson: ____________________ Date: //____
Final approved wording stored at: __________________________
H. Closure & Archive
Status: ☐ Open ☐ Monitoring ☐ Closed
Final summary (2–4 lines):
Archive code / file location: ______________________________________
I. Sign-off
Prepared by: __________________________ Signature: ________________
Reviewed by (Compliance/IT Lead): __________________ Signature: ______
Date: ____ / ____ / ______
End of Template TK-054
