Legal

Privacy Policy

Last updated: July 2026

Privacy Terms Data use Help center
On this page
  • What we collect
  • How we use it
  • Not used for training
  • The model provider
  • Storage & retention
  • Cookies & local storage
  • Your controls
  • Children
  • Changes
  • Contact
Plain-English summary
  • We collect what's needed to run Wren: your account, your chats, and how you use the product.
  • We do not train models on your chats or Projects. Full stop.
  • To answer you, we send your prompt to a hosted model provider — that's how a response gets generated.
  • You can delete your chats and your data whenever you want.
  • Wren is for adults — you must be 18 or older.

A note on this build. Wren is a reference / demo build made for cshell's calibration sweep. It is not a commercial service, and it is not affiliated with Anthropic. This policy is written to read like the real thing and to describe exactly how a demo like this actually handles data — no more, no less.

This policy explains what information Wren collects when you use the web app, why we collect it, and the choices you have. We've tried to write it in plain language. Where we simplify, the intent is honesty, not evasion — if something here is unclear, get in touch and we'll explain it directly.

What we collect

We keep collection narrow — only what's needed to make Wren work.

  • Account & visitor identity. If you sign in, we store a basic account record (an identifier and, if you provide it, an email). If you use Wren without an account, we assign an anonymous visitor id so your session and chats hold together across page loads.
  • Your chats. The messages you send and the responses Wren returns, so your conversations persist and you can come back to them.
  • Projects. The chats you group into a Project, along with any custom instructions you set for that Project.
  • Frames. The artifacts Wren builds with you — HTML pages, charts, small apps — including their versions. If you choose to publish a Frame, it becomes reachable by its link (see Terms).
  • Usage. Lightweight signals about how you use the product — which features you open, message counts against your plan's fair-use limits, and basic error/diagnostic events — so the app runs and we can fix what breaks.

We do not ask for and do not want sensitive personal information. Please don't paste anything into Wren that you wouldn't want stored to run the product.

How we use it

We use the information above to run the product and for nothing surprising:

  • To generate responses — your prompt, together with the relevant context from your chat or Project, is sent to a hosted model provider that returns the answer (see below).
  • To store and show your chats, Projects, and Frames so they're there when you return.
  • To keep the app working — authentication, session continuity, fair-use limits, and debugging.
  • To secure Wren against abuse and to enforce our Terms.

We do not sell your data. We do not use your content to build advertising profiles. We don't share it with third parties except the model provider needed to answer you and standard infrastructure that hosts the app.

Your chats and Projects are not used to train models

This is the important one, so we'll say it plainly: we do not use your chats, Projects, or Frames to train, fine-tune, or improve any AI model. Your conversations are stored so that you can use them — not so that a model can learn from them.

Wren is a product built on top of hosted frontier models; we are not a model lab, and we have no training pipeline that your content feeds. When we improve Wren, we improve the product around the model — the interface, the prompts we write, the Frames tooling — not the model's weights.

Prompts are sent to a hosted model provider

Wren does not run its own AI model. To generate a response, your prompt and the relevant context are sent to a hosted model provider through a proxy, which returns the completion that Wren streams back to you. This is a necessary part of how the product works — there is no way to answer you without sending the model something to answer.

We list this data flow and the sub-processor honestly on our Data use notes page. The provider processes the prompt to produce a response; the no-training commitment above covers this path.

Storage & retention

Your chats, Projects, and Frames are stored so they persist between sessions. We keep them until you delete them or delete your account. Anonymous visitor sessions and their chats are kept for a limited window and then cleared.

Usage and diagnostic signals are kept only as long as they're useful for running and fixing the app, then aged out. When you delete content, we remove it from active storage; residual copies in routine backups age out on their own cycle and are not used for anything.

Cookies & local storage

Wren uses a small amount of browser storage to function — no advertising trackers, no third-party ad cookies.

  • Session & visitor id — kept in local storage or a first-party cookie so your session and chats stay attached to you.
  • Preferences — your chosen style (Normal / Concise / Explanatory / Formal), model tier, and UI settings, stored locally so the app remembers them.

You can clear this at any time from your browser. Clearing it signs an anonymous session out and forgets local preferences.

Your controls

Your data is yours to manage.

  • Delete a chat — remove any conversation from your history, and it's gone from active storage.
  • Delete your data / account — remove your Projects, Frames, and account record. Published Frames you've shared are unpublished when you delete them.
  • Export — you can copy your chats and download the code behind any Frame at any time.
  • Preferences — clear local storage in your browser to reset preferences and sign out an anonymous session.

Need help with any of this? The Help center walks through it, or contact us.

Children

Wren is intended for adults. You must be 18 or older to use Wren. We don't knowingly collect information from anyone under 18. If you believe a minor has used Wren, contact us and we'll delete the associated data.

Changes to this policy

If we change how Wren handles data, we'll update this page and move the "Last updated" date. Because this is a reference build, changes here are about keeping the description accurate rather than expanding what we collect.

Contact

Questions about privacy, or a request to delete your data? Reach us at privacy@s-d753c7de0a328440.pages.dev, or start in the Help center. Related reading: our Terms of Service and Data use notes.