eri

Security

Your code stays on your machine.

eri is a desktop app. Model calls go from your machine to the provider (eri inference, Anthropic, OpenAI, or a local endpoint). The cloud side handles accounts and billing — that's it. This page is the honest version of how the pieces fit together.

How requests flow

your machine ─────────────► eri inference (default)
              │
              ├──────────► Anthropic / OpenAI / Google (BYOK)
              │
              ├──────────► local endpoint (Ollama, etc.)
              │
              └──────────► tryeri.ca (auth + billing only)
                              ↑
                              │ never receives:
                              │ - prompts
                              │ - code
                              │ - voice
                              │ - gaze

With BYOK, the request goes from your machine to the provider you chose — the operator does not see the body. With the default eri inference proxy, requests are forwarded to the upstream model without retaining request or response bodies; only the metadata needed to count usage is recorded.

Auth + encryption

  • Passwords stored as salted hashes. The plaintext is never written down. OAuth sign-in (Google) skips passwords entirely.
  • Sessions are signed tokens with a finite lifetime, rotated on sign-in.
  • All traffic uses TLS in transit. tryeri.ca serves over HTTPS only.
  • BYOK API keys live in your OS keychain (macOS Keychain, Windows Credential Manager, Secret Service on Linux). They are never sent to the operator's servers.

What we collect

  • Email address (for sign-in and billing receipts)
  • Salted password hash, or your OAuth identifier if you signed in with Google
  • Subscription state from Stripe (plan, status, renewal date)
  • Usage counters (aggregate, no content)
  • Anonymous crash reports, if you leave telemetry on

What we don't collect

  • Your prompts or what you said out loud
  • Your code — written, generated, or otherwise
  • Your voice recordings (transcription is local; audio is never uploaded)
  • Your gaze data (it never leaves your machine)
  • Your API keys (BYOK keys are stored encrypted in your OS keychain)

Vendors

The third parties the cloud side talks to. The full sub-processor list, including model providers and what data each one touches, lives at /legal/sub-processors.

Compliance, honestly

eri is an indie project. The compliance posture page lives at /trust. The short version: GDPR / PIPEDA / CCPA-style requests are handled; SOC 2, ISO 27001, and HIPAA are not in place. If your review needs those today, eri is not the tool.

Report a vulnerability

Found something? Email phlotu@gmail.com with what you found and how to reproduce it. The full disclosure policy, including safe harbour, lives at /security/disclosure.