Monitoring stays local.

What the extension processes locally

While you enable monitoring, the extension may inspect the supported ticket webpage to find the supported availability control, identify the known no-seats message, recognize signs that human verification is required, determine monitoring state, and recognize the configured ticket-ready cart route.

This ticket-page information is processed locally in Chrome. It is not sent to our licensing service or Stripe.

Limited licensing data

To create and verify seasonal access, the extension sends our licensing service only the data needed for that purpose:

• a randomly generated installation identifier;
• a device public key or its fingerprint—the private key remains non-extractable on the device;
• the extension version and season identifier;
• a Stripe Checkout Session reference used to verify payment;
• a device-proof signature and request timestamp; and
• ordinary network metadata inherent in an HTTPS request, such as an IP address.

The licensing service uses this information only to create Stripe-hosted Checkout, confirm payment and refund status, and issue a signed seasonal license bound to that installation.

What we do not intentionally collect

Our licensing service does not receive ticket availability, ticket-page HTML or DOM content, human-verification contents or results, monitored ticket URLs, browsing history, University credentials, authentication cookies, payment-card numbers, or the device private key.

Payment processing

Stripe processes payment information on Stripe-hosted Checkout. The extension and our licensing service do not receive payment-card details. Our licensing service queries relevant Stripe payment records and identifiers to confirm whether the one-time seasonal purchase remains valid or has been refunded.

Hosting and retention

The licensing service is hosted on Cloudflare. The service is designed without a separate customer-account database. Local installation and license information remains in the browser until extension data is removed. Stripe retains payment records under the merchant account’s settings and applicable requirements, and Cloudflare may retain infrastructure logs under its service configuration and policies.

Your choices

You can stop monitoring at any time. Removing the extension or clearing its local data removes locally stored extension information, but it can also permanently remove the cryptographic identity tied to paid season access. Payment records maintained by Stripe are not removed by uninstalling the extension.

Contact

For privacy or support questions, email ticketclaimer.support@gmail.com.