App Lock and the phone lock

The field task

For a privacy review, make an inventory of saved trips, places, memories and exported files. Decide which copies you still need and delete unnecessary copies in the app or destination that holds them. A map link opened in another app and a CSV sent to another service are deliberate transfers. Local-only storage does not make those selected destinations part of Waymark’s own private database.

Waymark is an account-free app with locally stored records. Trips and places use an encrypted local database, with the encryption key kept in platform secure storage. Photos selected for the app remain in its private documents area. App Lock protects private screens while leaving the basic speedometer accessible. This design avoids a developer-operated trip-history account but still makes your device and exports important parts of data care.

A repeatable sequence

An app PIN does not replace the operating system's device security.

• Review the phone's lock
• Enable App Lock if useful
• Test each access path

After the session

A user wants to understand what each lock protects. This is an illustrative scenario, not measured field-test evidence.

Check private screens after a foreground return, and test your chosen unlock method while you have time to resolve a problem. The PIN fallback is useful when device biometrics are unavailable. Do not share the PIN with an exported dataset. A clear-data action and an ordinary navigation action have very different effects; read the confirmation and select the intended record category before proceeding.

Quick reference

At a glance

1. 01 →Review the phone's lock
2. 02 →Enable App Lock if useful
3. 03 ✓Test each access path