GridGrab privacy policy

Effective date: 8 November 2026

This policy explains how the GridGrab – Table & List to CSV/Excel browser extension (“GridGrab”) handles information. GridGrab is published by Matheus Mello, an individual developer based in Portugal (“I”, “me”). Contact: matheus.mello.developer@gmail.com.

Scope and free use

This policy covers the GridGrab editions for Chrome and Firefox. Both are free, work locally and require no account. Neither edition uploads extracted data or makes extension-initiated network requests. There is no analytics, advertising, telemetry or remotely loaded executable code. Normal website activity and browser-managed services remain subject to their own policies.

Page access and processing

Opening GridGrab lets its bundled code detect tables and repeated lists in the selected tab. It reads page text and, for lists, link and image URL values; it does not fetch those URLs. Detection uses visibility checks, but text inside a selected cell can include descendant text. Preview and selected rows are held in popup memory, rather than saved as page content in extension storage.

Both editions request only activeTab, scripting and storage, with no standing website host permissions. These allow temporary access to the selected tab, execution of the bundled reader and local preferences and usage storage. Regular HTTP/HTTPS pages are supported; local file access depends on browser permission. Browser and store pages may block access.

Chrome and Firefox differences

Both editions can outline and scroll to a candidate on the page. These inline style changes can be observed by the page’s own scripts; extracted rows are not inserted into the page.

• Firefox: when the popup connection closes, the content script removes the highlight, restores the previous outline styles and drops its candidate references. Private browsing is disabled by the manifest. Persistent extension storage contains only the CSV delimiter, UTF-8 BOM preference and UTC daily export date/count.
• Chrome: the content script has no corresponding popup-close cleanup. Its candidate references and last outline can remain until the document is unloaded, such as on navigation or reload. The manifest does not disable private browsing; access there depends on browser settings. Its local usage counter is not isolated by session type, so do not assume a separate private-session counter. Normal use stores the delimiter, BOM preference and UTC daily export date/count. Chrome also contains local storage handling for site-origin/selector settings; these are not extracted rows, and any existing entries can be removed in settings.

Limits, clipboard and downloads

Both editions allow unlimited TSV copying for Excel or Sheets and a combined five CSV, XLSX, Markdown or JSON exports per UTC day, resetting at 00:00 UTC. CSV and XLSX are generated locally as downloads; TSV, Markdown and JSON are written to the clipboard only when you select the corresponding action. Neither edition reads your clipboard. Chrome consumes the export count before output and does not restore it on failure; Firefox attempts to restore the count if output throws an error.

Download filenames include the source host name (or “page” when absent) and date. The browser may retain download history. Files and clipboard copies can contain sensitive source data and remain wherever you save or paste them; uninstalling GridGrab does not remove those copies.

Review untrusted page data before opening or pasting it into a spreadsheet. Spreadsheet applications may interpret some cell values as formulas; do not assume every installed edition neutralises those values.

Retention and control

Extension storage uses chrome.storage.local in the browser profile, with no extension-managed sync. Local preferences and counters remain until replaced, the extension’s local data is cleared or the extension is uninstalled. Chrome’s selector-removal controls do not clear all extension data. Firefox settings change CSV preferences; they do not provide a general data-clear button. Popup memory ends when the popup closes; Chrome’s page-side references have the longer lifetime described above.

Developer contact and your rights

I do not receive the data processed locally by the extension. If you email me, I receive the information you choose to send and use it to answer and handle your request, retaining it only as needed for that purpose or applicable legal obligations. Do not send extracted data unless it is needed for your request and you are entitled to share it. I do not sell personal data or share it for advertising.

For personal data I hold, you may request access, correction, deletion, restriction, objection or portability where applicable by contacting matheus.mello.developer@gmail.com. You may complain to the Portuguese data protection authority, the Comissão Nacional de Proteção de Dados (cnpd.pt), or your local authority.

Children and changes

This is a productivity tool and is not directed at children under 16. Changes to this policy will be published at this URL with an updated effective date.