Five guarantees
The product’s specification calls these the guarantees that are never traded away. Each is written here in plain words, with every exception the specification gives.
1
Nothing is posted without an approver who is not the drafter.
The list it covers is a reply, a comment, a message, a post and a platform report. The approver holds the approver role and is never the drafter.
2
Media Verdict never certifies media as real.
The list of verdicts has no such value, and every written explanation is checked before it is used.
3
Every configuration change, approval, verdict, flag and action is written to an audit log that is only ever added to.
The database refuses to update, delete or empty a line of the log.
4
Data, logs and reports are stored in India.
The services outside India that this guarantee leaves room for, and what each may receive, are set out by kind on the Data residency page.
5
Every probability shown is calibrated on Indian data, or is labelled uncalibrated.
High confidence needs two validated sources in different kinds of evidence. The only exception is trusted provenance: a valid content credential from a trusted signer, or a watermark from a trusted vendor. No positive verdict is ever built on sources that are not validated.
How each can be checked
| Guarantee | How the product keeps it | How a reviewer can check it |
|---|---|---|
| 1. An approver who is not the drafter | Requiring approval is a locked setting. The approver must hold the approver role and must not be the drafter, the editor of a draft a rule proposed, or the analyst who confirmed a verdict the action cites. Only the product’s own sending component holds the key that can send; the key used for collecting cannot reach a sending endpoint. | Ask a drafter to approve their own draft: it is refused with engagement.approver_is_drafter. Ask for a change that turns approval off: it is refused as a locked setting. A send with no approved action behind it raises the highest-severity alarm. |
| 2. Never certifies media as real | The verdict values are fixed in the product’s record schemas, and none means authentic. Written explanations are checked for words such as fake or synthetic, which are refused unless the verdict found something. | Read the verdict values in the record schemas. Read any verdict’s explanation beside its record. |
| 3. An audit log only added to | The database itself refuses to update or delete a line of the log. A refusal on policy grounds is written to the log as a new line. | Ask for a change to an existing line in a test: it is refused. Read the log on the Audit screen. |
| 4. Stored in India | The stores run in India. The configuration lists each outside service with an external address by kind, with the data it may receive, and its check fails if such a service is switched on without a row. The sending service and the alert and delivery channels are set out by kind on the Data residency page. | Read the list of outside services in the configuration, and run the configuration check, which is the same command the build runs. |
| 5. Calibrated or labelled | Without a validated calibrator, a score is shown in place of a probability and marked uncalibrated. In an installation’s configuration, no check decides a verdict without a validated row in the ledger; a setting that would let one is a protected change and is flagged by the configuration check. | Each probability or score on screen is marked as calibrated or not. Each verdict names the rule that decided it. The validation ledger lists which checks are validated, for which kind of media. |
Two people
Guarantee 1 is a control, not a convention. One path leads to a platform, and each step on it is recorded.

01
The draft
An analyst writes it, or a rule proposes it from the fields of the records. A proposed draft needs a person to edit it before anyone can approve it.
02
The second person
An approver, who under the installation’s sign-in requirement uses two factors, and who did not draft, edit or confirm what the draft cites, approves it with a reason.
03
The send
Only an approved action is sent, from an account in your official group, to one target.
04
The record
Who drafted, edited, approved and sent, and when, is in the engagement log and the audit log.
Take each guarantee to your reviewers, and ask us to show the check beside it on an installation.
Request a demo/trust/guarantees · The five guarantees