Updated 15 November 2026

Privacy Policy

This policy covers the public Pullsight website and explains how a self-hosted installation handles data. The website does not run reviews and does not offer an account.

This website

pullsight.dev is a static site. It does not create accounts, accept subscriptions, or store repository content. The pages do not set analytics cookies. The host that serves the files may keep ordinary access logs, such as IP address, user agent, and the URL requested.

If you email info@pullsight.dev, that message and your address are used to answer you.

Questions about personal data can be sent to the same address.

Self-hosted installations

Pullsight does not receive account, repository, or review data from an installation you run. The organization that operates the deployment controls the data stored there. Passwords are not stored. Sign-in on that deployment uses OAuth, one-time codes, or API keys.

The software keeps the following in the operator’s database:

  • Account: email, display name, and avatar URL.
  • Auth: hashed API keys, hashed one-time codes, and encrypted OAuth or personal access tokens.
  • Organizations and repositories: names, platform metadata, and webhook secrets.
  • Reviews: findings, severity, pull request metadata, and optional indexed file content used for review context.
  • Notifications: digest preferences, and messages when the operator enables email.
  • Audit: security event metadata, including the action, IP address, success, and resource identifiers.

Local models and external providers

With a local model, such as Ollama on hardware the operator controls, the diff and the prompt stay on that infrastructure. They are not sent to an external API, and they are not sent to Pullsight.

With an external API, the content needed for the analysis is sent to the provider the operator selected, such as OpenAI, Anthropic, Azure OpenAI, or Gemini. The operator chooses that provider and is responsible for the terms that apply to it. Provider keys are read on the server and are not sent to the browser.

Cookies on a self-hosted dashboard

A deployment sets a session cookie and an httpOnly cookie named ps_dashboard_key in the browser of people who use that dashboard. Those cookies belong to the operator’s host. The software does not include third-party analytics. This public website does not set those cookies.

Retention and requests

On a self-hosted deployment, review records remain until the operator deletes them or purges the database. The operator defines any further retention policy and handles requests for access or deletion. The software does not include an automated export or deletion API.

Questions about the software itself can be sent to info@pullsight.dev.