ENSTROLL ENSTROLL ENSTROLL
Product How it works Capabilities
Sign in Talk to us
Privacy

Privacy Policy

ENSTROLL is built for operational oversight, so the information it stores is practical: who is using the system, which patrol work was assigned, what happened during a round, and how alerts were handled.

Last updated

July 1, 2026.

Information we collect

We collect the information needed to run patrol operations and secure the product.

  • Account details such as names, work contact details, tenant membership, roles, and sign-in activity.
  • Operational records such as checkpoints, routes, task templates, assigned patrols, check-ins, checklist answers, alerts, acknowledgements, and exports.
  • Device and location information during active product use, including device enrollment details, live patrol location, SOS location, and beacon proximity signals.
  • Technical data such as browser or app version, IP address, logs, diagnostics, and security events.

How we use it

We use this information to provide the service, keep patrol records accurate, notify the right people when something needs attention, secure accounts, troubleshoot issues, and improve reliability.

Location data is used for patrol visibility, checkpoint verification, SOS response, audit history, and related operational reporting. It is not meant for unrelated personal tracking.

Who can see it

Access is controlled by the organization using ENSTROLL. Admins and supervisors may see patrol, alert, location, and audit records according to their assigned roles.

We may work with trusted service providers for hosting, notifications, analytics, support, and security. They only receive the information needed to perform those services.

Retention

Operational records are kept for as long as the customer needs them for security operations, audit, reporting, legal, or compliance reasons, unless a shorter period is configured or required.

Security

We use technical and organizational safeguards to protect ENSTROLL data, including access controls, tenant separation, authentication, logging, and infrastructure protections. No system can be guaranteed perfectly secure, but patrol data should never be casually exposed.

Questions

For privacy questions, data requests, or account-specific concerns, contact [email protected].

ENSTROLL ENSTROLL ENSTROLL
Product Privacy Terms
© 2026 Creobe