Govern
ARBITER access control
The query, target, purpose, requested range, current rules, legal basis, and required approval must agree before access is allowed.
Privacy Gate · Powered by ARBITER
Public safety without blanket surveillance access.
Privacy Gate puts a policy and authority boundary in front of sensitive surveillance access. The question is not whether a database can return location history. The question is whether this person or system may perform this search, for this purpose and requested range, under the current rules.
See the Utah proofOpen the integrator decision roomDiscuss a government or partner pilotSee the underlying ARBITER Gate
request → purpose and rules → approval if required → limited access → reviewable record
The core rule
Knowing the target is not authority to search the target.
Access to a plate, person, camera, or historical dataset is information—not permission. Privacy Gate checks the purpose, current rules, requested range, and required approval before sensitive access proceeds.
The product boundary
Govern the query. Do not attack the camera.
INTIGNAI is building a legitimate control layer for surveillance systems—not jamming, dazzling, plate obscuring, RF interference, anti-tracking evasion, or evidence destruction. The goal is less unnecessary collection and harder unauthorized access while preserving authorized public-safety workflows.
Control before access
Apply the rules before sensitive access happens.
- 01A person or system requests an exact surveillance-data action.
- 02Privacy Gate checks who is asking, the target, purpose, requested range, data source, and current rules.
- 03Current policy and required evidence are checked before access.
- 04Broad or sensitive requests can require approval for that exact use.
- 05If the target, requested range, rules, or approver context changes, the earlier approval no longer applies.
- 06The decision leaves a reviewable action record before any connected provider is allowed to act.
Product architecture
One control model, three practical layers.
Prove
Reviewable action records
Every important decision can preserve what was requested, what rules applied, who approved it, and what happened afterward.
Minimize
Provider-neutral boundary
Existing ALPR or CCTV systems can stay in place behind a limited connection. Technical capability never becomes blanket permission.
First jurisdiction proof
Utah: policy requirements turned into testable decisions.
The first Utah profile models a narrow law-enforcement captured-plate search path. It shows allowed public-safety purposes, required search evidence, blocked requests when required controls are missing, court-authority handling for nongovernmental data, supervisor approval for broader searches, and tamper-evident records of decisions that do not execute.
This is an engineering proof profile, not a claim of statutory completeness, legal advice, compliance certification, production deployment, or connection to a live ALPR provider.
Who can use it
One system, different accountability views.
States and municipalities
Turn purpose, retention, sharing, and audit requirements into controls that can block missing or invalid requests before access instead of relying only on after-the-fact review.
Law-enforcement leadership
Preserve legitimate investigative capability while making unauthorized or overbroad access mechanically harder and producing evidence that protects defensible use.
Privacy and oversight teams
Inspect what policy allowed, denied, held, or escalated without exposing live investigative targets or turning transparency into operational leakage.
CCTV / ALPR integrators
Keep existing hardware and deployment competence while adding a provider-neutral authority/privacy layer that supports public-safety governance and a lower-friction construction/private-security product path.
For a pilot jurisdiction
Start as an overlay before replacing infrastructure.
The practical first deployment adds controlled access around an existing workflow: one query type, one rule set, clear approvals where required, and a reviewable action history. Provider connections are set up separately and cannot expand permission just because an API supports more capability.
Scope a Privacy Gate pilotFor a hardware/integrator partner
Keep the field stack. Add the layer buyers will increasingly ask you to prove.
The partner decision room shows how an existing CCTV/ALPR company can preserve its hardware advantage while adding clear approvals, reviewable action history, and a privacy-focused construction/private-security offering without handing INTIGNAI customer secrets or live credentials.
Open the partner demo