We collect an email address when you join the offer-alert list. If you create an account or use Google sign-in, our authentication provider supplies the account identifier, email address, login provider, and basic profile information needed to identify your profile and save your reward-site progress. We record login timestamps and a sign-in count for account operations and security. Daily Run users may save a selected-site list, completion reminders, per-platform completion-cycle counts and link preferences, and optional self-reported cash-out entries containing a platform name, withdrawal amount, related deposit amount, payout method, short note, pending or received status, and timestamps. XClaims also stores XP events, level progress, earned achievement identifiers, a unique invite code, an optional user-chosen public username, and—if an invite is accepted—the account identifiers connecting inviter and invited account. A registered username appears in the user’s shareable XClaims invite URL; email addresses do not. Completion-cycle counts let XClaims stop repeatedly opening signup links after an account appears established. We do not receive your Google password. A contact or correction request may include your email address, subject, platform name, and message.
How we use it
We use this information to provide requested alerts, save account preferences, remember dismissed in-site notices, separate pending cash-outs from confirmed received withdrawals, calculate private cash-out summaries, award non-cash progress XP, prevent duplicate XP awards, calculate direct and all-depth referral totals, respond to questions, investigate corrections, prevent abuse, and operate the site. Referral dashboards show counts, not the names or contact information of downline members. Authorized administrators can review limited account-operation summaries, account status, and administrative roles. Administrative changes are recorded in an audit history. We do not sell personal information.
Service providers and external content
The site relies on OpenAI Sites for hosting, Supabase for account authentication, and database and infrastructure providers to deliver these functions. If you choose Google, Google processes the login under its own privacy terms. Company icons are currently loaded through Google’s favicon service, which means the visitor’s browser may send standard request information such as an IP address and user agent to Google. Outbound platforms have their own privacy practices, and their policies apply after you leave this site.
Cookies and authentication
Authentication and hosting services may use cookies or similar storage needed to keep you signed in, maintain security, and deliver the site. An XClaims invite link or approved creator portal sets a temporary, essential referral-code cookie and random creator-session reference for up to 30 days so a new account can be attributed after sign-in; they are removed when processed. The casino directory can store your voluntarily selected state in your browser, while signed-in users can separately save a state preference to their account for availability warnings. Our optional first-party analytics use an anonymous session identifier and a pseudonymous browser identifier that distinguishes new from returning visits. We measure page journeys, broad traffic sources and campaign tags, coarse country and state/region codes, rounded screen-size and input categories, scroll and time-based engagement, directory filters, outbound platform clicks and link-routing choices, newsletter conversions, saved-list actions, and site errors. Approved creators can see aggregate portal visits, traffic sources, device groups, platform clicks, and attributed XClaims signup totals; they do not receive visitor identities or email addresses. We also separate preview or automation signals from likely human activity. With separate consent, Meta and X campaign pixels may receive page views, outbound platform-click events, and newsletter conversions after their account IDs are configured. XClaims does not send those providers account emails, saved winnings, balances, wagers, notes, or external-platform activity. We do not store IP addresses, balances, wagers, full user-agent strings, precise locations, or activity inside an external gambling platform in XClaims analytics, and analytics records are not joined to account email addresses.
Retention and choices
Anonymous analytics events are retained for up to 13 months. Newsletter subscriptions are retained until you unsubscribe, and profile information—including Daily Run selections, reminders, XP history, achievements, referral relationships, and self-reported cash-outs—is retained while the account feature is in use. Pending cash-outs and legacy winnings entries can be removed from Daily Run. Confirmed received withdrawals are locked in the tracker to preserve the confirmed total, but you may request correction or removal through the Contact & Corrections form. Administrative audit records and correction requests may be kept as long as reasonably needed for security, accountability, and dispute review. You may also ask us to remove a newsletter subscription, profile record, or submitted request there. Global Privacy Control and Do Not Track disable optional first-party and campaign measurement.
First-party analyticsOn for this browser
Meta and X campaign measurementOff for this browser
Security and children
We use reasonable safeguards, but no online service can guarantee absolute security. XClaims is intended for adults age 18 or older and is not directed to children.
Policy changes
If our collection or use of information changes, this page will be updated with a new effective date. Material changes should be explained before they take effect when practical.