Strict Local-First Guarantee

Your data never leaves your device.

Effective August 2026. This policy describes how Wayvault manages data. Wayvault is architected as an offline-first vault: no user accounts, no cloud sync servers, no analytics trackers, and no telemetry beacons.

01. Zero Remote Data Collection

Wayvault does not require an account, advertising identifiers, tracking profiles, or network communication for core use. When you choose to download map regions, the app fetches static, open-source PMTiles vector archives directly from public object storage without transmitting your personal records or device identity.

02. Local Sandbox Persistence

All data created or imported into Wayvault is stored inside an isolated Drift SQLite database on your device sandbox:

Imported vault documents (PDFs, GPX trail routes, KML files, images, Markdown).
Emergency contact logs, severe allergies, and Medical ID profiles.
Timestamped trip journal observations.
Downloaded regional vector maps and custom PMTiles archives.
Saved GPS coordinates and waypoints.
Salted SHA-256 vault lock PIN configurations.

03. On-Device GPS & Sensor Processing

Device location and hardware compass access are requested strictly when you explicitly view coordinates, check solar ephemeris, or locate yourself on an offline map.

All coordinate, altitude, and heading computations execute directly on your phone's processor. Coordinates are never sent to external servers or developers.

04. Encrypted Local Backup Bundles

Wayvault includes a manual backup export/restore engine. Backup bundles are self-contained archives that you can save to your personal storage, iCloud Drive, or external drives. No automatic background cloud syncing occurs without your explicit command.

05. Contact & Support

For questions regarding code behavior, database schemas, or offline security architecture, contact: