Privacy notice
Updated September 23, 2026
About this notice
This notice describes information processed by DeployLint’s hosted website, GitHub integration, dashboard and agent tools. Contact privacy@deploylint.com about privacy, access, correction or deletion requests.
Information processed
- GitHub account identifiers, login name, avatar, installation access and workspace membership used to authenticate you and authorize repository access.
- Repository metadata and selected repository files, such as manifests, lockfiles, workflows and deployment configuration, together with commit identifiers, pull request and review information, scan findings, policy decisions and deployment receipts.
- Workspace preferences, setup and maintenance requests, agent-token records, usage counts, support correspondence, and private customer-operation notes entered by authorized operators.
- Stripe customer and subscription references, plan and payment status, billing event records, and information you provide to Stripe. Payment details are entered with Stripe; DeployLint does not receive your complete payment-card number.
- Session and sign-in cookies, authentication records, operational logs and product-usage events. Hosting providers may process request metadata, including IP address, user agent and requested URL, to deliver and protect the service.
Why we use information
We use this information to operate accounts, inspect authorized repositories, generate requested workflow changes, evaluate deployment policy, maintain audit evidence, enforce usage limits, administer subscriptions and trials, support customers, investigate abuse and improve reliability. The hosted service uses operational and product analytics; the earlier local-only pilot’s no-telemetry description does not describe this service.
On public pages, first-party analytics records page paths, a referrer hostname or direct label, and selected navigation actions such as opening the setup flow. It does not set an analytics cookie or send names, email addresses, full referrer URLs, or a cross-site visitor identifier. Global Privacy Control and Do Not Track stop this public event collection.
We do not sell personal information or use it for third-party behavioral advertising.
Providers and disclosure
Cloudflare hosts the application, storage and operational infrastructure. GitHub provides account authentication, repository access, pull requests, checks and deployment integrations. Stripe processes payments and subscription management. Information required for those functions is processed by the relevant provider. Support information may also be processed by the email service used to handle your request.
Repository comments, checks and pull requests are visible according to your GitHub repository’s access settings. A public repository may make that information public. We may disclose information when required by law or when necessary to investigate abuse or protect the service and its users. Providers may process data in countries other than your own.
Retention and deletion
Uninstalling the GitHub App removes its authorized access; it does not automatically erase historical records or cancel billing. Account, billing, support and audit records may remain after disconnection to operate the service, resolve disputes, prevent duplicate processing and meet legal obligations. Deployment receipts are audit records and are not presented as automatically expiring when the app is uninstalled.
Request access, correction or deletion by email. We may verify your identity and authority over the affected workspace before acting. We will explain any records that must be retained. Available rights and exceptions depend on your location.
Your controls and security
You can restrict selected repositories or uninstall DeployLint through GitHub, revoke agent tokens in the dashboard, and manage a paid subscription through the billing page. Keep tokens and repository secrets out of support messages. Access controls and other safeguards reduce risk, but no service can guarantee complete security.
Changes
We will update this notice when the service or its data practices change and display the revision date here. See the service terms for usage and billing information.