Loom

Privacy policy

Last updated 30 September 2026.

Loom is a chat app. You write to a language model, and the app keeps your conversations so they are there when you come back. This page describes everything it stores, everywhere that data goes, and how to get rid of it. It covers the Loom website and the Loom iOS app, which share one account and one backend.

Before submitting to the App Store: set CONTACT_EMAIL in app/legal/privacy/page.tsx. This page is the URL App Store Connect checks, and a policy with no contact address is a rejection.

What Loom stores

Your account

Your email address, the name you chose, and a hash of your password. Loom does not store your password itself and cannot read it. Accounts are handled by Loom itself and live in the same database as everything else below.

What you write and upload

  • Conversations — every message you send and every reply you receive, including the model’s reasoning and any tool calls it made, plus the conversation title, the model you picked and the reasoning effort.
  • Summaries — as a conversation grows past its memory window, older messages are folded into a rolling summary so the model keeps context. The summary is stored with the conversation.
  • Memory across conversations — after a conversation, a model writes short notes about you for later ones: who you are, how you want answers, what you are working on, what you care about, and the people and places in your life. Each note is shown under Settings → Memory, where you can delete any of them and switch the whole feature off; off, nothing new is written and nothing already written reaches a conversation. Deleting a conversation deletes the notes first written in it.
  • Memory graph (beta) — if you switch it on under Settings → Memory, a model also turns what you say into a small world of your own: the people, organisations, places, projects and tools you mention and how they relate, what happened and is coming, facts about them with a value on the other end — a name they go by, a birthday, a job title, a phone number — the day each fact began and, when it changes, the day it ended, and which conversation and file each fact came from. It can name people other than you and hold such values about them. The world is shown under Lore, where you can read every claim, undo what a conversation wrote, or delete the world; off, nothing new is written and nothing in it reaches a conversation. Deleting a conversation removes it as a source; the facts stay until you undo or delete them.
  • Files — images, PDFs, text files and voice recordings you attach. These are held in private storage (Vercel Blob) and are only served back through an endpoint that checks your session.
  • Workflows and their runs — the graphs you build or the model builds for you, and a snapshot of each run.
  • Settings — default model, memory window, whether memory across conversations and the memory graph are on, which tools are on, and which models appear in the composer.
  • MCP connections — if you add a tool server under Settings → Connections, Loom stores the address you typed, the name you gave it, the list of tools it reported, and — where the server requires you to sign in — the access and refresh tokens that sign-in produced. A call waiting for your approval is stored with the arguments it would send, and the result once it has run. Those tokens are held in the same database as everything else here and are never shown back to you or sent anywhere but that server. Removing the connection deletes them.

What stays on your device

Unsent drafts, a cache of recent conversations, generated images in the image studio, and your appearance and typeface choices are stored on the device — in your browser’s storage on the web, and in the app’s own container on iOS. They are not uploaded to Loom’s servers. On iOS, ready studio pictures are also stored in your own iCloud (a private CloudKit database) when iCloud is on. Signing out erases the copies on that device.

What Loom does not do

  • There is no advertising, no analytics service, no tracking SDK and no third-party cookie. Nothing tracks you across other apps or websites.
  • Your data is never sold, rented, or shared for advertising.
  • Your conversations are not used to train any model by Loom, and the providers below are used through interfaces that do not contribute your prompts to training.
  • Loom does not ask for your location, contacts, calendar, or health data. The iOS app asks for the photo library and the microphone only when you attach a picture or record a voice message.

Who else sees it

Running the app means handing parts of your data to the services it is built on. Each is used for one job and nothing else.

  • Railway — hosts the app and the database that holds your account, conversations, workflows and settings, in the EU (Amsterdam), and keeps ordinary server request logs (IP address, time, path), which exist for security and debugging.
  • Vercel — private storage for the files you attach.
  • Vercel AI Gateway — passes your message, the conversation it belongs to, any attached files, and the memory notes and, when it is on, the memory graph it holds about you to the model you picked. The gateway routes to that model’s provider, such as OpenAI, Anthropic or Google. Which provider receives a message is determined entirely by the model selected in the composer. Your email address and name are not sent with it.
  • Brave Search — receives a search query when the model uses the web search tool. You can turn that tool off in Settings.
  • Any website the model reads — when the model uses the fetch tool to open a page, that site receives a request fromLoom’s server for that one address, and sees the server’s IP rather than yours. Nothing is sent with it but that address, and the request only reads a page: it never signs in, submits anything, or carries an account of yours. You can turn the tool off in Settings.
  • CivitAI and OpenAI — receive the prompt and parameters when you generate a picture in the image studio or run a workflow node that calls them. Only used if you use those features.
  • Any MCP server you add yourself — receives a connection from Loom asking what tools it offers and, if it requires a sign-in, the authorization Loom holds for it. Once you switch MCP on for a conversation, or name the server on an agent, it also receives whatever the model passes to one of its tools, which is drawn from what you wrote in that conversation or asked that agent to do. Each of its tools is set separately: one left at Ask cannot be called until you approve the exact call on its card, with the arguments in front of you, and one you block is never offered at all. Such a server is chosen by you and run by whoever runs it, under their own terms rather than these.

How long it is kept

  • Conversations, files, workflows and settings are kept until you delete them or delete your account. There is no automatic expiry.
  • Deleting a conversation deletes its messages, its summary, its attachments and the memory notes first written in it immediately.
  • Generated images in the image studio are held on the server only long enough for your device to collect them, and are cleared within about a day.

Deleting your account

You can delete your account from inside the app: Settings → Account → Delete account on iOS, and the same place on the web. No email, no form, and no request to anyone.

Deleting signs you out on every device and starts a 24-hour window. During that window nothing has been erased and the deletion can be undone by signing back in and pressing Cancel — this exists so that one mistaken tap is not permanent. After the window closes, a scheduled job erases your conversations, messages, uploaded files, summaries, memory notes, workflows, runs, settings and any MCP connections with the tokens they hold. That erasure is permanent and there is no backup copy to restore from. The job runs on a schedule, so deletion completes at least 24 hours after you ask and normally within 48.

Your sign-in record — the email address and password hash — is erased in the same pass, so nothing of the account remains on Loom’s servers. Questions about a deletion can go to the contact address below.

Studio pictures the iOS app kept in your own iCloud are not on those servers, so the job cannot reach them. The app that asked for the deletion removes them the first time it is opened after the deletion completes — not before, so cancelling keeps them. If that app is deleted first, they stay in your iCloud until you remove them from your iCloud storage settings.

Your rights

You can read everything Loom holds about you from inside the app, since it is your conversations and your settings. You can correct your name at any time, delete individual conversations, and delete the whole account as described above. If you are in the UK, the EU, or another place with data protection law, you also have the right to ask for a copy of your data, to object to how it is handled, and to complain to your data protection authority.

Children

Loom is not directed at children under 13, and accounts are not knowingly created for them.

Changes

If this policy changes, the date at the top changes with it. A change that affects what is collected or who receives it will be announced in the app before it takes effect.

Contact

Contact address not set. Fill in CONTACT_EMAIL before this page goes in front of anyone.

Back to Loom