Where your words go when you talk to Wren — and where they don't. This is the lighter companion to the Privacy Policy: the actual data flow, the sub-processors we use, and how to get your data deleted.
Four steps, and none of them are a secret. Your message travels through Wren's app to a hosted model, and the response streams back to you.
You type a prompt in the chat, in your browser.
We attach the relevant context from your chat or Project, then store the message.
The prompt is sent to a hosted frontier model, which generates a response.
Wren streams the response into your chat — and renders any Frame it built.
Your content is sent to the model only to answer you, in the moment. It is not collected into a training set, not used to fine-tune anything, and not shared for model improvement. We're a product on top of hosted models — we have no training pipeline your data could feed.
We keep this list short and current. Since Wren is a reference build, the picture is deliberately simple.
| Sub-processor | What it does | Data it sees |
|---|---|---|
| Hosted LLM proxy the platform's model gateway |
Runs the frontier model that generates responses. Every message you send is routed through it. | Your prompt and the relevant chat / Project context, at generation time. |
| Static & app hosting Cloudflare Pages + platform storage |
Serves the Wren web app and stores your chats, Projects, and Frames so they persist. | Account record and the content you create in Wren. |
No advertising networks. No analytics resellers. No data brokers.
Wren's app and storage run on the platform's infrastructure, primarily in the United States. Prompts are processed by the hosted model proxy transiently to produce a response and are not retained by us as a separate training corpus.
Your chats, Projects, and Frames are kept until you delete them or delete your account. Anonymous visitor sessions are held for a limited window, then cleared. Usage and diagnostic data is aged out once it's no longer useful for running the app. When you delete something, it's removed from active storage; incidental copies in routine backups age out on their own cycle and aren't used for anything.
You're in control, and it's meant to be easy:
For the full picture — collection, cookies, controls, children, and contact — read the Privacy Policy. The rules for using Wren live in the Terms of Service, and the Help center has step-by-step guides.