Bhumir Sandhan

Privacy Policy

Privacy & Data Protection

Privacy Policy

This policy explains how Bhumir Sandhan collects, uses, displays, shares, protects and deletes information through its Android app, website, APIs and related services.

Effective date 20 September 2026
Last updated 20 September 2026
Policy scope App, website, APIs and related services

Privacy summary

Bhumir Sandhan collects and processes information needed to operate accounts, publish property listings, enable direct buyer–seller contact, secure the service, provide support, send notifications, understand app usage and diagnose crashes or technical failures. We do not sell personal data.

Important public-display notice

For every active property listing, the seller’s name and phone number, any optional WhatsApp number or email, property photographs, location details and the precise property map pin may be visible to all visitors, including people who are not logged in. A separate unticked consent checkbox is presented before publication. A seller may withdraw this public-display consent by deactivating or deleting the listing.

1. Scope and privacy contact

This Privacy Policy applies to the Bhumir Sandhan Android application, website, application programming interfaces (APIs), property pages and related services (collectively, the “Services”).

For privacy questions, correction or erasure requests, account-deletion requests or complaints, please use the Privacy and Grievance contact details provided in Section 16 at the bottom of this Policy.

2. Information we collect

2.1 Account information

  • Mandatory: name and phone number, including OTP-verification and account-security records.
  • Optional: email address and WhatsApp number.
  • Account ID, account-creation date, login/session information and records of accepted Terms, Privacy Policy or specific consent versions.
  • The current launch version does not collect a profile photograph through account registration.
  • We do not collect a user’s personal or home address for account registration and do not collect a full date of birth solely to verify age.

2.2 Property-listing information

  • Seller type, such as owner or agent/broker.
  • Property title, description, category, sale/rental type, price, area, unit, features and amenities.
  • District, block, mouza, village/locality, property address or directions, and precise map coordinates selected by the poster.
  • Actual property photographs and related upload information.
  • Ownership/authority declaration, public-contact consent, precise-map-pin consent, photograph authenticity/non-misrepresentation declaration, and the date/time of those declarations.

2.3 Support, reports, seller blocking and communications

  • Support message, account ID where the user is logged in, and app version or other information attached to the request.
  • In-app property reports require a signed-in account and may include the reporter account ID, reported listing ID, controlled report category, comments and supporting information voluntarily supplied by the reporter.
  • In-app seller reports also require a signed-in account and may include the reporter account ID, reported seller ID, a seller-name snapshot, controlled report category, comments, report status, review timestamps and related moderation records or admin notes.
  • When a signed-in user blocks or unblocks a seller, the service stores the blocker account ID, blocked seller ID and relevant timestamps so the preference can be applied and managed.
  • Visitors who are not logged in cannot use the in-app report APIs, but may still contact the Privacy/Grievance contact directly. Technical information such as IP address or device/browser details may be recorded for security, abuse prevention and investigation when a request reaches the Services.

2.4 Technical, usage and security information

  • IP address, device model, Android version, app version, browser or user-agent information where applicable.
  • Login dates, failed OTP attempts, API request logs, rate-limit records, authentication and fraud-prevention records.
  • FCM notification token and app/device installation identifiers used for authentication, notifications, analytics, security or service operation.
  • Searches, listing views, wishlist activity, post submissions and other app-usage events measured through analytics.
  • Crash and diagnostic information processed through Firebase Crashlytics, which may include crash stack traces, relevant app state at the time of a crash or non-fatal error, device/app metadata, timestamps, Crashlytics installation identifiers, Firebase Installation IDs and Firebase session identifiers. Where Google Analytics integration is enabled, diagnostic reports may also include breadcrumb information about app interactions leading up to a crash.
  • Technical information processed by Firebase, Google Maps, Google Places, Google Play services and other service providers needed to deliver their functions.

2.5 Information stored locally on the device

  • Login/access token, user ID and phone number needed to keep the user signed in.
  • Preferred district/block, language preference and wishlist information.
  • Scanned documents and GPS land-measurement data, as described below.

3. Information displayed publicly

Bhumir Sandhan is designed to allow interested users to contact listing users directly without requiring every visitor to create an account.

For an active listing, the following may be displayed publicly to logged-in and non-logged-in visitors:

  • Seller name and seller type.
  • Mandatory phone number.
  • WhatsApp number and email address only if the seller provides them.
  • Property description, price, area, photographs and other listing information.
  • Village/locality, mouza, block, district and the precise property pin shown on the map.

The Services may also provide a public seller-profile page showing limited public information such as the seller’s first and last name, member-since date, number of currently public listings and those public listings. Private account fields such as account email, mobile number, address, OTP information, deletion state, moderation notes or strikes are not intended to be exposed through the seller-profile endpoint merely because the profile is public.

Before publication, the seller must give separate affirmative consent through an unticked checkbox. Because public contact information and the property pin are core parts of an active direct-contact listing, withdrawing that consent will deactivate or remove the listing from public view.

Information displayed publicly may be copied, photographed, saved, indexed or misused by third parties. Bhumir Sandhan does not authorize such misuse and may act on reports, but cannot guarantee deletion of copies independently retained by third parties.

4. Location information

  • Property map pin: precise coordinates selected by the poster are saved with the listing and publicly displayed while the listing is active.
  • Property location fields: district, block, mouza, village/locality and property address or directions are used to display, search and manage listings.
  • Preferred area: the user’s preferred district/block is stored locally on the device and is not intended to be uploaded to the Bhumir Sandhan server.
  • Current-device location: precise or approximate location permission may be requested only when the user actively uses a map or measurement feature. Bhumir Sandhan does not request background-location permission and does not intentionally collect continuous background location.
  • A property pin is selected by the listing user and does not prove ownership, legal boundaries, road access, area or legal status.

5. On-device document scanner and GPS calculator

5.1 Document scanner

The document-scanner feature uses on-device/system document-scanning functionality. Scanned files are saved or handled on the user’s device and are not automatically uploaded to the Bhumir Sandhan backend merely because the scanner is used. If the user chooses to save or share a scanned file through another app or service, that action is controlled by the user and the receiving service’s own terms.

5.2 GPS land-area calculator

Boundary points and measurement calculations used by the GPS land-area calculator are intended to be processed on the device and are not uploaded to the Bhumir Sandhan backend merely by using the calculator. Google Play services, mapping providers or the device operating system may process technical information needed to provide location and map functions.

6. How we use information

We use information to:

  • Create and secure accounts and verify phone numbers through OTP.
  • Publish, search, display, deactivate and manage property listings.
  • Enable direct communication between interested users and listing users.
  • Send service notifications, including listing approval, rejection, reactivation, security and account updates.
  • Provide customer support and investigate reports, fraud, spam, fake listings or misuse.
  • Operate analytics to understand feature usage and improve app reliability and usability.
  • Use Firebase Crashlytics to detect, investigate and fix crashes, non-fatal errors, ANRs and related reliability problems.
  • Operate Firebase authentication, database/storage and related service functions used by the app.
  • Enforce the Terms, protect users and comply with lawful requests or legal obligations.

7. Analytics and third-party services

The launch version of the Services uses the following third-party service categories. These providers may process technical or service data according to their own terms and privacy practices:

Provider/categoryPurposeExamples of information processed
Firebase AnalyticsApp-usage measurement and product improvementApp interactions/events, app-instance or installation identifiers, device/app information and general usage information
Firebase CrashlyticsCrash, non-fatal error, ANR and reliability diagnosticsCrash stack traces, relevant application state, device/app metadata, timestamps, Crashlytics installation UUID, Firebase Installation ID, Firebase session identifier and, where Analytics integration is enabled, breadcrumb information about app interactions leading up to a crash. We do not intentionally attach phone numbers, email addresses, WhatsApp numbers, OTPs, full property addresses, precise property coordinates or other directly identifying listing/account data as Crashlytics custom keys, logs or user IDs.
Firebase Authentication, Realtime Database and StorageAuthentication and Firebase-backed app data, configuration or asset functionsAuthentication/session information, Firebase identifiers, IP/device information, and data or files used by the relevant Firebase-backed feature
Firebase Cloud MessagingService notificationsFCM token, installation/device information and notification-delivery information
Google Maps, Google Places and Google Play location servicesMaps, property-pin selection, place search and user-initiated location featuresMap/place requests, location context, search terms and technical information needed by those services
Google ML Kit document scanner / system scanning serviceOn-device document scanningDocument images and technical information needed to perform the scan, subject to the scanner/service implementation
Cloud hosting, database and property-image storage providersOperating the Bhumir Sandhan backend, database and property listingsAccount, listing, image, support, security and operational data needed to provide the Services
Authorized OTP/communications provider, including WhatsApp Business services where usedSending authentication or account-security messagesPhone number, message/OTP delivery information and related technical records

Bhumir Sandhan does not intentionally send a user’s phone number, email address, WhatsApp number, full property address or precise property coordinates to Firebase Analytics as custom analytics parameters. We also do not intentionally attach such information, OTPs or other directly identifying listing/account data to Crashlytics as custom keys, logs or user IDs.

Google/Firebase privacy and policy references

For more information about how Google and Firebase handle information in their services, please review the Google Privacy Policy and Firebase Privacy and Security information. Bhumir Sandhan is independently responsible for its own data practices and for accurately disclosing third-party SDK data handling. Google Play’s applicable transparency requirements are described in the Google Play User Data policy.

Future advertising services

Google AdMob and Meta Audience Network are not used to serve advertisements in the current launch version. Bhumir Sandhan may introduce advertising services later. Before doing so, we will update this Privacy Policy and implement any disclosures, consent choices and Play Console/Data Safety updates required for the advertising setup then in use.

8. How information is shared or disclosed

We may share or disclose information:

  • With the public and other users: only the public listing and seller-profile information described in the public-display section, subject to the applicable listing consent and visibility rules.
  • With service providers: Firebase/Google services, cloud hosting, database/storage, OTP/communications, mapping and other processors needed to operate the Services.
  • With authorized personnel: administrators, support personnel and developers who need access for operations, security, support, moderation or maintenance and are expected to protect confidentiality.
  • Reports and block relationships are not intended to be public. Report content may be reviewed by authorized moderation/support personnel and may be disclosed where reasonably necessary for investigation, response, legal compliance or protection of rights. A personal seller block is treated as the blocking user’s private preference rather than a public accusation.
  • For legal and safety reasons: where reasonably necessary to comply with law, court orders or authorized government requests, protect rights or safety, investigate fraud or enforce Platform rules.
  • During a lawful business reorganization or transfer of the Service, subject to applicable law and appropriate protection.

We do not sell personal data.

9. Data retention

  • Active accounts and listings: retained while needed to provide the account and listing service.
  • Deactivated listings: may remain privately available in the user’s account so the user can manage or reactivate them, until the user deletes them or the Platform removes them under its rules.
  • Ordinary account-deletion retention: under the Platform’s current fraud, dispute and investigation policy, listings and associated property media belonging to a deleted account may be moved into restricted private retention and kept for up to 180 days from account deletion, even where no specific complaint or legal hold applies. They are removed from public view and are not intended to remain available through normal public/app listing APIs.
  • Pending serious reports: relevant material connected with a serious unresolved property report or seller report may be preserved privately while the report remains New or Under Review. A pending report is not a finding of wrongdoing and does not automatically create a legal hold. When review closes, seller-report-only preservation may be released, returned to the ordinary account-deletion clock, or converted to the applicable moderation-retention period depending on the outcome.
  • Moderation and legal preservation: evidence connected with an actual moderation action may be retained for the configured moderation period, currently 180 days from the applicable decision/removal date. A valid court, police, government or other lawful preservation requirement may require a separate legal hold or longer retention.
  • Registration information and legally required preservation: information required to be retained under applicable intermediary or other law may be kept for up to 180 days after cancellation/withdrawal of registration. Content and associated records removed or disabled in connection with complaints, legal notices or lawful orders may also be preserved for up to 180 days for investigation, or longer where lawfully required.
  • Seller reports: moderation records may remain after account deletion where needed for moderation, audit, dispute handling or legal purposes. If the reporting user’s account is permanently deleted, the direct reporter-account link may be anonymized, while the moderation record remains. The original reported-seller identifier and a seller-name snapshot may remain where needed for moderation/legal lookup.
  • Seller blocks: personal blocker/blocked-seller relationships have no legal-retention purpose and are removed when either relevant account is permanently deleted.
  • Routine technical records: ordinary IP/API logs, OTP request and failed-attempt records, resolved support records and temporary diagnostics are kept only for as long as reasonably necessary for their operational, security or support purpose, or for a longer period where required for a security incident, fraud investigation, complaint, legal obligation or valid legal/investigation hold.
  • On-device data: scanned files, local preferences and measurement data remain on the device until the user deletes them, clears app data or uninstalls the app, subject to device behaviour.
  • Third parties: service providers may retain information under their own policies and legal obligations.

After the applicable period, personal data is deleted or anonymized where reasonably practicable unless continued retention is required by law or for a valid legal, security, fraud-prevention, moderation or dispute-related purpose.

10. Your choices and privacy rights

Depending on the feature and applicable law, users may:

  • Access and edit account information, including name, optional email and WhatsApp number.
  • Request correction or updating of inaccurate personal information.
  • Request a change of the registered phone number through the available verification process.
  • Edit listing information and add or correct permitted property-location fields where the app allows it. Some location fields may remain locked after publication where the Platform intentionally preserves the original administrative location selection.
  • Block or unblock a seller as a personal preference where that feature is available.
  • Deactivate a listing to stop its future public display, including seller contact details and the precise map pin.
  • Delete a listing or request account deletion.
  • Disable notifications through Android settings.
  • Withdraw consent where processing is based on consent, subject to the consequences explained at the time of withdrawal and any lawful retention requirements.
  • Contact us to request access, correction, updating, erasure or grievance redressal as available under applicable law.

A public listing cannot remain active without the required public-contact and map-pin consent because direct seller contact and location display are core features of the listing service.

11. Account deletion

Users can request account deletion through the in-app Delete Account option and through the Bhumir Sandhan website Account Deletion page.

Website deletion route: https://bhumirsandhan.in/account-deletion

After a valid account-deletion request, the account is closed for normal use, the user is signed out, and active or inactive listings, public seller/contact information, property photographs and map pins are removed from public view.

Account deletion does not necessarily mean that every associated record is destroyed immediately. Under the current Data Retention rules, ordinary listings and associated media may be kept in restricted private retention for up to 180 days from deletion for fraud, dispute and investigation purposes, and stronger report, moderation or legal-preservation reasons may require different or longer retention as described in Section 9.

Personal seller-block relationships are removed when either relevant account is permanently deleted. Seller-report moderation records may remain where needed for moderation, audit, dispute or legal purposes; if the reporting account is permanently deleted, its direct reporter-account link may be anonymized.

Other associated personal data is deleted or anonymized when no longer needed, subject to the limited retention described in the Data Retention section for security, fraud prevention, complaints, investigations, moderation, legal compliance or other lawful requirements.

The web deletion option is intended to let a user request deletion without needing to reinstall or regain access to the Android app.

12. Security

We use reasonable technical and organizational safeguards designed to protect information, including secure network transmission, access controls, authentication, rate limits, OTP-request controls, security logging, restricted administrative access and release-build hardening where applicable.

Uploaded property photographs may be resized, compressed or converted for storage and delivery. Image files can contain device-created technical metadata. Bhumir Sandhan does not intentionally display embedded photo metadata as public listing information; the public property pin is separately selected as part of the listing.

Users should not upload Aadhaar, PAN, deeds, khatian, mutation papers or other unnecessary sensitive documents as property photographs.

No internet service, device or storage system can be guaranteed to be completely secure. Users are responsible for protecting their devices, OTPs and account access.

13. Users under 18

Bhumir Sandhan is intended only for persons aged 18 or above. We do not collect a full date of birth merely to confirm age. Users are required to confirm that they are at least 18 and legally capable of using a property-listing service.

We do not knowingly create accounts for children. If we learn that a person under 18 has provided personal data or created an account, we may suspend the account and take reasonable steps to delete the information, subject to legal and safety requirements.

14. Processing outside India

Some cloud, Firebase/Google, mapping, communications or technical service providers may process or store information in India or other countries. Where information is processed outside India, that processing is subject to applicable law and the provider’s contractual and security safeguards.

15. Changes to this Privacy Policy

We may update this Privacy Policy when features, service providers, legal requirements or data practices change. The latest effective/update date will be shown at the top of the page.

Where legally required, or where a change materially affects a user’s choices or consent, we may provide an in-app notice or request fresh consent before the changed processing begins.

If advertising services such as Google AdMob or Meta Audience Network are introduced later, this policy will be updated to describe the then-current advertising data practices.

16. Language, questions and complaints

This policy is available in English and Bengali. If the two versions differ or are interpreted differently, the English version will control to the extent permitted by law.

For privacy questions, requests to access/correct/update/erase information, account deletion, or complaints:

Privacy and Grievance Contact: Suroj Pal

Email: support@bhumirsandhan.in

Location: Jhargram, West Bengal, India

Website: https://bhumirsandhan.in/