Privacy notice

This explains what RP Forge collects, how it is used, and the thing that matters most to a writer: what does and doesn’t reach the AI.

What we collect

• Account details: your email address and authentication data, handled by our auth provider (Supabase).
• What you create: character profiles, worlds and their lore, cast maps and the bonds you draw on them, and the scenes, sheets, and drift history you generate while playing.
• Basic technical data: standard logs needed to run and debug the service, including a record of what each AI call cost.

What gets sent to the AI

Several features work by sending your writing to third-party AI providers, which process it and return a result. The Arbiter’s rulings and drift, trait and shadow suggestions, scene openers, and chronicle recaps run on Anthropic (Claude). When you play solo against the Arbiter, the opposing character’s lines are generated by a separate AI model, reached through the routing provider OpenRouter. AI runs on our servers, never in your browser, and we never ask you for an API key.

Private Notes are never sent to the AI. Everything else in a character is part of what the Arbiter sees so it can rule in character: identity, capabilities, key facts, voice, example lines, psychology, appearance, background, and your custom sections. Portraits and internal data are excluded. If you want something kept out of the AI’s view, put it in Private Notes.

Alongside the character itself, a scene also gives the Arbiter:

• The bound world: the lore entries that match what is happening, within a budget. Lore you mark as secret is held back from readers, not from the Arbiter.
• Bonds and affiliations: how your character regards others, and the groups they belong to, with your role notes. Only maps drawn by writers actually seated at that table are used, so a third party’s annotations about your character don’t follow it to tables they aren’t at. Where you dragged the portraits and what colour you tinted a group are yours alone and never leave the app.
• Shared history: short recaps of earlier scenes between the same two characters, and only ones both sides were present for.

The AI providers process this to return a result. Under Anthropic’s API terms your writing is not used to train its models; the opponent model is reached through OpenRouter, configured to avoid providers that retain or train on your content. Some requests are refused or flagged under a provider’s usage policies — see the terms.

How we use it

To run the app: store and show your work according to the visibility you choose, operate the AI features above, keep the service secure, moderate against the community rules, and improve it as it grows. We do not sell your data, use it for advertising, or train models on it.

Keeping the service safe

To enforce the community rules in the terms, we may review content when there is a reason to — a report, a safety signal, or debugging a problem — and the AI provider may screen or refuse content under its own policies. We rely on automated checks first and look at content by hand only when we need to. This is part of running a shared service responsibly; we keep it to what’s necessary.

Who can see your work

Visibility is yours to set: private (only you), unlisted (anyone with the link), or listed (publicly discoverable). Private Notes are never shown on public pages.

Public pages are built around characters, not accounts. A listed character carries no key tying it to the person who wrote it, and no key tying it to your other characters, so browsing the public side cannot be used to collect your roster. Two things do reveal the link, and we would rather say so plainly than imply otherwise: the writers you sit down with in a scene can tell which characters are yours, and an Arbiter ruling may quote a bond you drew on your own cast map.

Scenes are visible to the writers seated at them. A finished page reaches another writer’s reading queue only when someone asks them to read it, and it is theirs to endorse or ignore.

Cookies

We use only the essential cookies that keep you signed in. There are no advertising or cross-site tracking cookies.

Where it lives, and moving across borders

Data is stored with our hosting and database providers (Supabase and Vercel) and processed by the AI providers named above. These providers may store and process data outside your country, including in the United States. Where the law requires safeguards for that transfer, we rely on our providers’ standard protections.

Your rights

You can ask to see the personal data we hold about you, correct it, delete it, get a copy to take elsewhere, or object to certain uses. To do any of these, email info@trpforge.app. We rely on a few lawful bases: performing the service you asked for, our legitimate interest in keeping it secure and moderated and in improving it, and your consent where it’s needed. If you’re in the EU or UK and think we’ve got this wrong, you also have the right to complain to your local data-protection authority.

Children

RP Forge isn’t for people under the age limits in the terms, and we don’t knowingly collect data from them. If you believe a child has given us data, email us and we’ll remove it.

Security

We take reasonable measures to protect your data, but no service is perfectly secure, and this is early software. If a breach ever affects your data, we’ll act on it and tell you where the law requires.

Keeping and deleting

We keep your data while your account is active. You can ask us to delete your account and its data at any time. Email info@trpforge.app and we will remove it. Note that we may also reset data while the app is still evolving, as described in the terms. Writing that is already part of a shared scene stays in that scene for the other writers in it, and we may keep limited records where the law requires (for example, a note that a report was actioned).

Contact

Questions or requests about your data: info@trpforge.app.