The receipt preserves the original finding and shows the verified repair instead of erasing history.
We compare the service outcome and connections after refusal with the state before choice. A non-observation remains a non-observation; it does not become a claim that a service can never appear.
metrics.example was not contacted after refusal in three runs.
Select a state to compare the three sources at the same moment. All states remain available when JavaScript is disabled or the receipt is printed.
The choice screen appeared before analytics initialisation.
In the revised policy, analytics remains optional.
The store declaration was updated on 4 August 2026.
Across three clean runs, no connection to metrics.example was observed before acceptance.
repeated non-observationLimit: This does not prove absence in untested features or future configurations.
Account activation continued without analytics.
The policy states that the core service remains available.
The store label marks analytics as optional.
metrics.example was not contacted after refusal in three runs.
repeated non-observationLimit: It does not verify deletion of events collected by the old version.
Analytics started after affirmative action.
The policy describes timing and purpose.
The store label declares app activity.
The first connection to metrics.example appeared 310 ms after pressing “Accept”.
screen + connectionLimit: Connection timing does not establish every transmitted field.
Sign-in remained available.
The policy describes stopping future analytics.
The store label does not detail the mechanism.
After withdrawal and restart, metrics.example was not contacted in three runs.
repeated non-observationLimit: Server-side retention was not tested.
A domain, infrastructure owner and legal recipient are different propositions. Each relationship carries its own provenance state.
metrics.examplethird partyThe connection appeared only after acceptance in the retest.
Claims are stored separately so a response, correction or retest can change one proposition without silently rewriting the rest.
Maximum wording: We can say the repair passed the retest journey, not guarantee all future behaviour.
The actor, minimum change and verification test remain attached to the original claim.
REP-CAL-301
Delay SDK initialisation until after acceptance.
Three clean installs covering refusal, acceptance and withdrawal.
Verified: August 5, 2026
cccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc
A real receipt would link every public claim to a sanitised evidence artefact and retain raw captures in a restricted vault.