Security Overview

CLIQR treats security as essential infrastructure for customer trust. This page summarizes how we approach protecting CLIQR systems and customer data. It is informational and does not replace contractual commitments in your order form or enterprise agreement.

• Role-based access with least-privilege defaults for internal tools and production systems.
• Strong authentication requirements for administrative access; phishing-resistant options where available.
• Periodic access reviews and automated logging for sensitive actions.

• Data in transit protected using modern TLS configurations for public endpoints.
• Sensitive secrets managed via dedicated secret stores — not embedded in source repositories.
• Logical separation between customer environments where architecturally applicable.

• Centralized logging and alerting for anomalies and service health.
• Backups and restoration procedures tested on a cadence appropriate to risk.
• Incident response playbooks with defined roles for detection, containment, and customer notification where required.

• Dependency and vulnerability tracking integrated into engineering workflows.
• Code review expectations for substantive changes; static analysis where practical.
• Controlled deployment pipelines with auditable release history.

CLIQR evaluates vendors for security posture and contractual data protection commitments. A current list of relevant subprocessors is available upon request for commercial customers.

If you believe you have discovered a vulnerability in CLIQR services, please email security@cliqr.app with detailed reproduction steps. Do not perform destructive testing or access customer data without authorization.

Security questions for procurement or compliance reviews: security@cliqr.app.