Hunter Rebornby Mažoji bendrija FARO applications
Legal

Privacy Policy

Effective: 2026-06-08Last updated: 2026-09-15

This Privacy Policy explains what information the Hunter Rebornmobile application (“Hunter Reborn”, “the app”) collects, how we use it, who processes it, and the choices and rights you have. Hunter Reborn is operated by Mažoji bendrija FARO applications, a Lithuanian mažoji bendrija registered under code 307725118, with its registered office at J. Savickio g. 4-7, LT-01108 Vilnius, Lithuania(“we”, “us”, “our”). We are the data controller for the personal data described here.

This policy applies only to the Hunter Reborn app. By creating an account or using the app, you agree to the practices described below.

1. Information you provide

  • Account.When you sign in with Apple, with Google, or with an email and password, we receive an account identifier and your email address. If you use Sign in with Apple, you may choose to hide your email, in which case we receive only Apple's private relay address. If you use Sign in with Google we ask Google only for the openid, email and profile scopes, and of what Google returns we store only the account identifier and the email address — we do not import your Google display name or your Google profile photo, and we never receive your Google password. Signing in with Google gives us no access to any other Google service, and if an account already exists with the same email address the two sign-in methods simply lead to that one account.
  • Profile & training data. Onboarding answers (experience level, goals, training location, schedule), your age, gender and height, body weight, workout logs (exercises, sets, reps, weights, rest times), GPS run routes, and an optional profile avatar you select from your photo library. From this we derive your pillar scores, Hunter Rank, and class.
  • Support correspondence. If you email us, we receive your message and your email address so we can respond.

2. Health & fitness data

With your explicit permission, the app reads sleep, steps, resting heart rate, and heart-rate variability from Apple Health (HealthKit), Android Health Connect, and/or a linked Oura Ring account. Where your device or wearable records sleep stages (deep, REM, light/core, and time awake) and the times you fell asleep and woke, the app reads those too, so it can show you your own sleep history. This data is used solely to calculate your in-app Health (HLT) pillar score, to produce your morning readiness reading, and to display your activity and sleep back to you. With your permission, the app may also write completed workout sessions back to Apple Health or Health Connect — the activity type, its start and end time, and, for GPS activities, the distance. On Android an in-app notice describing exactly that appears on the workout summary beforeHealth Connect asks for the write permission, and you can switch write-back off at any time in the app's Settings.

We never use Health data — including data obtained through HealthKit or Health Connect — for advertising, marketing, or any use-based data mining, and we never sell it or disclose it to third parties for their own purposes. Raw HealthKit and Health Connect records stay on your device; only the aggregated values needed to compute your HLT score are sent to our servers. You can revoke health access at any time in your device's Health / Health Connect settings or by disconnecting Oura in the app.

3. Location data

Hunter Reborn collects precise location (GPS) data, and it does so in the background while a run is being tracked. This section explains exactly when that happens, what is collected, why, and how to stop it.

3.1 When we access your location

Location is used for one feature only — run tracking. The app reads your position at exactly two moments:

  • When you open the run screen. A single current-position reading, so the map can centre on where you are rather than on an arbitrary part of the world.
  • While a run is active. A continuous stream of position readings, so the run can be measured.

We do not access your location at any other time. If no run is in progress, the app is not reading your position — not on a schedule, not while you use other screens, and not while the app is closed.

Before either of those happens, and before your operating system asks you for the location permission, the app shows you an in-app “Location access” notice on the run screen that states what is collected, that collection continues in the background during a run, and what it is used for. Nothing is read until you accept it. If you decline, no location data is collected at all and GPS run tracking stays switched off — the rest of the app is unaffected — and you can change your mind later from the same screen.

3.2 Background location — while your screen is locked

A run has to keep recording once the phone goes into your pocket. After you start a run, Hunter Reborn keeps collecting your location while the app is in the background and while your screen is locked, until you pause, finish, or discard that run. Without this, locking your phone mid-run would lose your route and under-count your distance.

  • On Android this uses the ACCESS_BACKGROUND_LOCATION permission and runs as a foreground service, which displays a persistent notification for as long as the run is being tracked.
  • On iOSthis uses the “Always” location permission together with the background location mode; iOS shows its own location indicator while tracking is active.

Background collection stops as soon as the run ends. It is never used to build a picture of your movements, to infer where you live or work, or for advertising, profiling, or analytics.

3.3 What is collected

  • Precise coordinates (latitude and longitude) with a timestamp, plus the accuracy, speed, heading, and altitude reported by your device.
  • Values derived from those readings: total distance, average and split pace, elevation gain, and the encoded route line drawn on your map.

3.4 Why we collect it

Solely to deliver the run feature you asked for: to measure distance, pace, and splits, to draw your route, to speak your audio cues, and to award the XP and Endurance (END) pillar score the run earns. The legal basis is performance of our contract with you (GDPR Art. 6(1)(b)); the operating-system permission itself is granted by your consent, which you can withdraw at any time.

3.5 Storage, sharing, and retention

Completed runs — including the route — are stored with your account in our EU-hosted Supabase database (§5) so you can review them later. We do notsell location data, share it with data brokers or advertisers, or disclose it to any third party for that party's own purposes. Your route — the coordinates themselves — is never shared with Oura, RevenueCat, or any analytics provider. When you finish a run, its distance, duration, and pace (never its coordinates, and never a start or end point) are included in the product-analytics event described in §5.1.

If your profile is public, other Hunter Reborn users can see a run's distance, duration, and pace on your profile. Route maps are not shown on public profiles — the map of where you actually ran stays in your own account. You can make your profile private in the app at any time. If you choose to share a run image yourself, that image contains a drawing of the route, and where it goes afterwards is up to you.

You can delete an individual run in the app, which deletes its route with it. Deleting your account (§7) deletes all runs and routes.

3.6 Your controls

You can decline location access, downgrade “Always” to “While Using”, or revoke it entirely in your device settings at any time. Run tracking is the only thing affected — the rest of the app (workouts, ranks, scores, health metrics) continues to work normally. Declining the in-app notice described in §3.1 means nothing is collected and GPS run tracking stays off; if you accept it but later downgrade “Always” to “While Using” in your device settings, a run may stop recording when your screen locks.

4. Subscriptions & payments

Subscriptions are processed by Apple (App Store) or Google (Google Play) and managed through RevenueCat. We receive your subscription status and a RevenueCat identifier mapped to your account. We never receive your full payment-card details.The payment transaction itself is governed by Apple's and Google's own privacy policies.

5. Where data is stored & who processes it

Your account and training data are stored in our Supabase (PostgreSQL) backend hosted in the European Union (Frankfurt, Germany), protected by row-level security so each account can access only its own rows. A session token and cached data are stored locally on your device. We rely on the following processors, each acting on our behalf under a written data-processing agreement and providing protections at least equivalent to those in this policy:

  • Supabase — authentication and database hosting (EU region). Primary store of your personal data.
  • RevenueCat — subscription status management.
  • PostHog — product analytics (EU region, Frankfurt). See §5.1 for exactly what is sent and how to turn it off.
  • Oura Health — only if you link an Oura Ring, via OAuth, to read the metrics in §2.
  • Google Cloud (Vertex AI) — generates the written System analyses described in §5.4. Receives training summaries, never your name or email. Google does not use Vertex AI customer data to train its models.
  • Apple / Google — sign-in, health-data frameworks, and payment processing.

Where a processor transfers data outside the European Economic Area, we rely on the European Commission's Standard Contractual Clauses and/or the EU–US Data Privacy Framework where applicable.

5.1 Product analytics

To understand how Hunter Reborn is actually used — and, above all, where people get stuck or give up — we record a small set of product events through PostHog, hosted in the European Union. This is first-party analytics: it exists to improve the app, and the data is never sold, never used for advertising, and never used to track you across other companies' apps or websites.

What is sent:

  • Which screens you open, as route names (for example /workout/[id]) — never the contents of a screen.
  • Which onboarding step you reached, so we can see where the sign-up flow is failing people.
  • That an event happened: you signed up or signed in (and whether by email or Apple), finished onboarding, viewed the paywall, started or restored a subscription or a purchase failed, started, finished or abandoned a workout, started or finished a run, completed a daily quest, began a campaign, ranked up or levelled up, connected a health device.
  • Coarse figures attached to those events: a workout's set count, duration, volume and XP; a run's distance, duration and pace. Your app version, operating system and language.

What is not sent: your name, email address, avatar, body weight, health metrics, run routes or any coordinates, and the contents of your workout logs. Events are keyed to your account identifier — a random ID, not an advertising identifier — so they are pseudonymous rather than anonymous, and are covered by the access and deletion rights in §8. Session replay and screen recording are switched off.

Our legal basis is legitimate interest in maintaining and improving the app (GDPR Art. 6(1)(f)). You can turn this off at any time in the app under Profile → Settings → Anonymous Analytics; when it is off, the app sends nothing. That switch governs what your device sends; the profile snapshot described in §5.3 is made on our own servers, and §5.3 explains how to opt out of that as well.

5.2 Crash and error diagnostics

When the app crashes or hits an error it cannot handle, we record the failure through the same PostHog account so it can be fixed. This is diagnostics, not behavioural tracking.

What a crash report contains:

  • The error message and the stack trace — the list of code functions that were running when it failed.
  • The part of the app it came from(for example “workout service”), the screen you were on, and your app version and operating system.

Stack traces describe our code, not you, and we never deliberately place personal data in an error message. We cannot promise one is impossible: a message is written by software — including software we did not write, such as the operating system or a third-party library — and can occasionally quote the technical value it choked on. We do not use crash reports for any purpose other than diagnosing and fixing faults.

The Anonymous Analytics switch in the app covers this too: turn it off and no crash reports are sent either.

5.3 Making the app fit you

Onboarding asks you where you train, how long you want a session to run, how often you want to train, and what has stopped you before. Those answers shape the app you get — the raids it builds for you, the campaigns it offers, the rank it starts you at. They are saved to your profile so the app can act on them.

We also want to learn from them in aggregate, because that is how the app gets better for everyone: which options people actually want, which starting points lead to people training and which leave them stuck, and which questions are worth asking at all. The usage events in §5.1 tell us which step somebody reached, but not what they chosethere. So we copy a limited set of profile fields from our database into the same PostHog workspace, refreshed periodically and replaced in full each time — a snapshot, not a live feed.

Concretely, this is what lets us notice that people training at home need shorter sessions than the app offers them, or that a particular starting rank discourages people, and then fix it.

What we copy:

  • Your onboarding answers: the goal you picked, where you train, how long you want a session to be, how many days a week you train and which days you chose, the obstacle you picked at the first question, how long you have previously stayed consistent, the experience level derived from it, and the starting rank the app estimated for you.
  • Your self-assessment as a band, never an exact figure: the push-up and squat numbers you entered arrive only as a range (for example “21–30”), because the range is all we need to learn anything useful.
  • App settings and progress: metric or imperial units, whether reminders are on, whether your profile is public, whether a health device is linked and which kind, your equipped title and frame, your subscription status (including whether access was comped and why), the date your account was created, and your level, rank, class, peak rank, streak, grind streak, whether you are paused, and the date of your last workout.

What stays out of it entirely: your name, email address, age, gender, height, body weight, target weight, avatar, referral code, your pillar scores, and the contents of your workout logs. None of that is needed to improve the app, so none of it is copied. As in §5.1 the copy is keyed to your account identifier — a random ID — so it is pseudonymous, it is never sold and never used for advertising, and it is covered by the access and deletion rights in §8. Delete your account and the underlying profile goes with it; the next refresh drops your row.

Your control over this

We would rather tell you this plainly than let you assume otherwise: this copy is made server-to-server, between our database and PostHog, so your device is not involved — which means the Anonymous Analyticsswitch in the app does not stop it. That switch governs what your phone sends. If you would like to be left out of this too, email us at the address in §12 and we will exclude your account, no questions asked.

5.4 The AI System Coach

After a raid the app can show a short written debrief, and on a Monday it can show a weekly Hunter Report. Those are written by a generative model — Google's Gemini, running on Google Cloud Vertex AI in Google's globalregion. We are telling you this plainly because “the app wrote this” would not be true.

Your phone never talks to Google's model. The request is made by our own server, which sends a summary of the training being analysed: exercise names, set and rep counts, weights lifted, session duration, personal records, run distance and pace, quest and campaign completion, and your level, rank, class, streak and pillar scores.

What is never sent: your name, your email address, your account identifier, your age, gender, height, body weight, your GPS routes or any coordinates, and your raw sleep, heart-rate or heart-rate-variability readings. The model is given training numbers and nothing that identifies you.

Google acts as our processor here. Under the Google Cloud terms, Vertex AI does not use customer prompts or responses to train or improve its models. Each generated text is stored once against your account so the same debrief is not generated twice, and it is deleted with your account (§7). If the feature fails or is unavailable the app simply does not show it — nothing else changes.

6. How we use your information

  • To provide core features: scoring, ranks, workout tracking, runs.
  • To sync health metrics into your HLT score.
  • To verify your subscription and unlock paid features.
  • To respond to your support requests.
  • To maintain security and diagnose technical problems, including from the crash reports described in §5.2.
  • To see how the app is used in aggregate — which screens are reached, where onboarding is abandoned — so we can fix what is broken (§5.1). You can switch this off.

We do not run third-party advertising and we do not sell your personal data.

For Apple App Privacy purposes, Hunter Reborn collects: Contact Info (email, and the name you give your hunter), Health & Fitness, User Content (workout logs and avatar), Location (precise location, collected during GPS runs including while the app is in the background — see §3), Identifiers (user ID), Purchases (subscription status), Usage Data, and Diagnostics. None of this is linked to advertising or used to track you across other companies' apps or websites.

For Google Play Data safety purposes we collect: Personal info(email address, name, user IDs, and other info — the age and gender you enter during onboarding); Financial info (purchase history, i.e. your subscription status); precise Location, collected during GPS runs including in the background while a run is in progress; Health and fitness (health info — sleep and sleep stages, resting heart rate, heart-rate variability, height, body weight — and fitness info — steps, workouts and runs); Photos (only the avatar you choose to upload); App activity (in-app interactions); App info and performance (crash logs and diagnostics); and Device or other IDs (the random identifier the analytics SDK assigns to an installation before you sign in).

We declare no data as “shared”. That is not a claim that nobody else touches your data — the processors in §5 plainly do. It is Google Play's specific definition: a transfer to a service provider that only processes data on our behalf, under contract, is not “sharing”, and neither is a transfer you yourself initiate (linking your Oura account, or writing a workout to Apple Health / Health Connect). Every recipient we use falls into one of those two. We do not sell your data, we run no advertising, and no data goes to anyone for their own purposes. Data is encrypted in transit, and you can request deletion — see §7.

7. Data retention & account deletion

We retain your data for as long as your account is active. You can delete your account at any time directly inside the app (Profile → Delete account). Deletion is immediate and permanent: it removes your profile, workout and run history, personal records, stats, rank, uploaded avatar, and any linked health-data metrics from our active systems right away, and it cannot be undone. Deleting your account does not cancel an active App Store or Google Play subscription — you must cancel that separately in your store account settings. Residual copies present in our encrypted backups are overwritten on a rolling basis and are fully purged within 30 days.

If you have uninstalled the app or cannot sign in, you can still request deletion from our Delete Account page, or by emailing privacy@faroapplications.com from your account's email address. To protect your account we verify every such request before acting on it. You may also use these channels to request access to, correction of, or a copy of your data.

8. Your rights

Subject to applicable law (including the EU GDPR), you have the right to access, correct, delete, export, or restrict processing of your personal data, and to withdraw consent where consent is the legal basis. To exercise these rights, email privacy@faroapplications.com. You may also lodge a complaint with the Lithuanian State Data Protection Inspectorate (VDAI) at vdai.lrv.lt.

9. Children

Hunter Reborn is not directed to children under 13 (or the minimum age of digital consent in your country), and we do not knowingly collect personal data from them. If you believe a child has provided us data, contact us and we will delete it.

10. Security

We use industry-standard encryption in transit (TLS) and at rest, and passwords are never stored in plaintext. Access to production systems is limited and logged. No method of transmission or storage is perfectly secure, but we work to protect your data and will notify you and the relevant authority of a qualifying breach as required by law.

11. Changes to this policy

We may update this policy from time to time. Material changes will be reflected by updating the “Last updated” date above and, where appropriate, by in-app notice.

12. Contact

Privacy requests: privacy@faroapplications.com
General support: support@faroapplications.com