Skip to content

Legal

Privacy Policy

This policy explains how vetkit (“vetkit”, “we”, “us”) handles personal data when you use vetkit.dev, the vetkit app, the API, the MCP server and the vetkit GitHub App. This policy also covers the VetKit Network Monitor browser extension, the VS Code extension and the DAST desktop application.

Last updated
vetkit is in beta. We wrote this in plain language and will update it as the product matures; material changes will be announced on this page and, where appropriate, by email.

Summary

  • We read your code only to audit it, never execute it, and delete each checkout when the audit ends.
  • We store findings, not repositories. Secret values are never stored.
  • We do not sell personal data, show ads, or use your code to train AI models.
  • This website uses cookie-free Cloudflare Web Analytics for aggregated traffic and performance metrics, without advertising trackers or session recordings.

What we collect

Account and sign-in data

We store your chosen provider’s user identifier, verified email address and any display name or avatar it supplies. GitHub sign-in also provides your username and the vetkit GitHub App installations you can access. Email sign-in uses a short-lived, one-time link; we store only its token hash. We do not store social sign-in access tokens.

Single sign-on identity links

If your organization sets up single sign-on (OpenID Connect), we link your account to that identity provider when single sign-on creates your account (or first opens one your organization provisioned for you), or after you confirm the link while signed in another way. A link stores the organization, the provider’s issuer, client identifier and configuration version, your subject identifier at the provider (sub), the email address it reported, how and when the link was made, the last single sign-on sign-in and when we notified you about it. A pending confirmation is a one-time record (provider identity, email address and return page) whose link token is stored only as a hash and is valid for ten minutes. We email you when a link is confirmed and, once, when an account created through single sign-on is first opened another way. You can review and remove your links in the app under Settings → Security.

SCIM provisioning

If your organization provisions users through SCIM, its identity provider sends us each user’s email address (userName), external identifier, given, family and display names and active flag, which we store with the organization. Deactivating or deleting a user through SCIM removes the membership and revokes that user’s API keys, DAST desktop credentials, single sign-on sessions and pending invitations in that organization. SCIM tokens are stored only as hashes, with the time and IP address of their last use.

Repository and installation data

For repositories you connect: installation id, repository id, owner and name, visibility and default branch, and GitHub events about installation changes and pushes.

Audit data

For each audit: the ref and commit SHA, timing and status of each analyzer, tool versions, scores and grades, and findings. A finding contains the rule, category, severity, file path, line numbers, a short code snippet (up to 1 KB) and remediation guidance. Snippets for secret findings are redacted; to recognize the same secret across audits we store a one-way cryptographic hash of it, not the value. Analyzer logs are truncated and kept with the audit to help you debug failures.

Git history (optional check)

If you select the Git history check, the report stores up to 500 commits’ titles, dates and change statistics, and each author’s name with a stable hashed identifier so that activity can be grouped by contributor. Commit bodies, patches and author email addresses are not stored; email addresses inside commit titles are replaced before storage.

Report share links

You can create a read-only public link to a report summary. We store the link token’s hash, who created it, its expiry, whether it was revoked, how many times it was opened and when it was last opened; viewers are not identified. The public view shows the repository name, scores and the titles of top findings only, without file paths, line numbers, code, secret values or commit SHAs.

Browser network reports

If you explicitly approve saving a Chrome extension report to your account, we store page and resource origins, request counts, error and status types, durations, sizes, thresholds and up to 100 findings. URL paths are sent only if you separately choose to include them. Query strings, cookies, authentication headers and request or response bodies are not sent. Captures without this approval stay in your browser.

VS Code extension

When you sign in, the extension sends your device’s host name, which we use to name the API key it receives. The key allows reading findings, starting audits and requesting AI fix previews where permitted. To find the matching repository it sends the normalized git remote address (host/owner/name) of the open workspace. The API key is stored in VS Code’s secret storage on your device and is sent only to the vetkit API. The extension does not upload source code. You can revoke the key at any time by signing out or from your account’s security settings.

DAST desktop application

Dynamic scans run on your own computer with OWASP ZAP. When you upload a result, we store the target origin and scope origins, scan mode, status, ZAP version and add-ons, start and finish times, and each finding as a rule identifier, severity, confidence and occurrence count. URL paths, query strings, request and response contents and credentials never leave your computer. Signing in from the desktop application creates a device credential stored only as a hash; the approval screen shows the client name and the truncated network (/24 or /48) the request came from.

API keys and sessions

For API keys: name, prefix, scopes, rate limit, expiry and last-used time. Key secrets and session tokens are stored only as hashes.

Security and usage logs

Our servers log request metadata — IP address, user agent, timestamps, request id and response status — to operate the service and prevent abuse. Security-relevant actions in an organization (for example, creating or revoking an API key) are recorded in an audit log visible to organization admins. Organizations can also stream their audit log — including the acting user and IP address — to Splunk, Datadog or their own webhook endpoint (SIEM export).

Communications

If you contact us — through the early access form on vetkit.dev or by email — we keep what you send, such as your name, email address, team and the repositories you mention, to respond and follow up. Form submissions are delivered to us by email and are not stored on vetkit.dev.

Outreach emails to prospects

Our team may email people at companies that could be interested in vetkit. For each message we store the address, name and company, the template and note used, the message text, the delivery status, and the dates on which the booking link was clicked and the recipient unsubscribed. Links in these emails carry a signed token that identifies the message, so we learn when its booking link is used; there is no tracking pixel. Every message has an unsubscribe link and supports one-click unsubscribe, and unsubscribed addresses stay on a suppression list so that we do not write again. We send at most one outreach email to an address every three days.

Invite links

Every account has an invite code. If someone creates an account from your invite link, we store that relationship — who invited whom, when, and whether and for which audit the reward was granted — and add one promotional scan credit to each account after the invited person’s first eligible successful scan. Scan credits have no cash value.

First-party product usage

In the signed-in app we record the first report view and similar one-time product milestones, such as finishing onboarding, per user and workspace, with internal user/workspace identifiers and a timestamp. These milestones contain no code, findings, form contents, IP address or browsing history, and are not sent to an external analytics provider. Existing sign-in, repository connection and scan records help us understand where onboarding stops.

How you found vetkit

If you open the app from vetkit.dev and create a new account, we store where that visit came from, once: campaign labels from the link (utm_source, utm_medium, utm_campaign or ref), the referring website’s host name (never the page address), which vetkit.dev button you used and the site language. Only short labels made of letters, digits, dots, dashes and underscores are kept; anything else, including email addresses, is discarded. Nothing is recorded for existing accounts, and it is not sent to an external analytics provider. We use it to see which channels bring people who go on to use vetkit.

In-app credit requests

When you request more credits in the app, we store the amount you asked for, your optional note and the review decision with your account so an administrator can respond. Pro enquiries submitted before plans were retired (name, email, optional business details and requirements) are kept with your account/workspace context. A request is not a purchase.

What we do not collect

  • Your repository contents. Code is fetched into a temporary directory for the duration of an audit and deleted afterwards, whether the audit succeeds or fails. Only findings, as described above, are kept.
  • Secret values. Detected credentials are redacted before storage.
  • Sign-in and installation tokens. We do not persist social sign-in or GitHub App installation tokens. Email sign-in link tokens are stored only as hashes until expiry. Single sign-on link confirmations are likewise stored only as hashes and expire after ten minutes; we do not store identity provider tokens. Exception: if you connect a repository without the GitHub App, we store the access token you provide encrypted for audits and delete it when you disconnect the repository.
  • Payment data. vetkit is free during the beta and does not process payments.

How we use data

  • To provide the service: authenticate you, run audits you request, and show and export reports.
  • To keep it secure: detect abuse, enforce rate limits and investigate incidents.
  • To support you and send essential service messages, such as security or policy notices.
  • To improve vetkit using aggregated, de-identified metrics such as audit durations or rule hit rates.

Our legal bases, where the GDPR or UK GDPR applies, are performance of our contract with you, legitimate interests in securing and improving the service, and compliance with legal obligations.

Service providers

These external services are involved in running vetkit. Services marked optional are contacted only when you or your organization turn on the related feature:

  • GitHub — sign-in, GitHub App installations and repository access.
  • Google — authentication when you choose Google sign-in.
  • Apple — authentication when you choose Apple sign-in.
  • netcup — hosts the vetkit web app, API, database and audit workers in Germany.
  • Cloudflare — DNS, hosting and content delivery for vetkit.dev, bot protection (Turnstile) and delivery of early access requests sent from vetkit.dev, and forwarding of email sent to vetkit.dev addresses. Turnstile runs only when you open the request form. Cloudflare also provides cookie-free traffic and performance measurement through Web Analytics.
  • Resend — delivers our emails: one-time sign-in links, organization invitations and security notices (for example, a sign-in from a new device or a single sign-on identity linked to your account); the weekly security digest for organization owners and admins, which they can turn off under Settings → Organization → Monitoring, and the executive summary for members an admin lists; one-off messages from our team to a single user; and outreach emails to prospects. We keep a delivery log with each email’s type, recipient, subject and status, never the message body or its links.
  • OSV.dev (operated by Google) — dependency vulnerability scanning sends the names and versions of packages from your lockfiles and manifests, and looks up advisory details by their identifiers. Your source code is not sent.
  • deps.dev (api.deps.dev, operated by Google) — dependency health, license and package-existence checks send package names and versions. Your source code is not sent.
  • Public package registries — the hallucinated-dependency check asks npm, PyPI, crates.io, RubyGems, NuGet, Maven Central and Packagist whether a package that deps.dev cannot find exists. Requests contain only the package name and, for npm, the exact versions you declare. Packages your configuration resolves from a private registry or index, and local or workspace packages, are not looked up. When vetkit prepares a dependency upgrade fix, it reads release metadata for the affected package versions from npm, the Yarn registry, PyPI or the Go module proxy and checksum database.
  • CISA and FIRST — to prioritize vulnerabilities, we download CISA’s public Known Exploited Vulnerabilities catalog (from cisa.gov or CISA’s GitHub repository) and query FIRST’s EPSS API with CVE identifiers only.
  • Container registries — when you scan a container image, we fetch it from the registry it is published on (for example Docker Hub or GitHub Container Registry), using the credentials you provide for private images. Image search queries the Docker Hub API with the text you type.
  • Anthropic — only when the AI-authorship signal (beta) runs: a small, deterministic sample of files (at most 16 files, each truncated to 8,000 characters) and commit metadata are sent to Anthropic’s API for analysis. Under Anthropic’s commercial terms, API inputs are not used to train models.
  • AI providers you choose (optional) — only if your organization connects its own key for OpenAI, Anthropic, Google, Mistral, DeepSeek, Groq, xAI, Together AI or OpenRouter: AI review, AI fix previews, AI triage and AI evaluations send the code excerpts, findings or evaluation inputs they need to that provider, under your own agreement with it. Your key is stored encrypted.
  • GitLab and Bitbucket (optional) — repository access when you connect repositories from these services; your access tokens are stored encrypted.
  • Your organization’s identity provider (optional) — only if an organization admin sets up single sign-on: vetkit reads the provider’s public configuration and signing keys and, when you sign in through it, receives an ID token from which it takes your subject identifier, email address and name. The organization’s client secret is stored encrypted.
  • Credential issuers (optional) — only if your organization turns on secret verification: for up to 25 detected credentials per audit, we send each credential in a read-only request to the service that issued it (AWS, GitHub, GitLab, Slack, Stripe, SendGrid, Resend, OpenAI or Anthropic) to check whether it is still active. The value is held in memory only; we store the result, not the credential.
  • Integrations you enable (optional) — Slack, Microsoft Teams, Discord, Telegram, WhatsApp, Jira, Linear, ServiceNow, Splunk, Datadog or your own webhook endpoints receive the notifications, work items or security events you configure, such as finding titles, severities, repository names and links. Connection credentials are stored encrypted.

Retention

  • Repository checkouts: deleted when each audit ends.
  • Audits, findings and reports: kept until you delete them or their organization is deleted. You can delete individual audits in the app; disconnecting a repository keeps its audit history. When you ask us by email to delete your account, we delete the associated data within 30 days.
  • Deleted organizations: an owner can delete a team organization under Workspace settings → Organization by typing its slug to confirm. Access ends immediately: members lose access, queued and running audits are cancelled, API keys are revoked, repository tokens stored for individual audits are deleted and GitHub App installations are unlinked (the app stays installed on GitHub until you uninstall it there). After 30 days the organization and its data — including repositories, audits, findings, reports, memberships and its audit log — are permanently deleted. The deletion cannot be undone in the app. A minimal record of the deletion (the organization’s name and slug, the dates, and how many audits, API keys and installations were stopped) remains in our internal security log. Personal organizations belong to your account and cannot be deleted in the app; they are removed when we delete your account on request.
  • Report share links: expire at the time you choose or when you revoke them; the record is deleted 30 days later.
  • Browser network reports saved to your account are kept until you delete them or the associated user or organization is permanently deleted. Live captures clear at the end of the browser session; local reports remain until you delete them or clear browser data.
  • DAST desktop sign-ins: expire after 90 days. Uploaded results are kept until their organization is deleted.
  • SCIM provisioning records: deleted when the user is removed through SCIM or the organization is deleted; SCIM tokens expire after 365 days.
  • GitHub webhook payloads: pruned after 30 days.
  • Sessions: expire after 7 days of inactivity and in any case 30 days after sign-in, or when you sign out.
  • Single sign-on identity links: kept until you remove them under Settings → Security, an organization admin changes or removes the organization’s identity provider, the organization is permanently deleted or your account is deleted. Pending link confirmations expire after ten minutes and are then deleted.
  • Server logs: kept in rotating files on our server, at most three files of 10 MB per service. Older entries are overwritten as new ones arrive, so how long an entry survives depends on traffic rather than on a fixed period.
  • Email delivery log: deleted after 90 days.
  • Backups: deleted data may remain in encrypted backups until they roll over.
  • First-party product milestones: removed after 90 days and when the associated user or workspace is permanently deleted.
  • How you found vetkit: removed after 365 days and when the associated user is deleted.
  • In-app credit requests and earlier Pro enquiries: retained to handle your request until you ask for deletion or the associated user/workspace is permanently deleted.
  • Invite relationships: deleted with either of the two accounts.

Cookies & local storage

vetkit.dev sets no cookies. Cloudflare Web Analytics measures page views, referral sources, browser and device information, and page performance without cookies or cross-site tracking. We do not send form contents to analytics. Your light/dark mode and language choices are saved in your browser’s local storage. The vetkit app uses strictly necessary session and preference cookies, plus short-lived state cookies during social sign-in. The VetKit Network Monitor extension keeps live captures in browser session storage and saved local reports in extension local storage. To remember how you arrived, vetkit.dev keeps those campaign labels and the referring host name in this tab’s session storage until the tab is closed.

Your rights

Depending on where you live, you may have the right to access, correct, export or delete your personal data, and to object to or restrict certain processing. You can delete audits and disconnect repositories in the app, and uninstall the GitHub App from your GitHub settings at any time. You can review and remove single sign-on identity links under Settings → Security. Owners can delete a team organization in the app under Workspace settings → Organization; its data is permanently deleted after 30 days (see Retention). To delete your account, if you cannot delete an organization yourself, or for anything else, email privacy@vetkit.dev; we respond within 30 days. You also have the right to lodge a complaint with your local data protection authority.

International transfers

Our providers may process data in the European Union and the United States. Where data leaves the EEA or UK, we rely on appropriate safeguards such as the European Commission’s Standard Contractual Clauses. Services you connect yourself — such as AI providers, other code hosts and integrations — process data in the locations they offer and under their own terms.

Children

vetkit is a developer tool and is not directed at children under 16.

Changes & contact

We will post changes on this page and update the date above; material changes will also be announced in the app or by email. Questions about privacy: privacy@vetkit.dev. Security issues: see our security page.

Request early access

Tell us a little about your team and the repositories you want to audit. We onboard teams in small batches and will reply by email.

We use these details only to reply to your request. Privacy policy