Privacy policy
Last updated:
This page explains what personal data the HaideHai platform, operated by ATUMCOM SRL, with its registered office at Ramnicu Valcea Str. Ferdinand 34 Bl. CPL, registered with the Trade Register under no. J2020000208389, tax ID (CUI) RO42312113, processes and what rights you have over it.
What we collect
When you create an account: e-mail address, username and password (stored only as a cryptographic hash). Optionally, in your profile: display name, photo, bio, locality and contact phone — the phone is requested only when joining guided tours and is never shown publicly.
If you subscribe to the newsletter (on the site or on the launch page, haidehai.ro), we keep your e-mail address, language, the date you gave your consent and the page you subscribed from. The subscription is active right away: we send you an e-mail announcing it, with an unsubscribe link, in case it wasn't you who entered the address. We write when we launch and, rarely, with news: new routes, conditions, seasonal guides. The basis is your consent, which you can withdraw at any time with the link in any of our e-mails.
The phone app also sends us telemetry: which screens and features you use (for example that you started a recording or downloaded a map, with the identifier of the route or area downloaded), the platform and app version, for a few battery-related events also the make of the phone, and the app's errors, with the message stripped of e-mail addresses, coordinates and keys. It does not send your position, the tracks of your recordings or your account key. The events do not carry your account: they are tied to an app session, which starts when the app opens and each time you sign in or out. Because they are not tied to your account, they are not part of your data export and are not deleted with your account. So that they cannot be tied to an account, those that also have a row written on the server (signing in, reviews, reports, recordings, saved plans) are kept without a session, and the identifier of an unpublished route is removed. We use the IP address they come from for at most an hour, to limit how many events we accept, and we do not keep it with them; like any request, it appears for 14 days in the web server log. We keep them for 90 days, a period the platform administrator can set between 7 and 365 days.
When you measure on the map, the ends of the straight-line stretches — the points you place, not your location — reach the HaideHai server, rounded to about 10 m, so we can work out the ascent and descent of the ground between them. We do not keep them or pass them on.
Your username (or display name, if set) is shown PUBLICLY next to your contributions — reviews, field reports, proposed routes, articles, tours. A pseudonym is fine. Your e-mail address is never displayed publicly.
The content you publish (routes, reviews, field reports, photos, articles, public lists) is associated with your account and visible according to each content type's settings.
Personal marks (favourites, completed routes, private lists) are visible only in your account; your public profile shows aggregate figures only, never the list of routes you completed.
How sign-in works
Your session uses a token kept in your browser (localStorage). We do not embed advertising. What statistics we collect and what stays in your browser is explained below, under “Statistics, cookies and what we keep in your browser”.
Support access (“view as user”)
To diagnose a problem, the team can open a 15-minute, read-only session in which they see the platform exactly as you do — they cannot change your password or write anything on your behalf. A team account (administrator, moderator, etc.) cannot itself be the target of such a session. Every session leaves a trace in the audit log and appears in your data export.
Third-party services
For maps, weather, place search and elevation we rely on external services (OpenStreetMap contributors, MET Norway, Photon, elevation sources). Requests to them are generally made from our servers; we do not pass them your account data.
Push notifications on your phone are sent through Expo (the Expo Push service), which passes them on to Google's Firebase Cloud Messaging on Android or to Apple Push Notification service on iPhone. These services receive your phone's notification identifier, the notification's title and text, its identifier and category and, for most of them, the link to the page in the app. The title and text say what it is about: the outing's name, date and meeting point, the organiser's message or the reason for a cancellation, an excerpt of the reply you got, the name of the route, club or article, your role in the club, the type of field report and the names of other people — who follows you, replies to you, invites you, asks to join the club or announces an outing. For moderation and system notifications the text is generic and carries no link. The exception is the test notification, which a HaideHai administrator can send to check that notifications arrive: it goes out with its full text, which is fixed and contains no data about you. We do not send them your e-mail address or password. To get the notification identifier, the app contacts Expo directly while notifications are on, when it starts and at least once a week; Expo then sees the phone's IP address and an identifier of the app installation. The app asks for notification permission when it first starts and when you sign in. If the permission is already granted on the phone (on Android below version 13 it is granted by default), your account gets push notifications when you sign in, without us asking you. You can turn them off at any time with the “Notifications on this phone” switch in “Notification preferences”; after that, on this phone, we no longer ask and we do not turn them back on for your account by ourselves. The choice is kept on the phone: after a reinstall or on another phone, the rules above apply again. Most categories can also be turned off separately, in the same place. News (marketing) is not sent by e-mail or to your phone until you turn it on in “Notification preferences”, and you can turn it off at any time; it is a separate choice from the newsletter.
When a recording has no altitude from the phone, or when a route’s data is recomputed (the “Regenerate data” button), we send OpenTopoData points along the track line — about one every 60 m, rounded to about 10 m, start and end included — to get the elevation profile from the terrain model. We do not send your account, name or times. This also applies to private recordings.
For the weather forecast of a route, including one made from a recording, we send MET Norway points rounded to about 10 m: at most three on the route page and in the planner (the start, the end and one point in between), and one per day in day-by-day plans, from the middle of that day's section. We do not send your account, name or times. This also applies to private routes.
In the planner, the points you place on the map and the track you upload are sent as they are, start and end included, to routing services (BRouter, with OSRM as a fallback). For the forecast, MET Norway receives at most three points, rounded to about 10 m, start and end among them. For elevation, we send OpenTopoData points rounded to about 10 m: from straight-line segments and, from an uploaded track with missing elevation, about one every 90 m, start and end included in both cases. The same happens when you edit the track of a recording or a route, and when a HaideHai administrator edits it. We do not send your account, name or times.
When you save a place without an elevation — one you put on the map, whose coordinates you typed or that you took from the catalogue — we send its point to OpenTopoData, rounded to about 10 m, to look up its elevation in the terrain model. Places saved from your location, from a recording or from a file are not sent. We do not send your account, the place's name or its note. This also applies to private places.
When a recording is ready, or when an administrator rebuilds the surface type of the recording or of the route made from it, we send points from that track to BRouter, start and end included, about one every 250 m, to find out what kind of way you went on (paved, gravel, path). We do not send your account, name or times. This also applies to private recordings.
Statistics, cookies and what we keep in your browser
To know how many public pages are read, we run our own counter. For each page kept open for at least a second, the site sends us only its address, without anything after the “?”. We add up views per page, per day and per language — nothing more. In the same way we count, per day, how many times “Accept” and “Decline” are pressed in the “Usage statistics” window.
The counter sets no cookie and uses nothing kept in your browser, which is why it runs without asking for your consent. We use it in our legitimate interest in knowing how the site is used. Your IP address, browser and account do not go into its figures, so a page view cannot be linked to you; we look at the browser's name only to leave out robots. Sign-in and account pages, search, notifications, recordings, lists, day plans, your places, people's profiles, editors, flyovers, any page opened with a sharing link and the other pages with personal data are not counted. We keep the figures without a time limit; they say how many times a page was shown, not who read it.
Like any request to the site, this one appears in the web server log (IP address, browser, the time and the page it comes from, including anything after the “?”, except sharing codes), which we keep for 14 days for security and troubleshooting.
We load Google Analytics only if you press “Accept” in the “Usage statistics” window. Google then receives: the page address (without anything after the “?” and without the pages above that are not counted); the site you came from (its domain only) and our previous page; how long you stay on the page; the browser and device type, language and screen size; a random identifier, kept in the _ga cookie. It also learns when you do one of these: search from the box on the home page (without the words you searched for), open a route (with its range, activity, difficulty and source), download its GPX file, add it to your favourites, save a route from the planner (with the activity and a distance band), create an account or sign in (and how: e-mail, Google or Apple), sign up for an outing, subscribe to the newsletter. We send no people's names, text you typed into fields, coordinates or codes. Google derives your approximate city from your IP address.
We do not send it your account, we do not use Google Analytics for advertising and we have turned off linking the data to your Google account (Google Signals). Google Ireland Limited processes this data as our processor, under the data processing terms accepted in our Google Analytics account. The data may be transferred to Google LLC, in the US, which is certified under the EU-US Data Privacy Framework. Google keeps data tied to the identifier in the cookie for 2 months; reports with totals, without the identifier, remain in our account without a time limit.
You can change your choice at any time from the page footer, under “Statistics settings”. When you decline, the Google Analytics cookies are deleted and we send nothing more to Google; what it already received stays with Google until the period above ends.
On the sign-in and account creation pages, the “Continue with Google” button is loaded from Google together with the page, even if you don't press it: Google then sees your IP address and that you opened our page, and if you are signed in to Google, it uses its cookies to show you your account. Apple's code is loaded only when you press the Apple button.
In your browser we keep, in localStorage: the session token (hh_token), while you are signed in — the browser sends it with every request to us, so we know it's you; your statistics choice (hh_analytics_consent), until you change it.
Also there, until you clear them in your browser: display preferences (map layers and base map, walking pace, blog layout); what you chose in the planner (how far you want to go, the day and time you set off) and its draft (deleted when you sign out; its points go to the routing services only when you calculate the route, as described under “Third-party services”); the ticks on each route's equipment list; a copy of the list of map styles and point categories, so they load faster.
While the tab is open, in sessionStorage, we also keep the route sent from the planner to the day plan, the fact that you have just deleted your account and a confirmation message that is shown only once.
Only if you accepted statistics: the _ga and _ga_YQ02VE1E5E cookies, set by Google Analytics to tell one browser's visits from another's. They expire 2 years after your last visit and are deleted when you decline. Also in that case, in sessionStorage, hh_ga_deferred: the fact that you have just created an account or signed in, and how. The sign-in page is not sent to Google, so we keep this until the first page that is; it is gone anyway once you close the tab.
Retention
Account data is kept for as long as the account exists. Public content stays published until you withdraw it or it is removed through moderation. You can request deletion of your account and associated data at contact@haidehai.ro.
We keep your newsletter address while you are subscribed. After you unsubscribe you receive nothing more; we keep the address with the unsubscribe date, as proof of your choice, until you ask us to delete it at contact@haidehai.ro.
We also keep the points of a recording made with the phone as the app sent them (with the GPS errors and the positions from pauses, which the cleaned track doesn't have) for 90 days after the recording is processed, so we can check and tune the filter for those errors and auto-pause. Then we delete them; the recording and its cleaned track stay. You receive them too, in your data export; otherwise, only a HaideHai administrator can see them, and each access is written to our audit log.
Your rights
You have the right of access, rectification, erasure, restriction and portability over your data, and the right to lodge a complaint with the supervisory authority. For any request, write to contact@haidehai.ro.
You can object at any time to processing based on our legitimate interest by writing to contact@haidehai.ro; the page counter cannot identify you, so there are no visits of yours in it for us to stop. You can withdraw your consent to statistics at any time, from the page footer, as easily as you gave it; withdrawing it does not affect what was processed before.
Changes
Important changes to this policy will be announced on this page, with the date of the last update.