Privacy Policy

MYTIUS is an emergency continuity service engineered with strict data minimization and cryptographic boundary controls. We believe personal emergency details should only be accessible when you choose to unlock them.

Controlled Beta Notice: MYTIUS is currently operating in an active Controlled Beta Sandbox. Account preparation and emergency recovery mechanisms are functional for evaluation and verification. Do not rely on this sandbox as your sole lifeline for critical emergencies.

1. Operator & Contact Route

MYTIUS (“MYTIUS,” “we,” “us,” or “our”) operates the website at mytius.com and associated recovery services.

For privacy inquiries, data subject requests, or security reports, contact our privacy officer at [email protected] or [email protected].

2. Information We Collect

We deliberately minimize the personal information collected to only what is strictly required for authentication and emergency continuity:

  • Account Credentials: Your account email address and FIDO2/WebAuthn public keys. Passkey private keys remain in your device hardware and are never transmitted to or possessed by MYTIUS.
  • Emergency Contacts: Names, phone numbers, relationships, and optional email addresses for your designated emergency contacts, stored as AES-256-GCM encrypted ciphertext.
  • Essential Details: Travel lodging, policy numbers, emergency medical references, or safe-words, stored as AES-256-GCM encrypted ciphertext.
  • Emergency Passphrase Verifier: A cryptographic hash of your memorized passphrase computed using the memory-hard Argon2id algorithm with a dedicated per-user salt. Your raw passphrase is never stored on disk.
  • Physical Recovery Credentials: A public card ID (for card identification) and a cryptographic secret verifier. The plaintext secret exists only in the QR code or printed manual string on your physical wallet card.
  • Security Audit Events: Fixed, non-sensitive audit metadata (such as timestamps, event types, and hashed resource identifiers) linked in an append-only tamper-evident HMAC chain for access transparency.
  • Waitlist & Early Batch Inquiries: When you submit a priority reservation, we collect your provided email or phone number solely to update you on batch availability.

3. Cryptographic Storage & Processing

Your emergency contacts and essential notes are encrypted using an envelope encryption scheme:

  • Each account has a dedicated 256-bit Data Encryption Key (DEK). Stored records are encrypted with AES-256-GCM before database insertion.
  • The DEK is wrapped using a hardware-backed Key Management Service (KMS).
  • During an emergency recovery ceremony from an unfamiliar browser, emergency access is authorized by presenting both your physical recovery card secret and your correct emergency passphrase. During normal authenticated owner sessions, you manage and read your records directly via passkey authentication.
  • We do not sell, rent, or monetize your personal information or emergency records.

4. Service Limitations & Borrowed Devices

Emergency access is designed to function from unfamiliar or borrowed browsers when your primary phone is lost, stolen, or damaged. You should understand the following operational limitations:

  • Emergency sessions are strictly read-only and automatically expire after 30 minutes.
  • While emergency pages deliver strict no-store and no-cache directives, borrowed devices may run malware, keyloggers, or hardware screen capture that cannot be detected by web applications.
  • Always close all browser tabs and clear the borrowed device’s cache after completing emergency continuity actions.

5. Data Retention, Vault Export & Cryptographic Deletion

You retain complete control over your stored emergency information:

  • Self-Service Export: You may download a full, unencrypted JSON export of your saved contacts and essentials at any time from your account dashboard.
  • Account Deletion & Live Data Purge: When you delete your account, your live wrapped Data Encryption Key (user_crypto_keys) is immediately deleted from the primary database, personal contacts and essentials are hard-deleted, recovery credentials and sessions are revoked, and your user identity is pseudonymized.
  • Disaster-Recovery Backups: Operational database backups are maintained solely for disaster recovery and system continuity. Historical backups taken prior to an account deletion may contain snapshot copies of encrypted records and wrapped keys until pruned under backup retention cycles; operational restoration procedures require reconciling security guard deletion states before reconnecting application traffic.

6. Physical Card Fulfillment

Physical wallet cards contain only your card’s public ID and the unique recovery URL fragment with the recovery secret. Your emergency passphrase and personal emergency contacts are never printed on physical cards, sent to card printers, or stored in plaintext.

7. Policy Updates

We will notify active account holders of any material updates to this Privacy Policy via their registered account email and update the revision date below.

Last revised: 19 October 2026.

Questions about your privacy?

Review our security architecture or contact us directly.

Security ArchitectureTerms of Service