Chat with us

SmartLiveIn · Your information

Privacy & your choices

Understand what you share, how it is used, and the choices available to you. Browsing this site does not opt you into marketing or optional tracking.

Notice dated 2026-10-03 · Version 2026-10-03.1

Your privacy controls

Analytics: off until you choose. Optional marketing does not enable analytics.

Make or track a privacy request

Identity and scope

This notice explains information handling on smartlivein.com and the property, rental, sale, management, account and referral services reached through it. A feature described here applies when you choose that feature. Another organisation’s linked website is covered by its own notice.

Reading this notice, browsing or registering does not provide optional tracking, marketing or partner-sharing permission. Service terms, transaction agreements and individual consent choices have separate functions. Statutory privacy, consumer, regulatory and court remedies remain available.

Information and its sources

Accounts collect name, email, optional phone, role and authentication information. Passwords are stored as salted hashes; browser storage contains a session token, not your password. Verification workflows record challenges and results, separately from marketing choices.

Property workflows collect addresses and locality, unit and ownership or authorisation details, listing content, pricing, photos and service requirements. Buyer, tenant, owner, developer and channel-partner enquiries include contact details, budgets, preferences, referral references and relevant service history. Agreements and financial workflows use necessary transaction and accounting references.

General finance enquiries collect basic contact and requirement details. Calculators do not need identity records, credit reports or financial documents. Private agreements and supporting documents belong in the separate private-document workflow.

Enabled support, AI chat, voice and WhatsApp interactions can record messages, transcripts and requested actions. Information comes from you, authorised partners, public content and the use of the service. Self-declared or partner-provided statements are not automatically verified. Verification applies only to the specific fact checked.

Servers handle request and security metadata. Optional analytics measures permitted public-page visits and interactions. Visiting SmartLiveIn does not give us access to unrelated browsing history, address books, private messages or other accounts.

Purposes and processing basis

Account information supports authentication and your selected role. Property and requirement details support your requested listing, search, matching, enquiries, visits and property services. Agreement and transaction records support the particular transaction, reconciliation, accounting and legally required records. Support messages help answer and resolve your question.

Security information supports access control, abuse prevention, incident investigation and applicable legal duties. Optional analytics supports measurement and improvement. Personalised assistance uses the context you provide for that assistance. Promotional contact and independent partner referrals need distinct choices.

Where applicable law requires consent, we ask at collection. Information necessary for your requested service and legally required records are treated separately; this notice does not use a generic legitimate-interest claim to authorise every activity. Refusal may prevent the particular service that genuinely needs the information.

Consent and choices

Enquiry forms distinguish responding to your request from promotional contact and WhatsApp marketing. Optional choices start unchecked. Declining marketing does not block your enquiry. Analytics has its own preference. Silence and continued browsing are not permission.

You can withdraw through privacy requests without logging in or manage signed-in account preferences below. We verify the relevant account or enquiry proportionately. Queued messages and partner disclosures are checked against current permission. Our preference controls are internal tools, not a registered statutory Consent Manager.

Withdrawal stops activities dependent on that permission; it does not undo earlier authorised processing or remove genuine legal or ongoing-service requirements. We explain what cannot continue without the information. Existing consent records do not become permission for new purposes.

Public listings and interactions

Published descriptions, photos, features, prices and location information can be visible to visitors and search engines. Addresses, map coordinates, landmarks, faces and embedded contact details can disclose more than a locality. Review content before publishing and keep private documents out of public photos and descriptions.

Agreements and identity or ownership records use the private-document workflow. Access by property participants or partners depends on the relevant relationship and role. Review collection does not authorise automatic publication of the reviewer’s contact details.

Use a photo-removal request to identify an unintended document, contact, face or location disclosure and the affected listing. The team can review removal or a redacted replacement. Independent recipients and search-engine copies can take additional time to update.

Sharing and recipients

Authorised staff use information for the relevant service. Hosting, databases, file storage and activated communications, analytics or AI providers can process the information needed for their functions. Software containing an integration adapter does not establish that the vendor is currently receiving data.

Owners, developers, channel partners and lenders may be independent recipients. Referrals need a named recipient and a stated purpose; account creation does not authorise circulation to every builder or lender. The general finance form saves a SmartLiveIn CRM enquiry and does not automatically share it with a lender.

A valid legal requirement, specific incident or legal claim can require a limited disclosure. Restructuring does not create blanket authority to sell or repurpose information; any transfer needs a lawful basis, purpose limits and appropriate notice. This notice gives no permission for enquiry-data sales or unrelated affiliate marketing.

SmartLiveIn Money and home finance

The implemented home-finance page estimates EMI in your browser and captures an enquiry for SmartLiveIn follow-up. SmartLiveIn does not grant or approve a loan through this form. The calculator and general enquiry do not retrieve a credit report, submit a loan application or exchange lender status.

A future referral must first show the named partner, purpose, necessary shared fields and partner privacy notice, with a separate choice. Prefer direct secure document submission to that partner. Do not provide borrower documents, bank statements, credit reports, identity records, passwords or OTPs in ordinary enquiries or AI chat.

A separately enabled application workflow must explain any document handling and status exchange. Sanction and actual disbursal are distinct milestones; neither follows merely from an enquiry or referral.

AI and automated assistance

Rule-based matching and configured AI assist property search, conversations, descriptions and operational recommendations. Replies and matches can be incomplete or incorrect; they are not verified property facts, credit decisions, legal advice or guarantees. Ask the team for human help or submit a correction request.

Activated model providers can receive necessary prompts and selected conversation context. Routing depends on configuration; no zero-retention or no-training arrangement is asserted. Do not enter unnecessary personal information or sensitive documents. General-purpose AI must not be used for borrower documents, identity records, passwords or OTPs.

Voice requires your action and browser microphone permission. Browser or operating-system speech services can process speech under their own terms; SmartLiveIn can retain resulting transcripts and interaction records. Text and ordinary forms remain available if microphone access is refused.

Cookies and local storage

Essential browser storage supports your session, requested chat continuity and privacy choices. The web session store contains a token and account identifiers, not your password. Tab-scoped storage ends with the tab; local storage remains until cleared or replaced, subject to session validity.

Your analytics preference is kept in this browser for up to 180 days before we ask again. Optional first-party analytics stores a tab-scoped journey/session reference only after permission. Google Analytics runs only when configured and permitted. Its first-party cookies typically last up to two years, depending on property settings. No advertising pixel is part of the audited web implementation.

Reopen Cookie settings to accept or refuse analytics. Refusal preserves browsing, forms and account services. Withdrawal stops further optional collection and removes known Google Analytics cookies and first-party journey storage from this browser. New tracking purposes need a new choice.

Service and promotional communications

Responding to an enquiry or providing a necessary service message differs from promotions. Promotional contact and WhatsApp marketing have separate choices. The currently wired general notification provider is a local stub, not evidence of working email, SMS or WhatsApp delivery. External channels must meet their applicable requirements before activation.

Withdraw promotional permission through requests or signed-in preferences. Phone verification is not marketing opt-in. Opening WhatsApp involves Meta’s applicable terms; review any prefilled message before you send it.

Security and incidents

The implementation includes password hashing, role/resource checks, administrative MFA, private-document controls, expiring links, request limits and audit records. These measures are not an absolute guarantee or a statement that every item is encrypted in every environment.

Report suspected disclosure or misuse through the security-incident request type without sending secrets or copies of exposed documents. Investigation, authority reporting and affected-person notices follow the requirements applicable to the incident. Intake acknowledgement is not incident resolution.

Retention and deletion

Retention follows the relevant service and record requirement, not an indefinite rule for all communications. Account information is needed while the account or transactions remain active. Enquiries, support, documents, AI records and published content need review when their purposes end. Accounting, dispute and security records can need different periods.

Deletion requests cover CRM, accounts, property/documents, chat/voice, notifications, analytics, processors and backups. Unnecessary processing must stop; retained categories need a supported reason, restricted use and review. A category-specific legal hold is reviewed at its expiry and does not authorise unrelated marketing.

Completed privacy-request contact and free-text records are eligible for removal after the configured period, initially one year after completion, unless a supported hold applies. Minimal receipt, consent and audit evidence remains separately. Receipt is not confirmation of deletion: operational records require their owning workflow and evidence.

Backup copies may remain until their retention cycle ends rather than being rewritten instantly. Restored data must have outstanding withdrawal and deletion actions reapplied before optional processing. Instant removal from every backup or independent recipient is not promised.

International processing

Hosting, database, storage, browser speech and activated AI or analytics providers can involve different locations. There is no claim that all data stays in India. Sensitive-data transfers require the conditions applicable to the activity; sector-specific India-storage restrictions must be reviewed before activating finance workflows.

You can request recipient and processing information relevant to your service. A vendor in configuration or a deployment guide is not proof of its production region or contractual safeguards.

Children and authorised representatives

Property, account and finance services are intended for adults. Child information can still appear incidentally in family enquiries, photos or messages. Avoid children’s names, records and unnecessary dependent details. Use the child-data request type to seek review and minimisation.

Parents, guardians and authorised representatives can request help with proportionate verification of authority. No invasive identity upload is required merely to browse. Applicable child-consent and representative requirements depend on the law and feature; adult-service intent does not waive them.

Requests, grievances and escalation

The privacy request form works without an account for information, correction, withdrawal, erasure, grievances, nomination enquiries, photo removal, security and child-data concerns. Successful intake returns a receipt and private status code. Keep it confidential. An error or unavailable-service message is not an acknowledgement; no identity upload is required at intake.

Before revealing or changing personal records, the team verifies identity or authority proportionately, for example by an existing contact channel and enquiry reference. A status code alone does not prove ownership of an underlying account.

SPDI grievances, where applicable, have a one-month redress requirement. Intermediary complaints have separate acknowledgement, resolution and urgent-content periods. Core DPDP information, correction, erasure, grievance and nomination rights have staged commencement; accepting a request now does not claim all future statutory rights are already operative. Applicable deadlines are assessed for the request rather than replaced with one generic period.

This notice does not compel mediation/arbitration, appoint an arbitrator or impose exclusive Delhi jurisdiction. Statutory privacy, regulatory, consumer and court remedies remain available. Relevant escalation routes should accompany a grievance response.

Changes and previous versions

Each notice has a dated version and consent evidence records the version presented. Material changes should be communicated before a new activity starts. New purposes or recipients requiring permission need a fresh choice; updates do not retrospectively expand prior permission. Previous versions are preserved in the review archive and may be requested through privacy intake.

Make or track a privacy request ↗