Exporting changes where a copy lives

Define the outcome

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.

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.

Three checks to complete

The receiving app can keep its own copy outside Waymark.

• Choose the intended data
• Inspect the destination
• Open the saved file and review its location

Final review

A user sends trip summaries to a spreadsheet service. This is an illustrative scenario, not measured field-test evidence.

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.

Quick reference

At a glance

1. 01 →Choose the intended data
2. 02 →Inspect the destination
3. 03 ✓Open the saved file and review its location