Security and disclosure
Every message you send us may be an attack. We treat its text, attachments and links as untrusted data, open links only inside a short-lived browser with strict limits, and let rules cap what a model can say.
By Derick Payne, Rizonetech · Reviewed 31 Oct 2026
Email bodies, PDF text, page text and voice transcripts reach a model only inside delimited untrusted blocks, after hidden text has been pulled out as evidence of its own. A model never decides who receives mail: recipients, subjects and templates come from code.
When deterministic checks find critical evidence, such as changed bank details, a login form on a lookalike domain or a dangerous attachment type, the verdict cannot be Clean whatever a model says. A model can raise severity, never lower it below the floor.
Every sentence in a verdict must cite an Evidence ID from the checks that ran on that case. If a model cites a missing ID, the verdict is rejected, retried once, and then replaced by the rule-based verdict.
When Muse Wonder walks a suspicious link, the driver, not the prompt, enforces the limits: http and https only, at most 8 steps and 60 seconds, no file downloads, and only per-case canary details typed into forms. Every action is logged.
Every model output and tool argument is checked against a strict schema before it is used, and tool calls run in auto mode only.
Every call to Meta's Model API uses a Standard model ID with store: false, which asks Meta not to keep the request. Meta's API terms allow Meta to train on content only in Contributor mode, which we never use, and they publish no fixed retention period for requests.
Meta's Model API pricing and data termsFull data-handling details are on our Privacy and POPIA page.
Please report security issues privately through GitHub Security Advisories or by email to hello@isitlegit.co.za rather than a public issue, so we can fix the problem before details are public. We confirm receipt and who is handling your report within 3 working days, and credit reporters who want to be named once the fix is live.
In scope: the Worker, the report and verify pages, the mail intake pipeline, the walkthrough containment, and the tenant and bank-verification boundaries.
If you do not use GitHub, email hello@isitlegit.co.za directly.
