Privacy Policy

1. Scope and who we are

This Privacy Policy explains how Lani Quantum Solutions, Inc., a Washington profit corporation (“Lani,” “we,” “us,” or “our”), handles information in the standalone Brief website and browser application (“Brief”).

This policy applies to Brief only. Lani Prime, cloud workspaces, and other Lani products may have different data paths and are covered by the policies presented with those services.

Brief is intended for people who are at least 18 years old. It is not directed to children.

2. Data Brief accesses

Brief accesses information only after you choose a provider and authorize the requested permissions.

Mailbox and account data

• Your connected account identifier and email address.
• Email message headers, senders, recipients, subjects, bodies, thread information, timestamps, attachments or attachment metadata, and provider labels or folders needed for the feature you use.
• Mailbox organization such as Gmail labels or Outlook folders.
• Messages you approve for sending and label or folder changes you explicitly approve.

Information created on your device

• Settings, connected-account references, and local model selections.
• Summaries, topics, priority and spam assessments, embeddings, organization recommendations, drafts, and review state generated for you.
• OAuth credentials and any AI provider API key you enter, stored in Brief’s browser-local secure storage.
• Downloaded local-model files cached by your browser.

Basic website request data

The infrastructure that delivers the static Brief files may process ordinary request information such as IP address, browser type, requested URL, timestamp, and security diagnostics. This delivery data does not include the contents of your mailbox or Brief’s local results.

3. Where processing happens

Brief runs as a WebAssembly worker inside your browser. Its mailbox connection, working state, and local intelligence remain separated from Lani Prime and Lani cloud workspaces.

Local model

If you select a local model, model files are downloaded to and cached on your device. Message context, prompts, and generated results remain in your browser.

Your provider key

If you affirmatively select a supported external AI provider and enter your own API key, Brief sends the prompt and email context needed for the visible feature directly from its browser worker to that provider. Lani does not receive the API key or prompt. The provider’s terms and privacy practices apply to that processing.

Brief currently supports direct API requests to Anthropic and OpenAI. Review your selected provider’s account settings and policies before using that option with confidential email.

4. How data is used

Brief uses mailbox data and locally derived data only to provide or improve features that you can see and control, including:

• Reading and presenting the mailbox scope you selected.
• Generating summaries, topics, ratings, suggested organization, search indexes, and reply drafts.
• Sending only messages that you review and approve.
• Applying only provider-side label or folder actions that you explicitly approve, unless you separately enable a clearly disclosed automation mode.
• Restoring your settings and results on the same browser profile.
• Protecting Brief, investigating abuse, and complying with law.

We do not use mailbox data for advertising, sale, credit decisions, surveillance, or unrelated product development.

5. Google Workspace API data

Brief may request Gmail permissions to read messages and mailbox organization, send a user-approved reply, and apply a user-approved label. Brief requests access in context and uses the narrowest permission practical for the feature.

This commitment applies to raw Google Workspace data and data derived from it. In particular:

• We limit use to Brief’s prominent, user-facing email features.
• We do not sell Google Workspace data or use it for advertising, credit-worthiness, lending, or data-broker services.
• We do not use Google Workspace data to create, train, or improve a generalized or non-personalized machine-learning or artificial-intelligence model.
• Lani personnel do not read your Google Workspace data unless you give explicit consent for specific data, access is necessary for security, or access is required by law.
• Any transfer to an AI provider occurs only when you select that visible feature and provider, and only to produce the result requested by you.

6. Sharing and disclosure

Lani does not receive or sell the mailbox data processed by standalone Brief. Data may leave your browser only in these circumstances:

• To Google or Microsoft when Brief reads data or performs an action you authorized.
• To the external AI provider you affirmatively select, for the prompt needed to provide the visible feature.
• When you export, copy, send, or otherwise direct Brief to disclose information.
• When required to protect security or comply with applicable law.

Ordinary static-site delivery and security may be provided by hosting and network vendors acting for Lani. They receive website request metadata, not Brief’s browser-local mailbox database.

7. Retention, disconnection, and deletion

Brief’s local data remains in the browser profile until you remove it, clear site data, or the browser removes it. Local model files may remain in the browser cache independently of mailbox results.

• Use Clear everything in Brief to remove its connected-account references, tokens, provider keys, settings, and locally stored results from that browser profile.
• Clear the site’s browser data to remove remaining caches, including downloaded local-model files.
• Revoke Brief from your Google or Microsoft account security settings to revoke provider-side authorization.

Clearing Brief does not delete messages from your mailbox. Provider-side actions already approved and completed—such as a sent reply or applied label—remain with the email provider unless you change them there.

8. Security

Brief uses browser isolation, a WebAssembly worker, encrypted browser-local secret storage, OAuth authorization, and secure network transport where supported. API keys are not written into committed application source or intentionally exposed to page scripts after they enter Brief’s secure worker.

No system is completely secure. You are responsible for securing your device, browser profile, email account, and any external-provider key. Contact us promptly if you believe Brief has been involved in unauthorized access.

9. Your choices and rights

You choose whether to connect an account, which model mode to use, whether to approve a reply or mailbox change, and when to disconnect or clear local data. You can decline a requested OAuth permission, but the related feature will not work.

Depending on where you live, you may have rights concerning personal information Lani itself holds about you. Email legal@lani.run to request access, correction, deletion, or other available rights. Because standalone Brief’s mailbox data stays on your device, Lani generally cannot retrieve or delete that local data for you.

Changes to this policy

We may update this policy as Brief changes. We will update the date above and provide additional notice when required. If a change materially expands how Google user data is accessed, used, stored, or shared, we will provide notice and obtain consent before using that data in the new way.

10. Contact us