Privacy Policy

1. Who we are

Developer Connects is a discovery platform that helps people find the genuine official websites of real-estate developers. This policy applies to developerconnects.com and the Developer Connects product. Contact us at developerconnects02@gmail.com. Our registered legal entity and operating details are: [Legal entity name, registered office, and registration details to be confirmed]

2. What Developer Connects does

We maintain a directory of real-estate developers and review their official websites, approving each one as the developer's official website. Visitors can search and filter the directory and ask to connect with a developer. We also offer property assistance (see section 10A). We are not the developer of any project, and we are not a party to your agreement with a developer.

3. Information we collect

We only collect information that our actual, current features require. In practice, this is:

4. Information you provide directly

• Account information, when you sign in — provided by our authentication provider, Clerk. This may include your name, email address, and profile image, depending on how you signed in (e.g. email or a Google account).
• Profile information, entirely optional and field-by-field — things like city, budget range, property type interest, construction-stage preference, and preferred locations. See “Profile information” below for the full picture.
• Contact Us submissions — name, email, a reason category, and your message.
• Report Inaccurate Information submissions — the category of what's wrong, your description, and an optional email address.
• Newsletter subscription — just your email address.

5. Information collected automatically

When you use Developer Connects, we automatically record certain product-usage events:

• Searches you perform (the query text, and which Country/State/City filter, if any, was active)
• Which developer pages you view, and which official-website links you click
• Which search result you click, and its position in the results
• A coarse device type (mobile or desktop), derived from your browser's user-agent string
• An anonymous session identifier (see “Cookies” below) that lets us tell repeat activity within one browsing session apart from a brand-new visitor, without identifying you personally

If you are signed in, some of these events are also associated with your account, so that features like “Continue your research” and personalized search ranking can work. If you are not signed in, they are associated only with the anonymous session identifier above.

6. Authentication information

Sign-in is handled entirely by Clerk, our authentication provider — we never see or store your password. Clerk provides us your user ID and, where available, your name, email, and profile image.

7. Search and interaction data

Covered in “Information collected automatically” above — we're calling it out separately here because it's the category we use most for personalization and product improvement (see “Personalisation and recommendations” below).

8. Profile information

If you choose to fill in your profile, the fields currently available include things like name, phone, city, current locality, date of birth, gender, budget range, property type and configuration preferences, construction-stage preferences, purpose (self-use, investment, or just researching), preferred locations, family size, family income, and notification preferences. Every field is optional — nothing in your profile is required to keep using Developer Connects, and your profile is never shown to other users.

9. Developer/company information

We also hold information about real-estate developers themselves (company name, location and other business information). This is business information about companies, not personal information about you, and is described here only for completeness — see “How developer information is sourced” in our Terms of Service for detail.

10. Reports and contact submissions

Information you submit via Contact Us or Report Inaccurate Information is used to respond to you and to investigate/correct directory information. It is visible only to Developer Connects; reporter identity is never shown publicly.

10A. Property assistance enquiries

When you ask to connect with a developer through Developer Connects, we ask for your WhatsApp number or phone number so our property team can help with your property enquiry. The developer does not require this information through this flow; you are sharing it with Developer Connects.

• What we collect: your phone or WhatsApp number (stored in international format), your preferred contact method, your name if you give it, the developer you asked about, any requirement you tell us about (such as location, budget, configuration or timeline), and how you reached us (for example the page, referrer and campaign parameters).
• Why: to contact you about your enquiry through the method you chose, to keep a record of that enquiry, and to understand which of our pages and channels lead to genuine enquiries.
• Consent: we record when you gave it and the wording you agreed to. You can ask us to stop contacting you at any time.
• Remembering you on this browser: after you send a request we may set a cookie called dc_lead for 30 days so we can offer to continue with the number you shared earlier. It is httpOnly and signed, and contains only an internal reference to your enquiry record, an expiry and a signature — not your name, number or email. See our Cookie Policy.
• Erasure: you can ask us to erase your enquiry details by emailing developerconnects02@gmail.com. We then remove your name, phone number, email, location and any free text we recorded, and withdraw your consent record. We keep an anonymised record of the enquiry — for example its status, the developer it concerned, the structured parts of the requirement (such as budget range and configuration), how it reached us, any booking and a timeline of what happened and when — none of which identifies you. If you enquire again afterwards, you are treated as a new enquiry.
• Enquiry details are visible only to Developer Connects and are never shown publicly. We do not sell them.

11. Newsletter information

If you subscribe, we store your email address for that purpose. We do not currently send automated newsletter emails — when we do, every email will include a straightforward way to unsubscribe, and we will not send marketing email without an appropriate lawful basis.

12. Notifications

Signed-in users may receive in-product notifications (for example, a profile-completion tip). We store whether each notification has been read. You can control profile-completion notification preferences from your profile.

13. Cookies and similar technologies

We keep this deliberately minimal:

• Authentication cookies, set by Clerk, to keep you signed in. We don't control their exact names or contents — that's Clerk's infrastructure.
• An anonymous session cookie we set ourselves (necessary for the product to function — it lets zero-result searches and recently-viewed developers work), valid for up to a year, never used to identify you personally.
• Local browser storage for a small amount of non-essential state, such as whether you've already dismissed the sign-in prompt this browsing session, whether you have dismissed or used our “install the app” banner, and your cookie choice — never sent to our servers.
• Optional analytics cookies from Google Analytics, only if you choose “Accept” on our cookie banner. If you choose “Accept only essentials”, Google Analytics is not loaded and sets no cookies.

We do not use advertising or cross-site tracking cookies. See our Cookie Policy for full detail.

14. Why we use information

To operate the directory and search, to respond to your submissions, to keep your account and profile working, to improve search relevance and recommendations, to understand product usage and where our developer coverage has gaps, to maintain security, and to meet legal obligations.

15. Personalisation and recommendations

We use real product signals — like your recent searches, developer views, official-website clicks, selected filters, and any profile preferences you've provided — to make search results and recommendations more relevant to you. For example, if your profile city is set, developers in that city may be ranked slightly higher in your search results; you can always search anywhere regardless.

16. Search intelligence and analytics

We analyse search and interaction data in aggregate to understand what people are searching for, which searches return nothing useful, and which locations or developers are in demand. This helps us decide where to add developer coverage next. We do not publish or expose any individual user's search history.

If you choose “Accept” on our cookie banner, we also use Google Analytics to measure how the public site is used (for example pages viewed, approximate location and device type). We do not use it on our admin or account pages, and we do not enable Google's advertising features.

Whatever you choose on the cookie banner, we keep an anonymous count of what happens to our “install the app” banner: that it was shown, and whether it was used, postponed or dismissed, or the app was installed or opened. It carries no name, phone number or email, uses only our own anonymous session cookie, is stored in our own database, and is never sent to Google or any advertiser. We do not record it if your browser sends a Do Not Track or Global Privacy Control signal.

17. AI/ML and product improvement

Today, search ranking and recommendations use deterministic, rule-based logic driven by the real signals described above — not a trained machine-learning model. We are building the data foundation that could support a machine-learning-based ranking system in the future. If and when that changes, we will update this policy. We do not use AI to make decisions about you individually, and we do not claim any AI-driven profiling exists today beyond the straightforward, transparent ranking logic described above.

18. How we share information

We do not sell your personal information. We share information only with the service providers described below (to operate the product), when required by law, to protect rights and safety, or with your direction (for example, if you use a share button to send a developer's page to someone).

19. Third-party service providers

Developer Connects is built on a small number of infrastructure providers:

• Clerk — authentication and account/sign-in management.
• Neon — our PostgreSQL database provider, where product and account data is stored.
• Vercel — application hosting and deployment.
• Google Analytics — optional website analytics, used only if you choose “Accept” on our cookie banner. Google receives the usage data it collects, and may process it in countries outside your own.

Other than Google Analytics (optional, as described above), we do not currently use a third-party analytics platform, advertising network, or email-sending service — the analytics events described above are recorded in our own database, not sent to an outside analytics company.

20. International/cross-border data transfers

Developer Connects is intended to serve users in India and the UAE. Information may be processed in countries where we or our service providers operate infrastructure, which may be outside the country you're located in. We have not made — and do not make — a specific data-residency promise (for example, that all data stays physically within India or the UAE); where cross-border transfer occurs, we aim to rely on the service providers' own appropriate safeguards and applicable legal mechanisms.

21. Data retention

We keep information for as long as reasonably necessary to provide the service, maintain your account, support analytics and product improvement, meet legal obligations, and resolve disputes. We do not currently have fixed, published retention periods for every data category; retention depends on the purpose and applicable legal requirements. If you'd like a specific answer about a category of your own data, contact us.

22. Data security

We use reasonable technical and organisational measures appropriate to the information we hold — including relying on our infrastructure providers' own security practices. No system can be made 100% secure, and we cannot guarantee that information will never be accessed without authorization.

23. Your rights

Depending on applicable law, you may have rights to access the information we hold about you, correct inaccurate information, request deletion, withdraw consent where processing is based on consent, object to or restrict certain processing, and receive information about how your data is processed. Some of these rights are subject to conditions or exceptions under applicable law.

24. How to exercise your rights

Contact us at developerconnects02@gmail.com with your request. You can update most of your own profile information directly from your Profile page at any time. Account-level actions (like managing your sign-in details, or — where our authentication provider supports it — deleting your account) are available from the account menu; if you can't find a self-service option for something, contact us and we'll process it manually. We do not currently offer a fully automated, instant account-deletion button outside of what our authentication provider's own account management may provide.

25. Children's privacy

Developer Connects is not directed at children, and we do not knowingly collect personal information from children. If you believe a child has provided us with personal information, contact us and we'll take appropriate action.

26. Changes to this policy

We may update this policy as the product changes. The “Last updated” date at the top of this page always reflects the current version. Material changes will be reflected here.

27. Contact / privacy enquiries

Questions about this policy, or any privacy request, can be sent to developerconnects02@gmail.com.