Privacy
What this website does with your data
The short version: the site sets no cookies of its own, there is nothing to log in to, and two outside services measure how it is used — Google Analytics and the Meta pixel. The rest of this page says exactly what each part does, in the order you meet it.
Last checked against the site's code on .
Who is responsible
KTronics Pvt Ltd, company number PV 124279, of 722, Temple Road, Kohalwila, Kelaniya 11600, Sri Lanka. Questions about anything on this page go to info@ktronics.lk or +94 772 360 819, and a person answers.
Visit measurement: Google Analytics 4
Every page loads Google Analytics 4, Google's script from googletagmanager.com. It records the page view, and the site sends it three more events: contact when you press a WhatsApp, call, email or Facebook link, with which of those it was and on which page; generate_lead when an enquiry has been received; and assistant when you open the site assistant, ask it a question, start a quote or troubleshooting request, send a troubleshooting request, or use its estimate.
If you arrive on a link that carries Facebook's or Instagram's click id and no campaign tag of its own, the site tells Google Analytics the visit came from Facebook or Instagram, so the post that brought you is not counted as a direct visit.
What we see is aggregate: pages, countries and cities, devices and browsers, how visits arrived, and counts of those events. No name, phone number or message text is sent to Google Analytics. Google sets the cookies _ga and _ga_… for it, which last up to two years.
Advertising measurement: the Meta pixel
Every page also loads the Meta (Facebook) pixel — Meta's own script, fbevents.js, fetched from Facebook's servers. It records a PageView, a Contact event with the same method as above, and a Lead event when an enquiry has been received. We use it to see whether our Facebook posts and advertising bring enquiries, and to show the posts to people who are likely to want them.
If you are logged in to Facebook or Instagram in the same browser, Meta can connect the visit to your account. That happens on Meta's side under Meta's data policy; we never see who you are. Meta sets the cookie _fbp, and _fbc when you arrive from a Facebook or Instagram link.
The enquiry form and the site assistant
The form asks what the enquiry is about, your name, mobile number and district, for energy work the band your monthly electricity bill falls in, and a message; a business enquiry adds the company name. The assistant's solar quote request asks the roof and meter questions our engineers ask at a survey, plus your name and a mobile number or email. If you press "Use my current location" there, your browser asks your permission first, and the coordinates go into the request as a Google Maps link; you can type the address instead.
The assistant's troubleshooting request is for a system that is already running. It asks what is wrong, what the system is made of (the inverter, panels, battery, changeover and protection devices) and where it is, plus your name and a mobile number or email. If you want us to look at the system online, it also asks for the logins of the inverter's and the battery's monitoring portals.
When you press send, two things happen. WhatsApp opens with the details written into a message for you to send or not, and the same details are sent to our enquiry sheet: a Google Sheet in KTronics' own Google account, through a Google Apps Script that also emails the enquiry to us. With it go the page you were on, the time, a random id so a retried send is not counted twice, and where your visit began — "facebook", "google", the referring site, or "direct".
If that send fails, the browser keeps the enquiry in its own storage for up to seven days and tries again on your next page view here, so an enquiry is not lost to a dropped connection. Once the sheet has it, the copy in the browser is removed.
Monitoring passwords are handled apart from everything else. They go only to the enquiry sheet, over an encrypted connection: they are not written into the WhatsApp message, not included in the email we receive, and never kept in your browser. If the send fails, the request is retried without them and the engineer asks you for them instead. We use them only to look at and support your system, and changing the password in the portal ends that access at any time.
We use what you send to answer you, arrange the site visit, prepare the quotation or troubleshoot your system, and for nothing else. We do not sell it or pass it to anyone outside the company.
WhatsApp, phone, email and Facebook buttons
The WhatsApp buttons open WhatsApp through wa.me with a first message already written; the site keeps no copy, and nothing is sent until you press send there. The phone and email links open your own phone or mail app. The Facebook button is an ordinary link to our Facebook page and loads nothing from Facebook until you press it; the pixel above loads regardless. Pressing any of these is reported to the two services above as a Contact; the site sends only which method it was and which page.
The Google rating badge
Some pages show our Google rating and review count. The browser reads them from a small file on our own server; it does not contact Google for them. We refresh that file once a day, on our side, from Google's Places API. The badge is a link to our profile on Google Maps, and pressing it takes you to Google's site, under Google's terms.
Fonts
The pages use the Barlow and Inter typefaces served by Google Fonts, so your browser fetches them from fonts.googleapis.com and fonts.gstatic.com. Google receives that request — your IP address and browser — as any web server would.
Cookies and browser storage
The site sets no cookies of its own. The cookies you will find on ktronics.lk are Google Analytics' _ga and _ga_… and Meta's _fbp (and _fbc after a Facebook or Instagram link). Blocking them, or any tracker, breaks nothing on the site. There is no cookie banner because the site has nothing to ask you to accept beyond these two services, which this page is the honest account of.
Apart from cookies, the site keeps two short notes in the browser's session storage, which is cleared when the tab closes: where the visit began, and whether the site assistant was used. Both are attached to an enquiry when it is sent to our sheet, and nothing else reads them. The one thing kept longer is an enquiry that could not be sent: it waits in the browser's local storage for up to seven days, as described above, and is removed once our sheet has it. A monitoring password is never part of that copy.
The server, and what the site does not do
Like every website, the server that hosts ktronics.lk keeps the ordinary access log: the IP address a request came from, the page, the time and the browser. We use it for nothing beyond keeping the site running. There is no account to create, no newsletter, and the site takes no payment: the Pay page shows a bank QR code and explains how to ask for a card link, and the payment itself happens in your bank's app or on Dialog Pay's page, under their terms.
Your rights, and the law that applies
Sri Lanka's Personal Data Protection Act, No. 9 of 2022 is the law that governs what we do with personal data. In plain terms: we collect only what an enquiry needs, use it for that enquiry and the work that follows, and keep it no longer than that work and our records require. You can ask us at any time what we hold about you, to correct it, or to delete it. Write to info@ktronics.lk and we will answer.
This page describes the site as it is built. When the site changes in a way that matters here, the page changes with it and the date at the top moves. Anything else you want to ask is answered on the contact page.
