Privacy

Your data, kept simpleand never sold.

A plain-language map of what this site collects, where it goes, the external services involved, and how to delete your enquiry.

Share only the information needed for your request. Do not send Aadhaar, bank details, payment credentials or identity documents through this website.

What you may submit

  • Quote, contact, product and exit forms: name, mobile, city, enquiry type/interest, optional email and free-text message; some forms also ask for monthly electricity bill. If you add products to the tab-scoped enquiry shortlist, their product names may be attached when you submit.
  • Partner application: name, mobile, PIN, city, district, state, selected route and optional message.
  • Assistant questions and bill/district estimates are processed in this tab and are not uploaded or saved. For a separate callback, name, mobile and city are sent only after you choose to request it and agree; the rest of the chat is not included.
  • The site calculators process bill, usage and location inputs in your browser. Estimate links do not put those values in a URL or enquiry; bill details go to SRG only if you enter them in a separate enquiry and submit with consent.

Free-text fields can contain anything you choose to type. Please do not enter government ID, bank, card, UPI, password or other sensitive credentials. This site does not ask for date of birth, payment-card details or a customer's account password.

Where enquiry data goes

After you submit a form, the same-origin SRG server stores the allowed fields, your consent choice, reference, enquiry type, source, page, submission time and selected product names when attached to an enquiry in a protected SQLite database. Authenticated staff may also create/import records and add status, priority, internal notes and a follow-up date; these can contain personal information staff chooses to enter. The admin workspace can read records only after server-side authentication. Public API responses contain only the new reference; the health endpoint does not report lead counts. New or changed administrator passwords use salted scrypt hashes; an existing salted PBKDF2 hash from an earlier build is upgraded to scrypt after the next successful sign-in. No password or hash is returned by an API.

Enquiry records are automatically deleted after 24 months. The app does not save visitor IP addresses or user-agent strings; values captured by an earlier build are scrubbed. Application logs contain only request method and a coarse route label, not IP, form contents, contact details, passwords or tokens. Your hosting provider or reverse proxy may maintain separate connection/security logs under its own terms.

Visitor names, contact details, PIN/location, bill amount and message are not written to browser localStorage. The cart and enquiry shortlist use tab-scoped session storage for product/variant selections, with temporary UI-dismissal timestamps; the public site copy/contact configuration may be cached locally because it is already published on the website. Production admin login uses a protected HttpOnly cookie. Only the isolated embedded preview uses a short-lived signed token and session marker in tab-scoped storage; neither is a password or visitor lead.

External services and exact transfers

  • Postal PIN lookup service: when you enter a 6-digit PIN in the partner form, your browser sends that PIN to api.postalpincode.in and receives post-office, city/block, district and state results. The provider also receives normal request metadata such as your IP address and browser user-agent; no name or mobile is included in this lookup. It is optional; you can enter location manually.
  • WaveSun Energy catalogue: the SRG server periodically requests public product listings from wavesunenergy.com/api/products with pagination parameters (limit and page) and a fixed service user-agent. No SRG lead or visitor form data is sent. Live catalogue images may load from Cloudinary; the image host receives the requested product-image URL and normal browser/network metadata.
  • Optional lead webhook: only if the site operator configures an HTTPS SRG_LEAD_WEBHOOK_URL, the server relays the reference, enquiry type, submission time, and provided name, mobile, optional email, city/district/state/PIN, interest and message. It does not send monthly bill, cart items, internal notes, IP address or user-agent. The configured endpoint's provider and retention are controlled by the operator.
  • WaveSun shop and checkout: clicking through opens the separate WaveSun store; a product link may identify the public product listing, but the SRG cart/shortlist and lead details are not transferred into the store cart. If you enter account, delivery/billing or payment information after leaving SRG, you provide it directly to WaveSun and its checkout/payment provider (including Razorpay if used). Those separate fields and retention are governed by their policies and were not audited here. SRG does not receive those payment credentials.
  • WhatsApp, phone, email and maps: links act only when clicked. Visitor-facing WhatsApp links address SRG and may prefill the city you entered or selected product names/variants. In the authenticated admin workspace, a staff member may open WhatsApp or the phone dialer using the lead's submitted mobile number; WhatsApp receives that destination number and a fixed follow-up message, and no message/call is sent until the person chooses to send or call. A staff member may open an email draft addressed to the submitted email; it is not sent automatically. Public enquiry forms have no file-attachment field; an authenticated admin-only JSON backup import is available. If you attach a file yourself in an external messaging app, it goes to the chosen service and recipient. Google Maps receives the public office-address query, not your device location. Referrer data is disabled by the app server and the supplied Apache configuration.

There are no analytics, advertising, session-replay, error-reporting, Supabase, Stripe or OAuth integrations in this app. External services still receive the normal network metadata required to answer a request (including requester IP and browser user-agent); the app does not attach lead-form fields except where described above. Government, manufacturer and contact links are user-initiated navigation, and their destinations apply their own privacy policies. The app server and supplied Apache configuration suppress referrer headers.

Request deletion

Enter a reference and the mobile number used for that enquiry. If they match, the server removes all enquiry records associated with that mobile number. The request itself is not stored. The confirmation is deliberately the same whether or not the details matched, to avoid exposing records. If you no longer have the reference, contact us using the details at the bottom of this page so we can verify your request.

This deletes active SRG database records. It cannot erase copies already downloaded by an administrator or data held by a third party after you choose to contact that service; contact those providers separately.

Anything unclear about your data?

Ask us directly — we will answer in plain language.

Call WhatsApp Free quote