Answer
Mixer No Logs
“No logs” is a claim about what a service says it stores. It is not proof that nothing was stored, and the only way to check it is the statement itself — and what the service publishes alongside it.
direct answer
No-logs is a stated policy you can read, not a fact you can observe.
Framing follows the site's privacy claim requirement: absence of logs must be claimed and evidenced by the service itself, not inferred from absence of evidence.
Why the distinction matters
Absence of evidence is not evidence of absence
A service claiming no logs makes an assertion about its own storage. You cannot verify the negative from outside — you can only verify that the claim exists, is written down, and is specific about what is not kept and for how long.
The practical test: does the service say what it does not store, or does it just say “private”? Vague privacy language carries no information; a specific statement can be checked against the service's behaviour.
Evaluate the claim
Four tests for “no logs”
What you can verify
- — The statement exists and what exactly it covers.
- — Whether the service's requirements imply stored data.
- — Whether the policy names retention or disclosure terms.
What stays a claim
- — That no data was in fact retained — only the service knows.
- — That no logs means anonymity — a different property.
- — That the policy was followed in a specific past case.
source_state: No-logs evaluation criteria follow the site's privacy claim requirement (claim policy, 2026-10-30); no service is named as having or lacking logs without its own documentation. (recorded 2026-10-30)
Read the policy before the deposit
Continue to the handoff screen: the handoff destination is a separate service, shown before you go.