BEACON SECURITY

Protection that
doesn’t depend
on a promise.

Beacon is a private Manaspurti operating system. Its access controls are enforced by Firebase Authentication, Security Rules, and trusted server functions—not by hiding buttons in a browser.

Verified identity and second factor

Human access requires a verified email, an enrolled TOTP authenticator, and an active server-owned Beacon membership. A Firebase account alone does not grant access. Privileged operations additionally require a recent sign-in.

Least privilege, exact scope

Every person and agent receives only explicit workspace scope. Clients have no database write path. Firestore reads are bounded and scope-checked; realtime views are server-written and may only be read by the exact authorised principal.

Server-side authority

All mutations, access changes, audits, token minting, and sensitive reads pass through App Check-protected Callable Functions. Each command validates identity, membership, role, workspace, input, state, and audit evidence independently of the user interface.

Founder containment

The stored founder control identity can lock the organisation during an access incident. Locking denies normal Firestore, RTDB, and command access, advances the session floor, and revokes refresh tokens. Recovery requires a fresh founder TOTP session and records a reason.

Responsible disclosure