Security & Transparency

What We Protect

ClearHouseHQ stores and processes:

• •User accounts: Login credentials, contact info, preferences
• •Case data: Incident details, descriptions, status, metadata
• •Evidence uploads: Files you upload (photos, documents, correspondence)
• •Audit logs: Who did what and when

How We Protect It

ClearHouseHQ is designed with the following controls:

• •Encryption in transit: All traffic uses HTTPS/TLS 1.2+
• •Tenant isolation: Data is logically separated by organization; users see only their org's data
• •Access controls: Access is restricted through authenticated user access and share-link collaboration flows where explicitly enabled
• •Audit logging: We maintain logs of sensitive operations for accountability
• •Backups & monitoring: Operational backup and monitoring practices are used to reduce data-loss and availability risk

What We Don't Promise

• •No compliance certifications: ClearHouseHQ is not SOC 2, HIPAA, or legally compliant out-of-the-box. Compliance depends on your industry and how you use the tool.
• •Not a law firm: We provide property-defense legal-ops workflow tooling. We are not lawyers and do not provide legal advice.
• •Not guaranteed incident response: While we aim for availability, we do not guarantee 99.9% uptime or specific response times for security issues.

Report a Security Issue

If you discover a security vulnerability, please email us at:

Please include:

• • Description of the vulnerability
• • Steps to reproduce (if possible)
• • Affected endpoints or features
• • Your contact information

We review security submissions as quickly as possible, but do not publish a guaranteed response SLA on this page.

Infrastructure & Subprocessors

ClearHouseHQ uses third-party cloud infrastructure and services. If you need current infrastructure or subprocessors information for diligence review, contact the contact page and we will route the request appropriately.