Privacy and your data

What is stored

• Account information: your name, email address, sign-in methods, sessions and security information needed to protect access.
• Journey content: the stories, dates, places, captions, images and videos you add. Photos are stored privately as optimized images with embedded metadata removed. Videos use private signed playback through Cloudflare Stream in the local implementation, which is not deployed or release-validated. Unused ready images and videos persist in All media and use storage until explicitly deleted or their journey or owning account is deleted; removing a story placement does not delete the library item.
• Photo-generation metadata (planned local scope): selected capture date/time and GPS fields are retained separately and privately on journey assets, not arbitrary EXIF, camera identifiers or uploaded originals. Owners and accepted editors can use this information to preview a timeline. Missing or unreadable metadata is not guessed. Confirmed generation adds dates and map locations to the journey, where view-link readers can see them as shared content.
• On your device: essential session and viewer-access information, plus account-specific drafts when browser storage is available. A short-lived sign-in hint helps show the right header links while your session is checked; it contains no account details or sign-in credentials. Clearing site data or uninstalling can remove unsent drafts.

Who can see your journeys

A journey is private by default. Its owner and accepted editors can read it. Anyone with an active view link can also read it, without an account.

The media-bin inventory, unused images and videos, and private source metadata are available only to the journey owner and accepted editors, not view-link readers. Readers can access media placed in the story and the image cover without Pro. Removing a placement is not the same as deleting an asset, and reused media remains visible wherever it is still placed or, for images, used as a cover.

Editors can change shared content. Anyone who receives a sharing link can forward it. Revoking a link prevents new access and new signed video credentials through it. Previously issued video credentials can remain valid for up to five minutes. Revocation cannot recall downloaded copies, recordings or screenshots.

Services used to run Logaway

• Cloudflare hosts the app and its database, stores photos, and processes images. The local Pro video implementation uses Cloudflare Stream for video processing, private playback and thumbnails; deployed-provider validation is still pending.
• Resend delivers sign-in emails when email delivery is configured.
• Google Fonts supplies the app’s fonts. Loading fonts makes a request to that service.
• Mapbox supplies maps, place search and road routes. There is no advertising or separate product analytics installed in the current app.

What map services receive

Maps load when they become visible, in both read and edit mode. Mapbox receives requests for the map area, network information such as your IP address, and map SDK usage events. The referrer identifies the app’s origin, not your journal’s URL.

Place search sends the words you submit after pressing Enter or Search—not as you type or focus the field. Search requests omit cookies. A selected place’s name and coordinates are saved in your journey.

For car routes, Logaway sends the ordered stop coordinates through its API to Mapbox Directions. These requests do not include your journal text, place labels, account ID or sharing token.

Photo-generated maps use selected GPS-derived visits and straight lines, not Mapbox Directions. A conservative estimate may suggest walking or flying from photo locations and times; uncertain travel stays as Other. Once confirmed, their locations are journey content; displaying those maps still sends map-area requests to Mapbox as described above.

What deletion removes—and what remains

Deleting your account removes your identity, sessions, memberships and owned journeys. Media cleanup happens in the background rather than instantly.

Contributions to journeys owned by someone else remain with account attribution removed. Personal information you wrote inside a story or caption is not automatically removed from that content.

Copies saved by other people are outside Logaway’s control. Provider backup retention periods are not yet confirmed, so this notice cannot promise immediate removal from every backup.