Terms, Privacy & Grievance

Acceptance & eligibility

By creating an account or using BiddingPulse, you agree to these Terms. You must be at least 18 years old and capable of entering a binding contract under Indian law. If you're using BiddingPulse on behalf of a business, you confirm you have authority to bind that business.

Where the service is offered. BiddingPulse is intended for, and offered to, users located in India. The auctions and properties we research are within India, our pricing is denominated in Indian Rupees, our governing law is India and our exclusive jurisdiction is the courts at New Delhi (see Section 9). We do not market the service to, target, or knowingly monitor the behaviour of users outside India in any sense relevant to the General Data Protection Regulation (EU), the UK General Data Protection Regulation, the California Consumer Privacy Act, or any similar foreign privacy or consumer-protection law. We make no representation that the service complies with the laws of any jurisdiction other than India.

If you are accessing from outside India, you do so on your own initiative and at your own risk. You are responsible for compliance with any local law applicable to you. If your local law conflicts with these Terms or with how we operate, you must not use the service. We do not undertake any obligation to you under any foreign law, and any rights you may have under such law are not extended or implied by these Terms.

What BiddingPulse is — and isn't

BiddingPulse is an information and research platform. We aggregate publicly available auction data and host a moderated discussion forum.

BiddingPulse is not a real estate agent, promoter, listing service, or broker under Section 2(zm) or any other provision of the Real Estate (Regulation and Development) Act, 2016. We do not represent any party to any transaction, do not negotiate, do not list properties for sale, do not accept any advance, booking amount, earnest money or commission linked to any property transaction, and do not earn commission on any sale or transfer.

For qualifying third-party content in the discussion forum, BiddingPulse may rely on the conditional intermediary framework under Section 79 of the Information Technology Act, 2000. Any protection depends on satisfying the statutory requirements and applicable due-diligence obligations, including those in the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021. This framework does not cover BiddingPulse's own editorial research.

Access & pricing

Current access. The current auction bulletin, announcement pages, and public source-backed area briefs are free to read. A project’s full research view — exact reserves, EMD math, full source trails, and complete plot-level notes — requires a paid Insight unlock for that project, or Premium, which opens every current area and the concluded-auction archive.

Access tiers. Insight tier: ₹499 per project for 30 days, granting access to that project’s research. A new Insight unlock is sold while the project remains in current-auction research — including a scheduled-close record whose final status is still awaiting verification at the official source. An unlock remains valid for its full 30 days even if the auction is archived during that time; after expiry, archived research is available through Premium. Premium tier: ₹1,499 for 30 days — a one-time pass, no auto-renew — opening every current area and the full concluded-auction archive. Broker tier: a flat platform fee once broker flows open. Insight unlocks are not newly offered after an area moves into the archive; archived research requires Premium. "One auction" or research grouping means the source's own grouping where applicable.

Refund & cancellation. When paid unlocks are used, content is delivered immediately upon successful payment. As a voluntary policy, if you are not satisfied you may request a full refund of an Insight unlock within 24 hours of that unlock by submitting the refund form; on refund, your access to that unlocked project ends and the amount is returned to your original payment method — banks typically post it within 5–7 business days of processing. After the 24-hour window, the 30-day access period runs to its end date and refunds are available only where required by law — for example, where the service is not delivered, where there is a billing error, or where a statutory consumer right entitles you to one. As a further voluntary courtesy, you may also tell us if something went wrong after the window; we review such requests individually and may, at our discretion, issue a full or partial refund, though we are not obligated to do so. Premium payments have no self-serve window: we review Premium refund requests individually (write to support@biddingpulse.com), and if a refund is granted, Premium access ends when it is processed. Neither Insight nor Premium auto-renews — there is no recurring subscription to cancel; access simply lapses at the end of its window. We do not take a cut of any broker–buyer fee, and brokers (when broker tier opens) invoice buyers directly.

User conduct & prohibited content

You are responsible for the content you post. You will not host, display, upload, modify, publish, transmit, store, update or share any information that:

• belongs to another person and to which you do not have any right;
• is defamatory, obscene, pornographic, paedophilic, invasive of another's privacy (including bodily privacy), insulting or harassing on the basis of gender, libellous, racially or ethnically objectionable, relating or encouraging money laundering or gambling, or otherwise inconsistent with or contrary to the laws in force;
• is harmful to a child;
• infringes any patent, trademark, copyright or other proprietary rights;
• violates any law for the time being in force;
• deceives or misleads the addressee about the origin of the message, or knowingly and intentionally communicates any misinformation or information which is patently false and untrue or misleading in nature;
• impersonates another person;
• threatens the unity, integrity, defence, security or sovereignty of India, friendly relations with foreign States, or public order, or causes incitement to the commission of any cognisable offence, or prevents investigation of any offence, or is insulting to other nation;
• contains software viruses or any other computer code, file or program designed to interrupt, destroy or limit the functionality of any computer resource;
• is patently false and untrue, and is written or published in any form, with the intent to mislead or harass a person, entity or agency for financial gain or to cause any injury to any person.

You will not impersonate another person, scrape the platform at scale, or attempt to circumvent moderation. You will not use BiddingPulse to recruit users to off-platform services before the introduction flow completes. Repeated violations may result in content removal, account suspension or termination.

Broker conduct (when broker tier opens)

If you join BiddingPulse as a broker, you confirm that your RERA registration is current at intake and that you will keep it current. You agree to disclose, in writing within the BiddingPulse conversation thread, any commission interest you may have on non-auction listings you offer to BiddingPulse-introduced buyers. You agree to invoice buyers directly using your own legal name or registered firm name. BiddingPulse is not the merchant of record for any service you deliver and does not collect, hold, or refund any payment between brokers and buyers.

Content & moderation

User discussion posting is available where the discussion surface is live. Discussion posts, replies, reports, and edits are screened on submission. Clean items may publish after review, while blocked or borderline cases can move through the human-review appeal flow. We may remove, edit, hold for review, or label content that violates these Terms or our community guidelines. We act on actual knowledge of unlawful content within 3 hours of receipt of a court order or a reasoned written intimation from an authorised government officer, in accordance with Rule 3(1)(d) of the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021, as amended with effect from 20 February 2026 (G.S.R. 120(E), notified 10 February 2026). Voluntary moderation in good faith does not amount to editorial intervention.

You retain ownership of content you post. By posting, you grant BiddingPulse a non-exclusive, worldwide, royalty-free licence to display, distribute, and store the content within the platform, solely for the purpose of operating and improving the service. You can request your content be deleted at any time via the contact paths in the Grievance section below.

If you send us feedback, suggestions or corrections, including privately, you grant BiddingPulse a perpetual, irrevocable, non-exclusive, worldwide, royalty-free licence to use them to operate and improve the service, including publishing corrected information, without any obligation to pay or credit you. We are not required to act on or reply to ordinary product feedback. This permission does not authorise us to publish your private report, screenshots or personal information; our obligations under the Privacy Policy, Grievance mechanism and applicable law still apply.

If you believe content on the platform violates your rights, infringes copyright, or breaks the law, please raise it via the Grievance mechanism. We will acknowledge within 24 hours and resolve within 7 days — shorter statutory windows apply to specific complaint categories, set out in the Grievance section.

Disclaimers

BiddingPulse is provided "as is" and "as available." We do not vouch for the accuracy of any individual post, the quality of any broker's services, the truthfulness of broker self-declarations, or the outcome of any auction or transaction. Auction data is aggregated from public sources; layout depictions on the platform — including plot boundaries, corner markers, and edge lengths drawn over satellite or street-level imagery — are indicative only and are not surveyed cadastral drawings, and third-party imagery may predate current ground reality. Every figure should be independently verified on site and at the original source (the authority's portal or official tender — or, once bank-run auctions are covered, the bank's notice) before any decision.

We cover a selection of publicly announced auctions; we do not warrant that every auction is listed, that listings appear immediately after an authority announces them, or that live counts and dates shown are complete or current. The authority's own official source — its portal, notice board, or published notice — is the only complete record.

We do not provide investment, legal, financial, or tax advice. Nothing on the platform should be construed as a recommendation to bid, buy, or otherwise participate in any auction. We do not publish broker fees, ratings, testimonials, quality scores, or rankings.

Liability cap

To the maximum extent permitted by law, BiddingPulse's liability is limited to platform-level remedy: where a substantiated grievance is upheld, we may remove the offending content or broker from the platform. We are not liable for losses arising from broker conduct (fee disputes, service non-delivery, fraud, misrepresentation, transaction failures), nor for losses arising from your reliance on any post, research, guide, or auction data published on the platform, nor for any indirect, incidental, special, or consequential damages.

Aggregate monetary liability, where unavoidable, is capped at the fees you paid BiddingPulse in the twelve months preceding the claim, or ₹1,000 if no fees were paid.

Governing law & jurisdiction

BiddingPulse's decision on a reported issue is final at the platform level. Your independent legal remedies — including consumer fora under the Consumer Protection Act, 2019, the Real Estate Regulatory Authority for Delhi, the Data Protection Board of India, and law-enforcement agencies — remain available to you and are not affected by these Terms.

Modifications

We may update these Terms when our model, features, or regulatory environment change. We will publish the revised Terms here and update the "Last updated" date. Changes take effect when published, unless we state a later effective date or applicable law requires otherwise. For material changes, we will provide a prominent notice on the platform or notify you by email, as appropriate.

We will provide advance notice and obtain your agreement where required by applicable law before a change takes effect. Your continued use after the effective date constitutes acceptance of the revised Terms to the extent permitted by law. Any consent required for new or changed uses of personal data will be requested separately under our Privacy Policy.

Operating entity & contact

BiddingPulse is operated as a sole proprietorship based in New Delhi, India. Operating address: Sector 22, Rohini, New Delhi — 110086. Website: www.biddingpulse.com. Contact: founder@biddingpulse.com. Payment receipts are plain commercial invoices: BiddingPulse is currently below the GST-registration threshold, so no GST is charged and no GSTIN appears. The on-record PAN is disclosed on request in connection with a payment (write to founder@biddingpulse.com), and to regulators or law-enforcement agencies on a valid legal request.

For all general contact, support, broker onboarding, press, and grievance channels, see About. For formal grievance redressal under the IT Rules, 2021 and the Digital Personal Data Protection Act, 2023, see the Grievance section below.

What we cite (factual auction metadata)

Property identifiers, reserve prices, EMD amounts, areas, coordinates, contact officers, and bidding-schedule dates are drawn directly from publicly published source documents — government tender notices and their annexure listings issued by the relevant authority, and for bank auctions the banks’ own published sale notices and public listings on bankeauctions.com and the banks’ AuctionTiger sites. We state their reserve, EMD, dates and property facts in short descriptions with people’s names removed, and link the original sale notices rather than republishing them. Facts on the area-research and plot-research pages cite their specific source page and clause within the originating document; hub and guide summaries link the documents they draw on.

These are factual auction-listing details presented for research and reporting purposes; factual fields are not the subject of copyright (Eastern Book Company v. D.B. Modak, (2008) 1 SCC 1). Where a source is material published in an Official Gazette or another category listed in Section 52(1)(q) of the Copyright Act, 1957, that specific carve-out also applies. We link each claim to the official source document where it appears.

Where reasonably necessary to document, review, or report a public claim, BiddingPulse may preserve and display a limited, attributed extract or a single-page evidence capture. The page labels the issuing source and source page, links the official original, and does not present the capture as a live or current official record. We use such material only for the source-linked editorial context in which it appears, consistent with applicable fair-dealing principles for criticism, review, and reporting current events, including Section 52(1)(a) of the Copyright Act, 1957. The source owner retains all rights in the underlying document. BiddingPulse does not mirror or offer complete source documents for download and will review a substantiated correction, replacement, takedown, or rights-holder request through the contact channels.

Sale outcomes reported by news publications

Where a sale has concluded and an established publication of record has reported its outcome, the announcement page may republish the aggregate figures that publication printed — how many lots sold, what the sale raised, the reported highest and average rates. Three things are always true of that block. Every figure is attributed to the publication that printed it, named in the text and linked to the article with its publication date. Every figure is a fact — typically a number a public authority issued in a press release, or an officer stated on the record, which a newspaper then reported — and factual data of that kind is not the subject of copyright (Eastern Book Company v. D.B. Modak, (2008) 1 SCC 1). And nothing is inferred: a figure no publication printed does not appear, and where the publications differ we show what each printed rather than resolving it.

Where a short passage is quoted verbatim it is quoted as attribution — to show whose words established a figure, and whether the publication hedged it — with the publication named beside the quote and the article linked. These extracts are short, are used for reporting on and reviewing a matter of public administration, and are consistent with the fair-dealing principles in Section 52(1)(a) of the Copyright Act, 1957, including reporting of current events. The publications retain all rights in their articles. BiddingPulse does not reproduce articles, does not host their images or mastheads, and links out to every report rather than standing in for it. BiddingPulse publishes no outcome of its own and names no buyer or winning bidder. A publisher who considers a specific extract over-reaching can raise it through the contact channels and we will review it.

How we handle official layout & map geometry

Official layout drawings & map geometry. Where an auctioning authority publishes layout drawings, parcel or GIS polygons, or property-map data (for example, state GIS services such as KSRSAC/KGIS for BDA layouts), those works remain the property of the issuing authority. For some researched areas BiddingPulse derives simplified, indicative plot outlines from those official public sources, stores the derived geometry, and renders it as an orientation overlay with attribution to the issuing authority (for example, “plot boundaries from the official BDA map”). Derived overlays are for reference and research only, are not reproductions of the official document, and are removed or corrected on the issuing authority's request. For other areas a plot is shown as a point marker at the published source coordinate or as an in-house stylised orientation diagram.

Surveyed cadastral edges. We are not a licensed surveyor. Boundaries shown on this site are indicative only. For exact plot edges, use the issuing authority's official layout drawing — linked from each source on the relevant area-research page — and a site survey before any bidding decision.

Map tiles & third-party data

Satellite imagery on area and plot pages is served by Google Map Tiles and streams directly from Google with Google's own attribution: the Google logo in the map frame, and a credit naming the imagery providers in the current view (for example “Imagery ©2026 Airbus, Maxar Technologies”). We do not copy, cache, proxy or republish those tiles. By using the satellite view you agree to the then-current Google Maps/Google Earth Additional Terms of Service and Google's Privacy Policy, the same terms that apply to the Street view tab. The plot outlines, markers and edge lengths drawn over that imagery are BiddingPulse's own indicative overlay — not Google content, not a survey, and not a representation of legal title or extent.

Historical satellite captures on the Satellite history timeline come from Esri's World Imagery Wayback archive under our ArcGIS Location Platform subscription, and the latest frame is Esri's current World Imagery. They stream from Esri with Esri's own attribution: “Powered by Esri” and the imagery providers named in the frame. We do not copy, cache, proxy or republish those tiles, and nothing on the timeline is a measurement. By using it you agree to Esri's Master Agreement and Privacy Policy.

Infrastructure distances on area-research pages are straight-line approximations from public maps and official institution or transport pages (such as local transport, hospital, and education sources). They are not surveyed distances and are shown for orientation only.

Plot pages include Google Maps features and content (Street View street-level imagery and embedded mini-maps). By using those views you agree to be bound by the then-current Google Maps/Google Earth Additional Terms of Service and Google's Privacy Policy. We may suspend or terminate access to the Google Maps features — or to the platform account of a user who misuses them — where required to address violations of those terms. We do not copy, cache, or republish Google's imagery; it streams from Google with Google's own attribution, and the capture month shown is Google's metadata — imagery can predate current ground reality. The plot-boundary outline, corner markers, and edge lengths drawn over that imagery are BiddingPulse's own indicative overlay from our reviewed layout georeference — they are not Google content, not a survey, and not a representation of legal title or extent.

If you believe we've over-reached

If you are an authority whose records we cite, or any other entity holding rights in data we display, and you believe a specific element of BiddingPulse is outside the citation / fair-dealing boundary above, please follow the Grievance mechanism below. We will acknowledge within 24 hours and resolve the grievance within 7 days of receipt — where we accept the claim, the element is removed or replaced within that same 7-day window; where we believe in good faith we are within rights, we say so in the resolution. Shorter statutory windows apply to the expedited removal categories.

What we collect

We collect only what we need to operate the platform. Items below are itemised in the format Rule 3 of the DPDP Rules, 2025 will require when it commences on 13 May 2027 — we adopt it early, voluntarily.

• Account details you provide at sign-up: email address (required, immutable after verification), the display name shown on your posts, and an optional mobile number with country code. Sign-in is passwordless — a one-time email link or Google sign-in — so BiddingPulse never collects or stores a password for your account.
• Profile preferences you set on the Account page: research focus, budget band, preferred property kind, and preferred plot-size range. All of these are optional and editable at any time.
• Activity data generated as you use the platform: discussion threads, replies, edits, moderation appeals, project unlocks, and payment transactions processed by our payment provider where paid access is used. Voting is not enabled yet.
• Private product feedback you choose to send: your message, account identifier, page context, follow-up preference, and the screenshot and technical details shown in the form. See Private product feedback below for what is included and how to review it.
• Diagnostic and security data: page-view timestamps; a one-way HMAC hash of your IP address; a one-way HMAC hash of your user-agent string. We do not store your raw IP address or user-agent string; the hashes are used only to detect abuse and to satisfy audit-log integrity requirements.
• Aggregate analytics via Google Analytics 4, with strict PII filtering. Event payloads are scrubbed in code before they leave the browser to remove email addresses, phone numbers, raw IP, user IDs, and any personal-name fields. We do not transmit identifiable data to GA4.
• Behaviour analytics via Microsoft Clarity, when Session insights is enabled — on by default in India and other non-EU regions (you can switch it off at any time), and never offered or loaded in the EU/EEA/UK/Switzerland. Clarity records interaction data such as clicks, scroll position, viewport size, and session replay for product-improvement analysis. Sensitive forms, account controls, email, phone, password, discussion text fields, and the account avatar are masked before capture. For signed-in users, we may attach a one-way pseudonymous account key so a support or product issue for a known user can be found in Clarity without sending your name, email, phone, or raw account ID to Clarity.

Why we collect it (purpose)

• To operate the platform: authentication, session continuity, paid-access enforcement, payment receipts and refunds, content delivery, moderation queue management.
• To moderate content: automated screening on submission and on edit, human review of borderline cases, abuse and spam blocking.
• To comply with legal obligations — the IT Rules, 2021; the in-force data-protection regime (Section 43A of the IT Act, 2000 and the SPDI Rules, 2011) and, as it commences, the DPDP Act, 2023; valid law-enforcement requests; and audit-log retention for intermediary safe-harbor purposes.
• To improve the product: aggregated, anonymised analytics about which pages and features are used. We do not run cross-site behaviour profiling.
• To act on your feedback: investigate corrections, reproduce reported problems, assess feature requests, and contact you about your report when you allow follow-up.

We do not sell or rent your data to advertisers, brokers, or any third party. We do not use your data to train any third-party AI model.

Legal basis for processing

We process account, profile, and activity data on the basis of your consent, sought through a clear affirmative action at sign-up; you can withdraw it at any time using the contact paths in the Grievance section. Today that consent operates under India's in-force regime (Section 43A of the IT Act, 2000 and the SPDI Rules, 2011); it is designed to the standard of Section 6 of the DPDP Act, 2023. From 13 May 2027, we will continue to rely on consent and use a Section 7 certain legitimate use only where the facts fit one of that section's enumerated grounds — for example, a disclosure obligation under Indian law or compliance with a valid judgment or order. Fraud prevention, security, and audit-log integrity are purposes for which we use consent and comply with applicable legal obligations; they are not presented here as free-standing Section 7 grounds.

For private product feedback, the affirmative action is sending the form after reviewing what it includes. We use your message, technical details and any screenshot you choose to include to investigate and respond to that feedback. The screenshot and email follow-up choices start selected; you can clear either before sending. Follow-up is limited to that report, never marketing, and you can ask us to stop at any time. When Section 7(a) commences, we may rely on it for data you voluntarily provide for this stated purpose only where its conditions are met and you have not indicated that you do not want that use. See Private product feedback.

This Policy describes the rights available to you under Indian law. BiddingPulse is intended for users in India and is not offered to, marketed at, or used to monitor users outside India. On those facts, we operate on the basis that we are not a "controller" under the General Data Protection Regulation (EU) or UK GDPR, not a "business" under the California Consumer Privacy Act, and not within the scope of equivalent foreign privacy laws, and this Policy does not voluntarily extend the rights and remedies of those laws. That said, nothing in this Policy waives or limits any mandatory rights you hold under a privacy law that applies to you as a matter of law. If you are a resident of another jurisdiction and choose to access the service, the rights we administer are those provided by Indian law as described here.

What we share — and don't

What other users see: your display name and your public posts. Your phone number, email, and password are private. Phone and email become visible to a broker only if both you and that broker opt in via the share-contact flow (when broker tier opens).

Law-enforcement disclosure: we may disclose data on a valid legal request — court order, warrant, or summons under applicable Indian law, including the Bharatiya Nagarik Suraksha Sanhita, 2023. We do not volunteer disclosure outside that process and we challenge requests we consider overbroad.

Service providers and independent recipients (processors act on our instructions; independent recipients are separately identified below and handle data under their own terms):

• Supabase — managed PostgreSQL and authentication infrastructure. Hosts our application database. Bound by a data-processing agreement.
• Cloudflare (when private product feedback is enabled) — stores feedback messages, account identifiers, page context, technical details and our review history in D1, and screenshots in private R2 storage, to help us investigate and act on your feedback. Cloudflare processes this data on our instructions under its Data Processing Addendum. See Private product feedback below.
• Resend — transactional email delivery: verification and sign-in links, payment receipts and invoices, refund confirmations, and grievance acknowledgements.
• Vercel — application hosting/CDN, Vercel Web Analytics, and Vercel Speed Insights (aggregate, cookieless traffic and performance measurement) which run as part of Product analytics when that category is enabled.
• Google Analytics 4 (when enabled) — aggregate page and event analytics, with PII filtering applied client-side before any event leaves your browser.
• Google Maps Platform — satellite map tiles on area and plot pages, plus street-level imagery and embedded mini-maps on plot pages. Google is an independent recipient, not our processor: it handles this data as an independent controller under Google's Controller-Controller Data Protection Terms, and may use and retain IP addresses and latitude/longitude data to provide and improve its own products, as described in Google's Privacy Policy. Maps features load only when you open a map tab — the Satellite view tab, or the Street view tab, which is for members with research access to that plot. They never load on ordinary browsing, and nothing is requested from Google until you open one. At that point your browser talks to Google directly and Google receives your IP address, device information, and map-usage telemetry. We send Google the published coordinates of the area or plot to position the view — never your identity, account, or contact details.
• Esri — historical and current satellite imagery on the Satellite history timeline, under our ArcGIS Location Platform subscription. Esri is an independent recipient, not our processor: it handles this data under its own Master Agreement and Privacy Policy. The timeline loads only when you open it, and it is for members with research access to that plot or project; nothing is requested from Esri until then. At that point your browser talks to Esri directly and Esri receives your IP address and device information. We send Esri the published coordinates of the area or plot to position the view — never your identity, account, or contact details.
• Microsoft Clarity (when Session insights is enabled by your regional default or Privacy choices; never in the EU/EEA/UK/Switzerland) — heatmaps, scroll-depth analysis, dead-click/rage-click diagnostics, and session replay with sensitive content masked.
• Self-hosted local LLM runtime — large-language-model runtime used for AI moderation. Discussion text submitted for screening is processed within our own infrastructure unless a hosted provider is explicitly enabled for the workflow.
• Anthropic (planned, not yet active) — hosted AI provider for moderation review and research-content workflows where the self-hosted local model is insufficient. When this is enabled, only the specific text required for the task is sent; account identifiers, contact details, and unrelated fields are not.
• Razorpay — payment processor for one-time Insight (₹499) and Premium (₹1,499) payments under a redirect-only checkout (no auto-renewing subscription). We will not see, store, process, or transmit cardholder data; all payment-card data is handled inside Razorpay's PCI-DSS Level 1 environment.

Cross-border transfers

Cloudflare may store and process private feedback, screenshots and diagnostic details outside India. We request Asia-Pacific placement for D1 and R2; these location hints do not guarantee storage or processing in India. Cloudflare's Data Processing Addendum governs its handling of this data.

Some of our processors store and process data in jurisdictions outside India — typically the United States and the European Union — under the infrastructure provided by the providers above. From 13 May 2027, transfers will be subject to any restrictions notified under Section 16 of the DPDP Act, 2023 and to requirements specified by the Central Government under Rule 15 of the DPDP Rules, 2025 concerning making personal data available to a foreign State, or to a person or entity under that State's control. We also rely on contractual safeguards: data-processing agreements with each processor, and — for independent recipients such as Google Maps Platform — that provider's own controller terms and privacy commitments.

Cookies & tracking

We use first-party cookies for authentication and session continuity. These are strictly necessary for the platform to function and cannot be disabled. They are scoped to the BiddingPulse domain and use the SameSite=lax attribute to limit cross-site exposure. The short-lived verification cookie set during email-confirmation is HTTP-only and not readable by JavaScript on the page; authentication session cookies are set by our auth provider and are readable by the client SDK as required for the session-refresh flow.

Non-essential analytics fall into two categories you control: Product analytics — aggregate, anonymised usage measurement via Google Analytics 4, Vercel Analytics, and Vercel Speed Insights — and Session insights — masked session replays and heatmaps via Microsoft Clarity. The consent banner and preferences panel refer to these by category; the specific tools behind each are named here.

To understand how different groups use the product, we attach a coarse account-type label to this analytics and session-insight data — such as signed-out, free, a paid tier (insight, premium, or broker), or a restricted (banned) account. For signed-in users who have Session insights enabled, we may also attach a one-way pseudonymous account key to Microsoft Clarity so we can find a known user's replay during support or product debugging. We do not attach your name, email, phone, or raw account ID to GA4 or Clarity.

How they default depends on your region. In India and other regions outside the EU/EEA/UK/Switzerland, Product analytics and Session insights are on by default in a privacy-filtered form and you can switch either off at any time. In the EU/EEA/UK/Switzerland — and whenever your region cannot be determined — nothing loads until you explicitly accept, and Session insights (session replay) is not offered or loaded there at all; at most aggregate Product analytics runs after you opt in. You can review or change these choices any time through Privacy choices in the footer or under Account → Data & account requests. When you switch a category off, the app stops sending its events and attempts to clear the related first-party cookies (GA4 cookies for Product analytics, Clarity cookies for Session insights). We do not use cross-site advertising trackers, fingerprinting cookies, or behavioural-profiling cookies, and we do not track you across sites we don't operate.

Your rights

The DPDP Act's Data Principal rights (Sections 11–14) commence on 13 May 2027. We honour them today, voluntarily and ahead of that date:

• Right to access a summary of personal data we hold about you and the processing we do with it.
• Right to correction and erasure — to update inaccurate data and to have personal data erased once it is no longer required for the purpose it was collected, except where retention is required by law.
• Right to nominate another individual to exercise these rights on your behalf in the event of incapacity or death.
• Right of grievance — to raise a complaint with our Grievance Officer, and — once the DPDP complaint provisions commence and the Data Protection Board of India (established under Section 18 of the DPDP Act, 2023) is operational — to escalate to the Board after exhausting our internal grievance mechanism.
• Right to withdraw consent at any time, as easily as it was given. Withdrawing consent will stop processing for that purpose; some processing required for the platform to function (authentication, billing records, audit-log integrity) cannot continue without consent and you may need to close your account.

What you can change yourself today. Auction preferences (research focus, budget band, preferred property kind, preferred plot-size range) and your mobile number are editable directly on your Account page.

What still goes through us manually. Corrections to the name shown on your posts, email corrections, session management, account closure, and a copy of your data are handled manually. (Sign-in is passwordless, so there is no password to change.) Write to support@biddingpulse.com from the email address registered on your account, or use the Grievance path. Self-service controls for these items are on the roadmap.

Security

Sign-in is passwordless (one-time email links or Google), so there is no BiddingPulse password to store or leak. Network traffic is encrypted in transit. IP addresses and user-agent strings are hashed using HMAC before they enter our audit log; raw values are not retained. Database access is restricted to the application service; we do not run a query interface exposed to the open internet. In the event of a personal-data breach we commit to notifying affected users — and, once Rule 7 of the DPDP Rules, 2025 commences (13 May 2027) and the Board is operational, the Data Protection Board — within the Rule 7 timeframes.

Retention

For private product feedback, screenshots and technical diagnostics expire after 30 days; feedback text, page context, preferences and our review history expire after 180 days. Failed submissions expire no later than seven days after failure. Expired content is hidden from the feedback inbox while scheduled cleanup removes it. Account deletion queues feedback and screenshot erasure, with retries if storage is temporarily unavailable. A minimal deletion record may be kept for 90 days after cleanup completes. See Private product feedback below.

Account profile data is retained while your account is active. On account closure, account profile data is deleted within 30 days, except where retention is required by law (audit logs of moderation actions, grievance records, billing records). Posts and replies you have authored remain visible after account closure with the author label removed, unless you request specific posts be taken down. Aggregated, anonymised analytics that cannot be linked back to you may be retained longer for product-improvement purposes.

Children

BiddingPulse is not intended for, and not directed to, children under the age of 18. We do not knowingly collect personal data from anyone under 18. We do not run behavioural tracking, monitoring, or targeted advertising in respect of children. If you believe we have inadvertently collected data from a child, please write via the Grievance path and we will delete it.

Private product feedback

When you send feedback, we collect your message, topic, account identifier, the page path, title and record identifiers, selected search filters, any source link you provide, which control opened feedback, and your choice about follow-up contact. This helps us investigate corrections, reproduce problems and improve the product. Feedback is private to our team.

The form includes technical details and, by default, a screenshot of the product page. You can review both before sending, clear "Include screenshot" to send without the image, or cancel. Leaving the screenshot out does not remove the technical details. Only our website content is captured, never other tabs, browser controls or your desktop. Account controls and private entry forms are excluded. Screenshots can still contain information visible on the product page; please review the preview before submitting.

Please do not include passwords, bank or card details, or identity numbers such as Aadhaar or PAN in your message or screenshot. If you accidentally share these, contact support@biddingpulse.com with your feedback reference to request removal.

We capture only the visible area on phones, tablets, touchscreen laptops, small browser windows, and devices with limited or unknown memory capacity. This includes browsers such as Safari and Firefox that do not report the memory information needed for a full-page capture. On other supported devices, we may include the full page; if it exceeds our size or time limits, we use the saved visible-area screenshot. If capture fails altogether, the form lets you send your message without a screenshot.

Technical details include browser and operating-system names and versions, whether the browser is embedded in another app, viewport size and pixel density, theme, language, time zone, online status, page position, content and deployment versions, capture status, and recent error types, times, counts, code locations, failed-request status and opaque request identifiers. We do not include raw console or error text, request bodies, credentials, or raw user-agent strings. These details are sent with your feedback, not uploaded in the background. Sending feedback does not change your existing analytics or session-insight choices.

Cloudflare processes feedback records in a separate D1 database and screenshots in private R2 storage. Vercel hosts the submission service and Supabase verifies your account. As described in Cross-border transfers above, Cloudflare may process this data outside India. We do not make screenshots public or expose storage credentials to browsers.

Screenshots and diagnostics expire after 30 days. Feedback text, page context, preferences and our review history expire after 180 days; failed submissions expire no later than seven days after failure. Expired content is hidden from the feedback inbox while scheduled cleanup removes it. Account deletion also queues feedback erasure, including screenshots, with retries if storage is temporarily unavailable. A minimal deletion record may be retained for 90 days after cleanup completes to verify the deletion.

You can clear the email follow-up checkbox before sending. If you leave it selected, our team may contact your account email only about this feedback, never for marketing. You can ask us to stop follow-up at any time. We do not send automated acknowledgement or update emails. To request access to or erasure of your feedback, contact support@biddingpulse.com or use the Grievance channel.

Updates to this Policy

We will update this Policy when our processors, features, or the regulatory environment change. We will publish the revised Policy here and update the "Last updated" date. Changes take effect when published, unless we state a later effective date or applicable law requires otherwise. For material changes, we will provide a prominent notice on the platform or notify you by email, as appropriate.

We will provide any advance notice and obtain any consent required by applicable law before a change to how we process your personal data takes effect. Continued use of the platform does not replace that consent or change your existing privacy choices.

How to raise a grievance

The fastest channel is grievance@biddingpulse.com. Write from the email address registered on your account where possible. Please include:

• your registered display name and account email;
• the URL or thread/post identifier of the content concerned (if any), or the data-processing activity you are objecting to;
• a clear description of the issue and the outcome you are seeking;
• any evidence relevant to the complaint (screenshots, links, prior correspondence).

For broader contact channels — general questions, account support, press, broker onboarding — see About. Use grievance@biddingpulse.com for any formal complaint that requires the routes set out below.

Grievance Officer

Office: Grievance Officer, BiddingPulse.
Email: grievance@biddingpulse.com.
Operating address: Sector 22, Rohini, New Delhi — 110086.

The Grievance Officer is appointed under the IT (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021, and also acts as the point of contact under the Digital Personal Data Protection Act, 2023 for all data-protection grievances.

Acknowledgement & resolution timelines

Timelines follow the IT Rules, 2021 as amended with effect from 20 February 2026 (G.S.R. 120(E), notified 10 February 2026):

• Acknowledgement: within 24 hours of receipt of a grievance.
• Resolution for content, moderation, intermediary, or copyright complaints: within 7 days of receipt, in accordance with Rule 3(2)(a)(i) of the IT Rules, 2021. Resolution is complete disposal — for an accepted rights-holder data/IP removal request, the removal or replacement itself is done within the same 7-day window.
• Removal requests concerning content in the categories listed in Rule 3(1)(b) (other than sub-clauses (i), (iv) and (xi)) — for example obscene or privacy-invasive material, content harmful to children, misinformation, or impersonation: acted on as expeditiously as possible and resolved within 36 hours.
• Intimate imagery or impersonation in electronic form (including artificially morphed images): all reasonable and practicable measures to remove or disable access within 2 hours of the complaint, under Rule 3(2)(b).
• Resolution for data-protection grievances: within 30 days by default, and in any event no later than 90 days — our published commitment, ahead of the DPDP grievance regime's commencement.
• Action on a court order or a reasoned, authorised government intimation requiring removal of unlawful content under Rule 3(1)(d): within 3 hours of receipt.

Independent legal remedies

BiddingPulse's decision on a reported issue is final at the platform level. Your independent legal remedies are not affected by these Terms and remain available to you, including:

• consumer fora under the Consumer Protection Act, 2019, including the e-Daakhil online filing portal;
• the State Real Estate Regulatory Authority with jurisdiction over the property for any matter falling within RERA's remit (note that BiddingPulse is not a real estate agent or promoter under RERA; this remedy may apply to brokers introduced via the platform when broker tier opens);
• the Data Protection Board of India (established under Section 18 of the DPDP Act, 2023; its complaint jurisdiction commences with the DPDP regime) for data-protection complaints, after exhausting our internal grievance mechanism;
• law-enforcement agencies and the courts at New Delhi.