Effective: October 5, 2026
This policy explains how Rich City Hoops (“RCH”) uses cookies, local storage, service-worker caches and similar browser technologies across the website and installable app.
RCH and its authentication providers use browser storage and cookies when needed to keep you signed in, maintain a secure session, complete account recovery and help prevent unauthorized access. Disabling necessary storage can prevent authenticated features from working.
RCH may store preferences on your device so the service can remember interface choices and support installable-app features. The progressive web app may also cache selected static files so navigation remains fast and updated versions can be detected reliably.
If paid features are enabled and you choose to use them, payment checkout may be provided on a payment processor's hosted pages. That provider may use its own necessary security and payment technologies under its own privacy and cookie policies.
RCH uses first-party, section-level measurements to understand which areas of the service are useful. We may store a randomly generated per-tab session identifier in browser session storage and record broad categories (for example, Runs or News) in ten-minute intervals. Where a member is signed in, the measurement can be associated with the account for aggregate reporting. We do not include precise location, raw visited URLs, search terms or IP addresses in this analytics feature, and we honor supported browser Do Not Track and Global Privacy Control signals.
Analytics reports are limited to verified administrators and show aggregate counts, not individual browsing histories. If optional advertising or analytics technologies that require additional consent are introduced, RCH will provide the controls and disclosures required for that use.
You can control browser cookies and site storage through your browser or device settings. Clearing storage may sign you out, reset preferences, remove cached app files or require RCH to rebuild local app data.
We may update this policy as the platform or its service providers change. The effective date above identifies the current version.