Privacy Policy

Last updated: November 5, 2026

The short version

Looom is a local-first app. Your threads, photos, and project data stay on your device until you send or share something. Three things leave it:

We don't track you, we don't show ads, and we don't sell data.

What data stays on your device

All core app data is stored locally on your iPhone or iPad:

This data stays on your device unless you (a) send a record, share a defect, or export, or (b) use AI features, which transmit only the inputs needed for each analysis as described below.

AI features

Looom has two AI layers. The first is a heuristic analyzer that runs entirely on your device. It labels trade, severity, and category from your photo and notes with no network involved. The second is Claude (Anthropic), which generates natural-language summaries, suggested tags, descriptions, and titles.

When you use the Claude-backed features, Looom sends the relevant inputs to Anthropic via Looom's Cloudflare Worker at share.looom.build/api/ai/*. The worker forwards the request to Anthropic's API with a Looom-managed key and returns Anthropic's response. We never store your photos or transcripts on Looom servers. The worker proxies the request in-flight and writes only per-call counters (user identifier, model, token totals, timestamp) for cost monitoring and abuse prevention.

What gets sent for each analysis:

No training. Anthropic's commercial API does not use customer inputs or outputs to train their models. See Anthropic's commercial terms and usage policy.

Looom retention. Our worker holds the request only for the duration of the Anthropic round-trip (typically a few seconds). The only persistent record on our side is the per-call counter described above.

Anthropic retention. Anthropic's commercial API retains inputs and outputs for up to 30 days by default for operational and policy-enforcement purposes, after which they are deleted. Exceptions for legal or safety review may apply per Anthropic's policy. See Anthropic's retention policy for the current specifics.

Turning it on and off. AI features are off until you turn them on: the app asks the first time you use it, and nothing is sent to Anthropic before you answer. You can turn them off again from Settings › Shuttle, using the "Let Shuttle summarize new threads" switch. The on-device heuristic analyzer remains available regardless. Developer iteration uses a "bring your own key" path that bypasses our worker entirely; that mode is off by default and gated behind a debug toggle.

Sign in with Apple

Looom requires Sign in with Apple at first launch. Your Apple ID subject identifier, display name, and email address are stored on your device in the iOS Keychain. Your Apple ID email stays on the device. Your display name goes with the defects you share, as the sender's name. The subject identifier is sent to our server with AI requests (forwarded as Anthropic's metadata.user_id) so we can rate-limit and meter cost per user, and with defects you share so the server knows they are yours. It is not used for tracking, advertising, or any cross-app correlation. You can sign out at any time from Settings, which removes your credentials from the device.

Voice memo transcription

When you record a voice memo, Looom can show live captions and transcribe the recording using Apple's on-device speech recognition. Audio is not sent to Apple for transcription. Speech recognition may need to download language assets before it can transcribe; recording still works when transcription is unavailable. Voice transcripts may be sent to Anthropic when you use AI features, as described above.

Records you send

When you send a record, the app encrypts the page, its photos, and its PDF on your phone before upload. The key is in the part of the link after the "#", which browsers never send to a server, so Looom's server stores only data it can't read. Links expire after the time you pick (7, 30, or 90 days, or no expiration), and you can stop a link or withdraw a record from the app at any time. GPS coordinates and EXIF metadata are stripped from photos before upload. We count how many times a link is opened and when it was last opened, and show you that count.

If you set a PIN on a link, the PIN is hashed using PBKDF2 before being stored. We do not store PINs in plain text. Access attempts are rate-limited to prevent brute-force attacks.

Defects you share

A shared defect is worked by two people, so our server has to read it. When you share a defect or a punch list, these are stored on Cloudflare and are not end-to-end encrypted:

Anyone with the link can read the defect. Only the person who accepts it can work it. Photos are re-encoded without location before upload, from the app and from a browser.

How long it stays. A shared defect stays on our server as long as it exists in your app, because it is part of your record. Stopping or replacing a link closes it but deletes nothing. When you delete the defect in the app, its photos, video, voice memos, files, and rows are deleted from our server, and a short record that it was deleted is kept so the other person's phone hears about it.

Notifications. To tell you when a defect moves, we store an identifier for this install of the app and its Apple push token. Apple delivers the notification.

Working a defect in a browser

Someone without the app can take a defect in a browser. To do that, they enter their name, company, and email, and we email them a code through Resend, our email provider. The code expires after 10 minutes and allows 3 tries. To limit abuse, we keep a keyed hash of the requesting IP address with the code, not the address itself, and delete both within a day of the code expiring.

A confirmed browser gets one cookie, __Host-looom_web, on share.looom.build only. It keeps the person signed in to that defect's work and nothing else. It is HttpOnly, Secure, and same-site only, and it stops working 180 days after it was last used. When a photo is added in a browser, we keep the time it was taken (read from the file) and show it as coming from a browser. Its location is not kept.

If the same person later uses the app and confirms the same email there, we link the two so their work carries over. The person who shared the defect can see the email it was taken with.

Location data

Looom requests location access to tag entries with your job site coordinates. Location data is stored on your device and is stripped from photos before sharing. The one exception is the Weather feature below: when enabled, your coordinates are sent to Open-Meteo to fetch current conditions. No identifier accompanies the request. You can deny location access and the app works without it.

Weather data

Looom fetches current weather conditions based on your location to attach to entries. This request goes to Open-Meteo, a free weather API. Only your coordinates are sent, no device identifiers or personal information.

Analytics and crash reporting

Looom does not include third-party analytics or crash reporting SDKs. We rely on Apple's built-in crash reports, which you can opt out of in your device settings.

Third-party services

Children's privacy

Looom is not directed at children under 13 and we do not knowingly collect information from children.

Changes to this policy

If this policy changes, we'll update the date at the top of this page. Material changes will be noted in the app's release notes.

Contact

Questions about privacy? Reach us at hello@looom.build.