1Information We Process
Account and employee information
We process information associated with your authorized account, including:
- Name, email address, and mobile number.
- Profile photograph.
- User and employee identifiers.
- Department, designation, role, and reporting manager.
- Account status and access permissions.
- Login credentials, verification codes, and session information needed for authentication.
Account access and organization-assigned details are managed according to your organization’s permissions.
Customer and lead information
Authorized users can enter and manage customer and lead information, including:
- Names and contact details.
- Addresses and customer enquiries.
- Project and property preferences.
- Lead sources and broker details.
- Follow-up notes, appointments, and activity records.
- Information relevant to site visits and bookings.
Users must have the appropriate authority and any required permission before submitting another person’s information.
Booking and transaction records
Booking records can include:
- Customer names, date of birth, address, and family-related information.
- PAN, Aadhaar, and supporting identification details where submitted.
- Occupation, company, and designation.
- Project, site, property, and unit details.
- Property value, rates, booking amounts, and payment schedules.
- Loan requirements and related information.
- Purchase purpose, declarations, remarks, and broker information.
These details are processed to prepare, manage, and maintain the relevant business records.
Documents, photographs, and signatures
We process photographs, PDFs, and other supported files that users choose to capture or select.
This includes booking forms, supporting documents, profile photographs, and buyer, co-applicant, or authorized signatory signature images.
Signature images are used as part of the relevant business document or booking record. The Application’s signature-image features are not biometric identity recognition.
Location and visit information
Location-related features process information such as:
- Latitude and longitude.
- GPS accuracy and reading time.
- Distance from a project or site.
- Whether the device is within the permitted check-in area.
- Visit verification and completion details.
Device and service information
The Application and its integrated services process technical information needed to operate, authenticate, and deliver notifications. This includes device model or name, platform, account and session identifiers, notification registration tokens, and Firebase installation identifiers.
Network requests also disclose an IP address and connection information to the server or service receiving the request.
2How We Use Information
We use information to:
- Authenticate authorized users and manage account sessions.
- Display profiles and organization-assigned access.
- Manage leads, customer enquiries, and follow-ups.
- Schedule and manage site visits.
- Calculate site proximity and verify visit check-in eligibility.
- Display project and unit inventory.
- Prepare and maintain booking records and payment schedules.
- Extract information from selected booking documents.
- Attach and display submitted signature images.
- Deliver account-related and operational notifications.
- Save supported application preferences.
- Respond to support and privacy requests.
- Protect accounts and reduce unauthorized or fraudulent activity.
- Maintain records required for business, contractual, and legal purposes.
3Location Access and Verification
The Application accesses precise location while you use location-enabled screens or initiate features such as proximity checking and site visit verification.
Location is used to calculate distance from an assigned site and determine whether check-in requirements are met. Relevant location and verification information can be submitted to the business server and associated with your visit record.
The Android Application does not request background location permission or provide continuous background location tracking.
During verification, the Application checks the reliability of the location reading, including accuracy, freshness, and indicators of mock location. The Android release also checks certain developer and debugging settings to protect the verification process.
You can revoke location permission in device settings. Features requiring verified precise location will then be unavailable.
4Camera, Photos, Files, and Document Extraction
Camera access is used when you choose to photograph a document or other supported content.
The Application uses device selection tools to access the images and files you select. It does not request unrestricted access to your entire photo library for these features.
Booking document text recognition uses Google ML Kit on the device. Recognized information can be reviewed and corrected before it is submitted with the booking. Selected signature areas can also be captured or replaced with a user-selected image.
Although text recognition runs locally, information and signature images included in a submitted booking are transmitted to the business server. Local OCR does not mean that submitted booking information remains only on the device.
Google states that ML Kit processes recognition inputs on-device and can transmit operational and usage metrics to Google. See ML Kit Terms and Privacy.
5Login and Remember Me
The Application supports the authentication methods enabled for your account, including password or verification-code login.
When Remember me is selected, authentication tokens are saved using the device’s protected credential storage so your session can be restored. The mobile Application does not save your password through this feature.
Signing out clears the locally maintained authentication session. Signing out does not delete customer, visit, booking, or other records already stored on the business server.
6Notifications and Third-Party Services
Firebase Cloud Messaging
We use Google Firebase Cloud Messaging to deliver operational notifications.
A notification registration token and platform information can be associated with your authenticated account so notifications reach the appropriate installation. Firebase also processes installation identifiers and service information necessary to operate messaging.
Notifications are displayed using the device’s notification facilities and the Notifee integration. You can manage available notification preferences in the Application and device settings.
Google’s processing is described in Privacy and Security in Firebase.
OpenStreetMap
Map screens load map tiles from OpenStreetMap infrastructure. These requests disclose your IP address and requested map area to the map service.
Customer documents, booking forms, and signature images are not included in those map tile requests.
See the OpenStreetMap Foundation Privacy Policy.
External calling and messaging services
When you choose a calling or WhatsApp action, the Application opens the relevant external service with the selected contact information. That service’s own privacy practices apply.
The Application does not request access to your device’s contacts, call history, SMS messages, or microphone for these actions.
Third-party infrastructure can process service information outside your country, according to the provider’s infrastructure and applicable terms.
8Storage and Security
Submitted business records are stored in the systems used to operate the service. Documents and images can also be temporarily stored in the Application’s private storage or cache for processing and preview.
The Application uses authenticated requests for restricted business features and protected device credential storage for saved authentication tokens. Its private-document download flow includes restrictions intended to prevent credentials from being sent to unrelated destinations.
Temporary processing files are subject to application cleanup and operating-system cache management. Clearing local files does not delete records already submitted to the server.
No application or storage system can guarantee absolute security. Users should protect their devices, keep account credentials confidential, and promptly report suspected unauthorized access.
9Data Retention
We retain information according to its purpose and the requirements associated with the relevant account or business record.
- Account information is retained while needed to provide and administer authorized access.
- Customer, booking, payment, document, and signature records are retained while needed to manage the transaction, maintain business records, address disputes, or meet applicable obligations.
- Visit and location-verification records are retained while needed for visit management, accountability, and related business requirements.
- Technical and security information is retained while needed to operate and protect the service.
- Temporary local files are managed through application cleanup and device storage controls.
A deletion request is assessed against these purposes. Where information must be retained, we explain the reason and the applicable retention criteria in our response.
10Privacy Requests and Data Deletion
The Application does not currently provide an in-app option to delete your account or data. Account and data deletion requests are handled by the Administrator/Support team by email.
To request access to, correction of, or deletion of your personal information, or to delete your account, email us at support@technodha.com.
For an account or data-deletion request:
- Send the email to support@technodha.com with the subject “MD Realty Agent — Account/Data Deletion Request.”
- Provide your registered email address or mobile number and identify the information concerned.
- Do not send your password, OTP, or unnecessary identification documents.
- We may request reasonable verification before processing the request.
For organization-managed accounts, the relevant administrator may need to assist in identifying account permissions and associated business records.
Account access being disabled does not itself mean that associated personal information has been deleted. Our response will explain the action taken and any records that must be retained for business, contractual, or legal purposes.
Uninstalling the Application removes the installed application from your device; it does not automatically delete server records.
11Permissions and Your Choices
You can manage camera, location, and notification permissions through device settings. Selected-file access is controlled through the device’s file and photo selection tools.
Denying a permission can prevent the associated feature from working. Revoking permission stops future access controlled by that permission but does not automatically erase previously submitted information.
You can update supported profile fields and application preferences through the available screens. Organization-assigned fields and access permissions are managed by authorized administrators.
12Children’s Privacy
MD Realty Agent is a business application intended for authorized adult personnel. It is not designed for children.
If you believe that a child’s information has been submitted improperly, contact us so the matter can be reviewed and appropriate action taken.
13Changes to This Policy
We may update this policy when application features, service providers, data practices, or applicable obligations change.
The revised policy will show an updated date. Where required, we will provide additional notice or obtain consent before implementing the relevant change.
14Contact Us
For privacy questions, complaints, account requests, or data-deletion requests, contact support@technodha.com or the Privacy Contact Email below:
- Operating Organization / Legal Name
- Technodha Innovations Pvt. Ltd.
- Application
- MD Realty Agent / MD Agent
- Support Email
- support@technodha.com
- Privacy Contact Email
- technodhainnovations@gmail.com
- Website
- https://www.technodha.com/
