Valytica Capture privacy policy

Last updated 12 November 2026. Published at https://valytica.in/capture/privacy.

Valytica Capture is a Chrome extension published by Gnanalytica Technologies LLP (LLPIN ACQ-4389), which also operates Valytica. It is written plainly because the audience is a professional who is about to install a browser extension that can see government portals they are signed into. It covers the extension; the rest of what Valytica does with personal data — how long it is kept, your rights, and how to complain — is in the Valytica privacy notice at https://valytica.in/privacy.

What the extension can see

content.js is injected into a tab only while the capture panel is open on it. On a portal, that takes pressing Capture on a check in Valytica, or clicking the extension's icon on that tab; on any other website, only clicking the icon on that tab. A portal you simply browse to is not touched. It is never declared as a content script for portal pages in the manifest, so it does not load with the page and does not run in the background.

To keep the panel off every tab that is not a portal, the extension checks the address of the tab you are on — never its contents — and switches the panel off there. It does not ask for Chrome's tabs permission, so Chrome shows it an address only for the portals named in its permissions, for Valytica itself, and for a tab on which you click its icon. Every other tab's address is hidden from it, and such a tab is treated as "not a portal".

host_permissions names the specific portal hosts and Valytica's own two addresses. Not <all_urls>.

Why the screenshot needs a click from you. Chrome lets an extension take a screenshot of a tab only if it has access to every website (<all_urls>), or if you invoked it on that tab — its toolbar icon or Alt+Shift+S. This extension does not ask for access to every website, so the screenshot waits for that click, once per portal. Chrome keeps that permission while the tab stays on the same portal and drops it when the tab moves to another site or closes. To say when the click is still owed, the extension remembers, for this browser session only, which tab you clicked on and that portal's address — never the page's contents — and shows a badge on its icon there.

Fill values: what is typed into the portal

Fill values types the case's identifiers into the portal's own search form, in your browser, so you do not have to copy them across by hand. Only what that portal's search asks for, taken from the case you chose: district, mandal or taluk, hobli, village, survey number, khata or PTIN, document number and year, SRO. Never a person's name — not the owner's, not the applicant's — even where the portal's form has a field for one.

  • It never presses Search (or Submit, or anything else). You check what was filled and run the search yourself.
  • It never touches a captcha, an OTP, a password or a PIN box.
  • A list with no clear match is left as it was, and its options are shown in the panel for you to choose; it does not guess.
  • Where the form first asks how to search, it picks the mode the case calls for — "Land Value" or "Apartment Value", "Document No", "Door Number" — and opens a portal's own drop-down list to choose an office or municipality. It never chooses a mode that asks for a person's name ("Owner Name").
  • Fill sends nothing to Valytica, and reads nothing from the page beyond finding the boxes to type into. The identifiers come from the case the panel already has open. What you type or Fill types into a portal goes to that portal, as it would if you typed it — Save, below, is still the only way anything reaches Valytica.

What is read, and what waits

While the capture panel is open on a portal page and you have chosen the case it is for, the extension reads that page for the open check's fields: table cells beside or under a matching heading, and what the search form has selected. What it finds is highlighted on the page and listed in the panel.

It is then held, not sent. Held values stay in the browser — in the panel, and in chrome.storage.session (memory only, wiped when the browser closes) so that closing the panel does not lose them. A value you select by hand is held the same way.

Until you have chosen a case — by pressing Capture on a check in Valytica, or by picking the case in the panel — the page is not read at all. The extension does not fall back to the case you used last, and a choice lapses after four hours without a save.

What is sent to Valytica, and when

Only when you press Save (in the panel, or on the bar the extension shows at the top of the portal page). One press sends, to the case named on the button:

  • the values held — the cells read from the result, or text you selected;
  • for each one, the table row it came from, verbatim, including the Telugu or Kannada. This is the quote a bank reviewer checks, so it must be the words that were actually on the page;
  • the page URL and title of the portal page;
  • a screenshot of the visible portal page, taken when you press Detect values or when the panel reads the page, on a portal tab you have clicked the extension's icon (or pressed Alt+Shift+S) on (it shows whatever that page shows, including names on it), and sent only when you press Save;
  • which recipe rules matched and which did not, so we can tell a broken selector from a property with nothing to report.

One exception, and it is also a deliberate act: pressing Alt+Shift+S (or the toolbar icon) takes a proof screenshot, and when no values are waiting that screenshot is sent to the open check straight away.

Two other requests carry no portal data: the list of your open cases is fetched when the panel opens, and a case search sends the words you type to Valytica in the request body.

What Save writes

  • A value for one of the check's own fields is written onto that check in Verification, with the row it came from. A value you typed on the check yourself is never overwritten.
  • A value that is also a report field arrives as a suggestion, which you accept or reject in the case like any other.

The panel then says, field by field, what Valytica stored and what it did not, with the reason. Sending the same value twice stores it once.

What is never sent

  • The page itself. Not its HTML, not its text beyond the rows you saved.
  • Anything you did not press Save on. A value that was read and highlighted but never saved does not leave the browser.
  • Your portal session, cookies, or credentials.
  • Anything from a tab the capture panel is not open on.
  • Anything from a portal page while no case has been chosen.
  • Your Valytica password — the extension never sees one. Valytica hands it a session token, which lives in chrome.storage.session and is wiped when the browser closes.

Translation

Telugu, Kannada and Hindi values are translated on your own device, by Chrome's built-in translator. There is no API key and no network call. If your browser does not have it, the panel says so and shows you the original — it does not fall back to a translation service you did not agree to.

The translation is shown beside the original and never replaces it. What Valytica stores as the source quote is always the original text.

Where the data goes after that

Into your Valytica case, in the Mumbai region, under the same row-level security as everything else your firm holds. Nothing is written into a case without your Save, and nothing reaches a report without your accept: check fields land on the check you were working on, and report fields land as suggestions you accept or reject. It is kept as long as the rest of the case, as section 7 of the Valytica privacy notice describes.

Sharing, and the Chrome Web Store's rules

Apart from what Fill types into a portal's own search form, the extension sends what is described above to Valytica and to nobody else: there is no analytics or advertising in it, and no other company's code runs in it. What you save is used only to provide Capture and the Valytica case it belongs to. We do not sell it, use it for advertising, or transfer it to anyone for their own purposes; the companies that help us run Valytica itself are named in section 6 of the privacy notice.

Valytica Capture's use of the information it receives complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.

Permissions, and why each is asked for

  • activeTab: the proof screenshot, and the panel on a page where you click the icon.
  • scripting: to put the reader and Fill into the tab the panel is open on, when you open it there.
  • storage: session storage only — the sign-in token, values held before Save, the case you chose. All of it is wiped when the browser closes.
  • sidePanel: the capture panel itself.
  • Host permissions: the government portals the verification checks open, and Valytica's own addresses, so the extension can talk to your Valytica account.

Contact and changes

Write to privacy@gnanalytica.com. When this policy changes, the date at the top changes with it, and anything material is also reflected in the Valytica privacy notice.