Cookie Policy

This page explains the cookies, browser storage, and tracking tools used on BishopTech’s public website and demo experiences.

Last Updated: June 25, 2026

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 and measurement tools: Google Tag Manager, Vercel Analytics, Apollo website tracking, and the custom BishopTech analytics script may collect usage and device information.
  • 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: the custom analytics script uses localStorage and sessionStorage to generate visitor and session identifiers.
  • 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. Those services may use cookies, pixels, browser storage, or similar technologies according to their own policies. Current examples include Google Tag Manager, Vercel Analytics, and Apollo website tracking.

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

Your choices

  • 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.

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.

Privacy Policy

Read the broader data-handling policy for BishopTech.

View Privacy Policy

Live Site Updates

Browser storage and tracking behavior should always match the live site.

Ask a Question

Contact Support

Reach out if you want clarification on any browser storage behavior.

Contact Us