What our evidence establishes¶
Every claim needs a scope: an app version, the path inspected and the kind of check performed. This first documentation snapshot follows main commit 6102fa9, released as v1.8.0, with evidence reviewed on 28 October 2026. Dumpert was added against main 8ca0ddb (v1.9.0) later in the same writing session. Earlier app evidence keeps its original source pin. Later app or patch versions need their own review.
Five kinds of evidence¶
| Label | What it establishes | What it leaves open |
|---|---|---|
| Documented capability | A provider documents a feature or data field. | Whether this app enables or uses it. |
| Traced in app code | Inspected call paths create events, pass values or reach a sender. | Whether a particular phone session executed that branch. |
| Configured / shipped endpoint | A resource or SDK declares/selects a destination. | Whether a request occurred and what the server retained. |
| Web policy coverage | The patch blocks an identified request if that web content loads it. | Whether every listed domain was present in a session. |
| Runtime observation | A recorded action, log or inspected request demonstrates specific behaviour. | Other actions, devices, accounts, later configuration and server-side uses. |
An embedded SDK may be inactive. Exodus makes the same distinction in its methodology FAQ. A DNS connection record establishes a contacted name; it does not expose every encrypted payload field.
How the patches are checked¶
The existing project checks individual selections and combinations, rebuilds/signs artifacts, independently decodes output and verifies changed and retained contracts. Device reports add startup and feature checks. These checks answer different questions: a correct code replacement, a valid installation and a working article view do not amount to a network-capture audit.
The existing destination evidence register records provenance and unknowns. The app pages link their detailed audits. No new packet capture or device test was performed for this writing pass.
Claims we keep separate¶
We do not infer sale, onward sharing, retention periods, legal compliance or a person's real identity from a hostname alone. A code field that can connect events supports an explanation of linkability; downstream profiling requires separate evidence. A blocked sender does not establish that every service in an app has stopped collecting.
When something changes¶
Review the original app version, patch bundle version, inspected paths and retained services again. Keep old source references available. Mark evidence added by a new capture separately from older static findings. Corrections are welcome through GitHub issues.