Synthetic example showing how the product separates an observed connection from a conclusion about transmitted content.
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.
After refusal, no further connections to analytics.example were observed in two runs. The synthetic value LAMPA-7Q2 was observed in the request to api.orastest.example.
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 app opened. The form had not yet been used.
The policy describes optional analytics after consent.
The store label declares app activity for analytics.
The phone contacted analytics.example 420 ms after launch, before the choice screen.
connection observedLimit: The full content was encrypted; only destination and connection metadata were established.
Consent is described as optional.
The store label does not describe initialization timing.
The choice screen appeared after the first analytics connection.
screen + connectionLimit: This does not establish that a personal identifier was transmitted.
The report could be submitted without optional analytics.
The policy says refusal does not affect the core service.
The store label says deletion can be requested.
After refusal, no further connections to analytics.example were observed in two runs.
repeated non-observationLimit: Absence in one journey does not prove the service cannot appear in other features or under remote configuration.
The policy describes sending the photo, location and text to the institution.
The store label declares photos and location for app functionality.
The synthetic value LAMPA-7Q2 was observed in the request to api.orastest.example.
exact synthetic tokenLimit: The value establishes transmission to the service endpoint; it does not by itself establish each operator’s legal role.
The core service and optional analytics operated.
The policy describes pseudonymous usage events.
The store label declares app activity.
Connections to analytics.example continued. A readable event_name=report_submitted field was observed; the full identifier was not interpreted.
readable data categoryLimit: An event name does not show whether the provider can link it to a person.
Reporting remained available.
The policy promises to stop future analytics.
The store label gives no withdrawal detail.
After withdrawal and restart, analytics.example was not contacted in two runs.
repeated non-observationLimit: The test does not verify deletion of data already held server-side.
A domain, infrastructure owner and legal recipient are different propositions. Each relationship carries its own provenance state.
api.orastest.examplefirst partyThe synthetic report text was observed in the payload.
analytics.examplethird partyThe destination and an event name were observed; the full identifier was not established.
Claims are stored separately so a response, correction or retest can change one proposition without silently rewriting the rest.
Maximum wording: We can state when the connection began; we cannot state that profiling occurred.
Maximum wording: The exact value left the device in the observed request.
The actor, minimum change and verification test remain attached to the original claim.
REP-CAL-001
Initialize the analytics SDK only after explicit acceptance, or remove it from the core journey.
Repeat the journey on a clean install and confirm no pre-choice connection.
ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
A real receipt would link every public claim to a sanitised evidence artefact and retain raw captures in a restricted vault.