Privacy

Privacy Policy

BoardCheck is a Chrome extension and website for spotting warning signs on supported job-board pages. This page has two voices: a plain-English version first, then the more formal policy terms.

Effective April 23, 2026.

Plain-English version

  • BoardCheck does not sell your data.
  • The extension does not collect your browsing history.
  • Job-page matching happens locally in your browser.
  • BoardCheck does not upload job listings or page contents for warnings.
  • The website only collects what it needs for accounts, billing, browser linking, and support.

What you are getting

In normal use, BoardCheck looks at supported job-board pages in your browser, checks company names against a local reviewed-company dataset, and shows warning context when there is a match. That warning flow is not built around uploading your job search to BoardCheck.

If you create an account or use paid features, BoardCheck needs account and billing data so it can sign you in, confirm your access, link the extension to your account, and manage your subscription. If you contact support through the website, BoardCheck receives the message and contact details you choose to send.

Formal policy

This Privacy Policy describes how BoardCheck collects, uses, stores, and shares data through the BoardCheck Chrome extension, the BoardCheck website, and related account, billing, extension-linking, and support services. By using BoardCheck, you understand that these services process data as described below and as required to provide the features you choose to use.

No sale of collected data

BoardCheck does not sell personal information and does not share personal information for cross-context behavioral advertising. BoardCheck uses data only to provide, maintain, secure, support, and improve the extension, website, account, billing, and support workflows described in this policy.

No browsing or page-content collection

  • No browsing history collection
  • No job-listing text or page contents uploaded for the warning flow
  • No default analytics tied to your browsing activity
  • Local page inspection only on supported job-board surfaces

Matching, warning prompts, auto-hide behavior, and local allowlist or blocklist behavior are handled in the browser against the bundled reviewed-company dataset and your local settings. BoardCheck does not use this local warning flow to create a remote profile of your job search.

What may stay local in the extension

The extension can store the bundled reviewed-company dataset, your protection mode, auto-hide threshold, theme preference, local allowlist and blocklist, and small UI prompt state in browser extension storage on this device. It can also keep the currently captured company, supported-site status, and temporary popup state in extension session storage so the side panel can reopen with the latest supported click without sending that value off-device.

What the bundled dataset is and why it exists

The bundled reviewed-company dataset is the local file the extension uses to decide whether a company has already been reviewed and whether that review supports a Caution label.

The dataset is assembled from manually reviewed company records based on public sources, including company sites, public warnings, news reporting, regulator or court material, and other public evidence described in BoardCheck’s review rubric and research workflow.

What changes when you use account or premium features

Account-linked features need a small amount of remote state. The website uses Clerk for sign in, Stripe for checkout and billing management, and a Neon-backed BoardCheck account service for product-owned account records. Those records can include your Clerk user ID, Stripe customer or subscription identifiers, subscription status, trial or billing-period dates, complimentary entitlement grants, temporary extension-link requests, and hashed extension session tokens.

When you link the extension to your account, the extension stores your signed-in email, user ID, opaque extension session token, session expiration, billing summary, and entitlement summary locally. The extension uses that token to refresh access to paid features. It does not send the currently captured company, job listing text, or browsing history as part of that entitlement refresh.

What the website may collect

Public website pages are static product and policy pages. They do not load the account script and are not designed to collect analytics by default. BoardCheck may receive ordinary technical request data from website and backend hosting, including IP address, user agent, requested URL, timestamps, and error or security logs.

The account page loads Clerk sign-in controls and calls the BoardCheck account service to show access status, complete extension linking, start Stripe Checkout, open the Stripe billing portal, or revoke linked extension sessions when you sign out. During extension linking, the website may temporarily keep a link verification token and extension return target in browser session storage, then scrub the token from the URL.

The contact form, if you use it, sends the name, email, subject, and message you provide to the BoardCheck contact endpoint, which relays the submission through Brevo email delivery.

Who data may be shared with

The local warning and auto-hide flow is not shared with third parties. If optional account features are enabled and you choose to use them, limited account-linked data may be processed by the project-controlled website and entitlement backend.

Account, billing, and support workflows may also involve Clerk for authentication, Stripe for payment and subscription processing, Neon for product-owned account records, Brevo for contact email delivery, and Cloudflare or similar hosting infrastructure for the website and backend. BoardCheck does not sell personal information and does not share personal information for cross-context behavioral advertising.

BoardCheck may also disclose information if required by law, legal process, security investigation, fraud prevention, protection of rights or safety, business transfer, or enforcement of applicable terms.

Retention and deletion

Local settings, theme preference, and local allowlist or blocklist entries remain in browser extension storage until you change them, clear extension storage, or remove the extension.

The currently captured company, popup context, and website link tokens are temporary session state. Extension-link requests expire quickly, and linked extension sessions are stored as hashed tokens by the backend until they expire, are refreshed, are revoked, or you sign out.

Billing and entitlement records are retained as needed to provide paid access, prevent duplicate trial use, maintain billing history, and satisfy operational, tax, accounting, dispute, security, and legal obligations.

You can remove local extension data by changing settings, clearing extension storage, or uninstalling the extension. For account or support data requests, use the contact method provided on the BoardCheck website.

Permissions and why they are needed

storage stores your local settings, local company lists, bundled dataset state, and optional account session or entitlement state.

windows lets the extension focus the current browser window before opening the warning popup. Supported host permissions let the content scripts read supported job-board pages so company matching and auto-hide behavior can happen locally in the browser.

sidePanel lets BoardCheck show warning and account controls in the browser side panel.

Contact and sensitive information

If you contact BoardCheck through the website contact form, send only what is needed to understand and respond to your request. Do not include passwords, government ID numbers, financial account numbers, or other sensitive personal information.

If you contact BoardCheck through Chrome Web Store reviews, Chrome Web Store support, email, or another third-party platform, your message may also be processed under that platform’s own policies.

Changes to this policy

BoardCheck may update this Privacy Policy from time to time. The effective date above identifies the current version. Material changes will be reflected on this page and, where required, in the Chrome Web Store listing or in-product disclosures.