Privacy Policy
Last updated: 2 September 2026
Treksup works without an account, and most of it never talks to a server at all. Routes, plans, packing lists, your recorded hikes and your body figures live on your phone and stay there. An account is only needed for the community feed and trail reports — and everything you put in those is yours to export or delete, from inside the app, at any time.
Who is responsible
Treksup is run by an individual developer in Belgium. Under the GDPR that makes us the data controller for anything described below. Questions, requests and complaints all go to the contact address at the foot of this page.
What stays on your phone
None of this is sent anywhere, and there is no copy of it on any server:
- Recorded hikes and their GPS tracks
- Planning progress, packing-list ticks, readiness answers and your chosen trip month
- Your body figures (weight, height, age, and which form of the resting-energy equation to use) — used only to work out the food plan on the device
- App settings, including language and units
Deleting the app deletes all of it. You can export a recorded hike as a GPX file; where you send that file is entirely your choice.
What happens if you create an account
An account is optional. Without one you can read the community feed but not post, comment, like, follow or report a trail hazard. Everything else in the app works exactly the same either way.
| What | Why |
|---|---|
| Email address and password | To sign you in. The password is stored only as a cryptographic hash — we never see it. |
A username, which Treksup generates for you — something like misty_moor_669 | So other walkers know whose post they are reading, without you having to give a name. |
| Posts you share: route, stage, title, description, photos, and optionally a rating and the distance, time and climb from a hike your phone recorded | They are the feed. |
| Comments, likes, follows and blocks | To make the feed work and to let you shut out someone you would rather not see. |
| Trail hazard reports: coordinates, the kind of hazard, your note, and when you saw it | So other walkers know what is on the path. These coordinates are published — that is the point of the feature. |
| Reports you make about other people's content | So a moderator can act on them. |
Anything you post is public
Posts, photos, comments and hazard reports can be read by anyone using Treksup, including people without an account. A hazard report carries the location you were standing in when you made it. Please do not post anything you would not want a stranger to see, and think before reporting a hazard from somewhere you would rather not be placed — your home, for instance.
Where it is stored
Account data is stored by Supabase, our hosting provider, on servers in the European Union. Supabase processes it only on our instructions, under a data processing agreement. Nothing is transferred outside the EU by us.
How long we keep it
- Your account and its content — until you delete it. Deleting your account removes your profile, posts, photos, comments, likes, follows and hazard reports. Reports you filed about other people's content are kept as part of the moderation record below, but are no longer linked to you.
- Trail hazard reports — these expire on their own, between two weeks and six months depending on the kind, because stale trail information is worse than none.
- Moderation records — the record of a report and of any decision taken on it is kept, whatever the outcome, so decisions can be reviewed or reversed.
Your rights, and how to use them
Under the GDPR you can ask for a copy of your data, correct it, delete it, or object to how it is used. Two of those are buttons in the app rather than emails:
- Export everything — Account → Export everything. Returns the email address on the account, your profile, posts, photo records, comments, likes, who you follow and who follows you, blocks, reports you filed, hazard reports and hazard votes.
- Delete your account — Account → Delete account. Immediate and permanent.
For anything else, write to the address below. You also have the right to complain to the Belgian Data Protection Authority (gegevensbeschermingsautoriteit.be).
Location
Treksup asks for location permission for three things: to show where you are on the map, to record a hike, and to place a trail hazard report. The first two never leave the device. The third is published with the report, and the app says so on the screen where you make one. There is no background tracking — the app cannot follow you when it is closed.
Photos
The app asks for photo-library access in two places, and they are not the same.
A profile picture and a name you type into the app stay on this phone. They are held in the app's own storage alongside the body figures the food plan uses, and none of it is ever uploaded — not even once you have an account. The account itself carries a username Treksup generates, and nothing else about you.
Photos you attach to a post are uploaded and public the moment you share it, and can be seen by anyone using Treksup including people without an account.
Other services the app talks to
None of these receive your name or your account, but like any internet request they see your IP address:
- Open-Meteo (open-meteo.com) — weather forecasts for the coordinates of route stages.
- RainViewer (rainviewer.com) — rain radar imagery.
- Wikimedia Commons (wikimedia.org) — the licensed photographs shown on route and stage pages.
- External links — tapping a link to a refuge, a timetable or an official trail-status page opens that site under its own privacy policy.
What we do not do
No advertising. No analytics or tracking SDKs. No selling or sharing of personal data with anyone. No profiling, and no automated decisions about you.
Children
Treksup is not intended for children under 16, and accounts should not be created by them. If you believe a child has created an account, write to us and we will remove it.
Security, and what happens if it goes wrong
Access to account data is enforced at the database level: every table has row-level security policies so that one account cannot read or change another's. If a breach affecting your data ever occurs, we will notify the supervisory authority within 72 hours and tell you directly where the law requires it.
Changes
If this policy changes in a way that affects what we collect or why, the app will say so before anything new is sent. The date at the top always reflects the current version.
Contact
sebbedehond@gmail.com