Privacy Policy
Version 1.28 · 7 November 2026
Who is responsible
AELaboratories is the data controller for everything in this notice except one thing. Postal address: 500 Westover Dr #34489, Sanford, NC 27330, United States. support@borehole.dev.
The exception is a private survey. For the bundle the collector sends and the private report made from it, we are a processor: we act on the instructions of the customer who ran the collector, under our data processing agreement. That customer is the controller of its developers' data. If you worked on a private repository, ask that customer first; we help it answer you.
Our representative in the European Union (GDPR Article 27) is Cristina Kelly Emerson Fernandez del Pino, in Jerez de la Frontera, Spain. You or a supervisory authority can write to her about anything in this notice, in English or Spanish: eu-representative@borehole.dev.
The short version
- Reports do not record commit authors' names or email addresses. Authorship is stored as counts and bands, such as "top author more than half of 257 commits" or "40 of 56 authors have exactly one commit". On any project, a finding about the top contributor describes one person, so we treat it as personal data. A quoted line can contain a name someone wrote in it, and whoever controls the repository can remove it. After 2 years a public report no longer carries findings about one contributor. See if you contributed to a repository, which also says how to object.
- Your IP address is held for 30 days with your session when you sign in, and for 30 days in the servers' request logs. Free-survey counts, and the count of reports read while signed out, never store it: they use a hash under a secret salt, because the only question we ask of it is whether it is the same subject as before.
- Our servers and database are in the EU, with Google Cloud in europe-west1 (Belgium). Mail you send us is not: Google Workspace holds it, in the United States and other Google locations. The servers' request logs stay in the EU too, for 30 days.
- We do not sell anything to anyone, and there is no advertising.
What we store, and why
| What | Why | Lawful basis | Kept |
|---|---|---|---|
| Your GitHub id, login, display name, email and avatar, if you sign in | To know who you are, to apply your allowance, and to show you what you bought | Contract | While the account exists |
| Whether you want product updates and promotional email, and when you chose. For an account you delete, its address until Brevo confirms deleting the contact | To send product updates and promotional email through Brevo, to accounts that have not opted out (below) | Legitimate interest; you can opt out at sign-in, in your account, or from any email | The choice: while the account exists. At Brevo: until you opt out or delete your account. A deleted account's address: until Brevo confirms, then deleted |
| Session id, user agent and address, and the GitHub token that signing in gave us | To keep you signed in, to spot session abuse, and to ask GitHub whether you still control a repository when you act as its owner | Legitimate interest | 30 days, then deleted |
| Collector tokens: the name you gave each one, its first characters, a hash of the token, what it may do, and when it was created, last used and revoked | To accept bundles from your collector and, within the scopes you gave a collector token, to delete your private reports or start surveys of public repositories for your account. The collector token itself is shown once and never stored | Contract | Until you delete the account |
| Each detection ruleset issued to your collector: when, its version, the collector's version, the requesting software's user agent, a salted hash of the address it asked from, and the made-up names that mark that copy | To trace a ruleset found outside the account it was issued to back to that account, as the Terms say, or to its orders once the account is deleted | Legitimate interest | While the account exists, because a copy can surface years later. Deleting the account detaches them from it: each stays, with no link to the account, and records the orders the account held or spent, if it had any. Those orders lose their link to anyone after 7 years, as the orders row says |
| Each time GitHub confirmed you control a repository: its name, your permission on it, and when | A record of who acted as a repository's owner, for example to delist a report, answer a finding or remove quoted text | Legitimate interest | Until you delete the account |
| Where the Borehole GitHub App is installed: the GitHub account's login and number, whether it is a person or an organisation, which repositories it covers, and whether it is suspended | To know where the App is installed, which GitHub tells us whenever that changes | Legitimate interest | Until the App is uninstalled. Deleting your account deletes the installation on your own GitHub account; if the App is still installed there, GitHub's next notice about it records it again. An organisation's installation is the organisation's |
| Free-survey counts per day: under a salted hash of your address when you are signed out, never the address itself, and under your account's number when you are signed in | The free allowance | Legitimate interest | 30 days. Deleting the account deletes the counts under its number at once |
| Which public reports were read while signed out: a salted hash of the address, never the address itself, and each report's number | To let a signed-out visitor read 5 reports in any 30 days, then ask them to sign in | Legitimate interest | 30 days, then deleted |
| The surveys you start: the repository, whether it was private, when it ran and how it ended, whether you reached the finished report from its waiting page, and who asked for it (your account's number when you are signed in, the salted hash above when you are not, or the Report key that paid). Until the survey has finished and been counted, the analytics id below that you started it under | To run the survey, show you its progress, connect it to the report it produced, and email you a link if you are signed in and left before it finished | Contract (signed in, or with a Report key) · Legitimate interest (signed out) | While the account exists. Deleting the account detaches them from it: they stay, with no link to the account, and a survey a Report key paid for stays linked to that key's order. A signed-out survey's salted hash is removed 30 days after it ran |
| Each survey run with a Report key: the repository, the commit, when, whether it was private, and the account it was charged to | To prove what a Report key was spent on, and to show whoever holds the Report key what it surveyed | Contract | As long as the order. Deleting the account detaches them from it: they stay with the order, with no link to the account |
| The bundle your collector sends, as it arrived | To score it into your report. It waits in a storage bucket for the survey worker, because the part of the service that receives it has too little memory to score a large one | Contract | Until scoring begins, when it is deleted as it is read, whether the survey then succeeds or fails. A bundle never scored is deleted after a day. The bucket keeps no backups, versions or deleted copies, so no backup holds it |
| Reports: findings, evidence pointers, bands, rejection log | The product. A report is about a repository. Its authorship figures are counts and bands, and a finding about the top contributor describes one person | Legitimate interest (public) · For a private report, we are the customer's processor (above) | As long as we run the service, because a verification code has to keep resolving. A public report's findings about one contributor: 2 years from the survey, then withheld, and People is no longer rated. The account that bought a private report can delete it on the account page; its code then says it was deleted |
| The facts a survey of a public repository read: commit hashes, dates and subjects, file paths and counts, dependency names, and matched lines of up to 120 characters. Author names and addresses, and the address that committed each change someone else wrote, are hashed first, under a key made for that one survey and never kept, and email addresses and @handles are removed from commit subjects; never whole files | To re-read a public report under new checks without cloning the repository again | Legitimate interest | As long as the report. 2 years after the survey, the author and committer hashes in them are replaced with values made under a key nobody keeps, as after an objection. Never kept for a private repository: what crosses from one is never whole files; facts and short excerpts of up to 120 characters where a check matched, and it is deleted once scored, as the bundle row says |
| Share links you make: which report, when, and when revoked, and the link itself, which is how we recognise it | To let someone without an account read a report you chose to share | Contract | A link works until you revoke it. Deleting the account revokes every link you made, every link to your private reports, and every link made under an order you paid for. The record of a link is kept as long as the report |
| Order reference, amount, tier, email, Stripe identifiers, and the account you added the Report key to, if you did. For a Report key we give, who at Borehole issued it and a note of whom it was for. The analytics id below that you started the checkout under, and where you came from: the campaign tags on the link that brought you, the page you landed on and the site that linked you, never an ad click id | To take payment, prove what you bought, and let the collector spend it. For a given key, to know whom we gave it to. To count the payment in the funnel and know which campaigns bring buyers | Contract, then legitimate interest in keeping tax and accounting records and in answering a payment dispute. A given key's note: legitimate interest | The order: 7 years from the order, as a tax and accounting record. Then the account it was added to, the Stripe identifiers and the repository hint are removed. A given key's order is no tax record, and is kept as the record of what the Report key was spent on, on the same schedule. The email address, a given key's note and the analytics id: 13 months from the order, then removed |
| Mail we send you: your address, the subject and the message, including a receipt's key. Once it is sent, Resend's id for it, and whether Resend reports it delivered, bounced or marked as spam, with the time. Not the reason a mail server gave | To deliver it, to try again if delivery fails, and to know when a receipt did not arrive | Contract | 30 days after it is sent or given up on, then deleted. Deleting the account deletes it at once, sent or not |
| An address we stopped mailing because mail to it bounced for good or was marked as spam: a SHA-256 hash of the address, the reason, and the date. A hash of an address is still personal data | Not to send mail to an address that cannot take it or does not want it | Legitimate interest | Until you ask us to remove it, or your account is deleted. It has no end date because its job has none: forgetting it would mean mailing an address that bounced for good or asked not to be mailed |
| An assessment request, the analytics id below that you sent it under, and where you came from: the campaign tags on the link that brought you, the page you landed on and the site that linked you, never an ad click id | To reply to you and scope the work. It goes to a partner firm only if you agree to be referred to it. To count how a request was answered in the funnel, and know which campaigns bring requests | Steps you asked for before a contract | 180 days after you send it, then deleted, or sooner if you ask or your account is deleted. Our reply and what follows are mail, kept as the mail row below says |
| A message you send through the site's form: the address you give, what you write, and the page you sent it from | To answer you | Legitimate interest | 180 days after you send it, then deleted, or sooner if you ask or your account is deleted. Our reply and what follows are mail, kept as the mail row below says |
| Mail you send to an address at borehole.dev: your address, what you write, and anything you attach | To answer you, and to act on a refund, access, deletion or takedown request or an objection | Legitimate interest · Legal obligation, for a request under data-protection law | 180 days after the last message in the thread, then deleted. What the request changed (a refund, an erasure, an objection) is kept where the rows above say |
| A rating of a report, or a free key holder's answers about one, and any comment you add | To learn which reports were useful and what to improve | Consent | Until you withdraw consent by asking us to remove it, or your account is deleted |
| A rebuttal you publish, and the GitHub login that proved you control the repository | To publish your answer beside the finding it answers, signed, so a reader knows it came from the repository's owner | Legitimate interest | As long as the report. If you ask, or delete your account, it is anonymised: the words stay, because a reader may have relied on them, and your login goes |
| A pseudonymous analytics id — a hash, under a secret salt, of your address and browser, or of your account's number when you are signed in; never the raw address or your GitHub identity. Signing in joins the hash of your address and browser to your account's number. Each step counted under it carries your browser's user agent, and whether the request looked automated | To count how many people reach each step | Legitimate interest | One year, PostHog's retention on our plan. What was counted under your account's number, and under the hash joined to it, is deleted with the account |
| The pages you open, counted in your browser by PostHog's script: the page's address with the campaign tags and no other query string, the address of the site that linked you here without its path, when you arrived and left, your browser's user agent, and random ids that count your visit as one visitor. The ids sit in the tab's session storage until you close the tab. No cookie, and nothing kept from one visit to the next | To count how many people visit, which pages they reach and where they stop | Legitimate interest | One year, PostHog's retention on our plan. The random ids tie a visit to nothing else, so it cannot be found again to delete |
| Recordings of your visit during the beta, held by PostHog under the same random ids: what each page showed you, and the scrolling, mouse movement and clicks on it, with everything typed into a form masked in your browser | To see where the site is hard to use | Legitimate interest | 30 days. Nothing ties a recording to you or to an account, so it cannot be found to export or delete first |
One cookie, bh_src, that our server writes only when you arrive from another site or a campaign link: the page you landed on, the name of the site that linked you, the campaign tags on the link (utm_source and the like), an ad click id if the link carried one (gclid, fbclid, li_fat_id or rdt_cid), and the number and band of the last public report you read. A later arrival from another site or a tagged link replaces the latest arrival; the first stays. Signed, so a value we did not write is ignored, and no script can read it |
To know which sites and campaigns bring the people who survey, buy and ask us to work for them, and to tell Stripe that with an order | Legitimate interest | In your browser, 90 days from the latest arrival, then your browser deletes it. Not written with Do Not Track or Global Privacy Control on, or on a private report's page |
| Server request logs. For each request to the site: the IP address it came from, the full address requested, including any query string, your browser's user agent, the linking page when your browser sends one, and the time, status and size. Cloud Run writes one for every request. Our own line for a request keeps only the path, the status and the time it took | To run the service, and to investigate faults and abuse | Legitimate interest | 30 days in Google Cloud's logging, in europe-west1 (Belgium), then deleted |
Borehole's administrators can see an account's activity, read from the records above, to run the service and answer support: when it signed in, its collector tokens by name, the surveys it ran, the Report keys it holds and the links it shared. That view never shows a collector token or the name of a private repository. For the same reasons, administrators can open a private report, which names its repository, and see that name in the list of recent surveys.
What we deliberately do not store
- Your source code. We never clone or hold a private repository: the collector reads it on your own machine, and what crosses is never whole files; facts and short excerpts of up to 120 characters where a check matched. A public repository is cloned for its survey, and the copy is deleted when the survey ends, including when it fails. What survives is the report. On a paid survey of a public repository, the parts of it a review reads are sent to Anthropic for that review (see below). Never a commit author from the history, and never who bought the survey. A file it reads reaches it as written, with any names the file holds (see if you contributed).
- The collector's bundle, once scored. We hold it
only until it is scored, as the table above says.
It waits in a storage bucket that keeps
no backups, no earlier versions and no deleted copies, so once it is
deleted it is gone: no backup of ours holds it.
What we keep is the report. It is never attached to error reports.
Since collector 0.4.0 it also lists the dependencies your lockfiles pin
from public registries (name, version, ecosystem). We accept
collector 0.7.16 or later, which lists a package only
when its lockfile shows a public registry served it; every other one
is left out on your machine, whether it came from a private registry,
a git URL or a local path or its lockfile does not say, and the bundle
carries only how many. Every NuGet and Gradle package, whose files do not say
where it came from, is left out too. So is every Go module, for the same
reason, unless a published security advisory already names it or it is
one of a few published error-reporting libraries. From collector 0.7.9,
the history of your manifests crosses the same way: a dependency name
crosses readable only when a lockfile pins it from a public registry
or it is a common development tool; every other name crosses as a
fingerprint salted for that one survey, so the report can count it
and no one can recover it. A dependency with no lockfile crosses as
its version range and line, never its name. Your project's own package name crosses to our server as its manifest declares it, and when you run the collector our server sends that name to no one: it looks up a project's own package, in OSV or anywhere else, only for a public repository we survey ourselves. From collector 0.7.15, a Go module path on a host that does not serve modules to the public crosses as a fingerprint salted for that one survey instead.
Commit subjects cross as your files write them, with secret-named
values blanked, whatever host or package they name. So does the host
of an address named for telemetry, usage statistics or crash reports
when it is a known public service's, such as Sentry's or Datadog's;
from collector 0.7.15 any other reporting host crosses as a
fingerprint salted for that one survey. Earlier collectors send it,
and a Go module's own path, which names the host its code lives on,
as written. Our server, not the collector, looks the locked names and
versions up in OSV, a public vulnerability database. OSV receives each package's
ecosystem, name and version and nothing else: no repository name, no
path, no code, and nothing about you. For a public repository we survey
ourselves, the server also asks OSV about the surveyed commit and the
package the repository publishes, GitHub about the repository's own
advisories, and NVD about the product it is: public facts about public
code. Since collector 0.5.0 the
collector also reads committed
.envfiles, only to find credentials in them: it sends where a credential-shaped value sits and its kind, never the value and no other line. From collector 0.7.2 it also sends a short fingerprint of each value, salted for that one survey with a value that is never sent or kept, so equal values can be counted once and no value can be recovered or recognised. - Contributor identities. Authorship is counted, not named. Reports do not record commit authors' names or email addresses. A quoted line can contain a name someone wrote in it, and whoever controls the repository can remove it.
- Card details. Payment happens on Stripe's pages. We never see a card number.
- Your collector token. We keep a hash of it, which is enough to recognise it and useless to anyone who takes it.
- Commit author names and email addresses. Authorship reaches a report only as counts and ratios. The collector hashes names and addresses on your machine before sending them. From collector 0.7.12 each hash is keyed with a random value made for that one survey, which stays on your machine and is never sent or kept, so nobody, Borehole included, can test whether a guessed address belongs to an author. Bundles from earlier collectors were salted with the head commit, which the bundle carries. From collector 0.7.15 the collector also sends a hash, made the same way, of the address that committed each change someone else wrote, so the report can tell when one account applies most of the work. The hashes are still pseudonyms, not anonymous: each commit's id, date and subject travel beside them. We use them only to count, and discard them with the bundle. For a public repository we survey ourselves, names and addresses are hashed the same way, under a key made for that one survey and never kept, and kept with its stored facts for as long as the report exists, as the table above says, so that a re-read under new checks needs no fresh clone. So is a hash, made the same way, of the address that committed each change someone else wrote. The repository is public, so its commits name their authors to anyone. The key stops the kept hashes from being reversed. It does not stop anyone looking a commit up.
One exception, stated rather than hidden. Four checks quote a small amount of text as evidence: up to five TODO-style comments, up to four commit subjects, up to five unpinned dependency lines and one status line from the README's first screen, such as “no longer maintained”. In each case the quoted text is the evidence, which is why it is kept by default — paraphrasing a TODO would be worthless. Whoever controls the repository can remove it from a report at any time, which rewrites the stored report, so afterwards the report does not hold it at all. The pointers stay, so the line can still be found. For a public repository we survey ourselves, removing the text from one report removes it from every report of that repository, and every later report, including a re-read, is stored without it. The facts we keep to re-read the repository (see the table above) still hold the lines the checks matched, because the checks read them; no report made from them quotes the lines again.
Product email
When you sign in, one box asks whether you want product updates and promotional email from Borehole. Left unticked, you get them; ticked, you do not. They go through Brevo, an EU company, which receives your email address, your GitHub login, the date you signed up and your unsubscribe link, and nothing else about you. An account that has not chosen receives none. The lawful basis is legitimate interest. You can opt out at sign-in, under Manage my account, or with the link in any of these emails, in one click. Opting out deletes your contact from Brevo. Receipts and replies are not affected.
Who else processes it
These services process data we hold, on our behalf.
Stripe also acts as a controller in its own right: Stripe decides for itself how it handles your card and the payment, for fraud prevention and its own legal duties, under its own privacy notice. GitHub also acts as a controller in its own right: Your GitHub account, and what GitHub records when you sign in with it, are GitHub's, under its own privacy statement.
| Processor | For | Where | Transfer mechanism |
|---|---|---|---|
| Google Cloud | Hosting, database, scanning | europe-west1 (Belgium) | Google LLC: the EU-U.S. Data Privacy Framework and its UK Extension, under which it is certified, with the 2021 standard contractual clauses in its data processing terms as the fallback |
| Stripe | Payments | United States and globally | Stripe, Inc.: the EU-U.S. Data Privacy Framework and its UK Extension, under which it is certified, with the 2021 standard contractual clauses in its data processing terms as the fallback |
| Google Workspace | The mailboxes at borehole.dev: support@, billing@, takedown@ and security@ | United States and other Google locations | Google LLC: the EU-U.S. Data Privacy Framework and its UK Extension, under which it is certified, with the 2021 standard contractual clauses in its data processing terms as the fallback |
| GitHub | Sign-in, metadata for public repositories, and who controls a repository | United States | GitHub, Inc.: the EU-U.S. Data Privacy Framework and its UK Extension, under which it is certified, with the 2021 standard contractual clauses in its data processing terms as the fallback |
| OSV (Google Open Source Security) | Known-vulnerability lookups | United States | Receives nothing about a person |
| NVD (US National Vulnerability Database) | Known-vulnerability lookups for a public repository | United States | Receives nothing about a person |
| Anthropic | Review of paid reports on public repositories | United States and other Anthropic locations | Anthropic, PBC: the 2021 standard contractual clauses in its data processing terms. It is not certified under the EU-U.S. Data Privacy Framework |
| Resend | Transactional email | eu-west-1 (Ireland) | Resend, Inc.: the EU-U.S. Data Privacy Framework and its UK Extension, under which it is certified, with the 2021 standard contractual clauses in its data processing terms as the fallback |
| Brevo | Product updates and promotional email | France (EU), run by Sendinblue SAS | Kept in the EU by an EU company: no transfer outside the EU |
| Sentry | Error reports | Germany | Functional Software, Inc.: the EU-U.S. Data Privacy Framework and its UK Extension, under which it is certified, with the 2021 standard contractual clauses in its data processing terms as the fallback |
| PostHog | Product analytics | EU cloud | PostHog, Inc.: the EU-U.S. Data Privacy Framework and its UK Extension, under which it is certified, with the 2021 standard contractual clauses in its data processing terms as the fallback |
What each one receives, and which the service can run without.
Stripe, Google Workspace, GitHub and Anthropic keep data outside the EU. You cannot use the paid product without Stripe, or sign in without GitHub. Google Cloud, Resend, Sentry and PostHog keep data in the EU regions named on the sub-processors page, but they are US-headquartered, and their terms allow access from the United States. The table above names the transfer mechanism for each one. For a copy of the clauses that apply, write to support@borehole.dev. Google Cloud keeps the servers' request logs in europe-west1 (Belgium).
Who else receives it
These are not processors. They receive data we hold and use it for their own purposes.
| Who | What they receive | When |
|---|---|---|
| Whoever you give a key to, such as a company that runs the collector on its own repository for you | What the key is, when it was bought, how long it has left, and every repository surveyed with it and when. Never your name or email address. | When you send them the key. Anyone holding a key can see this, so treat it like the key. |
| A partner firm | Your assessment request. | Only if you agree to be referred to it. |
Error reports and analytics
Error reports are scrubbed before they leave the process, by key name and by value shape: access tokens, Stripe keys and clone tokens are removed rather than redacted after the fact.
Page views are counted in your browser, without a cookie. Each page loads PostHog's script, which records the page you opened and when you left it. It sends the page's address with the campaign tags and no other query string, the address of the site that linked you here without its path, and your browser's user agent. Anything shaped like a paid key, a share link or a verification code is removed first. To count one visit as one visitor, the script keeps random ids in your browser's session storage for that tab. Your browser deletes them when you close the tab, and nothing is kept from one visit to the next. Your browser sends PostHog your IP address, as it does to any site it loads; PostHog discards it. The script does not load on a private report's page or on your account's pages.
During the beta, visits are recorded. While Borehole is in beta, the same script records what each page showed you and what you did on it: scrolling, mouse movement, clicks and the pages you moved between, so we can see where the site is hard to use. Whatever you type into a form is masked in your browser before anything is sent. It records nothing on the pages where you buy or use a Report key, pay, sign in, check a verification code or unsubscribe, on a share link, on your account's pages, or on a report as its buyer or the repository's controller reads it. The name and picture in the page's header are never recorded. PostHog deletes a recording after 30 days. We rely on legitimate interest: a product in beta has to see where people get stuck. Recording ends when the beta does.
Steps are counted by our server. Steps such as a survey started or a Report key used reach our server, which counts them. Each count carries a hash, under a secret salt, of your address and browser (or, when you are signed in, of your account's number), never the address itself or your GitHub identity; your browser's user agent; and the campaign tags on the link that brought you. No step names a private repository or carries anything made from its name. From our server, PostHog never receives your IP address or an ad click id. When you sign in, the hash of your address and browser is joined to your account's number, so the steps you took before signing in count as the account's. The export on your account page says what can have been counted under your account's number, and deleting the account deletes it.
PostHog, hosted in the EU, keeps both for one year on our plan, then deletes them. With Do Not Track or Global Privacy Control on, the script does not load and nothing is counted or recorded. Session replay is on during the beta, as above.
The site's fonts are served from borehole.dev, so a visit sends nothing to Google Fonts. The site itself runs on Google Cloud.
Your rights
Under the GDPR, and in the United Kingdom the UK GDPR, you may ask for a copy of your data, ask us to correct it, ask us to delete it, ask us to restrict what we do with it while a question about it is settled, object to processing based on legitimate interest, and complain to a supervisory authority.
In the EU, you can complain to the authority where you live or work, or to Spain's Agencia Española de Protección de Datos (AEPD, aepd.es), in the member state where our representative is. In the United Kingdom, complain to the Information Commissioner's Office (ICO, ico.org.uk). We would rather hear from you first, at support@borehole.dev.
Where we rely on your consent, which is a rating and its comment, you may withdraw it at any time: ask us to remove the rating, or delete the account. Withdrawing does not make what we did before unlawful.
Where we rely on your consent or on a contract with you, you may also take the data you gave us elsewhere. The export on your account page is that copy, in JSON, a machine-readable format.
Export and deletion are self-service, on your account page. The export is a list of queries over the tables that hold something about a person, and it finds rows by every address and login that deletion uses. A list like that goes stale the first time a table is added, so a test reads the database schema and fails the build when a table with an account or address column is neither exported nor excluded with a stated reason. Credentials are left out: session ids, share-link tokens, keys and token hashes. For anything these do not cover, write to support@borehole.dev.
When an account is deleted: the account record is anonymised, and its GitHub id and login are replaced by values that identify nobody; sessions are deleted, collector tokens are deleted, proofs of repository control are deleted, the GitHub App installation on your own GitHub account is deleted, keys are detached from the account, form submissions are removed, and a published rebuttal is anonymised rather than deleted — removing it would alter what a report said. Survey history is detached from the account: the surveys it started, the surveys run with its Report keys and the collector rulesets issued to it stay, with no link to the account. A survey paid with a Report key stays linked to that key's order, and a ruleset records the orders the account held or spent, so a copy found outside it can still be traced. Its free-survey counts are deleted. Its contact in Brevo, if it had one, is deleted; if Brevo cannot be reached, the address waits until it confirms. Orders are kept for 7 years as tax and accounting records. Every order's email address, and a given key's note, is removed 13 months after the order, whether or not the account is deleted. Private reports the account bought are deleted with it unless the person unticks that box, and each one's verification code then says it was deleted. Public reports are unaffected: they do not record a commit author's name or address. What analytics counted under the account's number is deleted from PostHog, events included. If PostHog cannot be reached at the time, the deletion is queued and retried until PostHog confirms it. Steps counted under the hash of your address and browser are joined to the account's number when you sign in from that browser, and are deleted with it. Those from a browser you never signed in from, and every page view, are linked to nothing, and PostHog deletes them after one year.
If you contributed to a repository we surveyed
A report on a public repository is built from its public commit history. We read who authored each commit, and which account committed it, in order to count authors and to measure how the work is spread among them. A report does not record commit authors' names or email addresses: it keeps counts and bands. On any project, a finding about the top contributor, such as "one contributor wrote nearly all of the commits", describes one person, and that person may be you. A quoted line, such as a TODO, can contain a name someone wrote in it; whoever controls the repository can remove quoted lines from its reports.
Findings about one contributor go out of date. 2 years after a public report was made, it no longer carries them, and the hashed authors in the facts kept with it are replaced, as after an objection.
The lawful basis is legitimate interest: a buyer or investor needs to know how much of a codebase rests on one person. You may object. Write to support@borehole.dev with the report's address. We will remove the findings about one person from every reading of that repository, including later ones, and say on the report that they were removed. We also replace the hashed authors and committers in the facts we keep for that repository with values made under a key nobody keeps, so no one, Borehole included, can test an address against them again.
A project's own files can name you: an AUTHORS file, a
copyright line, a CODEOWNERS entry. When a paid survey of a
public repository is reviewed, the review reads files like any others,
and each file it opens is sent to Anthropic as written, names
included, for that review only. The report still stores no name.
If a report is wrong, or you want it removed
A finding shown to be wrong is a fault in the check that made it. We correct the check and read the repository's newest reading again. The new reading of that commit replaces the old one on the report's page, and the earlier reading says that a newer one exists. A reading of an older commit is not read again. Whoever controls a repository can also answer a finding beside it, remove quoted lines from its reports, and delist its reports. A contributor can object, as the section above says. Takedown and delisting says what each of these does, and what stays.
Children
This is a tool for professionals. It is not directed at anyone under 16 and we do not knowingly collect their data.
Changes
A material change will appear here with a new version and date.
See also the Terms of Service, the data processing agreement and the sub-processors.