Security

Security matters twice here in the product and in the proof.

A compliance readiness platform has to earn trust in how it handles sensitive information. This page explains the principles Liance is designed around as the product evolves.

Security trail
01 Access
02 Visibility
03 Trust

Principles

Liance is built around a simple idea: a trust-sensitive workflow should minimize unnecessary access, keep proof traceable, and make it easy to understand who did what and why.

How we think about data access

Where possible, Liance should prefer the least-privilege path needed to collect and organize evidence. The product is intended to make compliance work more reviewable, not to pull in more sensitive information than the job actually requires.

Operational expectations

  • Strong authentication and controlled access to internal systems.
  • Logging and traceability around important product actions.
  • Clear retention and deletion expectations as the product matures.
  • Thoughtful review of the vendors and infrastructure used to run the service.

Reporting concerns

If you believe you have discovered a security issue related to Liance, please contact hello@liance.com with as much detail as possible so we can investigate promptly.

Current state

This security page is part of the public trust layer for the site. As the product and infrastructure become more mature, this page can expand to include details such as security practices, testing approach, disclosure policy, and formal compliance posture.