Privacy Policy

Rift Atlas is an unofficial fan project for Riftbound. You can browse much of the site without an account, and Rift Atlas does not sell personal data. Account, multiplayer, customization, support, analytics, and membership-linking features process the information described below.

When you browse Rift Atlas, the hosting and analytics stack may process technical data such as IP address, approximate location, browser and device information, referring pages, visited URLs, and timing or interaction data.

When you create or use a Rift Atlas account, Clerk provides authentication and Rift Atlas may handle your Clerk account identifier, verified email or other sign-in details, display name, avatar, saved decks and other account content, multiplayer identity, feedback, account roles, session information, and report or moderation records needed to secure and operate account features. If you link Discord or use in-game community help, Rift Atlas also handles the linked Clerk and Discord identifiers, Discord display name, rules questions, community answers and ratings, community Judge chat messages and their audience, bug reports, limited room or app context, delivery status, and Discord thread identifiers. Public and private rules questions that pass submission checks are posted to the configured Rift Atlas Discord forum; private changes only who can see the question, thread link, and answer inside the match.

When you submit a community rules question or bug report, Rift Atlas may send the submitted text and submission type, plus the submitting display name, to OpenAI to create a short title and check for spam, unrelated or unintelligible content, and severe abuse. This also applies to Private questions. Ordinary match chat is not included in these automated submission checks. Rift Atlas does not add account IDs, room details, or gameplay state to that request, but the text includes whatever you choose to write. Generated titles and automated submission decisions are stored with the submission. Severe abuse in a submission or display name can trigger an indefinite account ban; moderation evidence may be retained for enforcement and appeals. AI does not answer rules questions; answers come from community members.

If you choose to connect Metafy, Rift Atlas receives your stable Metafy user identifier and may receive profile details, community and tier identifiers, membership status, lifecycle events, and verification timestamps. Rift Atlas uses the stable identifier rather than email to link the two accounts. Clerk retains the OAuth connection credential; Rift Atlas does not copy it into its application database and does not receive your payment-card details.

Rift Atlas stores your Simulator customization selections and derives eligible tier badge, nameplate, and board-cosmetic access from the current linked membership. Other players and spectators may receive only the approved tier emblem, current-tier membership month count, and approved public cosmetic identifiers needed to render a match, not your Clerk or Metafy identifiers, email address, or billing details.

When you use the contact form or send email to Rift Atlas, the site may receive the name, email address, subject line, and message content you provide, along with related delivery metadata needed to process or reply to that message.

The contact form also stores an unsent draft in your browser's local storage so you do not lose your message before submission. That draft stays on your device until it is sent, cleared, or manually removed.

Rift Atlas uses information to:

• operate, secure, and improve the site,
• measure traffic and feature usage,
• authenticate accounts, operate multiplayer, customization, community rules help, and bug reporting, verify membership access, attribute community answers, and prevent duplicate or abusive account linking,
• review reports, enforce account sanctions, deliver warnings and sanction updates, and process ban appeals,
• respond to support requests, feedback, and partnership inquiries,
• debug delivery, abuse, or reliability issues.

Rift Atlas uses Clerk for authentication and connected-account verification, Convex for account-linked application and moderation data, Vercel for hosting and web analytics, Cloudflare for realtime game traffic and service delivery, Discord for community rules and bug-report forum threads, OpenAI for short submission titles and checks of community submissions and display names for spam, unrelated or unintelligible content, and severe abuse, Resend for contact-form delivery, inbound email, and transactional moderation notices, and Metafy for optional membership billing and verification. These providers process data under their own terms and privacy practices or on behalf of Rift Atlas as needed to provide their services.

Rules questions and bug reports sent to Discord are visible to members who can access the configured Rift Atlas Discord forum, even when a rules question is marked Private inside a match. Metafy controls subscription checkout, payment processing, cancellation, and its community service. Other third-party links on the site, including card pricing or external play tools, are likewise governed by the privacy practices of those third parties once you leave Rift Atlas.

Rift Atlas does not use ad-tech tracking. The site uses cookies or similar storage for authentication, security, preferences, account features, analytics, and browser-local drafts or game data. Metafy may use its own cookies and storage when you visit or connect its service.

Account, connected-account, customization, moderation, community-help, bug-report, and minimal webhook records are retained while needed to operate and secure the service, preserve settings and contribution history, reconcile access, prevent duplicate links or abuse, resolve disputes, or meet legal obligations. Expired one-time link challenges and stale delivery cooldown records are cleaned up; limited records of account links, cases, generated titles, automated submission decisions, delivery, contributions, and audits may remain for those purposes. Discord threads and other provider-held data follow the applicable community settings, operational needs, and provider retention policies.

Connecting Metafy or Discord is optional. You can disconnect Metafy from Rift Atlas to stop membership verification and immediately disable linked entitlements, but disconnecting does not cancel your Metafy subscription or stop billing; manage those actions on Metafy. You can clear browser-local data through browser controls and contact Rift Atlas to request access, correction, deletion, or help removing or moving a connected-account link, subject to records that must be retained for security or legal reasons.

Rift Atlas may update this policy as the site changes. Material updates will be reflected by changing the "Last updated" date on this page.

Questions about this policy can be sent through the contact page or by emailing hello@riftatlas.com.