# Facts Pack Request — CyberSight Forensics website **BTC-CS2026-OW-DS-FR-0001-FactsPackRequest_A1-C01** · prepared by the design/build team · 13 June 2026 **For completion by:** the Principal (Sanju Varkey) · **Return to:** design/build team + Themis Legal **Why this exists:** Themis RP-0001 §C and ON-0001's Facts Schedule list the real-world facts the website needs before it can go public. They are currently rendered as visible **`[bracketed placeholders]`** in the build so nothing fake ships. This sheet pulls every one of them into a single fill-in list so none is overlooked at the Go-Live Gate. > **This does not hold up the build.** Engineering can build now against the placeholders; each fact below is wired as a swappable config/content value and drops in without a rebuild. What it *does* gate is **going public** — items tagged **[GATE]** are hard blockers on the IN-0001 Go-Live Gate. --- ## How to use this sheet 1. Fill the **"Your answer"** cell for each item. If something is genuinely "none"/"not applicable", write that explicitly (e.g. VAT → *"not registered"*) — a blank is treated as outstanding. 2. Anything tagged **[EVIDENCE]** also needs a document or attestation **held on file** before launch (not published) — the ASA/CAP rule is that a claim must be substantiated *before* it appears. 3. Return the completed sheet; the design/build team swaps the values into the single config points and Themis re-checks the live build. --- ## A · Corporate & legal identity | # | Fact needed | Where it shows | Your answer | |---|---|---|---| | A1 | **Registered office address** — ✅ *supplied 12 Jun 2026* | Footer, Privacy, Terms (`REGISTERED_OFFICE` config) | `167-169 Great Portland Street, 5th Floor, London W1W 5PF` | | A2 **[GATE]** | **Company rename status** — is "Managed Cybersecurity Services Ltd" registered at Companies House yet? If not, target date. The site launches under the **current** registered name (Phishermans Ltd) and swaps on registration only. | Footer name (`REGISTERED_NAME` config) | ______________________ | | A3 **[GATE]** | **VAT** — VAT number, **or** confirm "not registered". | Footer VAT line (shown only if registered) | ______________________ | | A4 | **ICO registration** — confirm **ZC098139** covers the website enquiry processing, and that the registered name on the ICO entry will be updated after any rename. | Footer + Privacy (already shows ZC098139) | ______________________ | | A5 | **Site contact email** — the address for enquiries, privacy requests and accessibility queries. ⚠ *The Contact section currently shows `support@cybersightforensics.com` as a working value — confirm this is correct and may be used everywhere, or supply the correct address.* | Contact section + Privacy + Accessibility (`[contact email]`) | ______________________ | ## B · Claims & evidence (advertising-standards critical) | # | Fact needed | Where it shows | Your answer | |---|---|---|---| | B1 **[GATE][EVIDENCE]** | **Certifications actually held now** — list each with **certificate number + date**. Anything *not* held stays off the site (no badge); only held certs get a badge that click-throughs to the issuer's register. Everything still in progress stays as the text-only "Working towards…" line. | Footer + Compliance section | ______________________ | | B2 **[GATE][EVIDENCE]** | **Service-level evidence** — documentary basis you hold for each target before it appears: the **4-working-hour** emergency response (retainer), the **24–48h** pilot intake turnaround, any **24/7** availability claim. | Stats strip, Process, Engagement, Contact | ______________________ | | B3 **[GATE]** | **Forensic standing** — which **FSR-listed forensic activities** CyberSight will perform; current **ISO 17025 / CREST / NCSC-training** status (so the Tier-1 "working towards / aligned with the FSR Code" wording stays accurate). | Compliance section | ______________________ | > **Claims ladder (for context).** Everything is built at **Tier 1** (launch) wording. **Tier 2** (individual-capability claims) unlocks only when a named qualified person is actually in post; **Tier 3** (accreditation claims + official badges + "court-ready") unlocks only when the company holds the accreditation. Each step up is a wording swap that needs a fresh Themis sign-off — tell us when a milestone is reached and we'll request the Tier-2/3 copy. ## C · Form backend (engineering supplies these — listed so they're tracked) | # | Fact needed | Where it shows | Status | |---|---|---|---| | C1 **[GATE]** | **Form/email provider** + written UK/EEA **data-residency attestation** + signed **Art 28** processor terms. | Privacy "who else is involved" (`[form/email provider]`) | Engineering → see *Form Backend Build Brief* | | C2 **[GATE]** | **Hosting provider** + data-residency attestation + signed Art 28 terms. | Privacy (`[hosting provider]`) | Engineering → see *Form Backend Build Brief* | | C3 | **WhatsApp notification** — confirm the notification recipient number(s) and approve the **PII-free notification** design (no enquiry personal data sent to WhatsApp/Meta). See the *Form Backend Build Brief* §4. | Operational only (not shown on site) | Principal + Engineering | | C4 **[GATE]** | **Retention period** — confirm enquiry data is kept **12 months** from last contact (non-engaged), or set a different period. | Privacy (`[12 months]`) | ______________________ | ## D · Policy & content decisions | # | Decision needed | Where it shows | Your answer | |---|---|---|---| | D1 | **Modern Slavery statement** — keep the short **voluntary** statement (recommended for procurement credibility) or remove it? | `/modern-slavery` policy + footer link | Keep / Remove: __________ | | D2 | **"Website by Managed Services" credit** — keep, amend, or remove? (After the rename the natural form is the new company name.) | Footer | Keep / Amend / Remove: __________ | | D3 | **Welsh language** — any Welsh public-sector contract that requires Welsh content **at launch**? If yes we commission translation served at `/cy/`; if no, the picker ships with a "Cymraeg yn dod yn fuan / Welsh coming soon" state. | Language picker | Yes / No: __________ | | D4 | **Trade-mark** — do you want a UK IPO clearance search + filing on "CyberSight Forensics" (word) and the logo actioned now? (Advised before major marketing spend; does **not** gate launch.) | n/a | Yes / No / Later: __________ | ## E · Launch logistics | # | Fact needed | Where it shows | Your answer | |---|---|---|---| | E1 **[GATE]** | **Canonical domain** — the final live domain (e.g. `https://cybersightforensics.com`). | ``, sitemap, OG tags | ______________________ | | E2 | **Go-live date** — used to date the policy pages ("Last updated") and the accessibility statement. | Privacy, Cookies, Terms (`[go-live date]`) | ______________________ | | E3 | **Real social-media URLs** — Facebook, LinkedIn, Instagram, X (or tell us which to remove). | Footer social icons (currently `#`) | ______________________ | --- ## Sign-off | | Name / role | Date | |---|---|---| | Facts supplied | Sanju Varkey (Principal) | | | Facts loaded into build | design/build team | | | Live-surface re-check | Themis Legal | | *Cross-references: IN-0001 Go-Live Gate · RP-0001 §C · ON-0001 Facts Schedule · WD-0001 bracketed items · SP-0001 (form backend). Return completed items quoting these IDs.*