Privacy policy

Who is responsible

Gor Baghramyan, based in California, United States, operates QuestForge and is responsible for the personal information described here. Contact us for privacy, access, deletion, support or security reports.

Information and sources

• Website accounts: display name, email, password hash for email sign-in, provider account identifiers/profile information, linked sign-in methods and session records. Google or Discord sign-in can provide a name, email and profile image; authorization tokens may be stored to operate that connection. We do not receive your Google, Discord or Riot password.
• League profiles and games: submitted or locally detected Riot ID, PUUID and other game identifiers, region, profile icon, level, mastery, ranked information, match details and timelines. Riot-sourced match payloads can include other participants’ identifiers, teams, champions, statistics and timestamped game events. The companion’s own-history importer uploads a reduced set of your statistics rather than other players’ raw history.
• QuestForge activity: accepted quests, goals, eligibility evidence, results, XP, levels, badges, daily claims, streaks, time zone, saved match reflections and preferences. These are product records, not Riot account rewards.
• Connections and security: installation/device identifiers, scoped credentials or their hashes, connection times, app versions and permission/buffer metadata. Authentication sessions can contain IP addresses and user-agent details. When a later sign-in method is added, security context can include a hashed IP address and country inferred by the host. A hashed identifier remains potentially personal information.
• Requests and delivery: information you send for support and the technical request details processed by hosting, authentication, email and asset-delivery services, such as IP address, browser/OS, requested resource and time. Do not send us passwords, developer keys, pairing secrets or private chat logs.

Sources include you, your chosen sign-in provider, Riot’s web APIs, local League interfaces and our service operations. Public champion/item reference does not require a website account. Your dashboard and private reflections are intended for your authenticated account; they are not a public player-profile directory.

Purposes and legal bases

Where laws such as the GDPR require a legal basis, we distinguish the following purposes:

• Requested service: account access, imported match review, companion sync, quests, rewards and your saved preferences are processed to provide the features you request and perform our service agreement.
• Security and reliability: proportionate authentication, access control, abuse prevention, the bounded operational log and troubleshooting serve our legitimate interests in protecting the service and its users, subject to applicable balancing and objection rights.
• Optional research and uploads: your separate permission controls local research recording and requested diagnostic/support uploads. Declining them does not prevent ordinary quests or essential sync. You can withdraw permission in companion Account settings.
• Legal requirements: information may be processed when necessary to comply with applicable law or respond to valid legal process.

We do not currently sell personal information or share it for cross-context behavioral advertising. We do not use your gameplay to train a generative AI service in the current product. Reading this policy or accepting the Terms does not enable optional recording, uploads, marketing or future data uses.

What the companion reads and syncs

The Windows app reads local League identity, phase, champion selection, available players, supported live game measurements and your recent game history. It uses these to show current context and send reduced account-bound progress evidence. Essential connection, history, quest and reward requests are separate from optional research uploads.

Local detection can create or resume a separate device-scoped guest profile. Access to existing website progress requires approval from your signed-in website account. Guest progress is not automatically merged by matching a Riot name. Local League identity remains client reported; browser approval is not Riot Sign On or verified Riot ownership. A companion session does not provide website credentials. Switching League profiles clears private app context before the next profile syncs.

CPU use and network-interface byte counters are sampled locally to reduce background work under load. Raw scheduling readings stay on your PC. Only broad workload-change reasons may enter an optional support-log upload. This does not inspect network packet contents or measure game-server ping or rendering FPS.

Optional research and support logs

Gameplay research: a rolling local buffer of up to 10 MiB stores selected client phases, champion/role/queue context, your measured scores and visible event types/times. It does not intentionally record private chats, voice, video, wallet/loot contents or authentication secrets. This buffer is separate from essential cache, credentials, downloaded updates and the support log; it is not a 10 MiB limit on the whole app.

Support log: a separate rolling local file of up to 1 MiB records app starts/exits, error types, method names and workload reduction/recovery. It excludes exception messages, file paths, account names, raw gameplay and chat. The local operational log is enabled for reliability; uploading it is optional. An unclean exit does not prove a crash.

Research recording and requested uploads start off unless you have explicitly chosen them under the current notice. Older preselected choices need review. Support can request uploads only under your sharing permission; research uploads additionally need recording enabled. Transfers wait for idle/lower-load conditions, with best-effort cancellation if play starts, profiles change or permission is withdrawn.

Server acknowledgement removes the confirmed uploaded chunks or log prefix locally, preserving newer log entries. Rolling caps can discard the oldest local entries without uploading them. You can clear the buffers in companion Account settings. Disabling an option does not by itself erase files already retained or copies already received; use Clear or request deletion. Silent updates do not grant new permissions.

Cookies and local storage

We currently use only essential website cookies for sign-in, session security and account functions. We do not set advertising or behavioral-analytics cookies. There is no optional website tracking category to enable, so we do not show an Accept all banner. Sign-in cookies normally last up to seven days and may be renewed while you use your account; choosing not to stay signed in uses a browser-session cookie. Short-lived security cookies support sign-in and provider redirects. You can sign out or remove cookies in your browser; blocking them can prevent sign-in. Your sign-in provider has its own storage policy. The native companion stores settings, limited cache, pending own-game evidence, device/connection credentials and update files locally. Windows DPAPI protects its saved connection credentials; ordinary cache, research and log files are not promised to be encrypted.

Startup is an installer choice and can be changed in Account settings. Minimizing or closing the app normally leaves it running in the tray; choose Quit to stop it. Uninstalling may leave local data in your Windows profile, including the legacy %LOCALAPPDATA%\Riftbound\Native directory retained for upgrades.

California tracking disclosure: QuestForge currently includes no advertising pixels or third-party behavioral-analytics SDKs. We do not change essential service processing in response to the browser’s Do Not Track signal. We do not sell/share data for cross-context advertising, so we do not use Global Privacy Control as permission for any such processing. Browsers or the companion may contact external asset providers, which receive normal connection details under their own policies.

Who receives information

Authorized operators/admins can access service records and, when enabled and requested, uploaded diagnostic data for support and operations. We use OVHcloud for hosting, private MySQL for application storage, Google/Discord when you choose their sign-in, and Resend when configured to send password-reset email. Riot supplies game data and assets; some app assets can load from CommunityDragon or other explicitly referenced content hosts. Direct requests disclose normal network details to those hosts.

These services receive information needed for their functions and can have their own independent responsibilities. We do not share your game history with a sign-in provider merely because you use it to log in. We may disclose necessary information for valid legal requests or protection against abuse. We do not sell the service’s Riot API data as a third-party data-broker product.

See Riot’s privacy notice, OVHcloud, Google, Discord and Resend. These providers’ policies do not replace our responsibility for QuestForge.

Retention and deletion

• Account, guest, match and progress records: currently kept for the relevant service features until removed through available controls or a handled deletion request. There is no general automatic inactivity deletion schedule yet. We do not claim that pseudonymous guest progress is anonymous.
• Diagnostic uploads and support snapshots: expire seven days after receipt; database cleanup is asynchronous. Diagnostic/support inventory expires after 90 days without a new report. Local caps are size-based rather than fixed time limits.
• Sign-in-method security context: hashed address/country context expires after 30 days. Credential-link history and authentication records have separate operational retention; session expiry alone is not a guarantee that every stored record is immediately erased.
• Riot disconnect: the current flow removes the linked account, imported matches/raw matches/timelines/profile snapshots, sync runs, quest evaluations, non-daily reward transactions, tracker installs/observations, practice plans and saved match reflections. Your website login and daily-login reward transactions remain. Some acceptance, preference, security, diagnostic and inventory records are outside that flow.

Revoking companion access or pausing sync is not full account erasure. Settings → Account data & privacy offers a data export and an account-deletion request. Export and requesting deletion require a recent sign-in. Deletion requests are reviewed; submitting one does not instantly erase your account. You can also request access, correction or deletion by email. We may need reasonable identity verification and may retain specific records where law or a justified security purpose requires it. We will explain applicable exceptions rather than promise that every copy or third-party backup is immediately deleted.

Your choices and rights

You can change supported account/time-zone settings, disconnect Riot imports, pause/revoke companion sync, disable startup/research/sharing, clear local buffers and stop or uninstall the app. Withdrawal of optional permission affects future processing and does not undo lawful past processing.

Depending on applicable law, you may request access, a copy or portability, correction, deletion, restriction, or objection to processing, including processing based on legitimate interests. You can complain to the relevant privacy regulator and use an authorized agent where allowed. We do not penalize you for exercising applicable privacy rights. Contact us from your account email where possible; a Riot name alone is insufficient proof for a private account request. We respond within applicable legal deadlines and explain any lawful extension or refusal.

International processing and security

The operator is in California. Hosting, database, email and other providers may process information in the United States or other countries. Local data-protection rules can differ. Where applicable transfer law requires safeguards, those safeguards must cover the relevant transfer; accepting this notice is not itself a substitute for a lawful transfer mechanism. Contact us for information about the arrangements relevant to your data.

Access controls, HTTPS for service traffic and Windows-protected companion credentials reduce risk. Local League endpoints use their local self-signed certificates. No system is completely secure, and these measures do not establish Riot ownership verification. Please report suspected unauthorized access promptly. Required breach notifications will be handled under applicable law.

Age eligibility

QuestForge accounts and companion progress sync are for people aged 16 or older. We do not knowingly offer these features to younger users. If local law requires a higher age or additional valid parental involvement, those requirements also apply. We do not currently operate a verified parental-consent service.

If you believe we hold information about an ineligible child, contact us so we can assess the report and take appropriate action. We request a 16+/Terms declaration before website signup and first companion progress sync; this is not verified age or parental consent. The service does not infer age from League or a sign-in provider.

Changes to this policy

We update the date when we revise this policy. Material new uses require appropriate advance notice and, where required, fresh permission before they start. Adding a future feature to a plan does not authorize collecting its data today.

Notice version: 2026-10-29. For Riot account deletion or Riot privacy requests, contact Riot separately; deleting QuestForge records does not delete your Riot account, and a Riot deletion request does not automatically reach us.