Giveaway Privacy Notice

• email address and email-confirmation records;
• Twitch username and Discord username;
• registration, referral relationship, ticket codes, confirmation state, eligibility and Internal classification;
• transactional email queue, provider-delivery status, and resend audit records; and
• limited request and security information used for rate limiting, abuse prevention, and troubleshooting.

RaidReady uses this information to create and confirm registrations, issue first and referral tickets, provide the private participant dashboard, send required transactional emails, investigate fraud, prepare the eligible ticket export, conduct the manual draw, contact selected participants, and maintain an operational audit.

Brevo receives the registered email address and a private single-use action link for four customer scenarios: confirm the registration, open the confirmed first-ticket dashboard, notify the participant of a new referral ticket, and recover dashboard access. Giveaway registration does not request or record marketing consent.

Supabase stores the giveaway registration and ticket records. Brevo transports the transactional messages. Hosting and security providers may process limited technical information required to operate the page. The authenticated delivery webhook stores only a job correlation, delivery event, provider message identifier, and timestamp—not the webhook email address, subject, IP address, or raw payload.

There is no public participant leaderboard. Email addresses, Twitch usernames, Discord usernames, referral relationships, and ticket numbers are visible only in the participant’s private dashboard where applicable and in the authenticated RaidReady admin console.

RaidReady retains giveaway records for administration, fraud prevention, fulfillment, audit, dispute handling, and applicable recordkeeping. Participants may request access or correction through RaidReady’s published support channels. Some evidence may be retained where needed to preserve ticket integrity, prevent duplicate entry, or meet an operational or legal obligation.

Private dashboard links are single-use and time-limited. Stored action tokens are hashed, mail payloads are encrypted before processing, new operational tables use forced row-level security, and admin exports require authenticated operational access.