Privacy Policy

LitRPG Next, operated by RedLit Reads, LLC ("we," "our," or "the site"), is committed to protecting your privacy. This policy explains what data we collect, how we use it, and what choices you have. We keep it straightforward: we collect what we need to run the site, we don't sell your data, and we don't use it for advertising.

Account information. If you create an account, we store your email address and authentication credentials via Supabase. If you sign in with Google, we receive only your email address and public profile information from Google.

Tier list and preferences.When you build a Taste Profile, your tier list rankings, genre preferences, and free-text preferences are stored locally in your browser (localStorage). If you're signed in, this data is also saved to your account on our servers so it syncs across devices.

Reading history. When you mark volumes as read or mark a series as Did Not Finish (DNF), that information is stored locally in your browser (localStorage). If you are signed in, it is also saved to your account on our servers so it syncs across devices.

Catalog feedback and suggestions.If you submit a tag correction on a series page, or suggest a new series via the "Suggest a Series" form, that submission is stored in our database along with your account ID so we can attribute and review it. Submissions enter a moderation queue before any changes are applied to the catalog.

Recommendation rate-limiting records. Each time you generate recommendations, a timestamp is stored in our database to enforce per-user rate limits. These records contain only your account ID and the time of the request; they are not used for any other purpose and are not retained beyond the rolling rate-limit window (one hour).

Usage data. Our hosting provider (Vercel) collects standard server logs including IP addresses, browser type, and pages visited. We also use Vercel Analytics and Vercel Speed Insights to measure aggregate page traffic and real-user performance metrics (such as page load times and Core Web Vitals). These tools are cookieless and do not track individual users or build user profiles — only anonymised, aggregated statistics are collected.

Error diagnostics. We use Sentry to automatically capture information about unexpected errors and application failures. When an error occurs, Sentry may receive the error message, stack trace, browser type, and — if you are signed in — your anonymised user identifier, so we can diagnose and fix the issue. Error data is not used for any purpose other than debugging and is retained for 90 days.

Username. You may choose a username when setting up your profile. If chosen, it is stored in our database and may be displayed to other users in community features. Usernames are permanent once set and must comply with our community guidelines. Choosing a username is optional — you may skip this step or set it later from Account Settings.

We use your data solely to operate and improve LitRPG Next:

• To authenticate your account and keep your session secure
• To generate personalized series recommendations using your Taste Profile
• To sync your tier list and reading history across devices when you are signed in
• To review and apply catalog feedback and series suggestions you submit
• To improve the catalog and recommendation quality over time
• To respond to support requests or bug reports you submit via the Contact page

We do not use your data for advertising, do not sell it to third parties, and do not share it with anyone except the sub-processors listed below.

You may choose to make your profile public in Account Settings. Users with a public profile may have their tier list visible to other readers in future community features, such as a "readers like you" discovery section. This setting is off by default — users who skip the profile setup prompt are treated as private.

You can enable or disable your public profile at any time from Account Settings. Disabling it removes your profile from community features as of the next page render.

When you request recommendations, your Taste Profile — including your tier list rankings, genre preferences, and any free-text notes — is sent to Anthropic's Claude API to generate personalized results. This data is processed under Anthropic's privacy policy. Anthropic does not use API inputs to train their models by default.

We recommend not including any personally identifying information in your free-text preference fields.

Your account data is stored in Supabase, a cloud database service with servers located in the United States. The site is hosted on Vercel. Error diagnostics are processed by Sentry (servers in the United States). All three providers maintain their own privacy and security standards.

Your tier list and reading history (including DNF status) are synced to our servers when you are signed in. Locally stored data also exists in your browser and is kept in sync automatically.

We use cookies only for authentication — specifically, a session cookie managed by Supabase to keep you signed in. We do not use advertising cookies, tracking pixels, or third-party analytics cookies.

You may at any time:

• Access the data associated with your account by signing in to My Account
• Delete your locally stored data by clearing your browser's localStorage
• Request a copy or deletion of your account data by contacting us
• Sign out and stop using the site at any time

If you are located in the European Economic Area or United Kingdom, you have additional rights under GDPR / UK GDPR, including the right to data portability and the right to object to processing. Contact us to exercise these rights.

LitRPG Next is not directed at children under 13. We do not knowingly collect personal information from anyone under 13. If you believe we have inadvertently collected such information, please contact us and we will delete it promptly.

We may update this policy from time to time. Material changes will be noted with a new "last updated" date at the top of this page. Continued use of the site after changes constitutes acceptance of the updated policy.

Questions about this policy or your data? Reach out via the Contact page.