Privacy policy.

Account information

When you create an account, we collect:

• Username
• Email address
• Hashed password (we never store your password in plain text)

Game statistics

We collect and store your game performance data, including:

• Puzzle completion rates
• Win/loss records
• Streak information
• Leaderboard rankings
• Submitted guesses, puzzle identifiers, and answer-checking results
• Hint counts, attempt counts, play duration, and gameplay timestamps
• Achievement progress, game session data, and Journey XP, levels, and badges

Usage and device information

We use analytics services to understand how you interact with our service:

• Vercel Analytics for web performance and user behavior
• MongoDB event tracking for game analytics
• Account-linked login and return events, and returning guest identification
• Native daily-play events: when a daily puzzle is opened and its entry path, whether a daily puzzle is finished, whether the Plus offer is viewed, and whether a reminder is successfully scheduled, an optional rating after the daily result is revealed, when sharing starts or iOS reports that a share activity completed, and a verified session restore for the current official daily puzzle

The iOS app stores a random device identifier in the Keychain and sends it to our servers to recognize returning guests. It also sends your timezone for daily puzzle boundaries and streaks. We associate gameplay and statistics with your account or guest account. Our service processes request IP addresses for security and rate limiting and stores IP-derived hashes on guest records.

Daily engagement events are linked to your account. Their stored fields are limited to the event type, local puzzle day, server-recorded time, and, where relevant, the entry path, finish outcome, or one of four optional puzzle ratings. The server also records when an authenticated session restores the current official daily puzzle. We use that timestamp with a later correct-solve event to calculate an aggregate median elapsed wall-clock time by puzzle date, shown to administrators only when at least five qualifying solves are available. Wall-clock time includes idle and background time; it does not measure active play or thinking time. A failed event write may be retried on a later restore, so the interval begins at the first recorded restore. The `share` entry path identifies a daily open attributed to a Rebuzzle share link. If you change your rating, the latest choice replaces your earlier choice for that account and puzzle day. These event records do not contain puzzle IDs, answers, guesses, explanations, journal notes, email addresses, reminder text, share contents, recipients, or the destination you choose. We use them to understand daily play and improve the game; ratings are self-selected and are not treated as objective difficulty measurements. An iOS-reported share completion does not confirm delivery or a recipient opening the link. When the web game reports a share-attributed open, the server also records the first accepted daily guess and terminal outcome for that same account and puzzle day. These account-day overlaps do not identify a recipient or prove that the sender and player are different people.

Information stored locally by the iOS app

Journey syncs a limited completion summary to your account: puzzle dates and IDs, solved or failed outcomes, attempt counts, optional hint counts, completion times, and the timezone used for the daily reset. It does not include your answers, submitted guesses, explanations, or journal notes. With a registered Rebuzzle account and current Plus access, journal note text is sent to Rebuzzle and stored with your account and puzzle ID so it can sync across your devices. The iOS app also keeps a local copy for offline use. Guest notes remain on the device until that guest account is upgraded; notes are not merged when you sign in to a different Rebuzzle account. Unsent drafts, cached puzzle results, and reminder preferences are stored locally. Journal notes are not included in analytics or prompts to AI providers. If you share a result using the system share sheet, the image or spoiler-safe text includes the puzzle date, result, attempt marks, hints used, and a Rebuzzle link. The destination you choose handles the content you share. Device backups may also include local app data, depending on your device and backup settings.

Resend

We use Resend to send transactional and notification emails. It processes recipient email addresses and email content. Achievement emails can include your username, achievement details, and progress.

Vercel

Vercel provides hosting and website analytics. Hosting services process request metadata, which can include IP addresses, requested paths, response status, and timing. Website analytics are separate from the account-linked gameplay and login events stored by Rebuzzle.

AI Gateway and model providers

Some submitted guesses are sent through Vercel AI Gateway to an AI model provider for answer checking. Eve’s short reactions also use a guess, puzzle type, and score category. These prompts do not intentionally include your account ID or email address, but anything you type in a guess may be included. Journal notes are not sent to these AI providers.

The providers configured for these features include Google, with OpenAI and xAI available as answer-checking fallbacks. A request does not necessarily use every provider. Provider processing is separate from data stored in your Rebuzzle account.

Apple and Rebuzzle Plus

Apple processes purchases of Rebuzzle Plus. The iOS app checks purchase entitlements through StoreKit and does not ask for or receive your payment-card details. Plus access is required to sync journal notes with a registered Rebuzzle account. Restoring a purchase restores Plus access; Rebuzzle stores the synced note text, not Apple. Apple handles purchase records under its own policies.

MongoDB

We use MongoDB to store your account information, game statistics, account-linked journal notes for eligible Plus players, and analytics events. Journal note records contain the Rebuzzle account ID, puzzle ID, note text, revision number, and update time. We do not include note text in analytics or application logs.