Private screens after returning to the app

The distinction that matters

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.

Know which records you are protecting and where copies exist. Enabling App Lock is different from enabling your phone lock, and exporting a CSV creates a file outside the database once you save or share it. The destination you choose controls its own copy. Before a device reset or reinstall, verify the exports you want to keep rather than assuming an account can recover them later.

Read the information in context

A quick app switch should not be assumed to leave private data unguarded.

• Enable App Lock
• Leave a private screen through the phone
• Return and check the unlock requirement

What this does not establish

A user checks how saved history behaves after interruption. 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 →Enable App Lock
2. 02 →Leave a private screen through the phone
3. 03 ✓Return and check the unlock requirement