Privacy Policy

Last updated: August 15, 2026

This Policy explains what Raise collects, why we use it, who can see it, how long we keep it, and the controls available to you. Raise is an 18+ Discord game using virtual coins only. For any privacy request, contact privacy@raisebot.cc.

1. Information We Process

• Discord identity and context: Discord user ID, username, avatar when provided, server and channel identifiers, server membership needed to authorize access, Activity instance identifiers, and server-scoped roles.
• Game and virtual-economy data: virtual balance and ledger, bets, stakes, outcomes, virtual payouts, fairness seeds and nonces, interactive game state, table membership, seats, actions, bingo cards and awards, poker escrow movements, and completed game records.
• Progress and preferences: XP, level, streaks, tasks, milestones, badges, rewards, records, tournaments, season standings, daily Core and weekly-consistency progress and replay receipts, favorite game, onboarding journey, reminder choices, breaks, and self-exclusion state.
• Activity and social features: room host or pit-boss role, session timing, room counts and recaps, share-link creation and opens, referral attribution and qualification, and ambassador invite use.
• Product and installation events: limited events such as an install-page visit, sign-in or authorization stage, game selection, accepted or rejected wager, settled result, reminder open, or feature experiment assignment. Installation events use a campaign name and a one-way hash of a random first-party browser identifier; they do not store your IP address or the identifier held by your browser. Player events may be linked to your server-scoped player account.
• Safety and support:staff notes and tags, access restrictions, abuse-review evidence, the text and error reference you deliberately submit in a private support ticket, support replies, the ticket's Discord-DM consent receipt, reliability records, and audited administrative actions where they concern your account.
• Operator announcements:an authorized operator-authored channel message, selected server and channel snapshots, approved-destination records, and audited delivery status or bounded error code. One batch may address multiple explicitly selected servers. A same-payload preview may be sent privately to the authenticated operator's Discord account; Campaigns does not bulk-message player DMs.
• Server administration:current server-admin assignments, the latest authenticated back-office entry time across the administrator's current assignments, the last observed Discord display name, and audited administrative changes. This marker does not identify which server was viewed. Raise does not keep a page-view history, route, IP address, device identifier, or session token for this activity marker.
• Technical data: strictly necessary session cookies, a short-lived first-party installation-attribution cookie, authentication tokens, rate-limit data, error diagnostics, and performance timing. Player performance telemetry is stored without a Discord user ID.

Raise does not ask for or store your Discord password. It does not read or store general user-generated Discord message content. It stores only support fields you deliberately submit through the private ticket form and message copy authored by an authorized operator for a reviewed channel announcement. It does not collect payment-card, bank-account, cryptocurrency-wallet, deposit, or withdrawal information. Raise coins cannot be purchased or converted into value.

2. Where Information Comes From

Information comes from Discord when you authorize the app or use it in a server, from the actions you take in Raise, from server operators when they configure their server or support a player, and from Raise's own fairness, integrity, reliability, and progression systems. Discord OAuth access tokens are handled only as needed to authenticate a sign-in or Activity session; Raise stores its own short-lived signed session rather than your Discord password.

3. Why We Use Information

• Authenticate you and confirm the Discord server, channel, Activity instance, and membership context.
• Run games, maintain server-scoped virtual balances and progression, and recover interrupted sessions.
• Make completed results auditable and provably fair.
• Operate tournaments, rewards, referrals, sharing, player-opt-in reminders, and reviewed one-time channel announcements.
• Measure whether installation and product features work, troubleshoot failures, prevent duplicate actions, and improve reliability.
• Detect and review automation, collusion, restriction evasion, manipulation, and other abuse.
• Answer support, privacy, security, and account requests.

Raise does not use Discord data to build advertising profiles, send unsolicited marketing, or make automated real-world eligibility, credit, employment, insurance, or financial decisions.

4. Who Can See Information

• You: your private results, player profile, controls, and export.
• Discord server operators: player and integrity information only for a server they are authorized to manage.
• Raise platform staff: information needed for support, moderation, security, reliability, and game integrity, subject to role-based access and auditing.
• Discord:interactions and authorization data handled through Discord's platform are also processed by Discord under its own Privacy Policy.
• Bot directories:a listing service may receive Raise's aggregate server count and summed server member count so the public listing stays current. Raise does not send it member IDs, server IDs, balances, gameplay, or campaign visitor identifiers.
• Infrastructure providers: hosting, database, backup, and monitoring providers process only the information needed to operate and protect Raise.

We do not sell personal information, share it with data brokers, or provide it to advertising networks. We may preserve or disclose limited information when necessary to respond to a valid request, protect users or the Service, or investigate serious abuse.

5. Server Isolation and Public Surfaces

Player accounts, balances, history, and progression are separate for each Discord server. A server operator cannot browse another server's data. Authorized Raise platform staff may work across servers for support and integrity. Public or shared surfaces are limited to information intended for that feature, such as a live-table summary, leaderboard, shared invite, or completed Casino Night recap; private cards and unrevealed fairness secrets are not published.

6. Cookies and Authentication

The Raise website uses strictly necessary cookies for Discord sign-in. The signed web session lasts up to one hour. A campaign install link may also set a random, first-party attribution cookie for up to 30 days so Raise can measure whether that visit reaches installation and first use. It is HttpOnly, SameSite=Lax, is not shared with advertising networks, and does not record browsing outside Raise. The server stores only a one-way hash of its random value. The Activity uses short-lived Discord and Raise tokens to authenticate the current session. We do not use advertising cookies or cross-site behavioral tracking.

7. How Long We Keep Information

• Profile identity and preferences are kept while the player account is active and are removed or anonymized when a valid erasure request is completed.
• Virtual ledger, bets, fairness proofs, settled multiplayer records, and reward history are retained as integrity records. On erasure they remain attached only to an irreversible, server-specific tombstone rather than your Discord profile.
• Product and retention events are kept for no more than 400 days. Campaign-installation events are kept for no more than 90 days.
• Channel announcement batches, approvals, target snapshots, and delivery receipts are kept while needed for delivery, duplicate prevention, troubleshooting, and operator audit. Messages already delivered by Discord may remain under Discord's own controls and retention.
• Player performance telemetry is kept for no more than 7 days.
• A server administrator's latest back-office visit marker is kept only while that current server role exists and is removed with the role or a valid account-erasure request.
• Acknowledged error records are kept for no more than 30 days; unresolved error records are kept for no more than 180 days.
• Raise-controlled database copies of unanswered private support-ticket content are kept for no more than 180 days. Once Raise sends or may have sent an answer, those database copies are kept for no more than 90 days after the latest attempt. They are then redacted together with direct reporter, server, channel, message, and support-contact identifiers; only body-free timing, status, and audit receipts remain. Messages already delivered by Discord may remain in Discord under Discord's own controls and retention.
• Expired share destinations stop working automatically. Session and table metadata is kept only while useful for continuity, recap, abuse prevention, and integrity, and direct Discord identifiers are anonymized on erasure.
• Server-scoped, purpose-separated one-way identity hashes may remain to keep a ban, break, or self-exclusion enforceable and to prevent repeated Welcome Stack, House Rebuy, same-casino-day daily-coin claims, repeated first-action legacy treatment, or repeated first-week proration and starter weekly repair grants after erasure. They are not used as a player profile, login, or advertising identifier. A separate global one-way hash only prevents automatic owner lifecycle DMs after erasure.

8. Your Controls and Requests

• Download: export the player, gameplay, multiplayer, progression, referral, and Activity records available through /api/me/export.
• Anonymize: use your player privacy controls to remove your profile identity. Personal preferences, product events, and daily Core/weekly-consistency progress and receipts are deleted. Guild-level experiment contracts, arm assignments, first-exposure timing, and the server casino timezone frozen for that analysis remain without a player identifier so aggregate experiment history is not rewritten. One guild-scoped one-way continuity receipt also remains solely to prevent an erase/rejoin cycle from granting the one-time legacy first action, prorated first week, or starter weekly repair again. Integrity records remain under unrelated server-specific tombstones so balances and completed results remain internally consistent.
• Correct or ask: email privacy@raisebot.cc to correct information, request additional records, or ask how information is used. Internal security, abuse, or other-player information may require review before it can be provided.
• Reminders and play controls: reminders are opt-in and can be disabled. Break and self-exclusion controls are available inside the Activity.

Depending on where you live, you may also have privacy rights that cannot be removed by this Policy. We may need to verify that a request belongs to the Discord account concerned.

9. Age Eligibility

Raise is intended for people aged 18 or older. We do not knowingly collect personal information from anyone under 18. If you believe a person under 18 has used Raise, contact privacy@raisebot.cc so the account and relevant data can be reviewed.

10. Security and Processing Locations

Raise uses access controls, short-lived authentication, audit records, data minimization, and technical safeguards designed to protect information. No online system can guarantee absolute security. Information may be processed where Raise and its infrastructure providers operate; we require providers to protect it and use it only to deliver their service to Raise.

11. Changes and Contact

The date above identifies the current Policy. For a material change, we will provide a reasonable notice through the Service where practical. Raise is the name of the Service operated through raisebot.cc and the Raise Discord application. Privacy requests go to privacy@raisebot.cc; support, abuse, and security reports may also be sent to support@raisebot.cc.