Privacy

Browsing events

You do not need a fan account. ASE counts page views and estimates browsing visits to understand which parts of the website are useful. Basic analytics uses no analytics cookie or saved visitor identifier, and does not collect search text, query parameters, form contents, precise location, or advertising information.

A random temporary value stays only in this tab’s memory while you browse. Reloading, opening a new tab, 30 minutes of inactivity, or a new Amarillo calendar day starts another visit. It is converted immediately into an aggregate estimate on the server; the value itself is never saved in the analytics database. The figures describe browsing visits, not identified people or returning visitors.

The database keeps daily counts, bounded page totals, and statistical estimates. These aggregate records have no automatic deletion schedule. A small bounded set of hashes of page-view request IDs prevents retry double-counting; those hashes are replaced as later traffic arrives and are not linked to visit IDs or browsing histories.

ASE does not use device fingerprinting or intentionally store raw IP addresses or raw browser user agents in its public analytics database. Our hosting provider processes network information to deliver and protect the website.

Event reports

If you use the Report button on an event, ASE keeps the event, report category, your comment, an optional supporting source link, and the submission time. The form does not ask for your name, email address, or phone number.

Your report appears on the event page as unverified community information. It can later be marked resolved or removed from public view, but it does not automatically change the event or become official confirmation. Event reports are not automatically deleted.

Tracked QR links

When you open an ASE QR link, ASE records the code, scan time, destination, redirect result, estimated traffic type, broad device type, browser family, and the referring site's hostname when available. These details are used to count and understand QR campaign scans; the human, bot, or unknown classification is only an estimate.

ASE's QR analytics records do not store an IP address, raw browser user agent, full referring URL, cookie, or stable visitor ID. QR scan records and daily counts are not automatically deleted.

Beta testing

Beta information is collected only after a tester chooses Start Beta Test. ASE then keeps a generated session ID; the starting page, referrer, and source; screen and viewport size; browser user agent and device platform; timezone and build details; selected page or feature actions; event context when applicable; submitted feedback; and final survey answers.

The current survey asks about three testing scenarios, likely uses for ASE, ratings, and optional written feedback. It does not ask for a name, email address, phone number, passwords, payment information, screenshots, demographics, attendance frequency, or a person's connection to local sports. ASE does not record page replay or keystrokes. Beta feedback and surveys are available to authorized administrators and are not posted on event pages.

Historical Version 1 survey records may contain optional profile answers from that earlier survey. The code gives beta records an expiry date 365 days after creation. Automatic deletion depends on Firebase TTL being configured for each beta collection in the deployment, and deletion may happen after the expiry date.

Browser storage and request protection

During an active beta, this browser's local storage holds the session ID and credential, active status, report count, build version, current stage, and draft survey answers. Draft answers are sent to ASE only when the final survey is submitted. ASE stores only a cryptographic hash of the credential on the server.

Completing or exiting the beta clears those local values. Clearing browser data also removes this browser's awareness of the session, but it does not erase reports or a survey already submitted.

Basic analytics does not set visitor or session cookies. If you choose an analytics preference, local storage keeps only that choice in this browser. A secure session cookie is used when an authorized administrator signs in. For analytics, beta, and contact requests, a network address is used in server memory to limit abusive bursts but is not added to their records.

Firebase App Check with reCAPTCHA Enterprise can also protect beta and contact requests. Whether it runs depends on deployment configuration; the code does not require it by default.

Optional support payments

When online support is enabled, you choose an amount and pay on Stripe’s hosted page. Stripe handles payment details under its own privacy policy. ASE does not collect or store card numbers.

ASE’s payment notification system stores the checkout, payment-link, payment-intent, optional Stripe customer, and notification identifiers, the paid amount and currency, payment mode, and timestamps. It does not copy names, email addresses, billing addresses, or the full payment notification into its database. A Stripe customer identifier can still refer to a person in Stripe’s system.

Support records are private, available only through trusted server access. They do not change event listings or ranking. Payment records are not automatically deleted.

Messages to ASE

When you send a message, we keep your reply email, your name if you provide it, the topic, your message, a submission identifier, and the time it was received. We use these details to read your message, respond, and follow up on the issue or suggestion.

Messages are private and available only to authorized ASE administrators. They are not posted on event pages or added to a mailing list. Please don’t include sensitive personal information.

Messages stay in ASE’s inbox until an administrator deletes them. There is no automatic deletion schedule. You can ask us to delete a message using the contact form.