Plans — and exactly what leaves your machine

langweave has two plans. A plan belongs to your account — not to a language or to the assistant you connect — and you choose it on the app’s Billing page.

• Free. Your profile, your words, your assistant weaves them. Nothing from your conversations ever leaves your assistant.
• Standard — €4.99 / $4.99 a month, first month free. Your assistant logs what it used and introduces new words as you go.

What each plan includes

	Free	Standard
Choose a language, change settings, the Words page, add words and mark them known in the app	yes	yes
get_language_profile	yes — known and learning words only: no introduce next, no topic	yes
stats	yes	yes
log_exposures, check_words, update_item	not available	yes
What your assistant sends to langweave	the language code and a bearer token	the target-language words it used or wants to look up, an event kind, an optional topic hint
What langweave stores from a conversation	nothing	your history and the word states worked out from it

The same thing in sentences — the ones the privacy policy and the terms use, word for word:

• On Free, nothing from a conversation is sent to langweave or stored: your assistant sends only the language code and a bearer token.
• On Standard, your assistant sends the target-language words it used or wants to look up, an event kind and an optional topic hint — never your prompts or its replies — and langweave stores them as your history and the word states worked out from it.
• On either plan, the words you add or mark in the app yourself are stored, because you typed them there.

lexmem keeps your memory on either plan; the plan decides what langweave does with it. In these sentences “langweave” means both services — langweave, and lexmem, which stores the history and the word states on its behalf.

Why Free sends nothing — two layers

The Free promise does not depend on your assistant behaving well. It holds at two layers, either of which would be enough on its own.

1. The tools do not exist. When a Free account connects, the server registers two tools, get_language_profile and stats, and the only argument either accepts is the language. The tools that carry words — log_exposures, check_words, update_item — are not registered, so they are not in the list your assistant sees, and a model cannot send what it has no tool to send with. In the source this is one branch in createMcpServer (packages/mcp-server/src/server.ts).

2. The server refuses anyway. Suppose a modified or out-of-date client called them regardless: the API answers the two routes that record and look up words with 403 plan-required for a Free account — that is requirePlan (packages/api/src/identity/plan.ts) — and the hosted connector refuses the same two calls with the same answer. A topic sent with a Free profile request is ignored.

Not a conversation, on either plan

Your prompts, your assistant’s replies, and any text other than individual target-language words never reach langweave — on Standard either. What Standard sends is a list of words like el río, what happened to each (used with a gloss, used bare, you asked its meaning), and optionally a short topic, such as food, so the next words fit the conversation.

Changing plan

• Upgrading. Your assistant sees the new tools the next time it connects — assistants keep the tool list they were given, so reconnect langweave in your client, or start a new conversation.
• Cancelling. Standard lasts until the end of the period you paid for, then the account is Free. Nothing is deleted: the words you knew and were learning stay in your profile, frozen as they were, and keep being woven. They start moving again if you subscribe again.
• A plan that lapses mid-conversation. The next logging call is refused, and your assistant is told to carry on weaving from the profile without retrying.

Self-hosting langweave against your own server has no plans: billing is off there, and every account has all five tools.