Skip to main content
Version 3.1 • 11 November 2026

Privacy Policy

Mobile Application & Website - Version 2.0 (Replaces all previous versions)

Operated by Tusker Trails (Pty) Ltd | Governed by the laws of South Africa

Summary

Kruger Companion does not sell your data. Map and navigation location stays on your device. When you are signed in with notification permission, your current camp and park region (never your coordinates) may be stored privately so we can send relevant service or safety alerts while you are in the park. Data donation is voluntary: donated sightings are stored pseudonymously (without your name, account or device ID). Conservation reports carry no personal identifiers. We comply with POPIA (South Africa) and align with GDPR principles.

  • Optional user accounts support Cloud Sync of personal sighting logs, saving trip plans from the website trip planner and Camp Chat participation.
  • Push notifications are optional for Camp Chat (per camp). Signed-in users who grant notification permission may also receive occasional service or safety announcements from Kruger Companion (not marketing ads).
  • An optional Referral / Invite programme attributes installs or invite codes so inviting users can earn points and badges; the Top-10 leaderboard requires a separate opt-in.
  • Crash reports are collected via Firebase Crashlytics to improve app stability.
  • Users may permanently delete their account and all associated cloud data at any time from Account Settings in the app or at krugercompanion.co.za/delete-account.

1. Information We Collect

1.1 Location Data (GPS)

Our App requires access to your device's location services to provide core functionality, specifically:

  • Displaying your current position on the map (both online and offline).
  • Calculating distances to points of interest (camps, gates, picnic spots).
  • Navigating along routes within the park.
  • When you are signed in: your coarse presence (the camp you are in, if any, whether you are inside the park, the park region north/central/south, timestamp and platform) may be written to your private device record so we can deliver relevant service or safety push notifications to people currently in the park or in a specific area. This is not a movement history trail. The app works this out on your device; GPS coordinates are not sent or stored.

Important: Continuous map/navigation location processing stays on your device. We do not sell location data. The private coarse snapshot (if any) is stored under users/{uid}/private/device, used only for operational targeting of service/safety pushes, and is removed when you delete your account.

1.2 User Accounts

Creating an account is entirely optional. If you choose to register (via the mobile App or the Website), we collect your email address, a password hash, and a chosen username (alias) to secure your profile. In the app and on the website you can instead sign in with Google or Apple. This uses Firebase Authentication (Google LLC) together with the respective provider (Google or Apple). In that case no password is created: Google or Apple confirms your identity and shares your email address, name and a user ID with us. When you sign in with Google or Apple for the first time, you choose a username (alias) and accept this privacy policy; the newsletter is an optional opt-in. The email address is stored in Firebase Authentication as described below; your name is only used on your device to suggest a username and is not stored. If you use Apple's "Hide My Email", we only receive a relay address from Apple that forwards to your inbox. Google's and Apple's own privacy policies also apply to signing in with them (policies.google.com/privacy, apple.com/legal/privacy). Your sightings are only synced to our secure cloud database if you explicitly turn on the "Cloud Sync" feature. Trip plans are only stored in your account if you click "Save to my account" in the website trip planner (see Section 4.7). You may log out, disable sync, or permanently delete your account and all associated sightings at any time via the app or krugercompanion.co.za/delete-account.

What is stored at registration

FieldWhere storedPurpose
Email addressFirebase Authentication only (not in Firestore)Login, email verification, password reset
Password (email sign-up only)Firebase Auth (hashed)Authentication
Google or Apple account ID (sign-in with Google/Apple only)Firebase AuthenticationLogin without a password
Alias (username)Firestore users/{uid}Display in Camp Chat
newsletterOptIn (boolean)FirestoreOptional newsletter
dataProcessingConsent + timestampFirestoreConsent at registration (required)
syncEnabled (boolean)FirestoreCloud Sync on/off
createdAtFirestoreAccount creation

Important: Your email address is deliberately not stored in Firestore (data minimisation under GDPR/POPIA).

Cloud Sync (Sightings, camp visits and saved trips)

The following personal data is stored per account in Cloud Firestore:

  • Sightings (only when you enable Cloud Sync) in users/{uid}/sightings: animal ID, date/time, GPS coordinates, notes, count
  • Camp visits from the app in users/{uid}/camp_visits
  • Trip plans you save with "Save to my account" in the website trip planner, one document per trip in users/{uid}/trips/{tripId} (see Section 4.7)
  • Not visible to other users
  • Only the account holder can read or delete this data

Account deletion

You can permanently delete your account under Account Settings → Delete Account in the app, or on the website at krugercompanion.co.za/delete-account (also available from your dashboard when signed in). This removes:

  • Firebase Auth account
  • If you signed in with Apple: your Sign in with Apple authorisation is revoked with Apple
  • Firestore profile (users/{uid})
  • All cloud sightings (users/{uid}/sightings/*)
  • All camp visits (users/{uid}/camp_visits/*)
  • All saved trips (users/{uid}/trips/*)
  • Push token (users/{uid}/private/device)
  • Camp Chat subscriptions
  • Newsletter entry
  • Alias (username) reservation
  • Referral profile fields (referral count, invite code, leaderboard opt-in) and related referral attribution records tied to your account
  • Your Tusker Trails Lodge waitlist entry, if you joined it while signed in (see Section 1.9)

Note: Camp Chat messages you have already sent remain visible in the chat history (with the alias used at the time of sending) until removed by an administrator. They are not automatically deleted when you delete your account.

1.3 User-Submitted Conservation Reports

If you choose to submit sighting reports, invasive species reports, environmental incident reports (trash, road damage, erosion) or disease alerts through the App, the following information is collected at the moment of submission:

  • GPS coordinates of the reported location
  • Photograph (if attached)
  • Report type and description
  • Date and timestamp

All conservation reports are anonymised before processing. No personal identifiers are attached to any report visible to our team or to third parties including SANParks.

1.4 Donated Data

The App includes an optional Donate Data feature (live auto-share of sightings). If you choose to activate it, each sighting you log is sent to our server and stored in a private database (a Google Sheet): species, date, time (to the minute), GPS position, a location description (for example "On H4-1, 2km N of Sunset Dam") and whether the position came from GPS or was entered manually. No name, account ID, device ID, advertising ID or IP address is stored with these records (your IP address is used only briefly for rate limiting to prevent abuse and is not stored with the sightings). Because a time and an exact position could in theory be linked into a trip, donated sightings are pseudonymous rather than anonymous. Inside Kruger National Park the exact position is kept, as conservation research needs it; outside the park the position is coarsened to about 200 m and used only to see in which regions and other parks the App is used. Rhino sightings are never stored. Data donation is entirely voluntary, is based on your consent and can be switched off at any time in the App settings; the App functions fully without it. Because donated records carry no identifier, we cannot attribute them to you and therefore cannot locate or delete an individual person’s donated sightings (Art. 11 GDPR). See Section 3 for details on how donated data is shared.

1.5 Anonymous Usage Analytics

We collect anonymous, aggregate usage statistics to understand which features are used most often (for example, how often the online or offline map, hub tools, or partner banners are opened). These counters do not include your name, email, account ID, device ID, advertising ID, IP address, or precise location. This is a simple counter. We cannot identify you from this data. The statistics are stored and used only to improve the app.

1.6 Push Notifications

If you enable push notifications for a camp chat room, we collect and store:

  • Expo Push Token - a device-specific identifier used to deliver notifications. Stored in users/{uid}/private/device (not on your public profile), together with device platform (iOS/Android).
  • Camp subscription record - which camp(s) you subscribed to, stored in camp_chats/{campId}/subscribers/{uid} including your push token for delivery.

Camp Chat push is entirely optional. You enable it per camp via the "Push On" toggle in Camp Chat. You can disable it at any time.

Separately, if you are signed in and have granted notification permission, we may store your Expo push token so Kruger Companion can send occasional service or safety announcements (for example park-related information). These are not advertising or third-party marketing.

We use the Expo Push Notification Service (operated by Expo / 650 Industries) to deliver notifications. Expo processes your push token solely to route messages to your device. Expo Privacy Policy: expo.dev/privacy

1.7 Camp Chat

Camp Chat is an optional community feature available to registered, email-verified users. When you participate, the following data is stored on our Firebase servers:

Messages you send:

  • Message text
  • Your alias (username)
  • Your user ID (UID)
  • Badge name at time of sending
  • Timestamp
  • Optional: reply reference (quoted message text and sender alias)
  • Optional: emoji reactions (your UID + emoji)

Presence data:

While you are actively viewing a camp chat, a lightweight presence record (lastSeen timestamp) is written so other subscribers can receive push notifications when you are not in the chat.

Moderation data (on your profile):

  • User reports from other chat participants
  • Warning count, temporary ban expiry, permanent ban flag
  • Link-sharing permission flag (admin-controlled)

Camp chats require email verification before you can send messages. Messages are visible to all authenticated users in that camp's chat room. Profanity is filtered client-side; repeat violations may result in temporary or permanent bans.

Camp chat messages are not automatically deleted when you delete your account. Previously sent messages remain visible with the alias used at the time of sending.

1.8 Referral / Invite Program

The App includes an optional invitation programme. Registered users may share a personal invite link, QR code, or short invite code with friends. When a new user is successfully attributed to an inviter, the inviter receives referral points. At 10 points, an "Ambassador" badge may be awarded. An optional Top-10 leaderboard (opt-in only) may show a temporary "Top Ambassador" badge while a user remains in the Top 10.

How attribution works

  • Android: A Play Store link or QR code can include an install referrer (ref=<Firebase User UID>). After install and login, attribution is recorded server-side via the Google Play Install Referrer.
  • iOS: App Store links/QR codes open the store only. Attribution requires the new user to enter a 6-digit invite code manually (Settings → Account, after login). Apple does not allow equivalent automatic install attribution via QR/link.

Data we store

  • Inviter identifier (Firebase user ID and/or short invite code on the inviter's profile)
  • Attribution record in referrals/{newUserUid}: referrer UID, referred UID, platform (android/ios), timestamp
  • referralCount on the inviter's profile (server-incremented only)
  • Optional leaderboard flags: leaderboardOptIn and leaderboardOptInAt

Sources

  • Android: Google Play Install Referrer on first launch after install
  • iOS: invite code entered by the new user after registration/login
  • Inviter: generated invite code / share link

Purpose

  • Attribute installs/registrations to an inviter
  • Award referral points, badges, and (if opted in) leaderboard ranking
  • Abuse prevention (e.g. blocking self-referrals; each account can be counted as referred only once)

Visibility

  • Referral attribution records are not public by default.
  • Leaderboard (opt-in only): authenticated users may see chat alias and referral count only - never email or UID.
  • Email addresses are not shared for referral purposes.

Processing runs on Firebase / Google Cloud (including a Cloud Function such as registerReferral), aiming for the africa-south1 (Johannesburg) region where feasible - consistent with Section 3.4.

Leaderboard participation is optional and can be turned off at any time in the App. Referral-related profile fields and attribution records tied to your account are removed or anonymised when you delete your account (see Section 1.2 and Section 5).

1.9 Tusker Trails Lodge waitlist

On the map in the App you can ask to be told when Tusker Trails Lodge can be booked ("Notify when available"). This is optional and does not require an account. We store:

  • Your email address (the one you enter or, if you are signed in, the email address of your account)
  • Your consent, the App language, where you signed up (the lodge on the map) and the time of your request
  • If you are signed in: your user ID (uid), so the entry can be deleted together with your account
  • Confirmation status (double opt-in): when the confirmation email was sent and when and how you confirmed

After your request we send a confirmation email from [email protected] through Google Workspace (Google LLC). Your address only goes on the list once you open the link and confirm. The link is valid for 7 days. Entries that are not confirmed are deleted automatically 30 days after the confirmation email was sent.

Purpose: only to email you once Tusker Trails Lodge can be booked. We do not use this list for any other marketing. Legal basis: your consent (Art. 6(1)(a) GDPR; section 11(1)(a) POPIA). You can withdraw it at any time by emailing [email protected]; we then delete your entry.

The entries are stored in Cloud Firestore (lodge_waitlist), and only our administrators can read them. Confirmed entries are kept until you withdraw your consent. If you joined the list while signed in, your entry and its confirmation link are deleted automatically when you delete your account.

2. How We Use Information

We use the information we collect solely for the following purposes:

  • Location data - to show your position on the park map, calculate distances and provide navigation (on-device). A coarse private snapshot may also support geo-targeted service or safety push notifications while you are signed in.
  • User accounts & cloud sync - to authenticate you, sync your personal sighting logs, camp visits and saved trip plans across devices, and manage your profile preferences.
  • Trip planner - to build your plan in your browser, create a share link when you ask for one and, if you choose, keep your trip plans in your account and sync them across your devices (and later open them in the Kruger Companion app), as described in Section 4.7.
  • Camp Chat - to enable community messaging between authenticated users at each camp.
  • Push notifications - to alert you of new Camp Chat messages when enabled per camp, and for occasional Kruger Companion service or safety announcements when notification permission is granted.
  • Referral / Invite programme - to attribute invites, award points and badges, run an optional leaderboard, and prevent abuse.
  • Crash reporting - to diagnose and fix app stability issues via Firebase Crashlytics.
  • Conservation reports - to process, anonymise and display incident data, and to share with SANParks under a formal data sharing agreement.
  • Donated sighting data - to contribute pseudonymised records to conservation research programmes; positions outside the park (coarsened to about 200 m) show us in which regions the App is used.
  • Anonymous analytics - to improve App performance and features.
  • Community submissions - to review and publish user-submitted experiences and ratings on our website, as described in Section 4.3.

We do not use your information for advertising profiling. We do not sell your data to any third party.

3. Third-Party Services

3.1 SANParks and Conservation Partners

We do not currently share donated sightings with anyone. If we do so in future, it will only be with SANParks Scientific Services or other named conservation partners under a formal data sharing agreement, and only in aggregated form or with positions coarsened so that individual trips cannot be reconstructed. You may withdraw consent to future data donation at any time via the App settings.

3.2 OpenStreetMap / Leaflet

The App uses OpenStreetMap and Leaflet for rendering online maps. When fetching map tiles, your IP address may be received by OpenStreetMap servers. This is a standard technical requirement of how map tile services function. No other personal data is shared with OpenStreetMap or Leaflet.

OpenStreetMap Privacy Policy: openstreetmap.org/privacy

3.3 Google Cloud Infrastructure

Server-side data (conservation reports and pseudonymised donated sightings) is stored on Google Cloud infrastructure. Google acts as a data processor on our behalf and is contractually bound to process data only as we instruct. We aim to use the africa-south1 (Johannesburg) region where technically feasible. User account data, Camp Chat, Cloud Sync and saved trip plans are handled via Firebase - see Section 3.4.

3.4 Firebase (Google LLC)

We use Google Firebase services as our backend infrastructure:

ServicePurposeData processed
Firebase AuthenticationUser login & registration (app and website, including sign-in with Google or Apple)Email, password hash or Google/Apple account ID
Cloud FirestoreUser profiles, camp chat, cloud sync, saved trip plans, referralsAlias, sightings, camp visits, saved trip plans, chat messages, push tokens, referral counts, attribution records
Cloud FunctionsServer-side referral attributionReferrer/referred UIDs, platform, timestamp
Firebase CrashlyticsCrash & error reportingDevice model, OS version, stack traces, app version

Firebase acts as a data processor on our behalf. Data may be processed in Google Cloud data centres. We aim to use the africa-south1 (Johannesburg) region where technically feasible.

Firebase Privacy Policy: firebase.google.com/support/privacy

Google Cloud Data Processing Terms: cloud.google.com/terms/data-processing-terms

3.5 Expo (650 Industries)

We use Expo Application Services (EAS) for:

  • Push Notification delivery (Expo Push API) - routes camp chat notifications to your device.
  • Over-the-air (OTA) updates - delivers JavaScript bundle updates without a full app store release.

Expo Privacy Policy: expo.dev/privacy

4. Website - Cookies and Local Storage

This section applies to our website at krugercompanion.co.za and is separate from the mobile App.

4.1 Cookies and Tracking

We use a consent banner to let you control optional storage and analytics. Essential storage is always active; everything else requires your opt-in.

  • Essential storage: We store your cookie consent preference so we do not ask you repeatedly. If you pick a language in the language switcher, a small cookie (kc_lang, 12 months) remembers that choice. Without it, we show the site in your browser's preferred language (English, German, Dutch or French) based on the language setting your browser sends with each request; nothing is stored for this.
  • Functional storage: If you accept functional storage, we save your packing list selections, saved routes, and community voting history in your browser's localStorage for your convenience. The trip planner saves your current plan in localStorage (kc_trip_planner_v1) and, if you saved it to your account, which saved trip it belongs to (kc_trip_planner_cloud_v1). This storage is needed for the planner to work, so it is used even without your consent to functional storage; it stays in your browser and is not sent to our server (see Section 4.7).
  • Analytics cookies: If you accept analytics, we load Google Analytics (which may set cookies such as _ga) and Umami Analytics to measure traffic and engagement. These tools do not load until you opt in.

Your choice: When you first visit our website, a consent banner lets you choose "Accept All", "Essential Only", or customize each category. You can change your preferences at any time using the cookie icon in the bottom-left corner of the screen.

4.2 Fonts

All fonts are hosted locally on our servers. No requests are made to third-party font services such as Google Fonts.

4.3 Community Features

Our website allows anonymous ratings and experience submissions. Community ratings are stored on our server without any personally identifiable information. When you use the "Share your experience" feature or submit a blog article, you are sending an email directly to us via your own email client. We do not store these submissions on our server until they are manually reviewed and published by our team.

4.4 Website Analytics

If you opt in to analytics, we use the following services:

  • Google Analytics (Google LLC): Measures page views, traffic sources, and general engagement. Google may set cookies and process data in the United States. We use Google Consent Mode so no analytics data is collected until you grant consent. IP anonymisation is enabled.
  • Umami Analytics: A privacy-focused analytics service that helps us understand which pages and accommodation links are most useful. Umami does not use advertising cookies.
  • Anonymous click statistics: When you click "Visit Official Website" or "Book Now" on accommodation pages, we increment an anonymous counter on our server (Firebase/Firestore). No personal information is stored with these clicks.

None of these analytics services load or collect data unless you accept the Analytics category in our consent banner.

Anonymous link and campaign statistics (no consent required): Our short links (for example the QR codes on our app stickers, /go/...) and links to our website that carry campaign parameters (utm_source, utm_medium, utm_campaign, utm_content) are counted on our server when the request arrives. Nothing is stored on or read from your device: no cookies, no scripts, no fingerprinting. We only keep daily totals per link or campaign, landing page, country (derived from the request by our hosting provider Cloudflare, Inc.) and device type (iOS, Android or other). Your IP address and the full browser details are not stored, and the totals cannot be linked to you. We do this to know which flyers, stickers, partners and campaigns work. Legal basis: our legitimate interest (Art. 6(1)(f) GDPR; section 11(1)(f) POPIA). Automated requests such as link previews and crawlers are not counted.

4.5 Affiliate / partner links

Some pages (for example our Literature reading list) may include links to online shops such as Amazon. Where we participate in an affiliate programme, we may earn a commission if you make a qualifying purchase after clicking such a link. We do not place Amazon affiliate cookies on our own domain; when you leave our site, the shop operator (e.g. Amazon) may process data under its own privacy policy, including cookies or similar technologies on its websites.

Affiliate participation does not influence which books we recommend. Product availability, pricing, and shipping are controlled by the shop.

4.6 Lead enquiry forms

On pages such as Lodge Companion and Cooperations, you may submit a business enquiry (company/lodge name, last name, email, optional first name, topic and message). That form posts directly to Zoho CRM (Zoho Corporation, EU data centre) so we can follow up. Zoho processes the submission under its own terms and privacy policy. We use the data only to respond to your enquiry (for example about Lodge Companion / Guest Companion, advertising or partner listings).

4.7 Trip Planner

Our website trip planner helps you prepare a visit to the park. A plan can contain your travel dates, the number of travellers by age group, your fee category (residency), arrival type, car choice, interests, the camps, lodges and towns you choose with the number of nights, optional names of your own accommodation, free-text notes you enter (for example booking numbers), chosen activities, ticked checklist items and the trip name. You do not need an account to use the planner. Your plan is stored as follows:

  • In your browser: without an account, the plan is saved in your browser's localStorage (kc_trip_planner_v1 and kc_trip_planner_cloud_v1, see Section 4.1). It is not sent to our server.
  • In the share link: if you copy the "link to this plan", the whole plan, including your notes, is encoded in the part of the link after the # sign (#p=...). This part is not sent to our server, but anyone who receives the link can see the full plan. Please do not put sensitive information in your notes if you share the link.
  • In your account (optional): if you are signed in and click "Save to my account", each trip is stored as a separate document in Cloud Firestore under users/{uid}/trips/{tripId}. You can save several trips. Only you can read and change them. Purpose: to keep your own trip plans and sync them across your devices (and later open them in the Kruger Companion app). Legal basis: performance of the service you requested (Art. 6(1)(b) GDPR; section 11(1)(b) POPIA). Saved trips are kept until you delete the trip or your account; deleting your account deletes all saved trips.

Note: The trip planner does not store health information in your account (for example, malaria tablets are not part of the plan).

5. Data Retention

Data typeRetention
Location dataMap and navigation location stays on your device and is not sent to our servers. Exceptions: donated sightings and reports you choose to send, and, for signed-in users, your current camp/park region (see Section 1.1).
User account, cloud sightings & camp visitsUntil deleted by the user via Account Settings
Saved trip plans (account)Until you delete the trip or your account
Trip plan in your browser (localStorage)Until you clear your browser's site data
Push tokenUntil push is disabled or account is deleted
Camp chat messagesIndefinitely (community history); alias remains visible after account deletion
Moderation records (bans, warnings)Until account deletion; reports reset after 7 days
Crashlytics crash reports90 days (Firebase standard)
Newsletter opt-in flagUntil account deletion
Tusker Trails Lodge waitlistNot confirmed: deleted 30 days after the confirmation email. Confirmed: until you withdraw consent or, if you joined while signed in, delete your account
Referral attribution & referral countUntil account deletion; then removed or anonymised with the account
Leaderboard opt-in flagsUntil opt-out or account deletion
Anonymised conservation reportsMaximum of 7 years, then deleted or further anonymised
Donated sighting dataMaximum of 7 years
Anonymous usage analytics12 months
Community ratings on the websiteIndefinitely in anonymised form

6. POPIA Compliance

Tusker Trails is committed to compliance with the Protection of Personal Information Act, 2013 (POPIA) of South Africa. In line with POPIA:

  • We collect only the minimum personal information necessary to operate the App and website.
  • All conservation and incident reports are anonymised - no personal information is attached to any report visible to third parties.
  • You have the right to access, correct or request deletion of any personal information we hold about you.
  • Right to deletion: Delete your account at any time via Account Settings → Delete Account in the app, or at krugercompanion.co.za/delete-account (automatic).
  • Right of access: Request a copy of your personal data by emailing [email protected].
  • Disable push notifications: Turn off push per camp via Camp Chat → Push Off, or delete your account.
  • Leaderboard opt-out: Turn off leaderboard participation at any time in the App (referral attribution for points may continue separately if you use the invite feature).
  • We have appointed an Information Officer responsible for POPIA compliance. Contact details are provided in Section 10.
  • We will notify affected users and the Information Regulator in the event of a data breach, as required by POPIA Section 22.

7. EU Users - GDPR Alignment

For users based in the European Union, we aim to align our data practices with the General Data Protection Regulation (GDPR). The lawful basis for processing your data is either your consent (for functional storage, analytics, data donation, accounts, Camp Chat, push notifications, and leaderboard display) or our legitimate interest / contract performance in operating the App (for essential site operation, crash reporting, community moderation, and referral attribution when you use the invite feature).

Lawful basis by feature

FeatureLawful basis (GDPR)
Account & Cloud SyncConsent (at registration)
Saved trip plans (account)Contract performance (Art. 6(1)(b); the service you requested)
Camp ChatConsent + contract performance (use of the feature)
Push NotificationsConsent (explicit opt-in per camp)
Referral attributionContract performance / legitimate interest (feature use; abuse prevention)
Referral leaderboardConsent (explicit opt-in; withdrawable)
CrashlyticsLegitimate interest (app stability)
ModerationLegitimate interest (community safety)

Your rights as a data subject

  • Right to deletion: Account Settings → Delete Account in the app, or krugercompanion.co.za/delete-account (automatic).
  • Right of access: Request via [email protected].
  • Disable push notifications: Camp Chat → Push Off, or delete your account.
  • Leaderboard opt-out: Disable leaderboard participation in the App at any time.

EU users may exercise all data subject rights under GDPR by contacting us at the address in Section 10.

App Store & Google Play - Data Disclosure Summary

The following summary reflects our disclosures for Apple App Store and Google Play privacy forms:

CategoryCollected?PurposeShared with third parties?
EmailYes (optional)AccountNo (Firebase as processor only)
Name / aliasYes (optional)Camp Chat displayNo
Location (GPS)YesMap, sightings, reports; coarse private snapshot for service/safety pushes when signed inNot sold; donated sightings pseudonymised; not currently shared
PhotosYes (optional)Conservation / infrastructure reportsAnonymised to Google Sheets
Device ID (push token)Yes (optional)Push notificationsYes (Expo as processor)
Crash dataYesApp stabilityYes (Firebase Crashlytics)
User content (chat)Yes (optional)Camp ChatNo

Tracking: No - we do not use advertising tracking frameworks, IDFA, or Google Analytics in the mobile App.

8. Children's Privacy

Our App is intended for general audiences and wildlife enthusiasts. We do not knowingly collect personally identifiable information from children under 13. If you become aware that a child has provided us with personal information, please contact us and we will take steps to delete it.

9. Changes to This Privacy Policy

We may update our Privacy Policy from time to time. You are advised to review this page periodically for any changes. Material changes will be communicated via an in-app notification. The effective date at the top of this document will always reflect the most recent version.

10. Contact Us

Tusker Trails (Pty) Ltd

Email: [email protected]

Information Officer: Alexander Hoppenrath

Postal Address: 1120 Vienna, Austria

Kruger Companion Privacy Policy | Tusker Trails (Pty) Ltd | Effective 11 November 2026 · v3.1