Skip to content

Privacy policy

What the surveillance module stores, who can reach it, how long it is kept, and what it does not do.

What this policy covers

This policy covers this site and the surveillance module's workspace: what the module stores, who can reach it, and how long it is kept.

PehromGroup is the name this product is built under. The legal entity that operates a particular deployment, the address a privacy question should be sent to, and the grievance officer are facts only an operator can supply; where this page does not name one, it has not been provided yet, and the page says so rather than inventing it.

What is stored

The business data lives in the module's own database. Audit records and diagnostics are written as files on the machine that runs the module, not as rows anyone can query.

  • Accounts: the email address you sign in with and a hash of the password. The password itself is never stored and never written to a log.
  • Cameras: the name, kind, place and state of every camera, and which device claimed it.
  • Events: what a camera reported, its kind, its state, and when it was raised and worked.
  • Investigations and evidence: who opened a case, what was decided to close it, evidence labels, and each move in a chain of custody.
  • Retention rules: what is kept, for how many days, and whether a rule is in force.

What is not done

  • No tracking, advertising or analytics scripts run on this site, and nothing about a visit is sent to a third party.
  • This site sets no cookie of its own. The workspace keeps a signed-in session in the browser's session storage, and that session ends when the browser session ends.
  • Nothing from this module is joined into another module's records or shared sideways with one. Each module has its own database.

Who can reach it

Every screen in the workspace is behind a sign-in, and the module decides what each account may do. There is no public demo and no anonymous view.

A module's administrator governs that module only. Nothing here gives reach into another module's data, people or settings.

How long it is kept

Recordings and events are kept under separate retention rules, each set in whole days. Until a rule is set, nothing is held on a timer.

Changing a rule decides what falls outside the window; removing media stays a separate, deliberate act. Removing a module never deletes its database.