Professional access
Planned access uses a work email and a verification code. Access conditions, employee departures and account management arrangements need to be defined.
Use & privacy framework
Trust begins with understandable uses and clear limits. These are the intended principles and the topics to document with each organisation.
Planned scope · Project overview
To clarify before any deployment
Framework
Evalert is designed as a complementary coordination tool. It is not intended to replace alarms, site instructions or emergency procedures.
Design principles
A framework for preparing product use, to turn into practical arrangements with your organisation.
Planned access uses a work email and a verification code. Access conditions, employee departures and account management arrangements need to be defined.
The coordinator triggers and closes an alert; employees read and respond. Responsibilities and permissions must be defined before use.
An alert’s scope is based on the relevant site. The organisation must clarify who is assigned to the site and how that information is kept up to date.
Location sharing is planned during an alert, subject to permissions and technical conditions. No continuous tracking outside an alert is presented.
Phone, operating system and network settings influence available capabilities. Their configuration and limitations must be explained to teams.
Purposes, data categories, recipients, retention periods, processors and the exercise of rights must be documented before deployment.
To clarify before any deployment
These principles do not constitute a certification or legal or technical validation. Hosting, security measures, availability and compliance remain to be specified and validated.
Read the draft privacy policyEvalert / Your organisation comes first
Tell us about your organisation to prepare a study, request a quote or discuss whether a site visit would be useful.