Your Legal Data
Never Touches Our Servers
A deep dive into our privacy-first architecture across all tiers. Learn how we've designed inchambers.ai so that your confidential client information stays exactly where it belongs: with you.
Privacy-First by Design
Client-Side Processing
All document analysis happens in your Microsoft Word instance. Your contracts never leave your computer.
Your Keys, Your Control
You bring your own API keys. They're stored encrypted on your computer or infrastructure, never on our servers.
No Sensitive Data Logging
We never log, store, or analyze your documents, prompts, or AI responses. We only track superficial usage metrics (DAU/MAU).
OAuth Without Admin Consent
Our authentication system is designed to work seamlessly without requiring organization-wide administrator approval.
Individual Consent Only
Users authenticate with Google or Microsoft using standard OAuth 2.0. No admin approval needed, no special permissions required.
- Works with any Google or Microsoft account
- No IT department or admin involvement
- Instant access after sign-up
- No organization-wide approval required
Scoped Permissions
We request only the minimum permissions needed for authentication and encrypted template backup.
- Basic profile only (email and name)
- Drive/OneDrive: app-created files only
- No access to personal docs or files
- Used only for encrypted template backup
What We Store:
User Account Data:
- Email address
- Name (from OAuth profile)
- Subscription tier and status
- Request count (free tier limit)
Identity and billing only
Usage Analytics:
- Active user counts (DAU/MAU)
- Feature usage timestamps
- Request counts per user
- Session duration metrics
Counts and timestamps only
What We DON'T Store:
- API keys (client-side only)
- Document content
- AI prompts or responses
- Templates or encryption keys
No sensitive data on our servers
How We Compare
Understanding the difference between our privacy-first approach and traditional SaaS AI tools.
| Feature | inchambers.ai | Traditional AI SaaS |
|---|---|---|
| Document data sent to vendor | ||
| API keys stored on vendor servers | ||
| Client-side processing | ||
| Self-hosted proxy option | ||
| Works with any AI provider | ||
| Admin consent required | Often | |
| Complete data sovereignty |