Privacy, terms, and support.

Lore is a context and trust service operated by Lore in the United States. This policy explains how we handle data from Slack and the Lore service.

Data we collect

When an administrator connects Slack, Lore receives workspace and channel identifiers, user IDs and display names, messages from public channels that the administrator selects and the bot has joined, direct mentions of Lore, and OAuth metadata. Lore does not request Slack email addresses, private-channel access, files, passwords, or payment data through the Slack app.

How we use data

We use selected Slack content to create a tenant-isolated, cited knowledge base and to answer direct @Lore questions with links to supporting sources. We also use limited operational metadata for security, reliability, abuse prevention, and support. We do not sell Slack data, use it for advertising, or use Slack data to train large language models.

AI processing

Lore sends only the context needed for extraction or an answer to Groq-hosted Meta Llama models. Model output can be inaccurate, so users should verify important answers against the citations Lore provides. Groq does not use API customer inputs or outputs to train models. Under Groq's default inference controls, inputs and outputs are not retained except temporary reliability or abuse logs for up to 30 days; zero-data-retention controls are available from Groq.

Storage, retention, and security

Customer data is logically isolated by tenant. OAuth access and refresh tokens are encrypted at rest using AES-256-GCM, requests are protected with TLS, Slack requests are signature-verified, and OAuth uses one-time state values. Selected source data is retained while the source or account remains active so Lore can provide cited answers. Customers may disconnect a source or request deletion at any time. We retain only limited records where required for security, fraud prevention, legal obligations, or dispute resolution.

Sharing and subprocessors

We disclose data only to service providers needed to operate Lore, to comply with law, or to protect users and the service. Our current subprocessors are listed below. We do not permit subprocessors to use customer data for their own advertising or model training.

Your choices and requests

Workspace administrators control which public channels Lore can read and can remove Lore from a channel or workspace. To request access, correction, export, restriction, or deletion, email info@jointhelore.com. We verify the requester and normally complete validated deletion requests within 30 days, subject to legal requirements and backup expiration.

Lore is not directed to children under 13. We may update this policy and will post the new effective date here.

By installing or using Lore, you represent that you are authorized to connect the relevant workspace and agree to these terms and the privacy policy above.

Lore provides read-only knowledge retrieval and AI-generated answers from sources an administrator selects. You are responsible for the content you connect, user permissions, and reviewing generated output before relying on it. Lore may produce incomplete or inaccurate output and is not a substitute for professional legal, medical, financial, or compliance advice.

You may not use Lore to violate law, another person's rights, Slack's terms, or security controls; attempt unauthorized access; distribute malware; or abuse the service. We may suspend access to protect customers, Slack, or Lore.

The service is provided on an “as available” basis without warranties to the maximum extent allowed by law. To the maximum extent allowed by law, Lore is not liable for indirect, special, incidental, consequential, or punitive damages. These terms are governed by the laws of the United States and the state where Lore is headquartered, without regard to conflict-of-law rules.

You may stop using Lore at any time and uninstall the Slack app. We may update these terms by posting an updated effective date. Questions can be sent to info@jointhelore.com.

Lore uses the following subprocessors to provide the service. Each receives only the data needed for its role.

• Vercel — application hosting, delivery, and operational logs; United States.
• Supabase — managed PostgreSQL database and authentication; United States deployment.
• Groq — hosted inference for Meta Llama models; United States. API customer data is not used for model training; limited reliability or abuse retention may last up to 30 days under default controls.
• Slack — workspace authorization, events, and message delivery under the customer's Slack agreement.

We will update this list when subprocessors materially change. Questions or objections may be sent to info@jointhelore.com.

Email info@jointhelore.com for product support, privacy requests, or security reports. No additional account is required. We aim to acknowledge support requests within two business days and prioritize credible security reports.

Include the affected workspace, a description of the issue, reproduction steps, and any relevant timestamps. Do not include passwords, OAuth tokens, or sensitive customer content in email.