Mitra OS Wiki
Browse the wiki

Security overview

Security · guide · Updated

Not every capability described on this wiki is available today.

Quick answer

Mitra OS protects members with passwordless device-bound sign-in, a fresh biometric confirmation for sensitive actions, AI that only reads and drafts, and audit logging.

Summary

Security is built into how the platform works. Sign-in uses passkeys, consequential actions need your confirmation, language-model calls are limited and grounded in live data, and failures in one domain are isolated from the others.

Key takeaways

  • Sign-in is passwordless and tied to your device.
  • Money, health data and irreversible bookings need a fresh biometric confirmation.
  • Language-model calls read and draft only, are grounded in live data and are audit-logged.
  • A failure in one domain does not spread to others.

Principles

  1. No shared secrets. There is no password to phish. See Passkeys.
  2. Confirm what matters. See Step-up confirmation.
  3. Constrain the AI. See AI safety and auditability.
  4. Isolate failures. Each domain fails on its own without taking the rest down.

Privacy explains where the legal terms live. Identity explains how verified identity ties these together.

Frequently asked questions

Does Mitra OS use passwords?

No. It uses passwordless, device-bound sign-in with passkeys.

What needs extra confirmation?

Anything involving money, health data or an irreversible booking requires a fresh biometric step-up.

Where can I read the formal privacy terms?

In the Privacy Policy at mitraos.ai. This wiki links to it from the Privacy page.

People also ask

Glossary terms on this page

  • MITRA: MITRA is the orchestration platform behind Mitra OS. Mitra is the name you talk to, and Mitra OS, Inc. is the company that builds it.
  • Step-up: Step-up is an extra, fresh biometric check required before a sensitive action, even when you are already signed in.

Sources

Last updated . Last reviewed .