Site Check account and report storage

Site Check uses the necessary, HTTP-only bt_sitecheck_preview cookie to securely retrieve an anonymous report for up to 90 days. Signing in stores a Supabase customer session in browser local storage under the BishopTech customer auth namespace. This supports sign-in and session renewal. These necessary account functions do not depend on optional analytics consent. Signing out clears the customer session.

What we use

BishopTech uses a limited set of first-party cookies and browser storage tools to keep the site running, support sign-in and demos, and understand how visitors use the public pages.

First-party cookies: used for demo usage limits and authentication-related browser state where needed.
localStorage and sessionStorage: used in dashboard, admin, and utility experiences to keep UI state and session state available across page views.
Analytics: Vercel Analytics, Google Tag Manager, and the first-party BishopTech analytics script load only after you enable the optional analytics category. Do Not Track also disables these measurements.
Marketing measurement: Apollo website tracking loads only after you enable the optional marketing category.
Third-party service storage: embedded tools and vendor scripts may set their own identifiers or store data according to their own policies.

Examples of current site usage

Homepage demo usage cookie: the public demo stores a first-party cookie named homepage_demo_usage to keep the demo time limit consistent for the visitor.
Authentication cleanup: the sign-in flow clears the bishoptech_auth cookie and related localStorage entries when a visitor signs in again.
Analytics storage: after analytics consent, the custom script uses localStorage and sessionStorage for anonymous visitor and session identifiers. It sends page paths and interaction metadata, not form field values or IP addresses.
Admin and dashboard utilities: several internal tools store interface state in browser storage so the UI remains usable between page loads.

Why we use them

Keep the website and demo features functioning as expected.
Maintain sign-in and session-related behavior where a feature requires it.
Understand which public pages are getting traffic and which content needs improvement.
Limit repeat demo usage where a visitor-facing demo is intentionally capped.

Third-party services

Some tools on the site are provided by third parties. Google Tag Manager and Vercel Analytics are optional analytics tools, while Apollo is optional marketing measurement. They do not load on the public site until the related category is enabled. Their own privacy and cookie policies may also apply when you enable them.

If you interact with embedded or external vendor features, their own privacy and cookie policies may also apply.

Your choices

Use the “Manage cookie choices” control on this page to change optional consent at any time.
You can block or delete cookies in your browser settings.
You can clear site storage to remove saved browser state.
You can disable JavaScript to prevent many non-essential storage features from running, although some pages may stop working properly.
The custom BishopTech analytics script respects the browser’s Do Not Track signal and stops when analytics consent is withdrawn.

Updates

We may update this Cookie Policy as the site changes. If we add new tracking tools or materially change how browser storage is used, we will update this page to match the live site behavior.

Contact

If you have a question about this policy or want to know more about a specific browser storage feature, contact us at matt@bishoptech.dev or by phone at (417) 629-7373.

Cookie Policy