Skip to content

Security and privacy

The PC Configuration studio shares the existing authenticated local boundary. Only check-in/Life Wheel settings are editable; drafts and undo/redo history remain in browser RAM.

Safety and privacy

Data flow on Android

flowchart LR
    APP[Steady app] --> ENC[record encryption]
    KEY[Android Keystore] --> ENC
    ENC --> DB[app-private SQLite]
    APP --> TOKEN[separate provider-token storage]
    KEY2[separate Keystore key] --> TOKEN

Security boundaries

Area Protection
Tracking data per-record AES-256-GCM in the app-private SQLite database
Keys non-exportable in Android Keystore
Provider tokens separate Keystore-backed storage
Companion memory encrypted private file
Screenshots blocked by default
App access optional device-lock authentication
Android system backup disabled

Optional PC entry

Only Start PC entry opens local HTTPS access. Before accepting a browser certificate exception, compare its SHA-256 fingerprint with your phone. The random four-digit code is valid once for ten minutes; five attempts per minute are permitted. Pairing replaces the previous session. Its cookie is Secure, HttpOnly and SameSite=Strict; writes validate CSRF and Host/Origin. The session ends at its chosen time, on stop, Wi-Fi change, process termination, restore or deletion. Without a time limit, stopping manually is required.

With Remember this computer for 30 days, pairing survives browser or service restarts. The cookie contains a random 256-bit secret; the phone stores only its SHA-256 digest and expiry in private app storage. The service must still be started explicitly and use the same address. Log out, Forget remembered computer, new pairing, restore and deletion revoke authorization. Stopping preserves it until expiry.

Ordinary daily fields remain editable for eight days. Analytics also provides read-only historical numeric/choice values, event metrics, Life Wheel, patterns and counters. Free text is represented only by presence for enabled text counts; journal content, event notes, reasons and reactions are not transferred through this analytics route. Entry additionally exposes editable contacts, exercise, self-care, urges, triggers and explicit zero check-ins for the eight-day window, including their notes, reasons and responses. Relapse saves need confirmation; the event and selected resets commit together. Relapse deletion is unavailable. Standalone counter changes remain on the phone. There is no PC database, browser persistence for tracking data, offline copy, export or sync feature. Browser memory and the pairing cookie are technically necessary. Browser history contains only a random session identifier and position, never tracking values, date filters or metric choices. The corresponding view snapshots stay in RAM and are discarded on known expiry or logout. Phone screenshot protection cannot cover PC screenshots, printing or extensions. Chats, tokens and provider data remain outside access. The service uses additional battery; screen-off behavior and background restrictions remain real-device tests, not confirmed acceptance.

Configuration additionally exposes current check-in section/field definitions, version metadata, Life Wheel axes and editor options. Its explicit Apply changes action submits only the allowed configuration, with revision and idempotent-mutation checks, through the same authenticated CSRF-protected boundary. The phone commits it atomically in encrypted storage and preserves historical definitions, excluded product data and unrelated private settings. The saved-versus-draft preview reuses read-only analytics. The studio's draft and grouped undo/redo history stay in browser RAM and are cleared on known expiry/logout. No provider request, token access, backup route or Companion permission is added.

Portable backups

Portable backups are encrypted with a key derived from the user's passphrase through PBKDF2-HMAC-SHA-256 and AES-256-GCM. The passphrase is not stored and cannot be reset. Before a complete restore, the app displays a summary and requires explicit confirmation.

From Alpha 20, “Back up everything” also includes Companion settings, chats, messages, memories, pinned source notes and credentials for configured endpoints. The backup is therefore also a credential vault: use a strong, unique passphrase. “Back up settings only” does not include these private records.

During restore, “Also replace Companion settings, chats, memories and credentials” starts unchecked. These records are replaced only if you explicitly select it. Afterwards, the Companion stays disabled and external-data consent must be granted again. Older tracking backups leave existing Companion data unchanged. App lock, Keystore keys, PC sessions and downloaded local models are not transferred.

Excel exports are readable analysis files and are intentionally not encrypted. The encrypted backup is the protected storage format.

What is intentionally not included

  • no telemetry,
  • no mandatory user account,
  • no Steady cloud synchronization,
  • no provider tokens in plaintext exports, logs or Excel,
  • no Companion data in settings-only or older tracking backups,
  • no personal demo data in the repository.

Encryption protects data at rest. An unlocked, rooted or otherwise compromised device is outside this protection model. Data deliberately transferred to an external AI provider is also subject to that provider's retention rules.

Sources