Security & Data Layers
Institution-grade isolation by default.
Security is not a configuration a customer opts into — it is the default state of every table and every session Houndtid touches. This page describes the architecture, plainly.
Row-level security by default
Every table our systems touch is governed by RLS policies scoped per tenant and per actor role. Isolation is enforced at the database layer, so an application-layer defect cannot become a cross-tenant data exposure.
Encryption in transit and at rest
Standard across every environment — not an add-on tier reserved for enterprise contracts. Data is encrypted the same way whether you're a pilot customer or a national ministry.
Scoped authentication
Google OAuth connector architecture with per-service scoping — Gmail, Drive, and Calendar access are granted and revoked independently, never bundled into a single all-or-nothing permission.
Incognito by design
Users can opt into a session mode where conversation history is not persisted at all — a deliberate architectural choice, not a settings toggle bolted on after the fact.
System status