The duty to inform lies with the venue operator, not the individual

What it is

The responsible party for public-sensing notice is the venue operator — the mall, the station, the property manager, the municipality — not the person being sensed. The default of "those who want to know will go read the policy" shifts the cost of notification onto every passer-by, while the information notification requires (what is installed, where, retained how long, used by whom) exists only on the operator's side. Notice is the operator's duty, not the user's skill.

Why the "individual look-up by default" model must fail: it assumes a world where everyone has the motive, ability and channel to check. The actual crowd is passing through, catching trains, preoccupied with something else; requiring each of them to initiate a policy enquiry for every space they enter designs a right that is certain to go unused. Data-protection legislation almost universally places the transparency obligation on the data controller — a institutional response to exactly this structural failure.

Why it happens

• The information asymmetry is irreversible: the sensing configuration is the operator's private information; however proactive the individual, they cannot look up what was never disclosed. The deeper trap is non-verifiability: even with a published registry, checking its completeness (any unregistered cameras?) is something only the operator can do. Placing the notice duty on the individual side asks the party without information to verify the party holding it — logically sealed shut.
• The efficiency logic of cost allocation: one compliant disclosure serves every person covered, at one-time cost; distributed look-up requires each person to repeat it, and almost no one will. The cost of notice should fall on the cheapest side — operator disclosure is orders of magnitude the cheaper social arrangement. This is not a moral judgement but an efficiency rule of institutional design.
• Aligning benefit with risk: the gains of collection accrue to the operator (security capability, operations data, cost savings); the risks fall on the sensed (exposure, misuse, breach). The duty to inform is the minimal mechanism reconnecting the two — the beneficiary of the gains bears the cost of explanation. Remove that connection and the risk is externalized as an ownerless cost.

Studying it

• Compliance-gap audits: surveys of notice practice in venues (how many carry the basic elements, at what position and readability) — empirical mapping of the compliance gap is a standard output of policy research.
• Legal and institutional analysis: analyses of "notice as controller duty" in data-protection scholarship; comparisons of actual awareness rates under different allocations (operator-push notice vs individual-pull enquiry).
• Natural experiments on awareness: comparing awareness rates between venues with active notice and venues with "query available" policies — a direct test of the two allocations.

Methodological caution: when evaluating an operator's notice effectiveness, the sample must cover non-regular visitors (passing-through, first-time) — regulars may know through other channels, overstating the notice's own effect. Report awareness stratified by visit frequency.

Where it stops holding

• The outward duty cannot be subcontracted: the operator and the sensing vendor (third-party analytics) may divide labour internally, but the duty toward the public always hangs on an operator the public can reach — "the system is outsourced" is no defence for missing notice.
• Duty intensity tracks intrusiveness: for low-intrusiveness, non-individualizing counting, meticulous per-site posting has low marginal value and simplified notice is acceptable; identifying, individual-linking collection (faces, plates, identity joins) warrants full registry and prominent signage. The grading principle matches the grading of notice content.
• Jurisdictions differ but the principle is stable: duties for governmental venues are usually codified; private venues rest on industry norms and consumer protection, with varying strength. This entry fixes the allocation principle (whoever benefits explains; whoever holds the information discloses); execution standards follow the jurisdiction.
• This entry governs only the allocation of responsibility; what the notice looks like (content, prominence, persistence) belongs to the neighbouring entries.

Applying it

• Establish a space-sensing registry: the operator maintains a public registry (type / purpose / coverage / retention / responsible party / enquiry contact); signs point to it, published online and at the entrances.
• Fold notice into facility acceptance and change management: opening and renovation acceptance include a notice-compliance check; adding sensors, changing purposes or vendors triggers a synchronized update of registry and signage — a process slot comparable to the fire inspection, not a publicity item.
• Keep a single reachable responsible party: whoever is posted must be findable, addressable and chargeable by the public (the venue operator), not a tech vendor's hotline.
• How to check: audit physical deployment against the registry item by item (any device found on site but absent from the registry is a violation); periodic intercept surveys of awareness as the operator's annual notice-effectiveness metric, reported to management.

Related

• Same group: Z8.03.1 Sensing in public places requires noticeable and persistent notice · Z8.03.2 Notice must state the purpose of collection, not merely the fact · Z8.03.3 The lack of an exit is what separates public monitoring from personal devices
• Nearby: Z6.06 Awareness of passive collection · Z8.04 Making city data visible and participatory
• Search terms: duty to inform · transparency obligation · data controller · privacy signage