Analytics, Cookies & Location Notice
Effective Date: June 6, 2026
This Analytics, Cookies & Location Notice explains how Level X Poker LLC uses cookies, local storage, analytics identifiers, feature flags, experiment exposure records, dashboards, and location-related data across levelxpoker.com, forwarded or related domains such as lvlxpoker.com, and related Services.
This notice supplements the Privacy Policy. If there is a conflict, the Privacy Policy controls unless this notice gives more specific information about analytics, cookies, or location handling.
This notice is specific to analytics, cookies, feature flags, experiments, dashboards, and location handling.
1. Why We Use Analytics
We use analytics to understand whether the Services are working, where users encounter friction, which tools and pages are valuable, whether experiments improve the product, and whether signup, checkout, study, support, and community workflows are reliable.
- Measure page views, surface views, tool starts, signups, checkout events, subscriptions, onboarding, course progress, and product engagement.
- Detect frontend errors, API errors, slow pages, broken flows, failed checkouts, and reliability issues.
- Evaluate GrowthBook feature flags and experiments by comparing exposure records with downstream outcomes.
- Build internal Superset dashboards and reports from first-party ClickHouse analytics data.
- Exclude or separate internal/admin traffic where practical so dashboards better represent real users.
2. Current Analytics Stack
Our current analytics setup is primarily first-party and operational. It includes:
- ClickHouse analytics tables that store event records, flag evaluations, experiment exposures, metrics, and aggregate reporting data.
- GrowthBook for feature flags, experiments, assignment diagnostics, and experiment analysis.
- Superset for internal analytics dashboards, reports, alerts, and administrative business intelligence.
- Application-side analytics code that sends route, event, context, performance, and error metadata to Level X Poker endpoints.
- Server-side analytics code that records signup, checkout, subscription, API, and other backend events.
GA4 and OpenReplay are currently deferred or disabled unless later configured and disclosed.
4. Analytics Events We May Collect
Analytics events are structured records about what happened in the product. Depending on the feature, events may include:
- Event name, timestamp, route, page, product surface, section, referrer, environment, app version, and event properties.
- User ID for logged-in users, anonymous ID for visitors, session ID, device ID, and selected account or subscription context.
- Browser, device, operating system, viewport, language, timezone, network context, user agent, and IP-derived approximate region.
- Feature flag key, variant, value, experiment ID, exposure timestamp, and GrowthBook evaluation context.
- Signup, login, onboarding, pricing, checkout, subscription, tool usage, course, training, watch, support, community, bankroll, finance, and admin analytics events.
- Frontend error messages, API error summaries, performance timing, web vitals, request route, status family, and diagnostic metadata.
5. Data We Do Not Intentionally Put Into Analytics
Analytics should help us understand product behavior, not expose unnecessary sensitive content. We do not intentionally send the following into general analytics events:
- Passwords, password reset tokens, authentication tokens, API keys, private keys, or full OAuth access tokens.
- Full payment card numbers or full bank account numbers.
- Raw direct message bodies, private support message bodies, internal support notes, or private chat transcripts as general product analytics.
- Raw hand histories, full player notes, full finance documents, receipt images, or uploaded file contents as general product analytics.
- Government ID numbers, Social Security numbers, or unrelated sensitive personal information.
Support and beta feedback tools may separately capture screenshots, console logs, network logs, and page context when you submit feedback. Do not submit secrets or unrelated sensitive information in those tools.
6. Feature Flags and Experiments
We use GrowthBook feature flags to turn features on or off, roll changes out gradually, run experiments, and compare product variants. Examples may include marketing copy variants, signup calls to action, checkout flow variants, pricing copy variants, tool layout variants, analytics dashboard access, and administrative feature controls.
- A feature flag evaluation records which flag was evaluated and which value or variant was returned.
- An experiment exposure records which variant a user or anonymous visitor saw at a specific time.
- Exposure records are joined with events such as signup, checkout, tool start, revenue, errors, retention, or engagement to understand impact.
- Flags may be targeted by account state, subscription tier, environment, route, rollout percentage, or other product attributes.
7. Location Information
We may use three kinds of location-related information:
- Approximate location from IP address or request metadata, generally used for security, fraud prevention, operations, traffic analysis, and regional reporting.
- User-entered locations, such as poker venue names, online poker site names, trip locations, session locations, finance locations, or schedule locations.
- Precise browser geolocation only if you grant permission through your browser or device.
Precise geolocation is optional. You can deny or revoke it through browser or device settings. Some location-aware features may be limited if permission is denied.
8. Internal Access and Dashboards
Analytics data may be viewed in internal dashboards, admin pages, Superset dashboards, GrowthBook experiment results, alert reports, logs, and exports by authorized Level X Poker staff, contractors, or administrators with a business need.
- Access is intended for product improvement, support, reliability, security, billing operations, experiment analysis, and business reporting.
- Dashboards should focus on aggregate metrics, funnels, cohorts, trends, and operational signals where practical.
- Raw event access should be limited to people and systems that need it for diagnostics, security, analytics setup, or product operations.
9. Your Choices
Your choices depend on the type of data.
- Required cookies and essential analytics are used to operate, secure, debug, and improve the Services.
- Marketing emails can be managed from email links or account settings where available.
- Precise geolocation can be denied or revoked in browser or device settings.
- Browser cookies and storage can be cleared or restricted in browser settings, but some account features may stop working.
- You can request access, correction, deletion, or account deletion through account settings where available or by contacting privacy@lvlxpoker.com.
10. Retention
Analytics, flag, exposure, dashboard, and diagnostic records are retained for as long as reasonably necessary for product measurement, experiments, reliability, security, trend analysis, business reporting, legal compliance, dispute resolution, and operational history. Aggregated or de-identified records may be retained longer than raw records.
11. Future Analytics Services
If we enable additional analytics or replay tools in the future, such as GA4 or OpenReplay, we will configure them with appropriate privacy controls and update disclosures or consent behavior where required. Replay-style tools, if enabled, should be masked and configured to avoid capturing sensitive inputs, private account content, payment details, secrets, or unnecessary personal data.
12. Contact
Questions about analytics, cookies, location, or privacy can be sent to privacy@lvlxpoker.com. Entity: Level X Poker LLC. Mailing address: 150 W 4800 S #30, Murray, UT 84107.