Predict the Runtime Privacy Gate
Predict the Runtime Privacy Gate
Predict the Runtime Privacy Gate
For the door alert, compare two payloads. The first contains flat=12, state=OPEN, time=02:14, and purpose=safety-response. The second adds resident name, full battery history, and the last week of door events. Only the first payload fits the immediate alert. The extra fields create more privacy exposure without helping the on-call worker answer the door event.
Privacy enforcement should also expose a reason code when it blocks a field. A denial such as purpose-mismatch helps the service distinguish a policy result from a broken door sensor or network timeout.
Now test a purpose change. A maintenance engineer may need battery voltage and device fault code, but does not need the resident’s night-time door pattern. Runtime enforcement can form a maintenance payload from those device fields and omit the household event trail. This is not one global “allow” switch. It is a field and recipient decision for each purpose.
The user-facing control must reach the same runtime policy. If optional analytics is off, the device or earliest trusted service should block the analytics fields before they enter a shared log or retry queue. Removing them only from the final dashboard leaves copies elsewhere. A regression test, which checks that an update has not broken earlier behavior, should inspect the outgoing message and the stored record after a software update.
Emergency access also needs a narrow end. A break-glass rule is a limited emergency override. It can record who used it, why, which flat was opened, and when access will close. It should not turn into permanent support access after the event. The running privacy system must return to its normal role and retention limits.
- Predict: A support worker requests last night’s detailed door events during an active safety call. The role, purpose, and time window match. What should happen? Check: The runtime policy can permit the minimum detailed view needed for that call and record the decision.
- Predict: A product analyst requests the same flat-level door trail to improve engagement. Does the safety consent automatically cover that use? Check: No. The new purpose needs its own lawful basis, the legal reason for using the data, field limit, and user-facing choice.
- Predict: The retention job fails and detailed events remain after their deadline. Is a written 30-day rule enough? Check: No. Runtime privacy requires evidence that expiry actually removed or de-identified, with details that identify people removed the stored events.