Policies & your choices
Privacy Policy
How enquiry details, vendor registrations, subscriptions and support information are handled—and how you can make a privacy request.
This draft reflects SolarQuery’s confirmed service-platform model. The registered operator’s full legal name and address, grievance-officer details, launch date and operating arrangements must be completed and reviewed before publication.
The practical version
- Project information helps the team verify your request and identify relevant providers.
- Eligible providers receive contact details under the stated permission and subscription access rules.
- Technology providers may process information to operate the platform; optional tracking has separate controls.
- You can ask for a correction, withdrawal or deletion at support@solarquery.com.
1. Who this policy covers
This policy explains how SolarQuery handles information about visitors, people requesting solar services, service-provider representatives, subscription buyers, applicants and people who contact support. It covers information provided through the website and related calls, email, CRM workflows and messaging channels used for these purposes.
SolarQuery introduces customers to independent providers. It does not carry out installations, sell physical products or collect a customer’s payment for a provider’s project. A provider that receives your details and agrees work with you has its own responsibilities for the information it uses. Ask that provider for its privacy information where appropriate.
This is an India-oriented platform policy. Mandatory rights that apply to a person in another country are not removed by this policy. Country-specific disclosures and operating arrangements require review before those markets are launched.
2. Operator and privacy contact
SolarQuery is the name of the platform described in this policy. Contact us at support@solarquery.com, +91 98179 97081 (India) or +1 415 484 0053 (USA). A support number does not establish a local office.
- Registered operator’s full legal name
- To be confirmed before publication
- Registered / principal business address
- To be confirmed before publication
- Grievance officer: name and designation
- To be confirmed before publication
- Grievance officer’s postal and direct contact details
- To be confirmed before publication
- Current support and policy enquiries
- support@solarquery.com
- Policy effective date
- To be set on approval and launch
3. Information we collect
We collect information that helps us understand a request, operate the platform or assess a business or job application. The exact fields depend on what you choose to do.
- Customer enquiry: name, email, phone number including country code, country of the project, postal code or locality, requested services, project setting and the description you provide.
- Verification and project brief: contact-verification results, a record of the team’s call or correspondence, property or site context, existing-system information, approximate energy use, timing, budget information if you choose to share it, and any other relevant answers collected during the conversation.
- Consent and case history: the notice or permission you accepted, its version, time and method; relevant provider-sharing and access records; corrections, withdrawal requests and support history.
- Vendor registration: business and representative names, contact details, service categories, working areas, website if supplied, registration status and information needed to understand the business. Further onboarding documentation should be requested only when necessary and through an appropriate channel.
- Subscription administration: the chosen plan, its validity and entitlements, invoices, transaction references, payment status and access history. Payment credentials are handled through the payment service used at checkout; do not send card numbers, CVV, banking passwords or payment OTPs to support.
- Website information: essential session data, security and error logs and, when the relevant tools are enabled and your choices permit, visit, campaign, device and advertising-measurement information.
- Job applications: contact details, CV or work-history information, the role applied for, relevant communications and recruitment notes.
Please do not put identity numbers, financial account credentials, medical records or unrelated information about other people into an enquiry. If documents are needed later, the team should explain why and provide a suitable route. A call note is different from a recording: any call recording would require a separate notice and any permission required by applicable law.
4. Why we use the information
- To respond to your enquiry and confirm that we can contact you.
- To clarify the project and identify service providers relevant to the requested work and location.
- To manage vendor onboarding, subscription entitlements, billing and authorised lead access.
- To send necessary updates about a request, account, subscription or support case.
- To assess applications for the roles that are open.
- To investigate errors, misuse, security issues and complaints and meet applicable record-keeping obligations.
- To understand demand and improve the platform using appropriately limited data and aggregated analysis.
- To send optional promotional messages or use optional measurement tools only in line with the relevant choice.
A service request does not automatically subscribe you to marketing. Accepting a subscription is not permission for unrestricted use of customer data. We do not use an enquiry to authorise unrelated advertising by vendors.
5. How customer leads reach providers
Customer submits a request
The initial details come to the SolarQuery team through the configured platform workflow. Operational notifications may be handled through email or business messaging.
The team confirms the project
A team member contacts the customer, gathers relevant additional details and confirms the purpose of any provider introduction.
Providers are identified
The service and working area guide provider selection. A limited brief can be made available without the customer’s name, phone, email or precise address.
Authorised details become available
A relevant provider with the required subscription entitlement can access the confirmed lead details under the customer permission and platform access rules. More than one provider may be considered; a lead is not necessarily exclusive.
We are currently onboarding vendors and have no registered businesses on the platform. Where no suitable provider exists, we may seek one manually. We should first approach a prospective provider with a limited, non-identifying description. Identifiable details must only be shared after confirming relevance, applicable access arrangements and the customer’s permission. An availability-update request alone is not permission to circulate contact details.
Relevant details may include the customer’s contact information and the project information needed to discuss the requested work. We do not make contact details a public directory. Vendors must use the data for the enquiry, protect it, respect no-contact requests and refrain from reselling it or adding it to unrelated marketing lists.
6. Other recipients and technology services
Running the platform involves technology providers as well as solar vendors. The statement that leads are shared with relevant vendors does not mean no technology company processes data. We expect to use the following types of services as they are configured:
- CRM and hosting services to hold and manage authorised enquiry, vendor and support records.
- Email, phone-verification and WhatsApp services to deliver relevant operational communications.
- Payment gateways to process vendor subscription payments and report transaction status.
- Google Analytics for optional website measurement and Meta Pixel for optional advertising measurement.
- Professional advisers, auditors or authorities where a lawful and necessary disclosure applies.
These providers receive information appropriate to their role. Some act on our instructions; some, such as communications or payment platforms, may also process information under their own notices. We do not promise that these tools receive no personal data. The actual provider names, operating locations and configurations must be recorded before activation.
Lead details are not offered for unrelated resale or advertising. Disclosure may nevertheless be required to comply with a lawful request, investigate abuse, protect legal rights or manage a genuine business transfer with appropriate safeguards and notice. Such circumstances are different from selling an enquiry list.
8. Calls, messages and optional marketing
We may contact you about verification, project clarification, provider availability, registration, billing or support using the details you supplied. If WhatsApp is used, the communication should be relevant to that purpose and follow the required messaging permissions. You can request email or another reasonable contact route.
Optional promotional messages need their own choice. You can withdraw it using the unsubscribe mechanism in a message or by emailing support. Stopping promotions does not automatically stop a necessary billing notice or a response to an active enquiry. A provider must not treat a project introduction as consent to its unrelated marketing.
9. How long we keep information
We retain identifiable records for the purpose that justified collecting them, for handling relevant disputes and for legally required records. “For analysis” is not a reason to retain identifiable customer details forever. Wherever practical, long-term reporting should use aggregated or irreversibly de-identified data.
| Record | What determines retention |
|---|---|
| Customer enquiries and verification notes | The active request, a documented follow-up period and any unresolved complaint or lawful hold. |
| Vendor profiles and access history | The business relationship, subscription administration, misuse investigations and required evidence of access. |
| Invoices and payment references | Applicable accounting, tax, payment and dispute obligations. |
| Applications | The recruitment process and a defined review period; retaining a CV for future roles should be separately explained. |
| Security and diagnostic records | Documented security purposes and applicable retention requirements. |
| Analytics and advertising records | The chosen provider settings, consent status and the minimum period needed for the stated measurement. |
Exact periods for server-held records have not yet been finalised. They must be documented, reviewed and reflected in the live notice before collection begins. Deletion requests are assessed against these purposes and legal obligations. Backups may expire through a controlled cycle; data under a necessary legal hold must be isolated from ordinary use.
10. Your choices and privacy requests
Email support@solarquery.com with “Privacy request” in the subject. You can ask to see or correct information you supplied, withdraw consent, stop future provider sharing, stop optional marketing or request deletion. Give the enquiry or account reference if you have one and enough detail to locate the record.
We may need proportionate verification to avoid disclosing or changing someone else’s information. We should not request excessive identity material for a routine correction. Where we cannot fulfil a request in full, we will explain the relevant reason and any information that must be retained.
Withdrawal can limit our ability to continue an introduction. It does not undo a disclosure already made lawfully. We can stop new sharing and notify relevant recipients as appropriate, but an independent provider may need to handle its own records and legal obligations. We can help identify the relevant provider contact.
The Digital Personal Data Protection Act, 2023 and the 2025 Rules have phased commencement. Statutory access, correction, erasure, grievance and nomination mechanisms apply as the relevant provisions become operative and where the Act applies. This draft does not claim every provision is already in force.
11. Security and overseas processing
The live platform should use appropriate access controls, limited staff permissions, protected communications, subscription-entitlement checks, audit records and secure handling of credentials. Payment and identity information should not be copied into ordinary support messages. The downloaded HTML is an interface; it does not itself establish server security or data-processing controls.
No online system can be described as completely risk-free. If an incident affects personal information, the response must include containment, investigation and any notifications required under the law then applicable. Report a suspected disclosure or misuse to support without including sensitive data in the first message.
A vendor may be in the customer’s project country, while CRM, hosting or communications services may process information elsewhere. Cross-border use must follow applicable restrictions and contractual safeguards. We do not promise that all data stays in India; actual processor locations must be assessed before launch.
12. Applicants and children
Applications are used to assess suitability for the advertised role and communicate about recruitment. Only people involved in that process and relevant service providers should access them. Sending an application does not mean your CV can be circulated to solar vendors. If the team wants to retain it for a future vacancy, it should explain the additional purpose and retention period.
The platform’s enquiry, registration and subscription services are intended for adults who can act for themselves or their business. Do not submit a child’s personal information. If we learn that information was submitted by or about a child without an appropriate basis, we will restrict the record and consider deletion or other action required by law.
13. Complaints, legal framework and updates
Contact support first so we can identify the issue and route it to the responsible person. The final grievance-officer details must be published in the operator section above. This draft proposes acknowledgement of platform complaints within 48 hours and resolution within one month, subject to any stricter applicable requirement. The team must put that process into operation before publishing the commitment.
The Indian legal review should cover the Information Technology Act, 2000 and applicable rules, the Consumer Protection Act, 2019 and e-commerce rules where applicable, and the phased Digital Personal Data Protection framework. Rights to approach a competent authority remain available; this policy does not require you to waive them.
We will update the notice when the service, processing arrangements or legal requirements change. The final page should display its effective date. Material changes to a purpose or sharing arrangement may require a fresh notice or permission rather than relying only on an updated webpage.