Legal
Beta and Early Access
What is different during the beta, what it changes about your rights, and when it ends.
Last updated 28 July 2026
1. What the beta is
1.1 A small invited programme, paid at full price. The beta will be a limited period during which we sell reports to people we invite individually. We plan to invite no more than fifty. You pay the published price for your region, tax included: the number shown at checkout is the number charged, and nothing is added afterwards. The single case where the amount taken differs from the amount displayed is a buyer who enters a valid VAT number and is therefore treated as a business; the Payment Terms explain that treatment, and there is no other reason the two figures will ever part company. There will be no free reports, no beta discount and no test accounts, because a free report tests whether people like the output and a paid one tests whether they buy it.
1.2 It is an ordinary sale. You buy the same product on the same contract as any other buyer, under the Terms of Service, the Refund Policy and the Payment Terms. This notice adds to those documents and takes nothing away from them. Where the Terms of Service set the order in which our documents are read together, that order governs; this notice claims no precedence over any of them, and section 7 is a rule about what the word "beta" means rather than a rule about which document wins.
1.3 What it covers. Any order placed while the product page shows a beta label, up to and including the beta end date in clause 4.2. If you cannot tell whether your order was inside the beta, ask us and we will answer from the record in clause 4.7.
1.4 Which products, and who may buy them. Your invitation names them. Where a Founder X-Ray or an Executive Package is included:
(a) the report may be about you, or about a person who has confirmed to us by email that they agree to it, and about nobody else. Clause 3.2 below sets out how that works and what happens if the person does not reply;
(b) the conditions on who a report may be about in the Terms of Service and in the Acceptable Use Policy apply in full, including your warranty about the subject; and
(c) there is no territory we exclude. An invitation may go to a buyer anywhere, and checkout declines nothing on the ground of country.
``
1.5 What the beta is not. Not a free trial, not an early-access licence, not a research study you are enrolled in, not a subscription, and not a product sold "as is" – see clause 7.4. Nothing here enrols you in a recurring charge; we sell one-time purchases only.
1.6 Who you are buying from. LeMans Labs OÜ, a private limited company registered in the Republic of Estonia. Our registered name, commercial register code, registered address and the routes for notices are in section 1 of the Terms of Service and, for anything about personal data, in the Privacy Policy. We publish two mailboxes and no others: [email protected] for anything about your order, this notice or the beta, and [email protected] for anything about personal data, yours or anybody else's.
1.7 What exists today. The website. Checkout is not open, no order has been taken, and no report has ever been produced. Every part of this notice that describes something happening to your order is written in the future tense for that reason, and the beta cannot open until the things listed in clause 2.3 exist. Where you read "will", it has not happened yet.
2. What is not built yet
2.1 Why you are being told this. Our own release rules make a written disclosure of what is unfinished a condition of the beta starting at all. This section is that disclosure. You are paying full price for a product whose parts have never been used by a customer, and you should be able to read what those parts are first.
2.2 How it reaches you. Before you buy we will send you this list individually, in writing, dated on the day it is sent, and we will keep the record of what was sent and when. The list below is current at the effective date of this notice. The one you were sent is the one that describes your order.
2.3 Part one: what we will not open the beta without.
| What must be working | Why it is a condition |
|---|---|
| A checkout showing the total price for your region, tax included, before you are bound, and recording what you were shown | Terms of Service, ordering and price; Payment Terms |
| The express request to begin producing immediately, the separate acknowledgement that you lose the right to withdraw, both recorded in the wording displayed, and the confirmation that follows on a durable medium | Refund Policy, withdrawal. Without all of them your right to withdraw survives delivery, and we would rather build the controls than rely on that |
| The eligibility and consent gate: proof that the report is about you, or a consent request answered by the person it is about, with the order cancelled and refunded automatically if it is not answered | Clause 3.2 below; Terms of Service, who a report may be about |
| Your warranty about the subject, and the separate attestation about decisions a report will not be used for | Terms of Service, who a report may be about; Acceptable Use Policy |
| A record against your order of which version of each of our documents you were shown, this one included, and of the beta end date displayed to you | Clause 4.7 below; Terms of Service, changes |
| Somewhere to read your report, and the emails that carry it | You are buying a delivered document |
| An automatic refund when a report fails, and when a consent request is not confirmed | Refund Policy, failed reports; clause 3.2 below |
| A refund record that can name the ground a refund was actually made on, this promise included | A refund we cannot record correctly is a refund we cannot explain, to you or to anyone asking us why our refunds run at the rate they do |
| A way of telling one buyer from another that does not depend on an account: the payment method, the order email and the billing details, matched together | Clauses 4.3 and 4.10. The promise in section 4 is counted per buyer, and a count we cannot run is either a promise we cannot keep or a limit we cannot fairly apply |
| The route for a person a report names: the published notice, [email protected] answered, a register of what we did, and a list of people who have asked us not to produce a report about them | They are not our customers, and their rights do not wait for our roadmap |
| The consumer-reporting statement on every page of a file exported from a report, and both that statement and the automated-production disclosure on the report itself and on any shared view of it | AI Transparency notice; Terms of Service |
2.4 Part two: what will still be missing, and what it means for you.
| Still missing | What it means |
|---|---|
| No person will read a report before it reaches you | Not a gap we intend to close. The AI Transparency notice explains why; clause 3.4 below says what we will do instead |
| No measured figure for how long a report takes, how often production fails, or how often we refund | Every such figure we publish is a budget we set, not a measurement we took. See clause 3.3 |
| No measured figure for how often a consent request is confirmed, or how long a person takes to answer one | Your order may wait on somebody else, and we cannot yet tell you for how long. See clauses 3.2 and 3.3 |
| No certification, no independent security test, no third-party attestation | We hold none. The Security notice lists what is and is not in place |
| No published statistics on reports produced, corrections made or objections received | None exist. The AI Transparency notice says when the first will |
| No programmatic or bulk ordering | Not offered, not priced, not documented, and not available during the beta |
| Sharing is narrow by design | You can export a report as a file and give a link to one person you name. We send the link, and that person confirms the address with a code before their first view, so there is no anonymous link to forward. Revoking a link stops the next request; there is no equivalent for a file |
| No way to take back an exported file | Once you export it, we cannot recall it, delete it or expire it, and neither a refund nor the end of the ninety days reaches it. Clause 4.9 says what that leaves you obliged to do |
| No check that closes export and sharing where a company report turns out to be about one living person | A company can be one person – a sole trader, a one-person company, a named partnership. Our pipeline detects that and writes the report under stricter rules. It does not stop the file or the link, that check is deferred and not built, and for such a report the lawful basis rests on our own legitimate interest rather than on a contract with the person it is about |
| A minimal account area | You may reach your report from a link in an email rather than from a library |
| One shared support inbox, [email protected], answered by one person | We will publish a response target and answer to it. No telephone line, no out-of-hours cover |
| No insurance behind what we do | We hold none, and nothing in this notice or any other should be read as saying otherwise |
``
2.5 A gap does not lower what a report has to be. Where something in part two would otherwise mean a report falls short of our own product description, we will not rely on this list to excuse it. If we ever need you to accept a specific shortfall, we will name it and ask you to accept that shortfall separately and expressly before you pay, rather than publish a list and treat your purchase as agreement to all of it.
``
3. What we promise during the beta
3.1 Everything else still applies, unchanged. Every right, remedy and commitment in our other documents applies to a beta order. This section is in addition to them, and what a report is, in the Terms of Service and on the product page, is what you are entitled to receive.
3.2 Who a report may be about, and how that is checked. Where a report is about a person, we will produce it in two situations and no others. Either the report is about you, and we have satisfied ourselves of that by your control of the email address or of the profile the report is bound to. Or it is about somebody else, and we have emailed that person a request naming you and the organisation you gave, describing what the report is and what it reads, and they have confirmed to us that they agree. Production does not start until then. If they do not confirm within the window stated in If a Report Names You, your order is cancelled and refunded in full, automatically, without your having to ask, and we will not tell you whether they refused or simply did not reply, because that distinction is information about them. Your own warranty about the subject still stands, and you still answer for it; asking them is on top of your word rather than instead of it. No person at LeMans Labs decides any of this: the check, the request, the refusal and the refund are automated.
3.3 We make no commitment about how long it takes. Any turnaround figure you see is an estimate, and during the beta an untested one. An order that waits on the confirmation in clause 3.2 waits for as long as the person takes to answer, and that is outside our control and yours. Nothing here creates a delivery deadline. If we have not delivered within a reasonable time you may cancel and be refunded in full, and a report that fails will be refunded automatically.
3.4 No person will read your report before you do. That does not change for the beta. A person will read delivered beta reports afterwards as a quality check, and where we find something wrong in yours we will tell you rather than wait for you to find it. That later read is a person at LeMans Labs reading the whole of a report about a named individual, so it is something that happens to them as much as to you: it is done by someone under a duty of confidence, it is recorded, and it has to be disclosed in If a Report Names You before the first beta report is read rather than only here. If we ever introduce a read before delivery, the disclosure changes in the same release and we say so before you buy, never after.
``
3.5 We will not build a picture of anyone from your order. What we measure during the beta is how our system performs, not the people the reports are about. We will not link reports about the same person across orders to accumulate a view of them over time, and evidence for a report about a person will be collected fresh for that report rather than reused. Where a second report is ordered about the same person, the consent step in clause 3.2 runs again, so it is a second decision for them rather than a consequence of the first. A report is a point-in-time reading of the public professional record, and nothing in the beta makes it more than that.
``
3.6 If the person a report is about changes their mind. Consent given under clause 3.2 can be withdrawn, and a person a report names can object, at any time and without giving a reason. Where that happens we may withdraw a delivered report and cancel your licence, and you are refunded in full whether or not you read it. That is not a concession that the report was faulty, and it is not something the beta, this notice or your contract can be used to resist. What follows is in the Refund Policy and in If a Report Names You.
3.7 We will not make a public claim out of your order. No buyer count, no conversion figure, no testimonial and no quotation from you will appear anywhere unless you have given permission under clause 6.3.
4. The beta refund promise, and until when
4.1 The promise. For a report you order during the beta, if you ask for your money back you get it. No reason, no explanation, and no exception for a report you have opened and read in full. It is not counted once per account, because there is no account: it is available on each of the first three beta orders on which you ask for it, and after that on any beta order where you tell us what the report got wrong. An order you never ask about does not use it up. This is a promise we choose to make to an invited cohort while the product is untested. It is not the standing position on refunds after delivery, which is in the Refund Policy, and it ends when the beta ends.
``
4.2 How long it lasts. Until the later of (a) [Beta end date – set before the first invitation is sent. This notice must not be published with this bracket in place: clause 4.8 makes the end date the only way the promise can ever be narrowed] and (b) thirty days after the report became available to you. An order placed on the last day of the beta carries the full thirty days, so the promise never has to be taken back from anyone.
4.3 What "each buyer" means, and why it is not "each account". We count the three by buyer rather than by mailbox: a match on the payment method used, on the email address used for the order, or on the billing details given at checkout makes it the same buyer. We count it that way because an account here is an email address with a code sent to it, and a limit counted per mailbox would bind only the people who did not think to use a second one. We will tell you when you have reached the three, before you order rather than afterwards. Past the third, the promise still runs on the single condition in clause 4.1: tell us what was wrong.
4.4 The refunds that do not depend on this promise at all. You are refunded in full, automatically and without asking, where a report fails to be produced, where a consent request under clause 3.2 is not confirmed, where we refuse or cancel your order before delivery, and where we withdraw a report under clause 3.6. None of those is counted against clause 4.3, none of them ends when the beta ends, and none of them depends on this notice.
4.5 It sits on top of the law, and on top of the Refund Policy, never in place of either. This notice adds a promise and removes nothing. Anything the Refund Policy gives you, and anything the law gives you – your right to withdraw, your remedies if a report does not conform, the automatic refunds in clause 4.4 – you keep in full, whether or not this notice mentions it, and this promise is available on top. Where the same money would otherwise be returned twice, it is returned once.
4.6 The Executive Package. Where part of one is not produced, the partial refund in the Refund Policy will be made automatically; you do not have to ask. You may decline it and take back everything you paid instead, for as long as this promise runs. A partial refund already paid counts towards anything refunded to you later for the same order, so you have back the whole of what you paid and never more than it.
4.7 How it is proved rather than asserted. We will record against your order the version of this notice you were shown, a content hash of it, the end date it displayed at that moment, and the date you ordered. If we ever disagree about what you were promised, that record decides it and we will produce it on request. We will also record when a report was first opened. That record is never a condition of a refund under this notice; where a payment is disputed with your bank after a report was delivered and read, we may put it to your card issuer, and we say so here rather than only in a log you cannot see.
4.8 We can only withdraw this promise forwards. We may publish a new version of this notice with a different end date or a shorter window. It applies to orders placed after publication and never to yours. We will not reduce a promise already given, and we will not need to, because clause 4.2 puts an end date on it from the start.
4.9 What a refund does to your report. It ends your access and your licence. The report leaves your account and every link you issued stops working from the next request, because we serve those views ourselves. A file you exported stays where it is: we cannot reach it and we do not claim we can, so you must stop using it and delete it, along with anything you copied out by hand. A payment reversed by your bank or card issuer has the same effect as a refund, from the moment the reversal is final. The Refund Policy and the Terms of Service set out what that means, and the part we cannot see is why that obligation is on you.
4.10 The one limit, and how narrow it is. If we conclude that a buyer is ordering reports in order to reclaim the money, we may tell that buyer in writing that this promise does not apply to orders placed after that message, and we may decline to sell to them again. Every beta order placed before that message keeps the promise in full. We identify a buyer as in clause 4.3. This clause reaches nothing else in any of our documents, nothing in clause 4.4, and no right you have by law.
4.11 Asking us is faster than disputing it. If you are unhappy, tell us at [email protected]. The Refund Policy explains what a payment dispute does and why coming to us first is quicker for you.
5. How the beta ends
5.1 When. On the beta end date in clause 4.2, or earlier if we publish that we have ended it. The label and this notice are two halves of one thing: while the label is displayed, this notice applies.
5.2 It comes off everywhere at once. The label will be rendered from a single setting, so it cannot survive in one place after being removed in another, and the date it came off is recorded in clause 5.6.
5.3 What ending it does to an order already placed. Nothing. Your refund promise runs for the full period in clause 4.2 regardless, including the thirty days after your report became available, your documents stay pinned to the versions you were shown, and your report keeps the access period that applied to your order under the Data Retention notice, and its licence.
5.4 Ending early, and extending. We may end the beta early, and we will publish the date; clause 5.3 still applies to every order placed before it. We may extend it by publishing a new version of this notice with a later date, which is a new promise to later buyers and does not shorten yours.
5.5 What follows. When the beta ends we stop making the promise in section 4 to new buyers. The Refund Policy then applies on its own terms, unchanged, and the automatic refunds in clause 4.4 are unaffected by the beta ending.
5.6 Dates. Beta opened: [Date – set when the label goes live]. Beta closed: [Date – set when the label comes off]. This clause is completed rather than deleted, so a buyer can check afterwards what applied on the day they bought.
6. Feedback
6.1 What we ask for, and that it is voluntary. A written response within seven days of reading your report: what you expected, what surprised you, what you did with it, what was wrong, and whether you would buy another. Nothing you have bought depends on it. You can ignore every request and keep every right in this notice, the refund promise included, and clause 4.1 asks you for a reason only past your third refunded order.
6.2 What we do with it. We use it to fix and improve the product. You give us no rights in anything you send beyond that, we owe you nothing for it, and we promise no particular change. We will not tell you a change was made because of your feedback unless it was.
6.3 Quoting you. We will not publish your name, your company, your words, or the fact that you bought, unless we ask first and you agree in writing. Permission is asked for each use and never assumed from your having given feedback. You may withdraw it at any time and we will stop using the quotation, though we cannot recall something already printed elsewhere.
6.4 Please do not send us more about the subject. Where a report names a person, that person agreed to the report being produced and to nothing else: not to this notice, not to the beta, and not to receiving anything further about themselves from you through us. Tell us what our report got wrong; do not send us further information about them. Anything you do send is handled under the Privacy Policy, and their rights apply to it in full.
6.5 Telling us a finding is wrong is not feedback. It is a correction, with its own route, record and answer: the Terms of Service and the Report Accuracy and Public Data notice. Marking a finding wrong inside a report goes into the same register, which records what we did about it.
7. What the beta label does not do
7.1 It does not reduce a statutory right. Not one, not by a day, not to any degree. A label on a page cannot do that, and it is not meant to.
7.2 It does not lower the standard the product must meet. A beta report must be what we describe a report to be. Where it is not, your remedies are those in the accuracy and remedies section of the Terms of Service and in the non-conformity section of the Refund Policy, in full.
7.3 It is not a limitation of liability, and we do not use it as one. We do not write the word "beta" into a warranty, a disclaimer, an exclusion or a liability clause, deliberately, so that nobody can later argue it was meant as one. If it ever appears in such a clause it carries no limiting effect, and we will not argue that it does. Our liability is limited by the limitation of liability section of the Terms of Service, in the same way for a beta buyer as for anyone else, and by nothing in this notice.
7.4 It does not mean "as is". You pay the full price for a finished report and you are entitled to a finished report.
7.5 It does not relax who a report may be about, or what it may be used for. The Terms of Service and the Acceptable Use Policy apply in full, and the gate in clause 3.2 runs on every beta order exactly as it runs on any other. Being invited does not put you inside it.
7.6 It does nothing at all to the person a report is about. They agreed to the report being produced, under clause 3.2, and to nothing else. They are not in the beta, and their rights against us are not reduced, delayed or made provisional by this notice or by anything you and we agree. They can withdraw that agreement at any time. Those rights are in If a Report Names You, and no limitation of liability in any of our documents reaches them, because they are not a party to your contract.
7.7 It does not make the price provisional. We are not entitled to charge you more later because the beta ended, and we owe you nothing back merely because it did.
7.8 If any of our wording ever reads otherwise. Where a clause anywhere in our documents appears to give the beta label a limiting effect, it does not have one. That is a rule about the meaning of one word and it decides nothing else: which of our documents governs which subject is settled by the Terms of Service.
Read this with: the Terms of Service, the contract your beta order sits inside and the document that identifies who you are contracting with; the Refund Policy, which owns the refund position section 4 adds to; the Payment Terms, for price, tax and how the charge appears; the AI Transparency and Limitations notice, for how a report is produced and why no person reads it before you do; the Report Accuracy and Public Data notice, for what happens when a finding is wrong; the Acceptable Use Policy, for who a report may be about; and If a Report Names You, written for the person a report is about rather than for you.