Privacy

This page is a plain-language description of how Adventure Machine handles your data. It is not a legal document and I am not a lawyer — but it is the truth.

What Adventure Machine Stores and Why

  • Account data — Your display name and a login identifier from Auth0. This is the minimum needed to let you log in and identify yourself to other players. No email or password is stored directly.
  • Characters, worlds, and mobs — The content you create on the site. Stored so it persists between visits and can be used in sessions.
  • Session transcripts — The full message history of your sessions, including DM responses. Stored so you can revisit past sessions and so the DM can reference earlier context within a session.
  • Memories — Facts automatically extracted from your sessions. Stored so the DM can maintain continuity across different sessions (e.g. remembering your character's choices or relationships).
  • API keys — If you provide an OpenRouter API key, it is stored on the server so the site can make LLM requests on your behalf. It is never shared with other users or used for any other purpose.

What I Can and Can't Do with Your Data

As the site administrator, I have access to the database that stores all of the above. In practice, I use that access to fix bugs, run maintenance, and occasionally verify things are working. I do not read your sessions, characters, or memories for fun or any other purpose.

I cannot see your OpenRouter API key in plain text once it is stored — it is only used server-side to make API calls. I cannot see your Auth0 password, as authentication is handled entirely by Auth0's systems.

I will not use your data to train models, build profiles, run analytics, or do anything other than make the site work as described.

There is no automated or human moderation of your session content. Nobody is reading or screening what you write. I want this to be as private as I can possibly make it for you. I may eventually need to add some form of content flagging for extreme or illegal material if the service grows, but that is something I would prefer to avoid and will be transparent about if it ever becomes necessary.

What Adventure Machine Does NOT Store

  • Email addresses or passwords (authentication is handled entirely by Auth0)
  • Payment information
  • Game client data beyond what the Dalamud plugin sends (character name, race, class)

AI and Your Data

Adventure Machine uses large language models (LLMs) via OpenRouter to power the AI Dungeon Master, memory extraction, and semantic search. When you play a session, your messages, character details, and relevant memories are sent to the LLM you or the host selects.

The default model is DeepSeek V3.2, but you can change this at any time from your session settings. Browse available models at OpenRouter's model catalog.

Adventure Machine does not train any AI models on your data. However, your prompts and responses pass through OpenRouter and the underlying model provider (e.g. Google, DeepSeek, Anthropic). Each provider has its own data handling policies. OpenRouter's privacy policy is available at openrouter.ai/privacy. You can choose which model to use per session, so you have control over which provider handles your data.

Data Sharing

Your data is not and will never be sold to third parties. I just want to make a cool roleplay tool and share it. Other players in your session can see your character details and messages, but not your API key, memories, or account settings. Friends you add can see characters and mobs you've explicitly shared with them.

Data Deletion

You can delete your characters, sessions, memories, and mobs at any time from the site. If you want your entire account removed, contact the site administrator.

An unhandled error has occurred. Reload 🗙

Connection lost. Reconnecting to the server...

Still trying to reconnect... next attempt in seconds.

Unable to reconnect to the server.
Check your connection and try again.

The session has been paused by the server.

Unable to resume the session.
Check your connection and try again.