Privacy notice

Data Limn handles

• Account data: identifiers and profile fields returned by GitHub sign-in, such as a GitHub user ID, username, display name, avatar URL, and email when GitHub provides it.
• Thread data: repository URL, file path, commit reference, selected text and surrounding anchor context, comment bodies, reactions, resolution state, author attribution, and timestamps.
• Operational data: request logs and product events needed to operate and understand the beta. Product analytics may include event names, account or anonymous identifiers, page or request paths, repository host, and campaign parameters.
• Contact data: the email address and message you send when contacting Limn or applying to the design-partner program.

Where threads live

Limn stores thread and comment records in its service database and associates them with a GitHub repository URL and file path. Threads are not committed to Git and do not become part of the repository’s history.

The current beta is for public repositories. Anyone who can open a public file in Limn may be able to read its threads. GitHub sign-in is required for actions that write or change thread data.

Browser storage and authentication

Limn uses browser session storage for the signed-in session token and for attribution parameters that need to survive navigation. Session storage normally lasts for the browser tab’s session. Signing out removes the Limn session token from supported browser storage.

GitHub sign-in and repository access are provided through GitHub. Authentication and provider credentials are processed by Limn’s API to perform the requested operation.

Service providers

Limn relies on GitHub, hosting and database infrastructure, and configured analytics or email providers to run the beta. Those providers process the data needed for their part of the service. PostHog product analytics is used when the deployment is configured with it.

Retention, access, and deletion requests

Limn does not currently publish a fixed retention schedule or provide a self-service export or account-deletion workflow. Submit a privacy request to request access, correction, or deletion. The team will review what can be completed in the beta and explain any technical or legal limitation.

Because this is an early beta, do not rely on Limn as the only copy of information you need to preserve.

Changes and questions

This notice may change as the product and its infrastructure change. The date above identifies the version currently published. Send privacy questions to privacy request form.