Skip to content

Privacy policy

Draft, last updated October 3, 2026

This page says what LabWren collects, why, how long it is kept, who else sees it, and how to have it deleted. LabWren is operated by Nicholas Foster, an individual, until it is incorporated as a company. Questions go to privacy@labwren.com.

The short version: files you upload are read in your browser and never kept. What you type, and the tool you get back, are sent to our AI model provider to build the tool and may be kept so we can fix failed builds. We do not sell your information, we do not show ads, we do not use analytics or tracking cookies, and we do not use your content to train models.

1. What we collect and why

  • Your requests and the tools built from them. When you ask LabWren to build or change a tool, we receive your message, the earlier messages in that conversation, and a description of your file (below). We use them to build the tool. When our logging is switched on, we keep the request, whether a file was attached (never the file), the tool we returned, and the result of its independent review, so the founders can see why a build failed and fix it.
  • Uploaded files. Your browser reads the file. We receive only the file name, the column headers, the column types, the number of rows, and at most 8 sample rows per sheet. The file itself never leaves your computer and is never stored.
  • The waitlist. Your email address, and if you fill them in, your role, institution, and what you would automate first. We use your email address to confirm your signup and to invite you, and your other answers to learn what to build. We do not store your IP address with your signup.
  • Shared tools. When you press Share, we store a copy of that tool with its name, summary, and a record of how it was made, so anyone with the link can open it.
  • Projects. When you import a project, we store its files, its brief, and the builds you make, under a key only your browser holds.
  • Usage counts. We count how many model calls and how many output tokens the service uses each day, with no link to who made them, to stay within budget.
  • Your IP address is used briefly, in memory, to rate-limit requests. It is not written to any store.

2. What stays on your device

Your tool library, its version history, the list of projects you opened, the links you shared with the secret that removes each one, your model choice, and whether you have seen the introductory tour are kept in your browser’s own storage. They never reach us unless you share or import something. Clearing your browser’s site data for labwren.com deletes them.

LabWren Desktop keeps its settings, your saved tools and workflows, and your conversation history in its own folder on your computer. It sends your messages, and the parts of files and command output it reads for a task, to the LabWren server you connect it to. It never uploads whole data files and has no analytics.

3. Who else sees your information

  • Our AI model provider. Anthropic receives your messages and the file description above to build and review tools, under its commercial terms. We do not allow your content to be used to train models.
  • Your own API key, if you add one. It stays in your browser (for this tab only, unless you choose to remember it on this device) and is sent with each request to build or review a tool. Our server passes it to Anthropic for that request and never stores or logs it. Requests made with your key are billed to your Anthropic account under Anthropic’s terms.
  • Cloudflare hosts the site and stores everything we keep on the server.
  • jsDelivr is where a tool’s chart and spreadsheet libraries come from. The website shows and shares a tool with our own copies of both, and a tool downloaded from the website or saved as a standalone file in the desktop app carries both inside the file, so none of these contacts jsDelivr. It sees your IP address when our copies fail to load in the website’s preview, or when a project you import loads scripts from it.
  • GitHub receives requests from your browser when you import a project from a GitHub repository.
  • Resend delivers the email we send you, such as the waitlist confirmation, so it receives your email address and the message, and keeps a delivery log for 30 days.

4. How long we keep it

  • Shared tools: 30 days, then the link stops working, unless the person who shared the tool removes it sooner.
  • Daily usage counts: 2 days.
  • Projects: until you delete them.
  • Waitlist signups: until you ask us to remove you, or until the waitlist closes.
  • Logged requests and tools: until we adopt a fixed retention period, which this page will state. You can ask us to delete yours at any time (below).

5. Deleting your information

  • Projects. Delete a project from its page. It is removed from our servers at once.
  • Shared links. After you press Share, a Remove link button appears next to the copied link. Pressing it deletes our copy of the tool, and anyone who opens the link is told it was removed or has expired. It can take up to a minute to stop working everywhere. Only the browser that shared the tool holds the secret that allows this, and we keep only a fingerprint of it. If you have lost it, or shared from LabWren Desktop, email us the link and we remove it.
  • The waitlist. Email privacy@labwren.com from the address you signed up with, or name it, and we remove your signup.
  • Logged requests and tools. Email us and say roughly when you made the requests and what you asked for. We can delete a single request, every request that produced a given tool, or everything from a period of time.
  • Things on your device. Clear your browser’s site data to remove your library, settings, and the list of links you shared.

For anything else, or if you are unsure what we hold, email privacy@labwren.com. We reply within 30 days.

6. Cookies

LabWren sets two cookies, both strictly necessary, and no others:

  • labwren_access remembers that you entered the access code, when one is required, for 30 days. It holds a fingerprint of the code, not the code.
  • labwren_dev keeps the founders signed in to the internal developer section for 7 days.

There are no analytics, advertising, or tracking cookies, so there is nothing to consent to and no cookie banner. If that ever changes, we will ask first.

7. Research data

Please do not put unpublished, confidential, or personal data into LabWren during this early stage. Use synthetic or published data where you can. Anything you type goes to our model provider as described above.

8. Age

LabWren is for adults. You must be 18 or older to use it, and we do not knowingly collect information from anyone younger.

9. Security

Traffic is encrypted, tools run in a locked-down sandbox in your browser, and access to stored data is limited to the founders who run the service. To report a security problem, email security@labwren.com.

10. Changes and contact

We will update this page when what we collect changes, and change the date at the top. The terms of service cover how you may use LabWren. Contact: privacy@labwren.com.