A quick walkthrough of what Wilo can and can't access in your account, and how to clear or pause that history.A quick walkthrough of what Wilo can and can't access in your account, and how to clear or pause that history.

#What Wilo can see

When you message Wilo, the assistant has access to:

• Your page context — the current route (e.g. /app/companions) and the entity you are viewing (e.g. a specific character's ID). This helps Wilo give relevant answers without you having to explain where you are.
• Your account profile — display name, plan tier, credit balance, total turns this month. Used to personalize answers and apply the right cost cap.
• Your previous Wilo conversations — recalled semantically via embedding similarity. Wilo can reference what you asked yesterday if it is relevant to today.
• Your wilds activity — characters, worlds, settings, recent sessions. Scoped to your account; Wilo queries the per-account stores when it needs to take an action or answer a "what do I have" question.

#What Wilo never sees

• Other users' data. Every query Wilo makes is scoped by your account_id at the database layer. The recall tool cannot return another user's memories; the listCharacters tool cannot return another user's characters.
• Your raw chat history with characters or inside game sessions. Wilo can only see summaries via the recall_memories tool — not the actual back-and-forth.
• Payment details, API keys, OAuth tokens. None of these are in any datastore Wilo can read.
• Your microphone audio. Voice mode transcribes locally in your browser; only the transcript goes to Wilo. The audio bytes never leave your device.

#Where the data lives

• Postgres wilo_threads + wilo_messages — your conversation history. Scoped by account_id via the thread's account_id column. Indexed for fast retrieval by the page UI.
• Postgres wilo_user_memories — semantic recall of past wilo conversations. Scoped by account_id. Each row carries an embedding vector for similarity search.
• Postgres wilo_tool_audit — every write-action Wilo proposed, whether you applied or cancelled it, and any undo token. Lets you see (and us audit) what Wilo did.

All three tables are encrypted at rest. The Postgres database is hosted on Linode in the same private network as the wilds app — no external access.

#How to clear history

#Per-thread

In the standalone page (/app/wilo), each thread in the left rail has an archive button on hover. Archived threads are hidden but not deleted — useful if you want to keep them for later reference.

To delete a thread permanently: archive it, then visit /app/settings → Privacy → Wilo data and click "Permanently delete archived threads."

#Account-wide

Same page (/app/settings → Privacy → Wilo data) has a "Delete all Wilo history" button. This wipes:

• All threads + messages
• All semantic memories
• All tool audit rows older than 30 days (recent ones stay for fraud protection)

Deletion is immediate and irreversible. Your account survives — only the Wilo-specific data is gone.

#Caps + limits

Detailed in the "How to use Wilo" guide. Short version: $0.50–$10/day per account depending on plan, 30 messages/minute, 20 turns per thread, $50/day platform-wide ceiling. All caps reset at midnight UTC.

#Reporting issues

If you spot a privacy concern — Wilo seeing something it should not, a wrong fact it stated as truth, a refusal that does not make sense — use the feedback button in the message footer (the small flag icon) or email [email protected] with the thread ID. We monitor every report and respond within 48 hours.