Using TripLibreLab

Data & privacy

TripLibreLab is designed to be local-first: no account, no server, and nothing shared unless you share it. This page describes that design. It will be updated to match the released app, including its App Store privacy disclosure.

TripLibreLab is not released yet, so the statements below describe how it is being built, not an audited result. Where behaviour has not been verified in the finished app it is marked Pending.

The short version

No accountNothing to sign up for and nothing to log in to.

No uploadYour diary is read and processed on the phone. There is no TripLibreLab server.

Read-onlyThe export you import is opened read-only and never changed.

You shareAn image leaves the phone only when you send it with the share sheet.

What TripLibreLab reads

Only the file you pick in the Files app. iOS does not let an app see other files, and TripLibreLab asks for no location permission: it reads your history from the export, not from the phone's GPS.

That file is TripLibre's travel.sqlite snapshot, which holds your entire TripLibre history, raw GPS points included, whatever range you chose when exporting. TripLibreLab reads the parts it needs to replay days.

What TripLibreLab keeps Pending

Data	Where
Imported diary	In the app's own storage on your phone, so you don't have to import it again. Removable from inside the app; deleting the app removes it.
Share images	Created when you open the preview and handed to the share sheet. Where they go next is your choice.
Analytics	None planned. TripLibreLab is not intended to include an analytics or advertising SDK.

Like any app data, what TripLibreLab keeps may be included in your iPhone or iCloud backups.

Network use Pending

The import, replay and share flow is designed to work with no network connection. Map tiles may be loaded by Apple's MapKit while you view a map; the exact list of network requests will be documented here before release.

What a shared image contains

Only what you see in the preview: a map of the day and the labels you chose to keep. Before sharing you can hide or generalise start and end places and leave out exact times. Nothing else from your diary is attached.

Risks of sharing travel history

Keeping data on the phone removes the server, not every risk.

Locations identify people. The places where a day starts and ends are often home and work, and those two alone can be enough to identify someone.
Patterns add up. Several shared days, even with redaction, can reveal a routine.
Exports travel. A travel.sqlite file sent to someone else gives them your full history. Share images, not the export.
Sharing can't be undone. Once an image is sent or posted, it may be copied, cached or kept.

Erasing your data Pending

Remove an imported diary from inside TripLibreLab, or delete the app to remove everything it stored. Your original TripLibre data and export files are not affected; manage those in TripLibre and the Files app (see TripLibre's Privacy page).