Trust has to be engineered.

How LOCI is designed

• Private by default with holder ownership checks and row-level database policies.
• Passwordless authentication, one-time token digests, short-lived review sessions, and same-origin mutation controls.
• Encryption in transit, managed encryption at rest, server-only service credentials, and no raw payment-card storage.
• Strict schemas, content and size limits, rate limits, private caching, security headers, and minimized logging.
• Purpose-bound agent authority with pause, revoke, budgets, evidence, and human confirmation for consequential actions.
• Place automation and publication are separate, fail-closed gates and default off.

AI, World, and Place boundaries

AI output is a proposal, not truth or authority. Bring My AI rejects unsupported and sensitive content at a bounded import edge and requires item-by-item review. A place cannot browse a Passport. The Place farm cannot consume Passport memory. Public source text and instructions cannot change policy or grant authority.

Report a vulnerability

Please email security@locipassport.com with the affected surface, safe reproduction steps, potential impact, and a contact method. Do not include credentials, raw Passport content, precise locations, voice, or another person’s data. Do not access data that is not yours, persist access, disrupt service, or use social engineering.

We will acknowledge a credible report, investigate it, and coordinate remediation and disclosure appropriate to its severity. Please avoid public disclosure until we have had a reasonable opportunity to protect affected people and places.

Scope and limitations

No system is perfectly secure. Preview and prototype clients may not have every production control until their release gate is complete. The canonical production deployment, protected environments, provider configuration, backups, monitoring, and incident operations must match the safeguards described here before broad availability.