WebSols Chrome Extension Privacy Policy
What the WebSols browser extension can see, what it sends and where, what it keeps on your computer, and how to remove it.
Last updated: 6 November 2026.
This policy is about one product: the WebSols extension for Google Chrome, as published on the Chrome Web Store. It sits beside our general Privacy Policy, which covers our website and services; where this page is more specific about the extension, this page applies.
1. Who we are
WebSols Pakistan, 1566/124 Walton Road, Lahore, Punjab, Pakistan, publishes the extension and is responsible for the data described here. We sell domains, hosting, business email, servers and development work.
Questions, or a request about your data: sales@websols.net, or the office line on our contact page.
2. What the extension is, and who it is for
The extension is a work tool for WebSols staff and the people we ask to help us, such as an SEO contractor. It talks to our own billing system and to nothing else. It does nothing until it has been given a code from that system, so it is of no use to anyone outside that group.
It has two jobs:
- SEO data for a quote. A member of our team opens a data request on a quote in billing and gets a code. The person collecting the data enters the code in the extension, then takes screenshots, tables, selected text, downloads, notes, files or links from the sites they use (their own SEO tools, for example) and sends them to WebSols, where they become source material for that quote.
- Meeting notes. In a Google Meet call that is a meeting arranged in our billing system, or one a staff member links to a project or a client, the extension records the audio and the live captions so that billing can write a transcript and a draft summary of what was agreed. The person taking the notes can switch it off at any time (see section 7).
3. What the extension can access, permission by permission
Chrome shows these when you install it. Here is what each one is used for, and nothing else.
| Permission | What we use it for |
|---|---|
| activeTab and scripting | To read the page you are looking at, only after you click a capture button in the extension, and only on that one tab. Used for the screenshot, full-page, region, tables and selection buttons. The extension cannot read any other tab, and cannot read a page you have not asked it to capture. |
| downloads | To notice the one file you download after pressing Catch download, and only for 5 minutes after you press it. Downloads at any other time are ignored. To keep the file, the extension fetches it again from the page you downloaded it from, using that page's own session. |
| storage and unlimitedStorage | To keep your code, name and pairing on your computer, and to hold captures and meeting audio on your computer until they have been sent. Screenshots and audio can be large, which is why the limit is lifted. |
| tabCapture | To record the sound of the Google Meet tab, only after you click WebSols in that tab to add the meeting audio (Chrome requires the click). |
| offscreen | Chrome does not let the extension's background process record audio, so a hidden extension page does the recording. It is used for nothing else. |
| alarms | A 30-second timer while meeting notes are on, which tells billing the recording is still going and lets billing switch it off. |
| Host access: api.billing.websols.net | The only server the extension sends data to. |
| Host access: meet.google.com | A small script runs on Google Meet pages. It reads the meeting code from the address, whether you are in the call (whether a "Leave call" button is on the page) and whether captions are on. While meeting notes are on it also reads the caption lines (who spoke and what they said) and shows a small "Notes on" label with a "Don't record" button at the top of the page. It does not read the Meet chat, the participant list or anything you type. |
| Microphone | Not an install-time permission; Chrome asks you once, on a page of the extension. Used to record your own voice during a meeting that is being noted, because the sound of a tab does not include your microphone. |
The extension asks for no access to other websites, cookies, passwords, your browsing history, bookmarks, email, or any page you have not asked it to capture. It does not run on any site except Google Meet and, when you press a capture button, the tab you press it on.
4. What it collects and sends
The extension sends data only to our billing servers at api.billing.websols.net, over an encrypted (HTTPS) connection. It sends no cookies. Nothing is sent to any other address, and the extension contains no advertising, analytics, tracking or error-reporting service.
SEO data (only when you press Send to WebSols)
- Each item you collected: a screenshot, a table saved as a spreadsheet file, the text you selected, a file you downloaded, a note, a file or image you added, or a link with a note.
- For each item: the address and title of the page it came from, the time it was captured, and the checklist line you chose for it.
- The code you were given, and the name you typed in the extension.
Meeting notes (only after the computer has been paired, and only in a meeting that is being noted)
- The Google Meet meeting code, so billing can check whether it is a meeting it knows about. This is sent to billing for any Meet you open on a paired computer, so that billing can say yes or no. If it is not one of ours, nothing else happens and nothing is recorded.
- When you use Take notes on this meeting on another Meet: the project or client you chose, the title of the Meet tab, and the words you typed to search for the project or client.
- Once notes are on: the audio of your microphone and, if you added it, the audio of the Meet tab, sent in 30-second pieces; the caption lines (speaker name as Meet shows it, the words, and the time); and the times each person spoke.
- A pairing: the device token billing gave this computer when you paired it with a short code, which proves that the requests come from your paired computer. The extension also keeps your name and work email address, as billing returned them.
What the extension does not collect: no browsing history, no page content except when you press a capture button, no keystrokes, no form fields, no cookies, no passwords, no location, no financial information. Nothing is recorded in a Google Meet unless billing has recognised it as a meeting to be noted.
5. Why we use it
The data is used for these two purposes only: to put the material you collected into the quote it was collected for, and to write down what was said in a meeting so that what was agreed is on record. We do not use it for advertising, profiling, credit or lending decisions, or anything else.
6. What happens to it on our servers
- SEO data becomes source material attached to one quote, visible to our staff who can open that quote. Our staff may use an AI service to help draft the proposal from that material. The web address and the name of the tool you took the data from are kept for staff and are not given to the AI.
- Meeting audio and captions are joined into a record on the meeting in billing. If the captions cover the conversation, they become the transcript. If not, the audio is sent to Microsoft Azure Speech for transcription after the meeting, by a private link that expires after 6 hours; the transcript is deleted from Azure once we have read it. The transcript is then summarised into a draft by an AI service (Anthropic's Claude), after email addresses and phone numbers have been removed from the text sent. The summary is a draft that a member of our team reviews; nothing is sent to anyone in the meeting.
- Access is limited to staff who need it for the quote or the meeting, and is logged.
These service providers handle the data on our instructions and for no purpose of their own. The servers behind billing are operated for us by an infrastructure provider in the European Union.
7. Control and consent
- People on the call. The extension shows a "Notes on" label and a red REC badge to the person running it. The person taking the notes can press Don't record at any time, on the label or in the extension; this stops everything and deletes what has already been captured. The same switch is on the meeting in billing and also stops a recording that is already running, within 30 seconds. We tell people we meet that we may record calls; see our Terms and Conditions.
- Only meetings billing knows about. Notes start only in a meeting that billing recognises for the paired person, or one that person has just linked to a project or a client. In any other Meet nothing is recorded, and a meeting held in person is never recorded.
- Nothing runs by itself on other sites. The extension only reads a page when you press a capture button on it.
8. Storage and how long we keep it
On your computer
| What | How long |
|---|---|
| Your SEO code, name and the request's checklist | Until you press Use another code or remove the extension |
| Captured items and files | Until they are sent (they are then removed from your computer), or until you remove them |
| Meeting audio pieces | Until billing has received them, then removed. If you press Don't record, removed at once |
| Pairing (device token, your name and email) | Until you press Unpair or remove the extension |
| Which meeting is being noted, and the caption lines waiting to be sent | Until the notes end or the browser is closed |
It is all kept in the extension's own storage in your browser. It is never sent anywhere except as described in section 4.
On our servers
| What | How long |
|---|---|
| Meeting audio | Up to 90 days, then deleted automatically (the pieces uploaded in the middle of a meeting are cleaned up sooner if the meeting is abandoned) |
| Meeting transcript and summary | Kept with the meeting record in billing, like other records of our work with a customer |
| A meeting you pressed Don't record on | What was captured is deleted; we keep a note that recording was switched off, who did it and when |
| SEO items | Kept with the quote they were collected for, for as long as we keep the quote; our staff can remove any item sooner |
| Audio sent to Azure Speech | Available to Azure for at most 6 hours; the transcript is deleted from Azure once read |
9. We do not sell it or share it
We do not sell the data the extension handles, and we do not share it with anyone for their own purposes, advertising or marketing. We use it only to provide the two features described in section 2. We do not use or transfer it to determine creditworthiness or for lending, and nobody at WebSols reads it except to do the work it was collected for, or where the law requires.
We use and transfer information received from Google APIs and Chrome only to provide and improve the extension's single purpose described in section 2, and we follow the Chrome Web Store User Data Policy, including its Limited Use requirements.
We may disclose data to a professional adviser or an authority where the law requires it.
10. Security
All traffic between the extension and billing is encrypted. The extension never sends cookies, and each request carries only the code or device token that identifies it. Codes expire, can be cancelled by our staff at any time and give access only to what they were issued for. A code cannot be used to read anything back from billing. The extension loads no code from anywhere else.
No system is perfectly secure. If a breach affects your data we will tell you what happened and what we are doing about it.
11. Your choices and rights
You can ask us to tell you what we hold about you from using the extension, to correct it or delete it. Ask at sales@websols.net. We will reply within 30 days, and may need to check who you are first. The rights and the way to raise a complaint are the same as in our Privacy Policy.
12. How to remove it
- In the extension, press Unpair (Meeting notes) or Use another code (SEO data). This removes your code or pairing from your computer. Also remove the computer in billing under My account → WebSols extension if you can.
- In Chrome, open chrome://extensions, find WebSols and press Remove. Chrome deletes everything the extension stored on your computer.
- To remove data we already hold, write to us as in section 11.
13. Children
The extension is for people who work with us. It is not directed at children and we do not knowingly collect data about children.
14. Changes to this policy
If the extension's permissions or what it does with data change, we will update this page and the date at the top before the new version is published. Chrome will also ask you to approve any new permission before it takes effect.
15. Contact
WebSols Pakistan, 1566/124 Walton Road, Lahore, Punjab, Pakistan.