Privacy policy
Version 2026-10 · effective 21 October 2026
This policy applies to the NaHrib services: the website nahrib.app in all languages, the user account with the hike log and check-ins, the application programming interface (API) and the official NaHrib mobile app, when and if we publish it. The app will use the same accounts and data; we will extend this policy when it is published.
1. Controller
The controller of personal data is GE-KO, Maja Dolžan s.p., Cesta Toneta Tomšiča 71, 4270 Jesenice, Slovenia, registration number 8732043000, e-mail info@nahrib.app, phone +386 51 821 907. We have not appointed a data protection officer because the processing is not large-scale or systematic within the meaning of Article 37 GDPR. Please send privacy questions to info@nahrib.app.
2. Which data we process and why
2.1 Visiting without an account
For every request the server records technical data: IP address, browser or device type, time and the requested address with its parameters (for example a search term, or coordinates when the app asks for a forecast at a point). We use them to run and secure the service and to limit abuse. Legal basis: legitimate interest. The web server access logs are managed by the hosting system and rotated after 21 days. Application logs contain technical error data; we deliberately do not write passwords, tokens or the content of private records into them, and we delete them after 30 days.
We do not use advertising or tracking cookies or third-party analytics, and we do not profile visitors. Search terms are not stored in the database.
Our own analytics, without cookies and without consent: to improve our content we measure which pages are read. We record the page address without parameters, the domain you came from, a coarse type of device, browser and operating system, the page language, any campaign tags (utm_) and an anonymised visitor identifier. The identifier is a hash computed with a key that changes every day, so it cannot link visits from different days. Your IP address, the full browser string or a cookie are not part of these records. We derive your country from the IP address at the time of the visit, using a local database and without sending it to third parties; we store only the two-letter country code, never the IP address. Robot requests are not recorded as views; we only count how many arrive per day by type of robot, without an IP address or browser string. A view only counts once the page confirms that a person is looking at it (a first action or 3 seconds); robots are not counted. If your browser sends a Global Privacy Control or Do Not Track signal, we do not record the view. Legal basis: legitimate interest (understanding and improving our content, without profiling).
The map, fonts and icons load from our own server, not from third-party servers. We build the base map ourselves from OpenStreetMap data.
Location on the map: when you choose "My location", your browser determines your position with your permission and shows it on the map on your device. We do not receive or store this position. We do not track your location in the background.
Hikes saved without an account stay only on your device (browser storage and the offline cache). You remove them by clearing the site data in your browser.
The "Directions" link opens Google Maps with the coordinates of the trailhead or place. Only when you click it does Google receive these coordinates and data about your device under its own rules.
2.2 User account
For an account we process your e-mail address, password (stored only as a one-way Argon2id hash; we do not keep a readable password and nobody at NaHrib can see it), optional name, language, account status, creation date, time of the last login, time the e-mail address was confirmed, and consents with policy version and time. When signing up you confirm that you are at least 16 years old; we do not collect your date of birth. Purpose: providing the service you asked for. Legal basis: contract (Terms of use).
E-mail confirmation: after sign-up we send a one-time link valid for 24 hours; only a hash of the token is stored. Private features (hike log, favourites, check-in) work at once; condition reports and photos can be sent only after confirmation. You can request a new link at most three times per hour. An account whose address is not confirmed within 7 days is deleted automatically.
Password reset: the link is valid for 60 minutes and works once. The answer is the same whether or not an account with the address exists. After the password change you are signed out on all devices.
2.3 Sessions and devices
When you log in on the web we create a session with a session cookie; the session is stored in our database and expires after 2 hours of inactivity. For the mobile app we issue a random device token, stored only as a hash, together with the device name, time of last use and a validity of 90 days. You see your devices in your account and can disconnect them. Legal basis: contract, for security also legitimate interest.
2.4 Hike log, favourite hikes and stamps
Logged hikes (date, hike, private note), favourite hikes and stamps are private and visible only to you. Legal basis: contract.
2.5 Location check-in
Check-in works only with your explicit consent, which you can withdraw at any time. When you check in, your device sends its position and its accuracy once; the server calculates the distance to the summit, hut or other place. A check-in succeeds within 150 m of the place and with an accuracy of up to 100 m. We store the place, time, distance and accuracy, but not the coordinates. Because the request is sent by POST, the coordinates are not written to the server access logs either.
Check-ins are private by default. They are public only if you choose this separately and have consented to public check-ins; they become visible only after 24 hours and may be shown only as the total number of visits to a place, without your name and never as a current position. If you withdraw this consent, all your check-ins, including past ones, become private. Legal basis: consent.
2.6 Condition reports
For a report we process the hike or place, the category (snow, ice, mud, damaged trail …), time of observation, the text and your account. A moderator reviews every report before publication. It is published without your name, with the date of observation and marked as unverified; it never changes the official trail status. Anyone can flag a report as inappropriate; we store the reason and, if the person is logged in, their account. Legal basis: legitimate interest (informing visitors about conditions) and contract. Retention: 24 months from submission; when you delete your account, the report is hidden and its text removed.
Reports of incorrect data and listing claims: we process the hike or place, the type of report, the text and, if you enter them, your name, email and phone (a claim requires name and email). We use them only to verify and reply; only editors can see them. To limit abuse we keep a one-way hash of the IP address. Reports are kept for at most 24 months.
2.7 Photos
When you upload a photo we re-encode it and remove all metadata, including location and camera data. It is stored outside publicly accessible folders under a random name. Until approved it is visible only to a moderator; after approval it is public next to the hike or place, without your name. Retention: as long as it is published or you have an account; when you delete your account we delete the file. You can ask for removal of a single photo at info@nahrib.app. Legal basis: contract and consent to public display.
2.8 E-mail
We only send messages needed for your account: address confirmation and password reset. We do not send newsletters at the moment. If you consent to news in your account, we keep the consent with policy version and time and respect it once we introduce news; you can withdraw it at any time.
2.9 Editorial work and audit trail
Logins (successful and failed, for failed ones with the e-mail entered), password changes, account deletion and staff actions (moderation, publishing hikes, changes of settings) are recorded with a hash of the IP address. Purpose: security, staff accountability and evidence. Legal basis: legitimate interest. Retention: 12 months.
3. Cookies and device storage
We use only strictly necessary cookies: a session cookie (ci_session) after login, which expires after 2 hours of inactivity, and a security cookie against forged requests (csrf_cookie_name) on pages with forms, which expires after 2 hours. Anonymous visitors without a form receive no cookies. In browser storage we keep saved hikes and the offline cache; this data stays on your device. Strictly necessary cookies need no consent, so we have no cookie banner.
4. Who receives data
Hosting provider (server, database, sending e-mail): G-SERVER d.o.o., Slovenia; server in a data centre in Slovenia. The provider processes data on our instructions under a data processing agreement.
The public: published condition reports and approved photos, without the author’s name.
Google: only if you click "Directions" (2.1).
Public authorities: where the law requires it.
Daily totals of views (without individual views or visitor identifiers) are read in our own tool GE-KO Insights, which we operate ourselves; we do not pass them to anyone else.
We do not sell data and do not use it for advertising.
5. Transfers outside the EU/EEA
The server, database and backups are in Slovenia (section 4). A transfer outside the EU/EEA can only occur if you click the link to Google Maps yourself, under Google’s rules.
6. How long we keep data
- Account, hike log, favourites, check-ins, consents: as long as you have an account.
- Account with an unconfirmed e-mail address: 7 days, then deleted automatically.
- Address confirmation link: 24 hours; new password link: 60 minutes; expired links are deleted 30 days after expiry.
- Device tokens: valid for 90 days; revoked and expired ones are deleted after 90 days.
- Web sessions: expire after 2 hours of inactivity, records are deleted after 2 days.
- Condition reports: 24 months from submission.
- Photos: as long as they are published or you have an account.
- Audit trail: 12 months.
- Application logs: 30 days.
- Individual views in our own analytics: 90 days, unconfirmed records 1 hour; after that only daily totals without visitor identifiers remain.
- Web server access logs: 21 days.
- Backups: encrypted; database up to 30 days, photos up to about 2 months (7 daily snapshots and 8 weekly archives); the same on a separate backup server.
- An automatic task that runs every day enforces these periods.
7. Account deletion and data export
You delete your account yourself in the account settings by confirming your password. We immediately delete the account, device tokens, consents, hike log, favourites, check-ins and photos (including the files). Condition reports remain for the history of conditions, but hidden and without text; they stay linked only to an anonymised account record without e-mail address and name. The audit trail remains until its 12 months expire. Limited copies may remain temporarily in encrypted backups until regular rotation overwrites them (database up to 30 days, photos up to about 2 months). Backups serve recovery after a technical or security incident; we do not restore individually deleted data from them.
In the account settings you can download all your data in a machine-readable format (JSON) at any time.
8. Your rights
You have the right of access, rectification, erasure, restriction of processing, objection (where we rely on legitimate interest), data portability and withdrawal of consent without affecting earlier processing. You can exercise most rights yourself in your account (export, deletion, consents). For anything else write to info@nahrib.app; we reply within one month at the latest. We verify your identity through the e-mail address of the account.
You can lodge a complaint with the Information Commissioner of the Republic of Slovenia, Dunajska cesta 22, 1000 Ljubljana, gp.ip@ip-rs.si, www.ip-rs.si.
9. Children
Accounts can be created by persons aged at least 16. We do not knowingly collect children’s data; if we learn of an account of a younger person, we delete it.
10. Automated decision-making
We do not carry out automated decision-making with legal or similarly significant effects. The distance calculation for a check-in is automatic but has no such effect. Community contributions are reviewed by a person.
11. Security
Connections are encrypted (HTTPS), passwords and tokens are stored only as hashes, photos are kept outside publicly accessible folders, staff access is limited by role and logged, and the number of login attempts and other actions is limited. No system guarantees complete protection. If a personal data breach occurs, we handle it as required by law and, where necessary, notify the supervisory authority and the people affected. If you suspect misuse of your account, change your password, disconnect your devices and write to us.
12. Changes
We update this policy for new features (for example the mobile app), new processors or new regulations. We inform account holders of material changes by e-mail at least 30 days before they take effect. The version and date are always shown at the top.