Hikers Guild Privacy Policy
How Hikers Guild handles your data, location information, subscriptions, and advertising privacy.
Last Updated: September 24, 2026
Operator and data controller: Nepherius, United Kingdom
Privacy contact: help@nepherius.dev
1. Who We Are and What This Policy Covers
Nepherius operates Hikers Guild and is responsible for deciding how the personal information described here is used. This policy covers the Android app, our associated servers and support communications. Contact help@nepherius.dev about this policy or to exercise your data protection rights.
Hikers Guild stores maps and recordings on your device so supported features can work offline. It also uses online services for authentication, maps, trail discovery and, when enabled, recording uploads and social features.
2. Key Privacy Choices
- Location access: Location permission is optional for browsing. Recording requires location permissions, which you can grant or revoke at any time in device settings.
- Analytics: Firebase Analytics is optional and off by default. You can enable or disable usage analytics at any time in Settings. Diagnostic crash reporting (Firebase Crashlytics) is separate.
- Advertising privacy and consent: On the ad-supported tier, you can review or change your personalized advertising consent choices at any time in Settings > Ads privacy & consent.
- Cloud recording uploads: You can turn automatic upload of completed recordings on or off in Settings.
- Profile visibility: Registered profiles are public by default. You can set your profile to Private in settings to hide it from user search and prevent other users from following you.
- Recording visibility: Saved recordings default to Public. You can set any recording to Private when saving or adjust its visibility later, restricting route access.
An exact route may reveal your home, workplace, routines or visits to sensitive places. We do not automatically hide the beginning or end of a shared route. Private visibility limits access by other users; it does not prevent us from processing a recording you upload to deliver the Service.
3. Information We Process
| Information | Source and Use |
|---|---|
| Account and sign-in information | You and your sign-in provider supply an account identifier, sign-in method, email address and available display-name information. Firebase handles email/password authentication or Google sign-in. Our application server receives identity tokens and account details needed to authenticate requests, rather than your sign-in password. |
| Anonymous-session identifiers | Anonymous access uses a device session and, when connected, a Firebase anonymous identity. These identifiers and technical requests can distinguish a session even when you have not supplied a name or email. |
| Profile and account status | Your chosen display name, selected avatar, public profile identifier, visibility, Free/Pro subscription entitlement status, saved favorite hikes and related account records support profile, customization and feature access. |
| Subscriptions and in-app purchase data | When you view paywalls, purchase or manage a subscription, Google Play processes your payment details directly (we never receive or store your credit or debit card numbers). RevenueCat processes an app user identifier (linked to your account or anonymous session), active entitlement status ('pro'), Google Play purchase tokens, store transaction identifiers, and renewal dates to provision, validate and restore your subscription. |
| Advertising identifiers and ad consent information | For users on the ad-supported tier, Google Mobile Ads (AdMob) processes mobile advertising identifiers (such as the Google Advertising ID / GAID), IP address, app interaction data, and diagnostic metrics to deliver advertisements and measure ad performance. Google User Messaging Platform (UMP) processes consent status, regional indicators (e.g. UK/EEA), and user privacy choices to record and enforce consent preferences. |
| Location and recordings | When enabled, the device processes precise coordinates, measurement times, accuracy and available altitude information to display your position and record a walk. Recordings also include a name, route, start/end information, duration, distance and visibility choice. |
| Hiking progress | Uploaded recordings generate processing results, distance and elevation statistics, completed-hike totals, XP, level, rank, landmark visits, achievements and activity entries. |
| Social information | We store who you follow and who follows you to provide profiles, shared recordings and the following leaderboard. |
| Searches and map requests | Online requests include trail or profile search text, selected resources and requested map/elevation areas. Tile requests can reveal the area you view or download and may indirectly indicate your location. |
| Device storage and files | The app stores settings, session information, downloaded maps and routes, imported GPX route names and coordinates, recordings and pending uploads/deletions. You choose files to import or export through Android's file controls. |
| Technical and security information | Servers and service providers process connection information such as IP addresses, request times, requested services, response status and errors. Our application logs include request identifiers and a derived account identifier. Authentication and app-integrity services also process their required device and security information. |
| Usage analytics and crash diagnostics | If you enable Analytics, Firebase collects app usage information and technical identifiers to help us understand app use. We also record which app section was opened, trail-detail selections, recording starts and completions, successful offline downloads and paywall opens using fixed categories, without route, location or account details in those custom events. Firebase Crashlytics collects crash reports and diagnostic information to help us investigate failures, whether or not Analytics is enabled. |
| Support correspondence | If you contact us, we receive your contact details, message and any files or location information you choose to include. |
The app integrates Google Mobile Ads (AdMob) to deliver advertisements on the ad-supported free tier, and Google User Messaging Platform (UMP) to manage advertising privacy consent. In-app subscriptions are processed through Google Play In-App Billing and managed via RevenueCat; we do not collect or store payment card details directly. Operational server logs, analytics, and authentication/security processing occur as described below.
4. Location, Recording and Offline Use
Live Location and Background Recording
Granting location permission lets the app display your position. Starting a recording stores successive GPS points on your device. On Android, recording requires background location access and uses an ongoing recording notification so it can continue when the screen is off or another app is visible.
You can pause or stop a recording and revoke location permissions in Android settings. Revoking permission prevents the associated features from working; it does not delete recordings already saved or uploaded. We do not stream real-time continuous location to our servers or broadcast your live position to followers. (For operational terms and safety disclaimers, see the Terms and Conditions.)
Uploading a Completed Recording
When cloud upload is enabled, completed recordings are uploaded when connectivity and account access permit. The request includes the recorded route and temporary point timestamps, accuracy and available elevation. The server checks the recording and calculates progress and achievements.
After processing reaches a final result, the server discards temporary per-point timestamps, accuracy and elevation from the active recording record. It retains the precise route path, start/end coordinates, bounds, name, visibility, duration, distance, maximum elevation and processing result. Copies in backups follow the retention arrangements in section 7. Device copies may still contain the original point information until you delete them.
Disabling future uploads does not delete previously uploaded recordings. Use the recording deletion control or contact us to remove existing data. A queued upload may already have been submitted; check the recording's status when changing your preferences.
Local Files and Downloads
Imported GPX route names and coordinates and downloaded route packs are stored on your device. Obtaining maps for an imported or saved route still sends requests for the relevant map areas. Files exported through Android's file picker (such as GPX route files) are saved outside the app's sandboxed storage under your control; deleting an in-app recording does not automatically delete exported external files.
Android device backup or transfer settings may copy local app data. Such copies are also subject to your device settings and the relevant provider's policies.
5. Why We Use Information and Our Lawful Bases
Our UK data protection bases are set out below. We only process the information needed for the relevant purpose.
| Purpose | Lawful Basis |
|---|---|
| Authenticate you, manage your account and deliver requested maps, downloads, recording storage and social features | Performance of our contract with you, where the processing is necessary to provide the feature you request. |
| Process in-app subscriptions, verify entitlements, restore purchases and deliver ad-free access | Performance of our contract with you to provide paid features. |
| Deliver advertisements on the ad-supported free tier and measure ad performance | Our legitimate interests in funding free-tier services through advertising, and Consent where required by law (such as for personalized advertising and accessing device identifiers via the UMP consent framework). |
| Manage advertising privacy and consent choices via Google UMP | Compliance with legal obligations and Consent. |
| Use optional precise-location features on your device | Consent for optional location access; you can withdraw it through device settings. Any additional consent required for device storage or access must be obtained separately. |
| Process recordings you submit and calculate associated progress | Performance of our contract to provide the recording and progress features you request. |
| Protect accounts, verify app integrity, investigate misuse and diagnose service failures | Our legitimate interests in operating a secure, reliable service, balanced against your rights. |
| Collect optional app usage analytics | Consent, which you can withdraw in Settings. Analytics is disabled until you choose to enable it. |
| Answer support enquiries | Performance of a contract where the enquiry concerns your service; otherwise our legitimate interest in responding to enquiries. |
| Meet applicable legal duties and handle legal claims | Legal obligation where a duty applies; otherwise legitimate interests in establishing, exercising or defending claims. |
Accepting the Terms and Conditions is not consent to every use of your data. Where we rely on consent, withdrawing it does not affect processing already lawfully carried out. Choosing Public visibility is a sharing instruction; a default setting must not be treated as affirmative consent where the law requires that consent.
You are not generally required by law to give us information. Without necessary account or security information we cannot provide protected online features; without location access we cannot show live GPS position or record a walk. You can still use supported browsing and previously downloaded content without enabling location.
6. Who Can Receive Information
Other Users
Public profiles can show your display name, public identifier, level, rank, badges, hiking statistics, landmark progress, follower/following counts and eligible completion activity entries. Profile information is available to other registered users; exact public recording routes require a current follower relationship. Public completion activity summaries have a wider audience than follower-only route geometry.
Private recordings are owner-only within the app's user-facing access rules. Making a profile private removes it from search, removes followers and prevents new follows. Returning it to public does not restore those followers. Visibility changes need a successful server request to change online access.
Followers may save a shared route to their local devices for offline use. While making a recording private or deleting it stops future server access, it cannot remotely delete copies or screenshots already saved on another user's device (see Terms and Conditions Section 6). Independently retained activity summaries and progress are described in section 7.
Service Providers and Other Recipients
- Google/Firebase: Firebase Authentication handles sign-in and identity management. Firebase App Check and Google Play Integrity help establish that requests come from a genuine app/device. Firebase Analytics processes usage information when enabled; Firebase Crashlytics processes crash diagnostics. Google sign-in also involves your Google account. See Firebase's privacy information and Google's Privacy Policy.
- Google Mobile Ads (AdMob) & User Messaging Platform (UMP): Google Mobile Ads SDK delivers advertisements on the ad-supported free tier. Google UMP facilitates advertising privacy and consent management. Google processes device identifiers, IP addresses, ad interactions, and consent records in accordance with Google's Privacy Policy and Google's advertising privacy information. You can review or change your consent choices at any time in Settings > Ads privacy & consent.
- RevenueCat: RevenueCat provides in-app subscription infrastructure, purchase receipt validation, entitlement tracking, paywalls, and Customer Center management. RevenueCat processes user identifiers (app user ID associated with your account or anonymous session), device metadata, store product identifiers, and Google Play purchase tokens. See RevenueCat's Privacy Policy.
- Google Play In-App Billing: Google Play processes subscription purchases, payments, renewals, and cancellations. All payment card and billing transactions are handled directly by Google; we never receive or store your financial payment details. Transactions are governed by Google's Privacy Policy and Google Play Terms of Service.
- Hosting and network providers: Providers running our servers, databases, backups and network protection process traffic and stored data as needed to deliver those services.
- Map delivery: Connected maps normally use our project-controlled gateway and hosting infrastructure. Map data attribution does not itself mean that GPS recordings are sent to OpenStreetMap. If a release uses direct external map endpoints, the provider receives connection and requested-area data.
- Legal recipients: We may disclose necessary information to authorities, courts or professional advisers where required by law or justified to protect legal rights. We assess requests rather than providing unrestricted access.
Outside of ad-supported free-tier features described above (which use Google Mobile Ads in accordance with your consent preferences), we do not sell personal information or share it with third parties for targeted advertising.
7. How Long Information Is Kept and How Deletion Works
| Information | Retention and Deletion |
|---|---|
| Local maps, routes, settings and recordings | Remain on the device until removed through app controls, storage clearing or uninstallation, subject to operating-system backups and independently exported files. |
| Accounts and profiles | Kept while the account exists. Account deletion removes the associated live account, recordings, social relationships, progress and activity records and requests deletion of the Firebase identity. Identity deletion can be retried if the provider is unavailable. |
| Uploaded recording paths and summaries | Kept until the recording or account is deleted. An offline recording deletion removes the local copy first; server deletion waits for a successful connection and authenticated synchronisation. |
| Subscription records and purchase tokens | Retained by RevenueCat and Google Play under their data retention policies and statutory accounting obligations. Account deletion clears in-app entitlement state from our systems; store subscription cancellation is managed independently via Google Play (see Terms and Conditions Section 8). |
| Ad consent preferences | Stored locally on your device and via Google UMP to maintain your consent status across app sessions until reset or updated in Settings > Ads privacy & consent. |
| Temporary uploaded point measurements | Kept while processing is pending, then discarded from the active recording record at a final processing result. |
| Progress, achievements, landmark visits and activity snapshots | Stored separately from recordings for the life of the account. Deleting one recording does not reverse earned progress or automatically erase its independent activity snapshot. Public-eligible snapshots can remain visible on a public profile after the source recording is deleted. Contact us about erasure of these records or delete your account. |
| Deletion markers | Limited identifiers are retained to stop delayed uploads restoring deleted recordings and to complete account deletion safely. |
| Firebase Analytics and Crashlytics data | Disabling Analytics stops future collection but does not automatically erase information already collected. |
Firebase publishes separate authentication retention periods: logged IP addresses are retained for a few weeks, and other authentication information is removed from live and backup systems within 180 days after the developer initiates user deletion. See Firebase's retention information.
Use Delete account in account settings while connected, or contact help@nepherius.dev. Uninstalling the app or signing out does not delete your server account. Deleting your Hikers Guild account removes your personal data from our active systems as described above. Because store subscriptions are managed independently by Google Play, deleting your account does not cancel recurring store billing (see Terms and Conditions Section 8). Anonymous users can also contact us about their information; we may need session details to locate it. Do not send us passwords or sign-in tokens. Any exceptional legal retention must have a specific reason and apply only for as long as necessary.
8. International Processing and Security
Our providers may process information outside the UK, including through Google/Firebase's international infrastructure. We do not claim that all information stays in the UK.
The Service uses authenticated access and permissions to restrict account and recording access. While we implement security safeguards designed to protect your personal data, no internet transmission or electronic storage method can guarantee absolute security. Contact us promptly at help@nepherius.dev if you suspect your account or information has been compromised.
9. Your Rights
Depending on the circumstances and the applicable lawful basis, you can ask to access your information, correct inaccuracies, erase it, restrict its use or receive a portable copy. These rights are subject to applicable legal limits; we will explain any limit that applies to your request. Exercising your statutory data protection rights is free of charge and does not require an active paid subscription.
Right to object: You can object to processing based on our legitimate interests, giving reasons relating to your circumstances. Contact help@nepherius.dev and identify the processing you object to.
You can withdraw consent for consent-based processing at any time, including by disabling Analytics in Settings, managing advertising consent in Settings > Ads privacy & consent, or revoking location permissions in your device settings. For stored or uploaded information, you can use in-app deletion controls or contact us directly. We may request proportionate evidence of identity and will respond within the statutory period, normally one month, explaining any permitted extension.
You may complain to the UK Information Commissioner's Office. You do not have to contact us before doing so, although we welcome the opportunity to address a concern.
10. Automated Activity Processing
The Service automatically checks uploaded route geometry, distance, duration, movement plausibility and account eligibility. It uses location proximity to recognise landmarks and applies progress rules to award XP and achievements. Results can affect whether a hike receives progress credit and what appears on your profile. A rejected recording can still remain stored and shared under its visibility setting.
These automated evaluations are used solely for in-game recreational progress (such as XP, levels, and badges) and do not produce legal or similarly significant effects on you. If you believe an automated hike evaluation or progress calculation is inaccurate, contact us at help@nepherius.dev to request a human review.
11. Children and Changes to This Policy
The Service is not directed to children under 18, and we do not knowingly collect personal data from children. If you believe that a child has provided us with personal information, please contact us at help@nepherius.dev so we can promptly investigate and delete the data.
We will update this policy when our practices change and show the effective date. We will bring material changes to your attention through an appropriate notice and obtain additional consent where required before new consent-based processing begins.
12. Contact
Email: help@nepherius.dev