Skip to content
Sections

Security

What Claria is designed to do to keep each organization's alerts and reports apart, and what is still planned.

A separate portal for each organization

Each organization is designed to have its own address and its own space for cases. A report is tied to the organization it was sent to.

Protection of stored data (planned)

Protecting stored data, including separate keys for each organization, is a design goal that is still being integrated into the product. It should not be read as already in force.

Role-based access and audit trail

Access to cases is limited by role: the people your organization assigns can see a case. An audit trail of actions is planned and still being integrated.

Sign-in security you control

Each organization chooses whether a second step (MFA) is required, optional or off, and which methods are allowed.

Data this site collects

This site currently uses only functional cookies for your language, theme, country for prices and sign-up progress. It does not include analytics or advertising tools. The full list of data is described in the Privacy Policy.

Tracking codes

A reporter's tracking code is shown once and only a keyed hash of it is stored, so the code itself cannot be read back from the database.

No system is risk-free, and Claria does not promise absolute anonymity or confidentiality. Whether a report can be anonymous depends on the policy your organization sets. Claria is software, not legal advice.

Back to home