Skip to content

Instantly share code, notes, and snippets.

@slayton
Last active August 21, 2026 13:53
Show Gist options
  • Select an option

  • Save slayton/f92e1ca506f2c09ce9b7517e641b0f2e to your computer and use it in GitHub Desktop.

Select an option

Save slayton/f92e1ca506f2c09ce9b7517e641b0f2e to your computer and use it in GitHub Desktop.
Privacy policy for fq-chrome-plug-in (FinQore internal Chrome extension)

Privacy Policy — fq-chrome-plug-in

Effective date: August 21, 2026

fq-chrome-plug-in is an internal tool built by FinQore for FinQore employees only. It is not intended for, marketed to, or usable by the general public — its features work only on FinQore-owned sites and require a FinQore employee account.

We do not collect data

This extension does not collect, track, store, sell, or share any user data:

  • No analytics or tracking of any kind.
  • No browsing history is read, recorded, or transmitted.
  • No third parties ever receive anything — there are no trackers, ad networks, or external services in the extension.
  • No background activity — the extension does nothing until you click one of its actions.
  • No persistent storage — nothing is retained after an action completes.

The one exception: what you explicitly submit

The only data that ever leaves your browser is content you deliberately submit yourself — for example, filing an internal support ticket (your written description, and a screenshot you preview and approve) or sending a work item to FinQore's internal tooling. That content goes directly and only to FinQore's own internal systems, exactly as if you had typed it into a FinQore internal web portal. FinQore is submitting data to FinQore; no one else is involved.

Authentication

The extension does not handle or store passwords or credentials. Actions are authorized through your existing signed-in FinQore session. If you are not signed in, actions simply fail.

Contact

Questions: devteam@finqore.com. Changes to this policy are published at this same URL.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment