Privacy Policy

This covers the hosted service at longhouse.ai. If you self-host, none of your sessions reach us — you are the operator, and the only third parties involved are the ones you configure yourself.

What We Collect

Account Information

When you create an account, we store your email address and display name to identify your account.

Your Content

Your agent sessions and conversation history are stored to provide the service. This data is associated with your account.

We store transcripts as your agents produced them. Longhouse does not strip secrets out of what it stores, so if a session printed an API key, an SSH key, or a password, that value is stored too. Treat your session history as sensitive, because it is.

Device Tokens

Each machine you connect gets its own device token. The server stores only a SHA-256 hash of it, never the token itself.

Install Pings

The installer, the first start of longhouse-server, and updates send one small anonymous ping to control.longhouse.ai: a random install id, operating system, CPU architecture, Longhouse version, and how it was installed. No prompts, paths, secrets or session content. Set LONGHOUSE_TELEMETRY=0 or DO_NOT_TRACK=1 to turn it off; it is already off in CI.

Alpha Testers

If you were invited as a tester and agreed on the launch screen, your hosted instance keeps counts and dates that the person running the alpha can read: when your first machine connected, how many sessions came from each provider and when the first one arrived, when you first searched, first opened a session in the iPhone app, and first sent an instruction to an agent, and which days you did any of those in the web app or the iPhone app. Never transcripts, prompts, file names, search text or code. Nothing is pushed anywhere: the control plane asks your instance. Tell us to stop and we delete the instance and everything in it. A self-hosted instance records none of this.

What We Don't Do

• We don't train AI on your data. Your conversations are yours.
• We don't sell your data.

We don't send your transcripts to a model provider unless you turn it on. Longhouse can use one to generate session titles and summaries, and that is off by default. While it is off, no transcript content leaves your instance: titles come from the first message of the session, or from the project and branch it ran in. We default it off because transcripts contain API keys, SSH keys, and database URLs, and we would rather not hand those to another company on your behalf.

Where Your Data Goes

The hosted service hands data to these companies. A self-hosted instance uses only the ones you configure.

• OpenRouter, routing to DeepSeek — excerpts of your session transcripts, for generating titles and summaries, and only if you turn that on. It is off by default, and while it is off we send them nothing. There is no self-serve switch yet: email us to turn it on, and email us to turn it back off.
• Google — your email address and profile name, if you sign in with Google.
• Stripe — your email address and your payment details, for paid plans. Card numbers go to Stripe, not to us.
• Amazon SES — your email address and the contents of mail we send you, such as email verification and alerts.
• Apple (APNs) — if you use the iOS app with notifications enabled, the session title and summary travel in the push payload.
• Backblaze B2 — off-site backups of the hosted database.
• Cloudflare — DNS and inbound mail routing for longhouse.ai.
• Umami analytics, which we run ourselves — page views on our marketing, signup, and billing pages, plus a session recorder that replays interactions on those pages. It is not loaded on the hosted instances that hold your sessions.

How Long We Keep It

Sessions and transcripts stay until you delete them or ask us to delete them. Nothing expires on a timer today.

Deleting removes data from the live service. Copies can survive in off-site backups until those backups rotate out, and we don't restore deleted data from them.

Account and billing records are kept while the account exists, and billing records for as long as Stripe and tax rules require after it closes.

Deleting Your Data

Deletion is partly manual right now. Concretely:

• In the app — revoke device tokens under Settings, and delete any share links you created.
• By email — to delete a session, your whole history, or your entire account, email support@longhouse.ai from the address on the account. We do it and confirm back within 7 days.

There is no self-serve "delete my account" button yet. We would rather tell you that than point you at a settings page that doesn't have one.

Your Other Rights

• Access your data through the timeline
• Revoke a machine's device tokens at any time in Settings → Devices

Cookies

We use essential cookies to keep you logged in and remember preferences. Analytics on our public pages is described under "Where Your Data Goes".

Contact

Questions? Join our Discord or email support@longhouse.ai

See also our Terms of Service and Security page.