Privacy
Local-first by default.
What stays local
Research Packs stores pack names, URLs, notes, tags, domains, capture dates and optional descriptive source metadata in Chrome local extension storage. AutoFill Pro stores profiles, local preferences, website rules containing a domain, optional path, selected profile and automation mode, a limited fill diagnostic history, and learned field corrections containing the domain, an anonymous field fingerprint and the associated profile field. Rules, diagnostics and corrections never store entered values or full page contents.
When a Pro user enables enriched source metadata, Research Packs asks Chrome for optional access only to the selected sites. Author, description, publication date, site, language, content type, DOI and canonical URL are read and processed locally. This access can be declined, and no page content or metadata is sent to Productivity Suite servers.
When a Pro user opens Reading View, Research Packs requests optional access only to that source. The readable article text is processed temporarily on the device, is never stored or uploaded, and is removed from memory when the view closes. A closed source may be loaded in a temporary background tab that is closed automatically after extraction.
When a Pro user creates a local summary, Research Packs temporarily uses the readable text from one source or from 2 to 6 selected sources to create a synthesis, select relevant points, attribute them to their source and detect frequent topics. The extractive summary is created entirely on the device, is not saved automatically, is not sent to an AI service or external server, and is removed from memory when the summary or dashboard closes.
If the user selects another language for a summary, Research Packs uses Chrome's built-in Translator API. Chrome may download the required language pack to the device; translation runs locally and the source text and summary are not sent to Productivity Suite or an external translation service.
Sign-in, authentication, SSO/OAuth and other restricted pages are excluded from metadata reading and are saved with basic tab information only. They never block metadata capture for other selected sources.
When AutoFill Pro runs, it reads visible form labels and technical field attributes on the current page to identify compatible controls. That information is processed on the device. Form contents and page contents are not sent to Productivity Suite servers, and the extension never submits a form.
AutoFill Pro may keep a limited local diagnostic and activity history containing the domain, profile identifier, fill method and counters. Learned corrections keep the domain, an anonymous field fingerprint and the associated profile field. These records never contain entered values, passwords or payment information.
What may be transmitted
ExtensionPay handles payment and licence verification for Pro plans, and its payment provider processes the checkout. Productivity Suite does not receive card details. Your research packs, profile values and form contents are not sent to ExtensionPay.
For licence checks, ExtensionPay handles the email used at checkout, an installation key and the licence or subscription status over HTTPS.
Chrome Web Store Limited Use
Productivity Suite's use and transfer of information received from Chrome APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. User data is used only to provide or improve the extension features described to the user. It is not sold, used for personalised advertising, transferred for unrelated purposes or used to determine creditworthiness or offer loans.
Website privacy
This website does not use analytics, advertising cookies, tracking pixels or newsletter forms. It stores only your chosen language and colour theme in local browser storage. If you email support, Gmail processes the message you choose to send.
Deletion and backups
You can delete extension data by removing individual packs or profiles, clearing the available local histories, or uninstalling the extension. Uninstalling removes its Chrome local storage, so export a JSON backup first if you want to keep a copy.