Security & Trust

Last updated: August 24, 2026

LeadsQue is built for teams handling sensitive customer and lead data. Here is what actually protects that data today.

Encryption

All traffic to and from LeadsQue is encrypted in transit via TLS.
Data at rest is encrypted by our database infrastructure.

Tenant isolation

LeadsQue is multi-tenant: every record belongs to exactly one company (“tenant”). Data isolation is enforced at the database level via row-level security policies, not just application code — a request authenticated as one tenant cannot read or write another tenant’s data, even in the event of an application-layer bug.

Access control

Role-based access: what a user can see and do is scoped to their role (Sales Rep, Manager, Director, Operations).
API keys used for integrations are stored hashed, never in plain text, and can be revoked instantly.

Public integration endpoints

Where LeadsQue accepts data from external sources (e.g. ad platform lead forms), each source is authenticated independently and every incoming submission is captured as an immutable raw record before any processing — so any issue can be traced back to exactly what was received and when.

Reporting a concern

If you believe you’ve found a security issue, contact contact@regalnex.com.

[Add any additional measures here once decided — e.g. MFA, third-party audits, SOC 2/ISO status. Do not claim a certification LeadsQue doesn't hold.]