For the person using the service
See what changed after refusal, whether the public task still worked and exactly where the evidence stops.
Public App Transparency Lab
The Policy and the Packet
What the app says. What the store says. What the phone did.
Public infrastructure for exact releases, reproducible journeys and verifiable repairs—without crude scores or turning an unexplained connection into an accusation.
01
The policy
What the institution states in the document applicable to the tested release.
02
The store
What the developer declares in the app store’s privacy section.
03
The phone
Which destinations and fields can be observed in a controlled service journey.
30real apps in the R0 registry
4synthetic calibration receipts
0real runtime audits
1verified calibration repair
The interface and standard are ready. The next public fact has to be earned on a device, not filled into a mock-up.
01 · The public problem
One service, three partial accounts
A resident may face a generic policy, a label completed by the developer and network activity they cannot see. The product places them on one timeline and keeps observation separate from inference.
PPR / A
For the institution providing it
Receive the smallest policy, SDK, choice or documentation change capable of removing the discrepancy.
For the people checking it
Get an exact release, repeatable script, evidence hierarchy and public proof bundle that can be challenged.
02 · Anatomy of a receipt
One exact release. One journey. One claim boundary.
A receipt aligns the public documents with the precise moment a connection or field was observed.
Public App Receipt / CAL-0014.8.1
CAL · synthetic
A connection before a choice is not yet a story about profiling.
The fictional scenario below shows the finding, its limit and the smallest repair at the same time.
Replay the whole journeyObserved
The phone contacted analytics.example 420 ms after launch, before the choice screen.
After refusal
After refusal, no further connections to analytics.example were observed in two runs.
Smallest repair
Initialize the analytics SDK only after explicit acceptance, or remove it from the core journey.
Evidence limit
The full content was encrypted; only destination and connection metadata were established.
03 · Evidence language
Each piece of evidence permits one sentence—not a stronger one
The interface does not begin with an adjective. It begins with the evidence class and constrains public language to what that evidence can support.
SDK found
“The tested package contains SDK X. The test did not establish that all its functions were active.”
Package evidence, not runtime evidence.
Connection observed
“The tested release contacted X during this journey.”
The destination is known; the payload may not be.
Readable category
“A request contained device-model information.”
A category is not proof of identity linkage or later use.
Exact synthetic token
“The request contained the synthetic email used only for this test.”
This establishes transmission in that request, not every legal role.
Recipient confirmed
“The institution identified X as its contracted processor.”
Documentary confirmation can resolve a technical inference.
04 · National scope
The seed registry
Thirty apps mediating identity, payments, transport, emergencies and local services. For now they are R0 records: audit selection and context, not technical findings.
R0 · catalogue
taxes and payments
Ghișeul.ro
The mobile app for Romania’s official online public-payment system, used for taxes, fines and other public services.
R0 · catalogue
identity and access
ROeID
Electronic identity used to sign in to Romanian public digital services.
R0 · catalogue
identity and access
ROeVPN
A VPN service intended for accessing certain Romanian public digital services and resources from abroad.
R0 · catalogue
identity and access
RO CEI Reader
An app for reading data from Romania’s electronic identity card chip over NFC.
R0 · catalogue
safety and alerts
Călătorește informat
The Foreign Ministry’s mobile platform for travel information, alerts and consular support.
R0 · catalogue
safety and alerts
DSU
An emergency-information and alert app, including alerts tailored to the user’s location.
05 · Product architecture
Investigation, standard, repair instrument
The same object must be readable by a resident, auditable by an engineer and usable by an institution to fix the problem.
The investigation
A finite set of apps and journeys, tested under editorial thresholds strict enough for every published sentence to survive scrutiny.
The standard
Public App Receipt 1.0 records the release, state, event, destination, evidence, limitation, response and retest.
The repair
A finding does not close on publication. It remains open until the change is documented and the behaviour is retested.
Version 1.0
The product is ready for its first real evidence.
The package includes the lab, protocol, schema, reply process and retest workflow. It does not include invented packets about existing apps.