Effective date: September 29, 2025
Last updated: April 18, 2026
Thank you for choosing Durg: Offline Navigation as your companion for exploring the outdoors with offline maps, trails, and navigation. Your privacy matters to us. This Privacy Policy explains what information we collect, how we use and share it, and the choices you have. Please read it carefully. By using our app and related services, you agree to the collection and use of information as described here.
This policy covers the mobile application and the online services we operate to power features such as account sign-in, trek recording sync, community features, optional media processing, and customer support.
Location data (foreground and background) — Used on your device for maps, navigation, trek recording, and safety-related features. When you sync a recorded trek, detailed GPS track points may be stored on our servers as described below.
Account information — For example, identifiers and profile details from your sign-in provider (such as Google Firebase Authentication), email address, and community username where applicable.
Device and app information — Such as device identifiers you provide for features like push notifications (Firebase Cloud Messaging token), app version, platform, and optional coarse location sent with token updates when the app chooses to send it.
Trek and activity data — Trip summaries (distance, duration, speeds, elevation, time range) and, when synced, per-point location tracks (latitude, longitude, time, and related sensor fields).
Offline map usage — Which areas or routes you have downloaded and device identifiers used to enforce fair download limits.
Purchases — Transaction identifiers and related data needed to validate Google Play (and, where applicable, other store) subscriptions or one-time purchases.
User-generated content — Such as forum posts, comments, reviews, images, GPX files, and metadata you submit when using community or media features.
Technical and operational logs — Server and security logs, diagnostic events, and similar data needed to run and protect the service.
To provide offline maps, GPS guidance, trek recording, sync, and optional route or safety features.
To create and secure your account and link it to community (forum) features.
To deliver notifications, process purchases, and enforce download or subscription rules.
To host and process content you upload (for example, images or GPX for video or sharing workflows).
To improve reliability and features, including search that may use AI embeddings of text you search for.
To protect users and the platform and to meet legal obligations.
We do not sell your personal data to third parties for money.
Location history and precise tracks are not sold to marketers. They are used to operate features you choose (such as sync and publishing, if you use them).
Community content you post under your username may be visible to other users, depending on the product surface.
If you publish a trek or similar content where the product makes it public, associated trip information may be visible to others as designed in the app.
We use service providers (for example cloud hosting, messaging, AI, and forum infrastructure) who process data on our behalf under appropriate terms.
We collect information in two ways: information you provide, and information collected automatically when you use the app or our servers.
Account and profile — When you sign in, we receive identifiers from our authentication provider (for example Firebase UID and email). For community features we may store a forum username and tokens needed for your session with the forum software .
Trek sync — When you choose to sync a recorded activity, we may receive a trip summary and an array of GPS points (e.g. latitude, longitude, timestamp, altitude, accuracy, heading, speed).
Token and device updates — You or the app may send a push notification registration token and optional headers such as app version, build/version code, platform, and sometimes approximate coordinates associated with that update.
Offline downloads — When you download regions or routes for offline use, we may record what was downloaded, when, and a device id you provide so we can apply per-device or daily limits.
Purchases — You or the store may send transaction IDs, receipts or tokens, product identifiers, and platform fields needed to verify and restore purchases.
Community and media — Text, images, GPX files, titles, descriptions, tags, and other fields you submit for posts, jobs, or uploads.
Location — As needed for navigation and recording on device; background location may be used for continuous recording or alerts, depending on your settings and the feature (see Your choices).
Server logs and diagnostics — We may log events (for example notification lifecycle, job processing, or errors) with technical context and identifiers needed to troubleshoot.
Search queries — Text you enter in features that suggest similar community topics may be sent to our systems and to an AI provider to compute search embeddings (see Third-party services).
We use the information we collect to:
Provide and maintain maps, navigation, trek recording, sync, and statistics.
Operate community features (posts, profiles, moderation) and optional similar-topic search.
Send push notifications and in-app messages where enabled.
Process and validate purchases and manage credits or entitlements where applicable.
Store and process uploads (for example on object storage) and run video or media jobs when you use those features.
Improve performance, security, and product design; detect abuse; and comply with law.
We only share information as needed to run Durg:
Your username and public posts (reviews, comments, photos, etc.) may be visible according to community settings.
Published treks (or similar features) may expose trip metadata to other users when you opt in to publishing.
Depending on configuration, we use or may use providers such as:
Google Firebase / Google Cloud — Authentication, Firebase Cloud Messaging for push notifications, and related Google services configured for the app.
Forum provider — Hosting and displaying community content tied to your account mapping.
Amazon Web Services (AWS) — Storage (S3) and related cloud processing for files and media; video rendering workflows may use AWS.
OpenAI — Generating text embeddings for search features and, where enabled, content analysis for operational features (for example notification assistance). Content sent to OpenAI is limited to what is needed for that request.
These providers must use personal data only to provide services to us, subject to their agreements and applicable law.
We may disclose information if required by law, regulation, or legal process, or to protect safety, rights, or security of users or the public.
In a merger, acquisition, or asset sale, information may be transferred as part of that transaction, subject to this policy or successor notice.
We do not sell your personal information as a commodity. We may share aggregated or de-identified statistics that do not identify you.
Data is stored on secured servers and cloud infrastructure. We apply reasonable technical and organizational measures to protect personal information.
No method of transmission or storage is 100% secure; we cannot guarantee absolute security.
We retain data as long as needed to provide the service, comply with law, resolve disputes, and enforce agreements. Some logs may be kept for shorter operational periods.
Depending on your region, you may have rights to access, correct, delete, export, or restrict processing of your personal data, and to object to certain processing.
You can also control:
Location — Grant, change, or revoke foreground and background location in your device settings. Restricting background location may limit or disable recording, navigation, or alerts that require it.
Notifications — Enable or disable push notifications in system settings or in-app where available.
Account and content — Update profile and delete certain content in the app where supported.
Account deletion — You may request deletion of your account and associated personal information by contacting us at the email below. We will process requests in line with applicable law and may need to retain certain records where required.
The Services are not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe we have collected such information, contact us and we will take steps to delete it promptly where appropriate.
We and our providers may process and store information in various countries where we or our vendors operate. Where required, we use appropriate safeguards for cross-border transfers.
The app may contain links to third-party sites or integrate third-party SDKs. Their practices are governed by their privacy policies. Review those policies for services you use (for example Google Play, Firebase, or device vendors).
We may update this Privacy Policy from time to time. We will post the updated policy in the app or on our site and revise the Last updated date. If changes are material, we will provide additional notice as appropriate.
If you have questions, concerns, or requests regarding this Privacy Policy or your data, contact us at:
Email: sagaryadav478@gmail.com
This policy is meant to describe our practices in plain language. If any summary section differs from a detailed section, the detailed sections govern.