01

Why we use this information

We use account, scoring and requested rules-question information to provide the service you request, on the basis of performing our contract with you. Proportionate security, fraud prevention, reliability and support processing rely on legitimate interests.

Optional product-news email relies on the separate consent recorded for that list, which you can withdraw. Applicable statutory billing or accounting records are kept to meet legal obligations. Account and security messages do not depend on a marketing choice.

02

Account and match data

You create an account or sign in with a supported credential before using the current app. Firebase Authentication processes your account identifier and the email, display name, photo and verification information supplied by your chosen sign-in method. An older account may have started anonymously; linking a credential keeps that account's records.

The app stores your preferences, sports, player or team labels, scores, match events and entitlements. Match records sync to Firestore under your account while connected. Score corrections append an event rather than silently rewriting the original. That does not prevent account erasure. Local arcade progress and device preferences also use device storage.

03

Camera processing

Camera use starts when you choose camera setup or a camera test. Current camera stills, short test clips, frames and tracking state are handled on the device; the current client does not upload these camera files to aiRef cloud storage. Temporary references and clips are removed when their setup or playback session ends, with best-effort cleanup if the app or operating system is interrupted.

You can keep score manually without camera access. Before using a camera around other people, explain the filming and follow the venue's rules. The app is not a tool for covert recording.

04

Ask the ref and AI service records

When you choose the rules companion, your question and the relevant bounded rules or match context go through the server gateway to Google Vertex AI's EU endpoint. The current rules surfaces reject inline image, video and audio attachments.

Server operation records can retain the sanitised request, result and usage information so that a retry is handled safely and spending limits work. These records are different from the short local conversation history. The gateway marks operation records to expire after 30 days; physical removal is asynchronous rather than a guarantee of deletion at the exact expiry instant.

05

Email, security and purchases

Early-access entries and account email choices can include your email address, age confirmation, accepted notice versions, optional-news choice, source, status and timestamps. Account service emails and optional product updates have different purposes. Optional product updates require their own choice and include an unsubscribe route. Mailgun's EU service processes recipient addresses and messages to deliver email; keyed hashes in some service records do not mean your address is never processed in readable form.

Authentication, App Check, installation and operational records help secure the service, investigate faults and enforce allowances. The app does not use Firebase Analytics or Crashlytics. The backend still keeps security and operational records.

Where purchases are offered in an admitted build, the selected store or Stripe handles payment details. The service receives the identifiers and purchase status needed to provide the entitlement and prevent duplicate credit, rather than your full card details. This pre-release notice does not claim that a purchase or payment method is currently available to the public.

06

Where records are held

The service uses Firebase Authentication, Firestore, Cloud Storage, Functions and App Check, Google's Vertex AI and the email or payment providers described above. Cloud Storage holds short-lived account export files. The service is configured to use Firestore in the EU multi-region, Functions in europe-west1 and model requests on the EU endpoint.

Providers and their support operations can process some information outside the UK. A configured service region is not a promise that every identity, support, payment or security record remains in that region. You can contact us for the safeguards and retention information relevant to your request.

07

Export, erasure and other rights

Account settings lets you prepare a portable account export and request permanent erasure. Export files are owner-only and the server's download authorisation expires after 15 minutes. The file you download or share becomes your own copy to manage.

Account erasure is a resumable server job that removes the account's stored records and files and deletes the Firebase identity last. It may take time to complete; a connection failure is not a promise of immediate deletion. Limited completion or security records can remain for their defined purpose, including a 30-day erasure receipt.

You can also ask us to provide, correct, delete or restrict your personal information, object where applicable, or provide a portable copy. We may verify ownership and will respond within the applicable statutory period, normally one month. You can complain to the Information Commissioner's Office.

Google Firebase privacy and security

Contact the UK Information Commissioner's Office

Contact

Questions about this policy

Email support@snowylakes.com.

Back to

aiRef

Clear when it knows. Clear when it's close.