Five refusals
These are the non-goals of the product’s specification. Each heading is the plain form; beneath it is the specification’s own wording.
No fake accounts or amplification
In the specification: “no sockpuppets or amplification”.
No private groups or profiles
In the specification: “no private groups or profiles”.
No public claim of fakery without an analyst’s confirmation
In the specification: no public “fake” claim “without analyst confirmation”.
No recognising private individuals
In the specification: “no identity recognition of private individuals”.
No WhatsApp
In the specification: “no WhatsApp (campaigns are organised there, we see them when they reach public platforms)”.
Why each
The product answers in public only from your organisation’s own official accounts, in its own name, after an approver has said so.
What is collected is what anyone can see in public. Data protection law governs what is kept and for how long, and the product keeps data for a stated purpose and period.
A verdict is a finding about evidence at a stated certainty, and checks can be wrong. A public claim that something is fake carries your organisation’s name, so a person checks the finding before it can be used outside your team.
A face is found in a frame only to decide which checks apply. Who the person is, is not a question the product asks.
Messages on WhatsApp are private. Campaigns are organised there, and they are seen when they reach public platforms; a video or screenshot forwarded from WhatsApp can be submitted and checked as a single file.
How the product enforces it
01
One path to a platform
A single sending service is the only code that can call a platform. It sends only from accounts in your official group, one target per action, and only an action that an approver who is not its drafter has approved. Requiring approval is a locked setting: a change that tries to turn it off is refused.
02
A separate key for sending
The key that can send is held only by the sending service; the key used for collecting cannot reach any sending endpoint. Use of a sending endpoint without a matching approved action raises the highest-severity incident.
03
Public collection only
Every way of collecting is a public listing, search, profile or post. There is no collection mode for private groups, private profiles or WhatsApp.
04
Confirmation before public use
Only an analyst’s confirmation releases a verdict for use outside your team. External reports carry confirmed verdicts only and need an approver to release; a reply can cite only a confirmed verdict, and the analyst who confirmed it cannot approve the reply. The written explanation is refused words such as fake or synthetic unless the verdict found something.
05
No recognition, and faces hidden
The face check gives no score and names no one. External reports have faces in key frames pixelated, drop key frames whose faces were not located, and remove handles and names other than public official handles. Account-level rows never leave internal reports.
06
Recorded
Every approval, verdict and action is written to an audit log that is only ever added to.
Put these five refusals to your legal and risk reviewers, and ask us how each is enforced in an installation.
Request a demo/methodology/will-not-do · What we will not do