Access and data

GitHub permissions

Lore checks repository access for both dashboard and MCP requests. An organization administrator does not automatically gain access to every repository. GitHub access changes may take up to five minutes to appear because permissions are cached.

Reading requires repository read access. Recording, editing, or retiring facts requires write access. Organization SSO, when enabled, adds an identity check; it does not replace GitHub repository permissions.

What is retained

Lore retains extracted text, evidence pointers, metadata, and optional embeddings. Scans use temporary clones rather than retaining a source-code archive. Extracted notes themselves are stored, so do not put credentials or other secrets in notes.

Classification and embeddings are separate integrations. Turning off AI classification does not also disable embeddings. Claims and search queries may be sent to the configured embedding provider.

Removing data

Retiring a fact hides it from normal retrieval and retains history. Disconnecting a repository hides its facts and schedules deletion after 30 days. Organization administrators can delete live organization data from Policy. Backups have a separate retention schedule.

For account-specific questions, use Support in the Lore dashboard. Do not include private source code, credentials, or customer data in a support request.