Privacy

Who is responsible for your data

EvaCount is sold to organisations — employers, building owners and building operators. When your workplace or building uses EvaCount, that organisation decides who is registered, what is recorded and how long it is kept. Under the GDPR they are the data controller, and Horseloop AS is their data processor: we handle the data only on their documented instructions, under a written data processing agreement.

If you use EvaCount because your employer or building operator uses it, address requests about your personal data to that organisation first. We will assist them in answering you.

For the evacount.com website, for demo requests, and for people who contact us directly, Horseloop AS is the controller.

What we process

The app requests notification permission, and asks for camera or photo-library access only at the moment you attach an image. It does not request microphone access; the recording permission is explicitly removed from the app.

Account and identity

Your name, work email address, phone number where your organisation provides one, language preference, and which organisation, building and floor you are attached to.

Evacuation and drill records

Whether you marked yourself as safe or requested help, when you did so, and which incident or drill it belongs to. This is the core of the service — it is what makes a roll-call possible, and it is retained as documentation of the drill.

A position you choose to share

If you request help, you may tap your position on the building’s floor plan. That records a floor and a point on that drawing. EvaCount does not use your phone’s GPS or any device location service, and it does not track your movements at any time.

Photos you attach

Images you deliberately add to an incident review, either taken with the camera or chosen from your photo library. Only the images you actively attach leave your device; the app has no access to the rest of your library.

Push notification tokens

An identifier issued by Apple or Google for your specific installation, so an alarm can reach your device. It is not tied to your phone number or your advertising identifier.

Technical and usage data

App version, device model, operating system version, crash and performance diagnostics, and product analytics events describing how the app is used.

Why we process it, and on what legal basis

To run an evacuation and produce a roll-call

Performance of the contract between your organisation and Horseloop AS, and your organisation’s legitimate interest in knowing whether everyone got out. Where you have requested help, we also rely on the vital interests of the person concerned (GDPR article 6(1)(d)).

To document drills and incidents

Your organisation’s legal obligation and legitimate interest: Norwegian fire prevention regulation requires systematic fire safety work, including training and drills, to be carried out and documented.

To deliver alarms to your device

Necessary to provide the service you have been enrolled in. An evacuation alarm cannot work without a way to reach the phone.

To keep the service secure, available and correct

Our legitimate interest in operating a reliable life-safety system — diagnosing crashes, preventing abuse, and fixing defects before they matter.

Analytics, crash reporting and session replay

In the production app we use PostHog for product analytics and session replay, and Sentry for crash and performance diagnostics. Both are configured to store data in the European Union.

Session replay records how the interface is used, so we can see where people hesitate in an interface that has to work under stress. It is configured to mask all text input and all images before anything leaves your device, so what you type and the photos you attach are not captured.

Analytics and crash reports identify you only by a pseudonymous user identifier. We do not send your name, email address or phone number to these tools, and Sentry is configured not to attach IP addresses or device identifiers.

Test and development builds of the app send no product analytics at all.

Who we share it with

We use a small number of processors to run the service:

Apple and Google

Apple Push Notification service and Firebase Cloud Messaging deliver alarm notifications to iOS and Android devices. Without them a phone cannot be woken.

Expo

Routes push notifications from our servers to Apple and Google.

Sentry

Crash and performance diagnostics, stored in Sentry’s EU region.

PostHog

Product analytics and session replay, stored in PostHog’s EU cloud.

Our hosting provider

Runs the servers, the database and the storage holding uploaded images.

• We do not sell personal data.
• We do not use it for advertising or profiling.
• We disclose it to public authorities only where the law requires it.

Transfers outside the EEA

The service, its database and our analytics and error-tracking processors are configured to keep data within the EU or EEA.

Push notification delivery necessarily involves Apple and Google, which are United States companies. Those transfers rely on the European Commission’s adequacy decision for the EU–US Data Privacy Framework, and on standard contractual clauses where it does not apply. The content of an alarm notification is limited to what is needed to raise the alarm.

How long we keep it

Account data

For as long as your organisation subscribes and you remain registered with it. When either ends, the account is deleted or anonymised within 90 days.

Evacuation and drill records

For the retention period your organisation configures, because these records are the documentation of the drill. Your organisation decides this, not us.

Photos attached to incidents

Kept with, and deleted with, the incident record they belong to.

Crash and performance diagnostics

Up to 90 days.

Product analytics and session replay

Up to 12 months.

How we protect it

• All traffic between the app, the portal and our servers is encrypted in transit.
• Sign-in credentials and session tokens are held in the operating system’s secure storage — the iOS Keychain or the Android Keystore — not in ordinary app storage.
• Access to production data is restricted to the people who need it to operate the service, and is logged.
• Analytics tooling is configured to minimise what it collects rather than to collect what it can.

Your rights

Under the GDPR you have the right to access the personal data held about you, to have it corrected, to have it erased, to restrict or object to its processing, and to receive it in a portable format. Where your employer or building operator is the controller, these requests go to them and we will assist them in answering.

You can withdraw consent to camera and photo-library access at any time in your device settings; the rest of the app continues to work. Turning off notification permission will stop evacuation alarms from reaching you, which is worth thinking about carefully.

If you believe your data is being handled incorrectly, you may complain to the Norwegian Data Protection Authority (Datatilsynet) or to the supervisory authority in your own country.

Children

EvaCount is a workplace and building safety tool. It is not directed at children and we do not knowingly register anyone under 16 other than through an organisation that is responsible for them.

Changes to this policy

If we change how the service handles personal data, we will update this page and the date shown at the top. Material changes are communicated to the organisations using EvaCount, who are responsible for informing their people.

Contact

Horseloop AS, Fossanveien 237, 3175 Ramnes, Norway.

Email: hei@evacount.com

Organisations using EvaCount can request our data processing agreement and the current list of sub-processors at the same address.