Privacy & cookies

Your plans and account

Trekfully stores your email address, household and trip access, gear and pantry records, participants, routes, meals, stays and notes. Household members share household inventory and trips. Trip guests see the trip shared with them, including its participants, plans, assigned gear and notes. Body weights are hidden from trip-only guests. Put booking details in a trip only if you want its collaborators to see them.

Account data is used to provide sign-in, collaboration and your requested planning features. Contact mail@bobwalrave.com for questions, access, correction or deletion of your data, and details of the hosting and email providers used by this installation.

Cookies and device storage

The essential trekfully_session cookie holds a random session identifier, not your email or route. It protects sign-in and form submissions. Without “Keep me signed in”, it is a browser-session cookie, with a two-hour inactivity limit and a twelve-hour maximum. If selected, sign-in lasts up to 30 days. Browser session restoration may retain session cookies, so use Sign out on a shared device.

Local and session storage remember interface choices such as filters, map layers and scroll position. These are not used for advertising. They reset when another account signs in. Trekfully is built around privacy: no advertising, no analytics trackers, and no tracking for marketing. We use essential sign-in cookies and local storage for your interface preferences.

External services

Visible maps request tiles directly from OpenTopoMap or Esri, which receive your IP address and the map areas requested. Leaflet is loaded from unpkg. Planning services receive the coordinates necessary for OSM/Overpass discovery, walking routes, elevation and weather. Requests made by the server use its IP address. AI weight estimation, if configured and requested, sends the entered item details to OpenAI.

The Support Trekfully link opens a separate Stripe payment page. Stripe handles payment details; Trekfully does not receive card information or embed Stripe tracking on this page.

Sign-in sessions

Account → Sessions shows your active sign-ins, a general browser and device description, and sign-in and last-activity times. You can end another session or all other sessions. We store the general description rather than the full browser identification string and do not add a location lookup. Session descriptions are removed when their sessions are cleaned up, or immediately when you delete your account.

Retention and control

Your plans are retained until deleted by their household owner or the service operator. Expired sign-in records and rate-limit records are cleaned by the scheduled worker, normally within a day of their expiry. You can manage your profile, sign out all devices and delete your account in Account. Account deletion removes your login identity and anonymises linked participants, while preserving shared planning quantities. Household owners must transfer ownership or delete the household first. Private household files are queued for removal by the background worker. Shared public map caches are retained. Free-text notes may still contain personal mentions; review them or contact us. Invitations expire after seven days; their access history is retained for administration. Server logs and backups follow the operator’s retention policy.

Contact the installation operator for details of its providers and retention arrangements.