Section 1When This Procedure Applies
This procedure applies whenever account activity is detected on a VML Kids account belonging to a child who has been reported missing or kidnapped. It applies regardless of the time of day, the day of the week, or which member of staff detects the activity. There are no exceptions and no circumstances under which this procedure may be delayed, modified or bypassed.
Section 2Immediate Actions — Simultaneous
The following two actions must be taken simultaneously, without delay, the moment account activity is detected. Do not take one before the other. Do not wait for authorisation from any other person before acting.
Action 1 — Safeguarding Director
Contact the on-duty Safeguarding Director immediately by telephone. A follow-up email containing a log of the account activity must be sent immediately after the call. Do not wait until the call is complete before beginning the email.
Action 2 — Police via 999
Call 999 immediately. Provide sufficient detail for the police to act — the child's name, account details and nature of the activity detected. A formal written report must follow immediately after the call is completed.
Section 3Evidence Architecture — Three Layers
From the moment of detection, the following three-layer evidence architecture must be maintained. Each layer serves a distinct purpose. They must never be merged, confused or compromised.
Real-time feed to Police
All account activity, device location data and communications are streamed to the investigating police authority in real time. This is live intelligence. It helps find the child. It does not form part of the core evidential record.
Verified copy for investigation and prosecution
A hash-verified copy of the core log is made available to the police and, where formally requested, to the Crown Prosecution Service or its equivalent in the relevant jurisdiction. Access requires the written authority of the Safeguarding Director and a formal written request from the requesting authority. Every access is logged with the name of the person accessing, the authority under which access was granted, the date and time, and the purpose.
Sealed, secured, untouched
The core evidential log is sealed at the point of capture and must not be accessed, modified or released under any circumstances without a Court Order. Its integrity is everything. If it has been accessed without proper authority, its admissibility in court proceedings may be challenged and a prosecution may fail. No member of staff — at any level, including the Safeguarding Director — may access the core log without a Court Order. The log is stored encrypted, password-protected and independently audited.
Section 4Procedure Flowchart
The following flowchart summarises the procedure and evidence architecture. It must be displayed prominently in the human review queue workspace.
Missing or Kidnapped Child — Critical Alert Procedure
Section 5Version Control
| Document Reference | VML-KIDS-CAP-001 |
| Version | 1.0 — Initial Issue |
| Issued | April 2026 |
| Next Mandatory Review | April 2027 |
| Owner | Teravoxus Holdings Limited — Senior Leadership |
Other Critical Alerts
Consequences of Non-Compliance
These procedures are non-negotiable and must never be altered. Failure to follow them could result in serious delay to an investigation and harm to a child, which is unacceptable.
Any delays will be internally investigated and fully audited. Systemic failures will be identified and corrected, training programmes adapted and shortcomings rectified. Any wilful delays or negligent behaviour identified in any member of staff will be considered gross misconduct and grounds for immediate removal from their position pending disciplinary action.
In extreme cases, the matter may be reported to the Crown Prosecution Service, or its equivalent in the relevant jurisdiction, for possible criminal prosecution. This will be especially applicable where such delays can be shown to have caused suffering or harm to a child.