Trulana is a local-first private context server. Apps query local context over REST or MCP, and only redacted answers leave the device.
Authenticate an agent, run a live query, watch redactions apply, and see the audit log update in real time.
Right now you have two choices. Give your apps zero personal context and get generic answers. Or hand over your emails, calendar, health data, and notes — and hope nobody leaks it, trains on it, or sells it.
Every session starts from scratch. The AI doesn't know your name, your schedule, or what you asked yesterday.
Send everything to the cloud. Your data trains models, populates dashboards, and lives on servers you don't control.
Trulana stores your personal context in an encrypted local vault. When an app needs to know something about you, it queries Trulana — and gets back a filtered, redacted response. Your name, email, location, and schedule never leave the device in raw form.
The app gets useful context. You keep control of the source material.
An app sends an auth request with its name, ID, and stated intent.
Short-lived, in-memory, 15-minute TTL. Doesn't survive a restart.
"What's their morning routine?" — sent to localhost, never to the internet.
Three stages: regex PII stripping, entity recognition, privacy-level generalization. Emails, phones, SSNs, locations — all caught.
The app gets useful context with all identifying details stripped. The raw data never moved.
Need user context without storage liability? Query Trulana via REST or MCP. Get personalization without the GDPR headache.
Use AI with client data, NDAs, and sensitive materials — without sending any of it to a cloud provider.
Get the "AI that knows you" experience without the tradeoff. Your context, your device, your rules.
Every AI app that stores personal context becomes a data liability. One breach, one policy change, one acquisition — and your users' data is somewhere it shouldn't be.
Trulana eliminates this by never collecting the data in the first place. The context lives on the user's machine. Your app queries it. The redaction engine enforces the boundary. You get personalization without the storage, the GDPR headache, or the trust problem.
I'm looking for a few macOS design partners building AI workflows that need local-first context and redacted outputs.