Cookie & Device Storage Policy

Which technology applies

The native CourtLoop app needs on-device storage for account sessions and app operation. We identified no first-party advertising cookie, cross-app advertising identifier integration or optional usage measurement SDK. Player performance analytics calculate sports results. Browser-based Google sign-in, external maps and any separately hosted website have their own storage behavior.

Authentication and local records

The app uses the operating system’s secure storage when available for Supabase authentication state. A memory fallback lasts for the running process. Access tokens have provider-controlled lifetimes and can refresh. Signing out ends the local account session.

Earlier session archives, in-progress scores and preferences such as theme can persist in local SQLite or its key-value store between launches. Their useful life depends on the record, removal of app data and device behavior. Account deletion and local cleanup are separate actions.

Short-lived links and delivery identifiers

Signed avatar links can be used by a holder for their short validity period. Generated friend and session keys expire after five minutes and can be revoked. These mechanisms allow specific requested actions. Where push is enabled, a device token routes notifications until it is replaced, invalidated or disabled under the service configuration. A camera permission or notification permission is an operating-system choice.

Your choices

Use CourtLoop’s notification preferences and the device’s settings for alerts and camera access. Choose manual key entry to avoid camera use. Manage provider browser cookies in the browser or provider account. Clearing app data can erase local archives and preferences; save any authorized backup first. If a site or later release adds optional tracking, each provider, purpose, duration and withdrawal control will be described before it is enabled where consent is required. Direct storage questions to support@clavisplus.com.