Security

Hailer protects your data at every step: when it travels, when it is stored, and when someone tries to access it.

Encryption

• In transit: all connections to Hailer use HTTPS (TLS). Browsers are required to always use a secure connection.
• At rest: the database, uploaded files and backups are encrypted.
• Passwords are never stored. We keep only a secure hash.

Access control

• Workspaces are separated. Users see only the workspaces they are members of.
• Roles and permissions. Workspace owners and administrators decide who can see and edit workflows and other workspace content.
• Files are available only to users with access to them, unless they are shared publicly, for example by an app, on a public form, or as a profile picture.
• Hailer staff access customer data only when needed for support and operations.

Sign-in

• Password sign-in requires a strong password.
• Single sign-on with Google or Apple, and Microsoft Entra ID for organization-managed accounts, lets your organization apply its own security rules, such as two-factor authentication.
• Account lockout: after repeated failed sign-in attempts the account is locked, and the user receives a one-time sign-in link by email.
• Inactive sessions expire automatically.

User API keys

• User API keys are shown only once when created and stored as a secure hash.
• Keys can be limited to specific IP addresses.

Infrastructure

• Hailer runs on AWS in private networks protected by firewalls.
• Video calls run on Hailer's own servers.
• Systems are monitored, and security updates are applied regularly.