Local-First Privacy Posture
Wayvault keeps all core data local.
Effective May 24, 2026. This policy outlines how the Wayvault application manages data. The app is architected with a strict local-first layout: no user accounts, no cloud sync databases, no analytics engines, and no tracking telemetry.
No Remote Data Collection
Wayvault does not require an account, advertising identifiers, tracking profiles, or internet handshakes for core features. Optional map downloads retrieve static PMTiles archives from object storage only when you choose to install a map pack. We do not operate cloud services to collect, index, or parse your travel dossiers or emergency files.
Local Storage Architecture
Every piece of data you create or load into the application resides inside secure, isolated Drift metadata tables on your device's physical storage sandbox:
- Vault metadata files and document copies you import (PDFs, images, etc.).
- Emergency contact logs and pinnable text notes.
- Timestamped journal observations.
- Downloaded country and subregion PMTiles map packs.
- Saved coordinates and GPS location markers.
- Encrypted database backup bundles.
GPS & Location Parameters
Device location permission is requested strictly on-demand when you explicitly initiate GPS operations (e.g. referencing coordinates, assessing altimeter values, or viewing your active position on an offline map).
GPS calculations occur directly on the device hardware. Latitude, longitude, and elevation are never transmitted to external APIs or developers.
File & Media Access
When you choose emergency guides, maps, or ID attachments, the app copies the files into its secure sandboxed document container so they remain accessible when cell coverage is zero. Wayvault does not inspect or index files outside of your manual imports.
Local Backup Portability
Backup bundles represent unified zip files of notes, database keys, and location coordinates. These exports remain entirely under your control. You determine the destination storage, and no background cloud backups are forced upon the application.
Complete Deletion Control
The application settings panel includes tools to delete cached maps, wipe notes databases, or perform a total sandbox purge. Deleting the application via OS commands completely clears all local persistent parameters.
Contact & Inquiries
For questions regarding code behavior, local database schemas, or offline priority architecture, you can contact the developer directly via email at tan@honhat.com, follow on X at @nottanho, or visit the portal at honhat.com.