Chrome Extension Privacy Policy

Last updated: November 12, 2026

This Chrome Extension Privacy Policy explains how GreeLogix ("we," "us," or "our") handles data in connection with the Google Chrome browser extensions we publish on the Chrome Web Store. For information about how we handle data on our main website, please read our general Website Privacy Policy.

1. Covered Chrome Extensions

This policy applies to Chrome extensions published by GreeLogix, including:

You can also explore dedicated product documentation for Secure TOTP Authenticator.

2. Data Collection & Local Processing

We design our Chrome extensions with a local-first, data-minimization architecture. Depending on the specific extension you install:

  • Secure TOTP Authenticator: Account titles, issuer labels, TOTP secret keys, and usage metadata are stored locally on your device inside Chrome extension storage. Verification codes are computed locally offline without transmitting your secret keys to GreeLogix servers. No user account or cloud registration is required, and there is no cloud sync or cloud backup currently. When you choose to export a backup file (password-encrypted or plain-text JSON), that file is generated locally on your device.
  • Secure Tab Locker: Domain lock rules, timers, and passwords you configure remain strictly local in your browser storage so tabs can be protected on your device without an external login.
  • Password Viewer: Operates solely on password input fields in the active webpage DOM when triggered by you. It does not store, log, or transmit your passwords to remote servers.
  • JSON Viewer Pro: Parses and formats JSON payloads directly inside your browser tab without uploading your data to GreeLogix servers.
  • File Organizer for Downloads: Inspects browser download metadata locally (such as file name and extension) only to route downloaded files into your configured folders.
  • Image Downloader & Scraper: Runs on the active webpage you explicitly trigger it on to list and save page image assets locally via Chrome downloads.
  • MeetFlow AI: Processes meeting context and prompts only when invoked by you using the extension permissions disclosed on its Chrome Web Store listing.

3. What We Do Not Do With Extension Data

  • We do not sell or rent user data from our Chrome extensions to third parties.
  • We do not transfer or use extension data for unrelated advertising, data brokerage, creditworthiness determination, or lending purposes.
  • We do not silently harvest browsing histories across unrelated tabs or sell personal information.

4. Browser Permissions & Limited Use Compliance

Each extension requests only the Chrome APIs and host permissions necessary to deliver its documented user-facing functionality (for example, local storage for saving user preferences or TOTP configuration, downloads for saving local backups or sorted files, or activeTab when acting on a tab you open). Always review the individual Chrome Web Store Privacy Practices tab for the exact disclosure of each extension.

5. Data Retention & Deletion

Because our utility and security extensions operate primarily using Chrome's local extension storage on your computer, your data remains under your direct control:

  • You can edit or delete individual items (such as saved TOTP accounts or tab lock rules) inside the extension UI at any time.
  • Uninstalling an extension from Chrome removes its sandboxed local extension storage from that browser profile. For extensions without cloud sync (such as Secure TOTP Authenticator), make sure to save an encrypted local backup before uninstalling or resetting Chrome if you need to keep your configuration.

6. Security & User Responsibility

Locally stored extension data inherits the security posture of your computer and operating system user session. Use strong device login credentials, enable full-disk encryption (such as BitLocker or FileVault), keep your browser updated, and store exported backup files and service recovery codes safely outside the browser.

7. Children's Privacy

Our browser extensions are built for general productivity, developer tooling, and security workflows and are not directed toward children under 13 (or the equivalent minimum age in your jurisdiction). We do not knowingly collect personal information from children.

8. Changes to This Policy

If we add cloud features, integrations, or new permissions to an extension that change how data is handled, we will update this page and update the "Last updated" date at the top, as well as the corresponding Chrome Web Store privacy disclosure.

9. Contact Us

If you have questions or requests regarding privacy for any GreeLogix Chrome extension, contact us at:
Email: [email protected] or [email protected]
Publisher: GreeLogix — Bahria Town, Lahore, Punjab, Pakistan
Related: Website Privacy Policy · Terms of Service · Chrome Extensions Hub