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/characters) 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_idat 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_memoriestool — 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. In voice mode your speech streams to the wilds.ai server, which transcribes it with Deepgram (ElevenLabs if Deepgram fails); Wilo receives only the transcript.
#Where the data lives
- Postgres
wilo_threads+wilo_messages— your conversation history. Scoped byaccount_idvia the thread'saccount_idcolumn. Indexed for fast retrieval by the page UI. - Postgres
wilo_user_memories— semantic recall of past wilo conversations. Scoped byaccount_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
All of these live on the standalone page, /app/wilo.
- Clear one conversation. Clear conversation above the open thread empties its messages and keeps the thread and its title.
- Delete one conversation. The actions menu beside a thread in the list offers Delete; the thread and its messages go, and this can't be undone. The same menu exports it as Markdown, JSON or plain text.
- Delete every conversation. Remove all above the thread list deletes every thread and its messages. Export all downloads them first if you want a copy.
The list files a thread under Archived once it has had no message for 14 days; archived threads stay readable until you delete them.
#Caps + limits
Detailed in the "How to use Wilo" guide. Short version: $0.10/day for guests and $0.50–$10/day per account depending on plan, 5 to 500 messages a day, 30 messages a minute (5 for guests), 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 team@wilds.ai with the thread ID. We monitor every report and respond within 48 hours.