Privacy notice

Last updated: 21 October 2026

Who this notice covers

The Indian Agency RE, known on this website as The Indian Agency or TIARE, operates this property website and The Indian Agency CRM, its staff workspace for responding to enquiries, matching properties, arranging visits and recording follow-up. This notice explains the website and CRM data flows, including optional connected services. Contact us about privacy at inquiry@theindianagencyre.com. For questions about the agency's Google connection, you can also contact theindianagencyre@gmail.com.

Enquiries and property services

When you submit an enquiry, contact form or property listing request, we receive the information you provide. Depending on the form, this includes your name, email address, telephone number, message, selected property, enquiry subject or interest, and property location, type, size and additional listing details. We also record the form's source page and submission time. Please avoid including passwords, identity documents or unrelated sensitive information in free-text fields.

Enquiries are stored in the website administration system and copied into the agency CRM. Authorized staff use them to respond, understand your requirements and manage the property relationship. Staff may record requirements such as budget, preferred location and timing, property matches, communication history, visit arrangements, notes and the progress of an enquiry or transaction. The website and CRM also retain operational records used to manage access, source records, permissions and changes.

Submitting an enquiry does not turn on optional website analytics. A separate recorded channel permission is required by the CRM's outreach workflow; a form submission alone does not enable automated marketing.

Optional agency website activity

Agency analytics is off until you choose Allow analytics. You can decline and continue browsing or submitting enquiries. When allowed, the website assigns random visitor and session identifiers and records public page/property views, selected interactions such as property or contact-button clicks, approximate click positions, scroll depth, time spent on sections, device category and form start/submission activity. A referring website's hostname may be recorded. This supports website reports, journey views and click heatmaps.

The activity collector does not record typed form values, passwords, screen recordings, full query strings or URL fragments. It excludes private/admin pages and recognized website admin sessions. Enquiry form information is collected separately as described above. If you submit an enquiry while analytics is allowed, activity in that session may be linked to the enquiry in the CRM, so it is no longer treated as an unidentified journey.

Active agency activity records are subject to a 30-day retention window and storage limits that may remove older records sooner. The choice cookie lasts up to 30 days; a session cookie lasts 30 minutes and is renewed during eligible use. Local browser storage also helps keep privacy choices consistent across tabs. Your shortlist is stored in your browser until you change it or clear site storage; closing the enquiry prompt is remembered for the browser session.

Use Privacy choices → Withdraw analytics to stop collection. When the website confirms withdrawal, it removes the activity associated with the current visitor identifier and records the withdrawal so the CRM can remove its corresponding imported activity and automatic enquiry links when it next synchronizes. The CRM computer must be running and connected for that synchronization. Minimal withdrawal records are retained for up to 35 days to prevent reimport. This does not delete the enquiry itself, every backup, another browser's records, or data already received by Google. If your choice cannot be saved, the page asks you to retry; contact us if needed.

Optional Google Analytics

Google Analytics has a separate opt-in, available after agency analytics is allowed. Agency analytics consent by itself does not activate Google Analytics. When you allow it, the site loads Google's tag and sends public page-view measurements using the public page path and a sanitized page address. Google also receives the network and device information involved in requests to its service and uses analytics cookies.

Our adapter does not send form answers, names, contact details, CRM/enquiry identifiers, typed searches, URL query strings or fragments to Google Analytics. It is configured for manual page views, with Enhanced Measurement, Google signals and advertising personalization off. The current setup does not send lead conversions or create advertising audiences. Private/admin pages and recognized website admin sessions are excluded.

You can withdraw the Google choice in Privacy choices. Withdrawing agency analytics also stops this site's Google collection. Withdrawal stops future collection and clears the site's configured Google analytics cookies; it does not erase information Google has already received. The site's Google choice and configured cookies last up to 30 days. That is not Google's data-retention period: data held by Google follows the property's retention settings and Google's controls. See Google's privacy policy.

Agency Google connections

Google Calendar. An authorized agency operator can connect Google Calendar so staff can review and synchronize property visits with a dedicated The Indian Agency CRM calendar. The permission is limited to creating calendars and managing events on calendars created by the app (calendar.app.created). This adapter does not browse unrelated personal calendars or import unrelated events.

Linked events contain the visit date/time, property name, locality, a generic description and technical identifiers that connect the event to its CRM visit. A completed/no-show status can appear in the title. The CRM reads linked event times, status, text and version information to detect changes and conflicts. Synchronization is manually previewed and applied by an authorized operator. Contact names, phone numbers, emails, budgets, notes and visit feedback are not copied into these events, and the integration does not add attendees or send invitations. Events are created with private visibility.

Google Ads. An agency operator can separately authorize the Google Ads connection. It can identify accessible Ads accounts and, where the account permits access, read account settings, campaigns, budgets and reporting data for the CRM's advertising workspace. Reviewed campaign status/budget controls require a separate operator action. The currently selected account is not enabled for reporting. This authorization does not by itself upload website visitors, launch a campaign or authorize spending. Google Ads authorization is separate from Google Calendar and optional website Analytics.

Google authorization credentials are kept in protected server configuration. CRM storage retains connection identifiers and the records needed for synchronization and review. The agency account owner can revoke access through Google Account connections. Revocation stops future authorized access but does not itself delete existing CRM records or events in Google Calendar. Contact us to request removal of retained connection data or linked records.

Information received through Google Workspace APIs is used for the Calendar feature described here. It is not sold, used for advertising, or used to train general-purpose AI models. Our use and transfer of that information adheres to the Google API Services User Data Policy, including applicable Limited Use requirements.

Email, communications and optional AI assistance

Instantly. The agency has connected its sending mailbox to Instantly. Prospect and staff sending are currently paused. If sending is enabled, authorized staff must review the intended recipient, sender, purpose and message. The CRM can provide Instantly with the selected recipient's email/name and message content to send an individual message, and retrieve related message/reply content and delivery, bounce or unsubscribe information. Relevant records are retained in the CRM. The implemented workflow is limited to CRM-linked messages and campaigns; it is not a general import of all mailbox history. Connecting the mailbox does not grant permission to contact every CRM contact.

Optional AI drafts. When an authorized member of staff requests an external AI brief or draft, the CRM can send OpenAI the staff request and selected CRM evidence: contact name, requirements, budget range, preferred localities, stage, timing, score and suppression state; up to four property matches with pricing/availability evidence; and up to eight recent interaction titles, bodies and times. Free-text requests or interactions may themselves contain personal information. The response is an editable draft for human review; generation does not send a message or make a property decision. The CRM stores generated output, references and staff feedback. Provider processing and retention need to be considered separately from CRM retention.

Clicking an external WhatsApp, map or email link opens the chosen external service. Information you provide there is handled by that service and any subsequent agency conversation. The current CRM has no automatic WhatsApp or SMS sending connection.

Storage, service providers and your choices

Website records are held on the agency's hosted website infrastructure and relevant records are copied to its CRM computer. Access is restricted through staff authentication and roles. Backups, audit records and copies deliberately exported by staff can exist separately. Network requests necessarily expose request information to the receiving website or provider; the optional activity collector's field limits do not mean that hosting infrastructure receives no network information.

The services described above receive information needed for the feature you or an authorized agency operator use. Google Analytics runs only after its separate visitor choice. Calendar uses the agency's Google authorization; Instantly handles the connected mailbox and enabled email workflow; OpenAI receives selected evidence only when its external draft function is requested. These services have their own account controls and data-handling terms. Service processing can take place outside your location.

Website enquiries currently remain until staff remove them; there is no automatic enquiry-age deletion rule. CRM, correspondence, audit and backup records also have no single automatic deletion period. Requests involving those records require review of the ongoing property relationship, unresolved work, recorded permissions and any applicable recordkeeping requirements. The 30-day agency analytics window applies to that activity data, not to the whole customer relationship.

To ask about your information, request a copy or correction, request deletion, or ask us to stop a type of contact, email inquiry@theindianagencyre.com. We may need to establish your identity and the records involved. A reviewed request can require separate action in the website, CRM, providers and backups. We will explain the scope of the action and any records that need to remain; revoking a Google grant or declining analytics alone does not erase all other records. Please do not send passwords or identity documents in your initial request.