Lorah
Download

Privacy

Privacy policy.

Lorah is a local-first desktop application. This describes how data flows in it, as of the date at the foot of the page.

Last updated 5 October 2026LaGuardAI

Privacy policy

In plain words

The policy below is short because the app is local-first. This is the same thing, organised by how you use Lorah.

The summary

  • The app on your computer keeps your workspaces, specialists, memory, chat history, documents and provenance on your disk. We cannot see them.
  • Your API keys are stored in your operating system's keychain and sent from your computer to the provider you chose, to authenticate each call. We never receive them.
  • Your prompts and their answers go to that provider under its own privacy policy. Not to us.
  • License and billing run on a separate service that stores five fields about your subscription. Payments are handled by Stripe.
  • Once a day the app checks its license with a random install id, the app version, your operating system, the license type and an approximate country. Never your IP address.
  • This website sets no cookies and does no cross-site tracking, which is why there is no cookie banner. The servers that host it keep a standard request log for 30 days, and your IP address is in it. We read that log only in aggregate and never to identify you.
  • Crash reports are off unless you switch them on, and never carry the content of your work.

What stays on your machine

Workspaces, specialists, project memory, chat history, the Materials and provenance records are stored locally in the app's data folder, which keeps its original name, Bond2: ~/Library/Application Support/Bond2/ on macOS, %APPDATA%\Bond2\ on Windows. LaGuardAI does not have access to this data.

What goes to AI providers

Prompt content goes directly from your machine to the provider you selected, Anthropic, OpenAI, Google, Perplexity or xAI, using your own key. Their privacy policies apply to that traffic.

What we collect

Seven things.

License records. The license service stores your email, your Stripe customer ID, the plan type, monthly or yearly, the subscription status and the date. Account and payment processing is handled by Stripe, which holds your email, payment method and billing address under its own privacy policy.
An install heartbeat. A daily license check records a random install identifier, the app version, your operating system, the license type, trial, paid or grant, and an approximate country. The identifier is random, not derived from your hardware, and not linked to your name or email. The country is resolved by our load balancer before the request reaches our service, so the licence service itself never receives or stores your IP address. The load balancer's own request log does record it, for 30 days, as described in the next paragraph. This tells us how many people use Lorah, on which versions and platforms, and nothing whatsoever about your work.
Server request logs. lorah.ai and license.lorah.ai are served through Google Cloud. Its load balancer writes a standard request log for every request: your IP address, your browser identification, the address requested, the referring page, the time, and any parameters in the address, including click identifiers that an advertising network may add to a link it sends you through. Google keeps that log for 30 days, then deletes it. We use it for security and for aggregate statistics: how many people visit, from which sources, on which browsers, and how many download the app. Download links on this site pass through the same servers so that a download can be counted. We do not use the log to identify visitors, and the aggregate figures we keep contain no IP address and no click identifier. This website uses no analytics script and no cookies.
Crash reports, only if you switch them on. Off by default. Opt in at first run or later in Settings, Data & Privacy. A report carries the error type, the app version and platform, and whether a sync succeeded or failed. Never chat content, memory, file names, prompts or API keys. You can review queued reports before they send. Two further switches, a redacted diagnostic snapshot and linking reports to your license, are also off by default.
Offer claims, only if you claim an offer. When you enter an offer code and your email at lorah.ai/claim, the license service stores your email, the offer code, when you claimed it and when you confirmed it, the advertising labels in the link that brought you (for example utm_source=facebook), the site that referred you, reduced to its domain, and an approximate country. We use them to email you a confirmation link and your licence code, to keep each offer to one licence per email, and to count how many people an offer brought and how many of them went on to subscribe. The emails are delivered by Resend, an email delivery service that processes your address only to deliver them. How long we keep it: a claim you never confirm is deleted 30 days after you made it. If you confirm but the offer cannot give you a licence, for example because your email already has one, that record is deleted after 12 months. The advertising labels, referring site and country are removed from every claim after 12 months, and the records of the emails we sent you about it are deleted after 12 months. A confirmed claim, meaning your email, the offer and its dates, is kept for as long as the licence record it created, because it is what limits each email to one offer licence. Claiming an offer does not add you to any mailing list, and we send you nothing else because of it.
Beta applications. The beta has ended and we no longer accept applications. We keep the applications we received: your name and email, your answers to the form, how you heard about Lorah and the link you came from, the site that referred you, reduced to its domain, and an approximate country. A copy also went to the Google Form and Sheet we used to review them. We use them to support the testers who joined and to keep a record of who received beta access. Ending the beta did not end anyone's licence. To have your application deleted, write to privacy@lorah.ai.
Update emails, only if you signed up. If you signed up for updates on this site, we keep your email address, where on the site you signed up, the site that referred you, reduced to its domain, and when you signed up or unsubscribed. We send a small number of product emails; reply UNSUBSCRIBE to any of them and we stop. To have your address deleted, write to privacy@lorah.ai.

What we never collect

Your API keys. Your prompts. Your completions. Your project content. Your chat history. Your documents. No content of your work, ever. No crash reports that capture your data. No cookies and no cross-site tracking on this website. No advertising network code on this website. We do not sell or share your data.

Contact

Privacy questions: privacy@lorah.ai, or message Yoram Golandsky directly. If this policy changes, the date below changes with it.

VersionLast updated 5 October 2026PublisherLaGuardAIPlain-language versionLocal-first by design