Practical collection
We only need enough information to operate the site, improve the product, and protect the platform.
How BestProp.ai handles information when you browse the site or use its property research, GST and Bhoomi RTC integrations.
We only need enough information to operate the site, improve the product, and protect the platform.
This policy is meant to describe what data categories exist, why they are used, and where third parties may be involved.
You can limit cookies in your browser and choose which browser controls to enable.
This Privacy Policy applies to BestProp.ai and the websites, pages, and services we operate under that brand, including public property research, informational pages, and related digital experiences.
Degen Innovations Pvt Ltd operates the BestProp.ai integrations. You can contact the operator about support or privacy at [email protected].
This notice explains how information is handled. Permissions, consent choices and controls depend on the feature you use and, for assistant integrations, the settings provided by your assistant host.
We use a self-hosted Umami analytics service to measure website traffic. Its tracker does not use cookies and is configured to honour browser Do Not Track signals. Analytics may process technical request information, including network address, browser details, page path, and referrer, to report visits; we do not describe this processing as anonymous or as collecting no personal data.
Analytics is enabled only on configured production sites. We do not send form field values or search terms as custom analytics events. Other site functions may use browser storage or cookies where needed; you can control those through browser settings.
We keep information only for as long as it is reasonably needed for the purposes described in this policy, including security, legal, operational, and record-keeping requirements.
Retention periods can vary depending on the type of information, the purpose for which it was collected, and whether a legal or dispute-related hold applies.
We use reasonable technical and organisational measures to protect information against unauthorised access, misuse, loss, or disclosure. No internet transmission or storage system is perfectly secure, so absolute security cannot be guaranteed.
Our site may link to third-party websites, official portals, maps, social platforms, or documents. We do not control the privacy practices of those third parties, and you should review their policies independently.
Property and project information may also originate from public records, developers, intermediaries, or other third-party sources. Independent verification remains the user's responsibility before any financial commitment.
The site is intended for adults making or researching property decisions. We do not knowingly collect personal information from children in a manner requiring parental consent under applicable law.
We may update this Privacy Policy from time to time to reflect product changes, operational requirements, or legal developments. The updated version becomes effective when it is posted on this page unless a different effective date is stated.
When an assistant calls a BestProp.ai tool, it sends the tool name and selected arguments to the public API. Property-research arguments can include a search phrase, location or builder filters, report slugs, content type and pagination. Personal information in a search phrase is also sent; use public property descriptions instead of sensitive details.
GST requests can contain tax amounts, GSTINs, invoice and transaction details, mappings, and selected spreadsheet or portal-evidence files. The assistant host supplies the chosen structured inputs or file download references. The service processes those inputs to produce calculations or review workings. Only supply records needed for the task, and never supply government passwords, OTPs, digital-signature keys or payment credentials.
When you explicitly start an RTC reading, the selected PDF or image and task context are sent through BestProp.ai to its private OCR service. A record may contain names, land identifiers and other personal information. Only supply the record needed for your task and which you are authorised to process. The website waits for Read my RTC before uploading; an assistant host may already hold the attachment under its own policies.
The RTC reader uses temporary processing jobs. The current implementation applies a 15-minute absolute job lifetime, which polling does not extend; the workspace may also lose access after service restart. Original input bytes are released after extraction and cleanup, while normalized results remain until expiry or discard. Clear requests discard and extraction cleanup. If confirmation is unavailable, the interface must show that limitation; a request alone is not proof of completed cleanup. The reader does not maintain a permanent document library or account history. This describes the reader implementation and does not establish the retention practices of assistant hosts, proxies, hosting or security services.
Private job capabilities and extracted results are delivered in private workspace metadata rather than ordinary tool-message text. The assistant host controls its own processing and retention. Removing a plugin or clearing a reader job does not erase the host's original attachment, conversation or already downloaded exports.
Default exports omit original page text and redact record values. Including private details requires an explicit choice and preview. Review any export before saving or sharing it; original files are not embedded in the export. Existing privacy statements about network requests, service diagnostics and separate provider policies continue to apply. No fixed infrastructure log-retention period or instant/automatic deletion outcome is promised.
The public tools do not require a BestProp.ai login or consumer API key. GST tool processing does not write the supplied books or calculation inputs to a database. This describes the tool implementation; it is not a promise that assistant-provider, network or infrastructure logs retain no data.
The application's standard request-log callback records a generated request ID, operation, response status and elapsed time. That callback does not include raw search phrases, full tool arguments, IP addresses, authorization headers or chat transcripts. Proxy, hosting and security services can process network and diagnostic information separately; this callback does not establish their logging fields or retention periods.
On supported hosts, the research workspace shares selected public report identities and the open report as app context. Choosing Discuss asks the host to send a discussion message containing public report links. The host controls its conversation storage, context handling and retention. Removing a connection does not itself erase conversations held by the host.
Report images, linked sources and selected-file downloads involve requests to the relevant services. Those services receive the information needed to handle their requests and have their own data-handling policies. Review your assistant provider's privacy policy before sending private records or files.