Privacy Policy

This policy describes how iamjoi handles data for the website, the browser chat app, iamjoi Link (the Windows bridge), JoiHUD (the Virt-A-Mate plugin), Playground (hosted AI chat with VaM characters), and Link local mode (try without an iamjoi account). By using those services you agree to this policy.

Short version. JoiHUD talks only to iamjoi Link on your PC. Virt-A-Mate never opens a connection to iamjoi servers. Local mode in Link (signed out, with a local LLM you provide) keeps chat, personality, scene text, and clothing actions on this PC. Nothing from that path is sent to iamjoi. Playground is a hosted AI service for signed-in Premium members: most chat is typed on the website and goes from your browser to our servers over HTTPS; Link then relays VaM-side data (look stills, triggers, in-scene HUD chat if you use it, and similar) to the same servers. We can read that Playground data while it exists on our systems. Login is the control you have; there is no per-field filter of what Playground sends. Chat inference uses the third-party LLM you select. Voice can run locally in iamjoi Link (Kokoro or Supertonic) or use cloud TTS (ElevenLabs or xAI). Some Playground helpers always use xAI.

1. Account identity

When you register we store your email, username, and password hash. If you link Patreon we store the Patreon identity needed to apply your membership. We do not store card numbers. Payments are handled by Patreon or PayPal under their policies.

2. Local mode (no iamjoi account)

Local mode is the try-without-paying path in iamjoi Link. You turn it on in Link, stay signed out, and point Link at an OpenAI-compatible LLM on this PC (for example Ollama). JoiHUD still pairs with Link on localhost. Chat is started from the in-scene HUD (Start Character). The model invents a personality on load unless you write one yourself.

In local mode, Link answers HUD chat in-process. Chat text, invented or edited personality, scene description, clothing take-off/put-on actions, and local TTS audio stay on this PC. They are not posted to iamjoi. We do not receive your local LLM prompts, replies, or a local ElevenLabs key you paste into Link.

Local mode can still talk to your providers, because you configured them: the LLM endpoint you set, and optionally ElevenLabs or another /audio/speech endpoint if you choose cloud voice there. That traffic does not go through iamjoi. Kokoro in Link stays on this PC.

Signing in to Link always uses Playground (section 3), even if the local-mode toggle is on. Local mode is the signed-out path.

3. What Playground sends (website, Link, JoiHUD)

Playground chat usually happens in the iamjoi website (including on a phone). That text goes from your browser to our API over HTTPS. It does not travel through Virt-A-Mate or Link.

Virt-A-Mate does not open a connection to iamjoi servers. JoiHUD connects only to iamjoi Link on localhost. After you sign in, Link relays VaM-side data to the same backend so the scene and the website stay in sync. That typically includes:

• Chat typed in the in-scene HUD (when you use that input instead of the website).
• Still images of character looks, used to generate an appearance summary and personality when you load a look.
• Scene/session metadata (loaded scene name, character slot names, clothing state, trigger/action keys, saved Context settings).
• Clothing-index search hits when you use garment search. Those IDs often include VaM package UIDs from AddonPackages.

In Playground, AI replies are generated on our servers whether you typed on the website or in the HUD, then sent back to the website and, via Link, into VaM as voice, subtitles, and triggers. That does not apply to local mode (section 2).

Link may write files under your VaM folder at iamjoiLinkData/ (saved personalities and appearance notes) and may write TTS audio in Link's local store. The server can request those writes. Paths are limited to that iamjoi data area, not arbitrary locations on your disk.

Playground chat is kept in server memory for the live session (currently capped and expired after about 24 hours). It is not a long-term VaM memory feature: chat does not carry across sessions yet. Saved personalities and Scene Contexts you choose to save are stored in our database until you delete them or your account.

4. Browser chat (legacy app)

The original browser companion chat stores conversation history in our MongoDB database, tied to your account, until you delete the chat or the account. That is separate from VaM Playground.

5. Who can read this

Operators of the iamjoi backend can technically access account data and chat/session content that is on our servers. Local-mode chat never arrives there. We do not sell transcripts and we do not provide a public admin browser for other users' chats. That is a practice, not a cryptographic guarantee.

Connections to our API use HTTPS. Chat is not end-to-end encrypted. A hosted AI has to read the prompt in order to reply.

6. Third-party processors

We share data only as needed to run the service:

• LLM providers — Playground chat is sent to the model you select in the header. Local-mode chat is sent only to the endpoint you set in Link, not to us. Current Playground options are routed through OpenRouter (for example Google Gemma), Nano, or xAI (Grok). The list of models can change. Some Playground helpers (Describe-scene expand and which character should reply) currently use xAI even if your chat model is not Grok.
• Speech. If you use local TTS in Playground (Kokoro by default, or Supertonic), iamjoi Link synthesizes audio on your PC and reply text is not sent to a cloud voice vendor. If you use cloud TTS, reply text is sent to ElevenLabs or xAI, depending on that setting.
• MongoDB Atlas — account data, credits, saved Contexts, and legacy browser chat history.
• Amazon Web Services — hosting for the API.
• Patreon and optionally PayPal — membership and credit purchases.
• Discord — community; subject to Discord's policy.

Those providers process data under their own terms. We do not sell personal data.

7. What you control

You choose whether to create an account, sign in to the website and to Link, and use Playground. Signing out disconnects Link from our servers and stops the browser Playground from sending new chat. There is no per-message or per-field filter of what the website or Link sends while you are using Playground. Local mode (section 2) does not send chat, looks, or keys to iamjoi.

You may review account details in the app and request deletion via the in-app delete flow or by emailing joi@iamjoi.ai. Deletion removes account records we store. Data already sent to an LLM or TTS provider, Patreon, or Discord is subject to their retention rules and may not be erasable by us.

8. Cookies

The website uses cookies for signed-in sessions (iamjoi_session). Disabling cookies will prevent staying logged in. The public site may also load Google Analytics when that feature is enabled, which collects standard page-usage data under Google's policy.

9. Virt-A-Mate content

Looks, scenes, and plugins in your VaM library belong to their creators and licenses. We do not claim those assets. Screenshots of looks sent for personality generation are used only to run Playground for your account.

10. Changes

We may update this policy. The date below is the last revision. Continued use after a change means you accept the revised policy. Questions: joi@iamjoi.ai or the iamjoi Discord.

Last updated: September 10, 2026