Terms of Service
Version 1.16 · 7 November 2026
1. Who you are contracting with
Borehole is operated by AELaboratories, a business registered in the United States. Postal address: 500 Westover Dr #34489, Sanford, NC 27330, United States. Contact: support@borehole.dev. In these terms, "we" and "us" mean AELaboratories, and "you" means the person or organisation using the service.
The service is for business and professional use. When you buy, you confirm at checkout that you are buying for your business or profession. That includes independent professionals, such as a freelance developer buying for their own work or for clients.
2. What the service is
Borehole surveys a git repository and reports what it found, with evidence. We read a public repository ourselves. A private repository is read by the Borehole collector on your own systems, which sends us facts about it and short excerpts where a check matched, never whole files (section 5). Every finding shows evidence you can check yourself: the commit, path and lines it rests on, or, for a finding that something is missing, what was looked for. Every check that ran and did not fire is published in the rejection log, with the numbers it observed.
A paid survey of a public repository is also reviewed by a language model, which reads the findings against the repository's code at the surveyed commit and withdraws a finding it judges the code contradicts. The review runs after a paid survey of a public repository, before the report is stored. It never runs on a private repository, a collected survey, a free reading or a re-read; a re-read keeps an earlier review's withdrawals only where the finding and its evidence are unchanged. If the review is switched off, fails or runs out of time, the report arrives as the checks wrote it. The review is a language model's reading of the findings against the code, and it can be wrong. It never adds a finding, never raises a band, and never removes a finding from a proven check or an advisory that affects the surveyed version. The report lists each withdrawal with the model's reason and evidence, so you can check it.
3. What the service is not
This matters more than anything else on this page, so it is stated plainly rather than buried.
- It is not advice. A report is a set of observations about a codebase. It is not legal, financial, investment or security advice, and nothing in it is a recommendation to buy, sell, invest in, acquire or decline anything.
- It is not a security audit. Some checks look at security-adjacent facts. A clean report is not a statement that a codebase is secure, and must not be presented as one.
- It is not a substitute for professional diligence. It is a tool that makes a human's diligence faster and better informed. The checks read six of seven dimensions, most only in part; a repository answers roughly three and a half in total. The report says which ones it could not answer and what a human would have to ask instead.
- It can be wrong. Every threshold is a judgement. Findings can be false positives, an absence of findings is not proof of absence, and the review of section 2 can withdraw a finding that was right. The evidence is published precisely so you can check rather than trust.
- A band is not a rating of the company. "Strong", "adequate" and "significant findings" are Borehole's reading of the repository against its own checks at one commit. They are not a rating of the company or its people, a certification or an endorsement.
You are responsible for any decision you make. If a decision matters, have a person who is accountable for it read the evidence.
Who may rely on a report.
- A paid reading may be relied on by its buyer, and only within these terms, including the limits in section 9. The buyer is the business or professional named on the order that paid for the reading, whether or not it holds an account, and whichever account ran the survey. A Report key we gave you (section 6) counts as bought here: you may rely on its readings as a buyer may.
- A report a target ran. Where a target ran the survey with a buyer's Report key, the buyer named on the order may rely on the report, and reading it through a share link does not change that. The target may read and share the report, and may not rely on it.
- A free reading is provided for information. Nobody may rely on it.
- Sharing does not extend reliance. A share link, a PDF, a badge or a copy lets someone read a report; it does not let anyone but its buyer rely on it.
- We owe no duty to the company whose repository is surveyed, or to anyone else who reads a report.
- Where a report says the code cannot settle a question, the report states nothing on that question.
- A human assessment is a separate contract, with its own scope, terms and reliance. A link to it from a report does not bring it into the report, and a person's view lives in that engagement's deliverable, not in the reading.
4. Repositories you may submit
You may submit a repository only if you have the right to do so — because it is public, because you own it, or because its owner has authorised you. You must not use the service to survey a repository you obtained without permission.
Public repositories are surveyed from publicly available data. If you control a repository and would rather its report were not listed, you can delist it yourself on /takedown when GitHub says you have admin or maintain permission on it, or write to takedown@borehole.dev and we delist it within 48 hours. We do not ask why.
To survey a public repository we clone it onto our infrastructure. The copy is deleted when the survey ends, including when it fails. When a paid survey of a public repository is reviewed (section 2), the findings and the parts of the repository the review reads are sent to our model provider, listed on /docs/subprocessors, for that review only.
5. Private repositories
We never clone or hold a private repository, and never receive a whole file of it. It is surveyed by the Borehole collector, which you run on your own systems:
- The collector reads the repository where it is and sends us a bundle of facts: commit metadata, file paths, where each detection pattern matched with up to 120 characters of the matched text, and counts. Excerpts are capped for each file and for each survey, as /docs/trust sets out; whole files are never sent. A credential-shaped match, in the files or anywhere in the history, is sent as its location and kind, and a fingerprint salted for that one survey, never its text.
- Author names and email addresses are hashed on your machine before the bundle is sent, under a key made for that one survey and never sent or kept (collector 0.7.12 and later). The hashes are pseudonyms: they let us count authors without receiving their names or addresses, and we cannot test a guessed address against them.
- You can read the entire bundle before anything is sent, by running
the collector with
--dry-run. - A collector token acts for your account within the scopes you tick when you make it: sending surveys from the collector, deleting your private reports, or surveying public repositories with your Report key. You answer for whoever holds it. Revoke a collector token you lose on your account page.
- We use the bundle to produce your report. We hold it only until it is scored, delete it as scoring begins, and delete one never scored after a day. What we keep is the report.
- No source content, and nothing from the bundle, is sent to any language model. The review of section 2 never runs on a private repository.
- A private report is not listed, does not generate a shareable card or badge, and is readable only by the account that ran the survey, by anybody GitHub says controls the repository when the survey came from a repository on GitHub, and by anyone holding a share link you chose to create. Borehole's administrators can also open it, to run the service and answer support. Nobody else can read it.
- So a buyer who sends its Report key to a target does not read the target's report by holding the Report key. The report belongs to the account that ran the survey, and the buyer reads it when that account sends a share link. Section 3 says who may rely on it. The repository's administrators on GitHub can read it too.
- A share link makes the report readable by anyone who has it, with no sign-in. You choose whether one exists and you can revoke it.
- For the personal data in a bundle and in a private report, we act on your instructions as your processor, under the data processing agreement (section 16).
Your code remains yours. What crosses is never whole files; facts and short excerpts of up to 120 characters where a check matched, and we claim no right to it beyond producing the report you asked for.
6. Payment
Prices are shown on the pricing page and are what you pay. Payment is taken through Stripe; we never see or store your card details. A purchase grants a Report key, which includes a one-page buyer's summary. For 30 days, counted from the first survey it runs, it allows:
- Public repositories: any number of surveys, by whoever holds the Report key.
- Private repositories, from two accounts at most: any number of surveys through the collector, by the account that signs in with the email address that bought the Report key, and by one account the Report key is added to. A Report key can be added to one account only. That account can be yours or a private target's, so one Report key covers one private target you do not control. Each further private target needs a Report key of its own.
We may also give you a Report key. A given key works as a bought one does, and carries no fee. We may ask to feature a report made with it as an example, and we do so only with your written permission. We may also ask for your feedback after the report; answering is optional.
Keys for products we no longer sell keep the terms they were bought on. A Raise-Ready key bought before 26 September 2026 works as a Report key. A pack, which we stopped selling on 25 September 2026, allows a counted number of surveys and does not expire.
A use is consumed only when a survey produces a report. If a survey fails and produces none, the use stays on your entitlement and you can run it again; a 30-day key whose first survey fails has not started its 30 days. If a repository's history is longer than a survey can read in full, the survey produces a report of the part it read: that report consumes the use and starts the 30 days, says at the top how much of the history it read, and carries everything a paid survey includes. If that depth is not enough for your purpose, section 7 applies.
The email containing your entitlement key is the only copy we send. If it does not arrive, write to billing@borehole.dev and we will re-send it.
7. Refunds
A survey that produces no report does not consume a use (section 6), so there is nothing to refund for it. We refund the order in full, on request to billing@borehole.dev within the 30 days of a Report key or 30 days of the purchase otherwise, when:
- a report you received contains no finding with evidence;
- a report read only part of the history (section 6), and that depth is not enough for your purpose; or
- a report you received is not what was described.
A refund ends the Report key. We would rather refund a disappointed buyer than argue with one.
The service is sold for business and professional use (section 1). If you bought as a consumer by mistake, tell us within 14 days and we refund the order in full.
8. Availability
The service is provided as it is. We do not promise it will be available without interruption. /status reports what is actually working at any moment, and it is designed to be able to say no.
9. Liability
To the extent the law allows, our total liability for any claim arising out of the service is limited to the amount you paid us for it in the twelve months before the claim. For a Report key we gave you, which carries no fee, the limit is the price of a Report key on the day we gave it. We are not liable for indirect or consequential loss, including lost profit or lost opportunity arising from a transaction you did or did not complete.
Nothing here limits liability for fraud, for gross negligence or wilful misconduct, for death or personal injury caused by negligence, or for anything else that cannot be limited by law.
10. Verification marks and badges
A report may carry a Borehole reading code. The code resolves to the report we actually issued, and it commits to the checks that ran at the time. It is not a certification, an endorsement or a rating, and it does not cover checks written after it was issued — the verification page says so when the two differ.
A badge shows a repository's band: Borehole's reading at one commit, as section 3 describes it. A badge is not a certification, an endorsement or a rating of the project or its people, and it does not let anyone rely on the report.
If you embed it: link it to the report, remove it if the report is delisted, and do not present it as a certification or an endorsement.
11. Acceptable use
Do not attempt to defeat quotas, probe for other people's private reports, or use the service to build a competing assessment product. Do not present a report as something it is not, including as a security certification or as our endorsement.
Do not use a report, or anything in it, to assess, discipline or dismiss an individual, or in any other decision about a person's work or employment. A report reads a repository. It is not a judgement about anyone who worked on it.
12. The detection ruleset
Where you run the Borehole collector on your own machine, it receives a detection ruleset for that run. The ruleset is unpublished proprietary work product, licensed to your account, provided in confidence, and not sold to you.
You may use it to survey repositories your account is entitled to survey. You may not copy it, publish it, disclose it to anyone else, or use it to build or improve a competing product. These restrictions survive the end of your account.
Every copy is individually marked. A ruleset found outside the account it was issued to can be traced back to that account. We say so here, and again in the ruleset itself, so that nobody can be surprised by it later.
13. Changes and termination
We may change these terms. A material change will be noted here with a new version and date, and we will not apply it retroactively to a purchase you have already made. You may stop using the service at any time. We may suspend access that is abusive or unlawful.
14. Governing law
These terms are governed by the law of the State of North Carolina, United States. If you are a business customer, the courts of Lee County, North Carolina, decide any dispute about them. Nothing in them takes away a protection the law of your own country gives you and does not allow a contract to remove. The data processing agreement names its own law (section 16).
15. Who owns a report, and your licence
We own each report: its wording, its structure and its selection of findings. You keep everything you owned before, including your code and the facts about it.
The buyer of a paid reading, and the account that ran a private survey, may use, copy and share that report for their own purposes, including with advisers, investors and the other side of a transaction. That licence does not expire and is not exclusive. It does not let you alter a report and present the result as ours, and sharing a report does not extend reliance on it (section 3).
Anyone may read, link to and quote a public report, with its address, on the same conditions.
16. The data processing agreement
When you send us a private survey, we process personal data in it on your behalf. The data processing agreement sets out how, and forms part of these terms. You accept it when you make a collector token, and the collector token records the version you accepted.
17. Sanctions
You confirm that you are not named on a United States, European Union or United Kingdom sanctions list, are not owned or controlled by anyone who is, and are not located in a country or region under comprehensive United States sanctions. You must not use the service for anyone who is. We may refuse or end the service where the law requires it.
18. General
- Transfer. You may not transfer your rights under these terms without our written agreement, except by giving a Report key to someone as section 6 describes. We may transfer them to whoever takes over the business, including a company formed to run it, and we will tell you.
- Severability. If a court finds part of these terms unenforceable, the rest still applies.
- Whole agreement. These terms, the data processing agreement where it applies, and your order are the whole agreement about the service. They replace anything said before. A human assessment has its own contract (section 3).
- Notices. We send notices to the email address on your order or your account. You send them to support@borehole.dev or to the postal address in section 1.
- Survival. Sections 3, 9, 12, 14 and 15 continue to apply after these terms or your account end.
19. Contact
General: support@borehole.dev
Billing: billing@borehole.dev
Takedown: takedown@borehole.dev
Security: security@borehole.dev
(how to report a vulnerability)
See also the Privacy Policy, the data processing agreement and the sub-processors.