Trust

Security built for public safety

Agencies trust REDENES with incident, personnel and location data. Here is how we protect it, and how to tell us if you find a problem.

Last updated October 24, 2026

How data is protected

  • Encryption: all traffic uses TLS. Data is encrypted at rest in our databases, storage and backups.
  • Access control: role-based permissions let each agency decide exactly what each member can see and do, down to individual modules.
  • Device registration: sessions are tied to registered devices with short-lived access tokens and refresh tokens, and administrators can remove a device.
  • Agency separation: each agency's data is kept separate, and sharing with another agency happens only when an administrator turns it on, for a set time.
  • Least privilege: our staff access customer data only to support the customer or keep the service running.
  • Hosting: REDENES runs on Amazon Web Services in the United States.
  • Monitoring and backups: we monitor the service around the clock and keep regular backups. Live status is at status.redenes.com.

Your agency's part

  • Give each member only the roles they need.
  • Remove members and devices promptly when people leave.
  • Use a screen lock on every device that runs REDENES.

Report a vulnerability

If you believe you have found a security problem, email info@redenes.org with the subject "Security report" and enough detail for us to reproduce it. We will acknowledge your report within three business days and keep you updated.

Please test only against your own account, do not access or change other people's data, do not degrade the service, and give us reasonable time to fix the issue before telling others. We will not pursue legal action against good-faith research that follows these rules. Our security.txt lists the same contact.