Security & Privacy by Design
Built with data security as a first principle. Your documents are processed and immediately forgotten — by design, not by policy.
Four Security Pillars
Security is not a feature we added — it's a design constraint we started with.
Zero Post-Processing Storage
Documents are processed in real-time. The moment processing completes, all input data is discarded. Nothing is written to our servers — only your renamed files go back to your disk.
On-Premise LLM Option
With Ollama integration, the AI model runs entirely on your machine. Your document content never leaves your network. Perfect for HIPAA, legal, and financial environments.
Minimal Data Footprint
Our architecture minimizes the data surface area. We don't log document contents, don't store file names on our servers, and don't build profiles from your usage.
Compliance Roadmap
GDPR, SOC 2 Type II, and ISO 27001 certifications are planned for Q4 2026. We are building toward these standards in every architectural decision we make today.
How It Works, Under the Hood
01
Document Read In-Memory
When you trigger a rename, the document is read into memory on your local machine. It is never written to any intermediate location.
02
AI Processing (Local or API)
The content is sent to the AI model — either locally via Ollama (stays on your machine) or via your own cloud AI API key (your account, your data agreement, not ours).
03
Output Written, Input Discarded
The AI returns extracted field values. The renamed file is written to disk. The input content is discarded from memory immediately. Nothing is retained.
API Keys Stored in OS Keychain
Your cloud AI API key is stored in macOS Keychain or Windows Credential Manager — the same secure storage used by your browser for passwords. DocRithm never has access to your key in plaintext beyond the moment of use.
Compliance Roadmap
We are building toward enterprise-grade compliance from the ground up. Every architectural decision today is made with these certifications in mind.