{"kind":"privacy","version":"2026-11-15.2","body_md":"<!-- version: 2026-11-15.2 -->\n# NakshaPro privacy policy\n\nNakshaPro is an independent land information and approximate measurement app. This policy covers Google accounts, India-only offline tracing subscriptions and usage reporting. Historical credit transactions remain subject to their original accounting retention requirements.\n\n## Your phone and external services\n\nPlots, government records, imagery, boundaries, edits, measurements, reports, queue results, preferences, district packages and agreement acceptance are stored on your phone. There is no cloud backup of saved plots. Uninstalling or clearing storage can remove them. Reports go to destinations you choose when sharing. Google Roads coordinate caches expire after 30 days.\n\nGovernment lookups, including background queue retries, go directly from your phone to the government service, not through our servers. That service receives the selected administrative identifiers and plot number. Map, imagery, road and elevation providers receive requests and relevant coordinates needed for their features. They and download-storage providers process connection metadata, including IP addresses, under their own policies. See the app's disclaimer for data sources. Our download-link service keeps aggregate district request counts by UTC day without an account or device identifier.\n\n## Accounts and billing\n\nGoogle sign-in uses Firebase Authentication, which stores your Google identity, verified email and account information. Sign-in and agreement acceptance are required before tours, downloads or app use. Agreements are bundled in the app; accepted versions, device acceptance time and app version are saved locally against your Firebase account and sent to our accounting server when available. Purchases additionally require your billing name, an Indian billing state or union territory and an Indian mobile number. The mobile number is stored in your Firebase Firestore user record, is used only for account and billing support, is not printed on invoices, and is deleted with your account. Server outages do not block agreement acceptance, purchases or subscription access. Google Play and Firebase still require their own connectivity. We request no access to Gmail, Drive or other Google content.\n\nGoogle Play collects payment details, manages auto-renewal and supplies purchase and order information. We do not collect payment card details. The app sends purchase tokens to our server over HTTPS for verification and invoice accounting. Tokens retained for reconciliation are encrypted. A purpose-specific account identifier binds a Play purchase to the signed-in NakshaPro account. Our server stores immutable commercial invoices and refund adjustments, including buyer email, name if provided, state, seller details, Google order reference, amount and dates. The seller is not GST registered; these documents are not GST tax invoices. Google Play's own receipts remain available separately.\n\nInvoices for verified paid purchases and renewals are emailed automatically, including renewals while the app is closed. Invoice copies are available in Account & invoices. Our email provider processes recipient addresses and message contents for delivery. Temporary encrypted email jobs expire within seven days for invoices; diagnostic job metadata is removed within a further seven days. Copies delivered to your mailbox are controlled by you and your email provider.\n\n## Completed trace reports\n\nSuccessful traces are counted locally by India calendar date (Asia/Kolkata). When you next open or resume the app on a later day, completed days are uploaded directly to Cloud Firestore in Mumbai. Each account has one record per active date, with a total, random installation subtotals, upload time and schema version. Retries do not double-count. These records contain no plot numbers, geometry, imagery, coordinates, owner names or government records. Zero-use days are not uploaded. Counts are approximate analytics, not billing evidence or quotas. Unsent counts can be lost if storage is cleared or the app is uninstalled, and the final day is not reported until the app is opened again. Daily records remain until account deletion; local cumulative counts and acknowledgements remain until deletion or app storage is cleared.\n\n## Retention and deletion\n\nOpen Account & invoices → Delete account to remove the Firebase account and daily usage records, plus the linked server accounting profile and account associations. Deletion needs connectivity to Firebase and our accounting service. You may also email a verified deletion request from your registered address to me.kostubh@gmail.com; manual requests are handled within seven days. Account deletion does not cancel a Google Play subscription. Cancel it in Google Play separately. Local saved plots remain until you remove them or clear app storage.\n\nPurchase invoices, refund records and necessary accounting snapshots are retained for eight years after the end of the Indian financial year of the transaction, or longer under a documented legal hold. They remain after account deletion with the account link removed. Purchase-token fingerprints prevent replay; encrypted tokens and billing snapshots support reconciliation during retention. Existing credit-system accounting and reward-abuse hashes remain subject to their original policies. Server recovery backups expire within 30 days. Financial backups contain accounting records and expire within 30 days; expired records are removed from these backups too. Deletion-request correspondence is removed within 30 days of completion.\n\n## Voluntary feedback and contact requests\n\nFeedback & contact opens a Google Form outside the app. Submission is voluntary. Google processes the information you enter and connection metadata under its own policies. We receive the submitted answers and any contact details you choose to provide, to investigate bugs, respond to complaints and contact requests, and improve the app. The app does not attach your account details, plots, coordinates, logs or payment information. Do not submit passwords, purchase tokens, payment credentials or sensitive land or identity records. Contact details are needed only if you want a reply. We remove identifiable feedback and support submissions within 90 days after resolution, unless longer retention is required by law; anonymized product suggestions may be retained. Privacy or deletion requests can also be sent to the email address below.\n\nThe app keeps a local count of successful traces to offer one feedback invitation after 20 completions. This count and the invitation choice stay on your device and are removed when app storage is cleared. They are independent of completed-trace reports described above.\n\n## Contact and choices\n\nSign out to stop account reporting from new traces until you sign in again. Unsent records already associated with an account are not reassigned to a different account. Manage payment and subscription data through Google Play. Support receives information you choose to email; do not send passwords, payment credentials or purchase tokens. Contact [me.kostubh@gmail.com](mailto:me.kostubh@gmail.com) for privacy questions.\n\nConsent history / सहमति इतिहास: Each agreement action, document versions, app version, device acceptance time and Firebase receipt time are stored directly in Firebase until account deletion. New consent records are not sent to the accounting server. प्रत्येक सहमति का इतिहास खाता हटाने तक Firebase में रखा जाता है।\n","published_at":"2026-11-15T09:45:31+00:00"}