DeployDoctor
ScanCheck my appFix a buildPricingMy scans
More ⌄
Site Check and launch trustFix a build logGuidesGitHub ActionAI / MCPRepo WatchStatsFor partners
Menu ☰
ScanCheck my appFix a buildPricingMy scans
Site Check and launch trustFix a build logGuidesGitHub ActionAI / MCPRepo WatchStatsFor partners

LEGAL

Privacy policy

What DeployDoctor stores, who else receives it, how long it is kept and how to have it deleted. Last updated 6 November 2026.

Who is responsible

Nytto Labs, operated by Fredrik Kornelind (Tullinge, Sweden). Swedish sole trader. Approved for F-tax. VAT-registered. Fredrik Kornelind, a Swedish sole trader trading as Nytto Labs, is the controller for the personal data described here. Write to privacy@nyttolabs.com about anything on this page.

Scans and reports

  • Public repositories. A scan saves a report with the repository address (which includes the owner's GitHub name), the commit, file paths, line numbers and the findings. Secret values in the formats the scanner recognises (Stripe live secret, restricted and webhook keys, AWS access key IDs, GitHub personal access tokens, Supabase secret keys and private keys) are masked: keys to their prefix and last four characters, private keys to their header line. A value that looks like a placeholder, for example one containing "example", "test" or "your", is not treated as a secret. A suggested .env.example also masks OpenAI, Anthropic and Stripe test keys and JWTs. A value in any other format, such as a password in a database URL, is not recognised and can appear as written. Reports of public repositories are public: anyone with the link can open them, search engines may index them, and the latest report for a repository can be found by its name through the score page and the README badge. A report stays published after the code changes; ask us to delete it.
  • Private repositories. The report is stored privately with your Stripe customer ID. It opens only in a browser that holds your purchase cookie (the browser you paid in, or one where you restored the purchase with its payment reference and your email) or with your API token, also after a pass has ended. An API token is valid for one year from when you create it, contains your email address and Stripe customer ID (signed, not encrypted), and creating a new one does not cancel an old one. Anyone who has your token can open your private reports until it expires, so keep it secret.
  • Scan history. Every scan made from a browser that holds your purchase cookie, or with your API token, is recorded with your Stripe customer ID: the report ID, the repository, the date and whether it was private. That includes free scans after a pass has ended. Only subscribers see this history under My scans.

GitHub access

  • A read-only GitHub token you paste, or a GitHub sign-in you approve for scanning, is kept only in an encrypted cookie in your browser for at most 8 hours and is never written to our database. If you select repositories on GitHub for private scans, the read-only DeployDoctor GitHub App stays installed on your account until you uninstall it there; we can read those repositories only while that sign-in cookie is valid.
  • A GitHub sign-in you approve for a fix is kept only in an encrypted cookie in your browser for at most 8 hours and is never written to our database. It can write to the repositories where the Fix app is installed, and we use it only to check that the fix can be delivered and to open the fix pull request. A token you paste to open a patch pull request is used for that one request and not kept.
  • If you install the DeployDoctor Fix GitHub App, it stays installed on your GitHub account until you uninstall it. While it is installed, DeployDoctor can create short-lived tokens with write access to the repositories you selected, the installation ID is stored with the Stripe checkout of a paid fix, and GitHub sends us commit status events for those repositories. We use those events only to see whether a fix commit's build passed. The app writes only the branch, commit and pull request it describes. Uninstall it on GitHub to end this access.

Purchases

Payments are processed by Stripe; DeployDoctor never sees your card details. After you buy a pass or subscription we store your email address, your Stripe customer ID, the plan, its status and when it ends. If you bought a "Fix this one" or "Fix all" repair (no longer sold), we also store your email address, Stripe customer ID, the report and failed check it was for, the plan, its status, anything you typed in the checkout field and the patch we delivered; these orders are listed under My scans in a browser that holds your purchase cookie. Stripe keeps the checkout details, which include the repository you were scanning when you bought (a private repository's name too) and anything you typed in the optional checkout field. For a patch or a fix pull request, Stripe also keeps the report ID and an encrypted copy of the patch, and for a fix any live site address, error summary, Rescue Wall choice and GitHub installation ID.

For a fix pull request we store the repository, the diagnosed commit, our fix commit, the pull request address, whether the repository is private, the amount, the Stripe checkout and payment IDs and any refund ID. We also store a short error summary taken from our diagnosis, which also appears in the pull request description. If you give them, we store your live site address and whether you agreed to the public Rescue Wall. The wall shows the repository name, error summary, live address and pull request only for public repositories, and only when the person who ordered the fix ticked the Rescue Wall box, gave a live address, and Vercel reported that the fix commit built successfully.

What you type in

  • AI build-log diagnosis. The log you paste is sent to Anthropic's Claude for analysis. Before it leaves our server, these formats are masked: Stripe secret, restricted, test and webhook keys (publishable keys are not), OpenAI and Anthropic API keys, AWS access key IDs (not AWS secret keys), GitHub personal access tokens (ghp_ and github_pat_), Supabase secret keys, JWTs (Supabase keys included) and private keys. Passwords in database URLs, other tokens and personal data such as names and email addresses are not masked, so remove them before you paste. DeployDoctor does not store the log; your browser keeps the log, exactly as you pasted it, and its diagnosis until you close the tab.
  • Watch this repo. We store your email address and the repository, send a confirmation email and then an alert only when new problems appear. While a watch is confirmed, we rescan the repository once a day after it gets new commits, and each rescan is saved as a new public report of that repository (see Public repositories above). Unconfirmed sign-ups are deleted by a daily job once their latest confirmation link is 7 days old. After you unsubscribe no more email is sent, and the address stays on record, marked unsubscribed, until you ask us to delete it.
  • Reviews and ideas. We store the name, text and rating you submit. A review is shown publicly (name, text, rating and date) only if you agreed and it has been approved. Ideas are never published.
  • "Did this solve it?" Your answer is stored with the report or diagnosis ID and the keyed hash of your IP address described below, so one visitor counts once. Only the total is shown.

Live site check and leak check

We fetch the site you enter from our server, identifying as DeployDoctor. We read its homepage, the JavaScript files it loads from the same host, robots.txt, a few usual policy addresses and two made-up addresses that show whether the site answers every address. We do not run its JavaScript, and nothing about the site is saved. If its footer shows an EU VAT number next to a VAT label (or, on a page without a footer, the end of the page does), that number alone is sent once to the European Commission's VIES service to check it.

IP addresses

DeployDoctor never writes your IP address to its database. A keyed hash of it, which stays the same from day to day, is used to enforce daily limits and stop abuse; that hash is kept in the daily usage counters and with any "did this solve it" answer. Our host, Vercel, receives your IP address with every request and may keep it briefly in its request logs.

Cookies and browser storage

DeployDoctor sets no advertising or tracking cookies. Every cookie below is needed for something you asked for, or remembers a choice you made.

  • dd_customer: your email address and Stripe customer ID, signed so they cannot be changed (not encrypted). It lets this browser use a purchase you made or restored, for 90 days.
  • dd_checkout: ties a checkout to the browser that started it, for 24 hours.
  • dd_patch_access: access keys for up to five patch offers you checked or bought, for 1 year.
  • dd_github, dd_github_flow, dd_github_install, dd_fix_flow, dd_fix_token, dd_fix_install: an encrypted GitHub connection, for at most 8 hours (set-up steps 10 minutes).
  • dd_review_owner: lets this browser edit its own review, for 1 year.
  • dd_lang: your language, for 1 year.

Your browser's local storage holds your recently opened reports, your "did this solve it" answers and the checks you chose to hide; session storage holds your last pasted build log and its diagnosis. None of it is sent to us. Page views are counted with Vercel Web Analytics, which does not use cookies.

Who else receives data

  • Vercel: hosting, request logs and cookieless page-view statistics.
  • Supabase: the database.
  • Stripe: payments, subscriptions, refunds and the checkout details above.
  • GitHub: reading repositories, opening pull requests you ask for, and build status events from the Fix app.
  • Anthropic: AI build-log diagnosis.
  • Resend: the watch-this-repo emails.
  • The European Commission (VIES): VAT numbers found by the live site check.

Several of these companies are based in the United States. Transfers rely on the EU Standard Contractual Clauses or the EU-US Data Privacy Framework, as set out in each provider's data processing terms.

How long data is kept

Reports, purchase and fix-order records, scan history, watches you have unsubscribed from, reviews, ideas and votes are kept until you ask us to delete them, and so are the daily usage counters keyed by the hash of your IP address. Accounting records are kept as long as the Swedish Bookkeeping Act requires: until the end of the seventh year after the year in which the financial year ended. Unconfirmed watch sign-ups are deleted by a daily job once their latest confirmation link is 7 days old. Cached results of public-repository scans stop being used after two minutes and are deleted at the next cleanup. Stripe, Vercel, Anthropic and Resend keep data under their own retention rules.

Why we may use it

To deliver what you ask for and buy (contract); to keep the service secure, enforce fair-use limits, publish reports of public repositories and improve the checks (legitimate interests); to send watch emails, publish reviews and list fixes on the Rescue Wall (your consent, which you can withdraw); and to keep accounts (legal obligation).

Your rights

You can ask for a copy of your data, and have it corrected, deleted, restricted or moved, and you can object to its use or withdraw consent. Write to privacy@nyttolabs.com with the report URL or the email address you paid with. If you are unhappy with the answer, you can complain to the Swedish Authority for Privacy Protection (IMY) or the data protection authority where you live.

The AI plugin has its own plugin privacy notice. Terms · Refund policy

DeployDoctorPrivacy · Terms · Refunds · support@nyttolabs.com