Skip to content

Legal

Acceptable Use Policy

What you may not ask us to report on, and what happens if you do.

Last updated 28 July 2026

1. What this policy covers, and who it binds

1.1 This policy forms part of the Terms of Service. It applies when you order a report, when you hold one, and when you read one through a link we issued. Clause 2.6 of the Terms of Service governs any conflict between the two: the Terms of Service govern the contract, and this policy governs its own subject matter, which is who a report may be about, what a report may not be used for, and what we do about a breach. Where a conflict cannot be resolved that way, the reading more favourable to you governs your order, and we correct the difference rather than argue about it.

1.2 It binds you, anyone ordering through your account, and anyone acting for you. Where you give a report to someone else on terms the licence allows, you remain responsible for what they do with it.

1.3 This policy is between you and us. It does not limit the rights of a person a report is about, who is not a party to it. Where that person has agreed to a report being produced under 2.2, they have agreed to that and to nothing else in this document: agreeing to a report is not agreeing to our terms, and it gives up no right they hold. Their rights are in If a Report Names You.

1.4 Where a term of this policy would be unfair to you as a consumer, that term does not bind you. We do not ask anyone to read a term down to whatever the law happens to permit, because clause 11.3 of the Terms of Service says we do not rely on that device and a term that is unfair is not made fair by a sentence saying so. The terms below are written to be fair as drafted. If one of them is not, it falls and the rest of this policy stands.

1.5 What is running, and what is not. This policy is published while the service is still being built, and this clause is the difference between the document and the product. Reports are bought, produced and read in an account for ninety days, and since this version a buyer can also export a report as a file and give a person they name a link to read it. What that costs and what it cannot undo is 5.4 and 10.1.

None of the following exists yet: the consent request in 2.2 and the automatic cancellation and refund in 2.3; the record of the warranty in 2.6; the subject-eligibility check in 2.7; refusal on possible minority in 4.1; the do-not-report list in 4.4 and 10.7; the fence around the context field in 6.2; the point-of-retrieval control in 6.6; the volume and pattern review in 7.3, including the part of it that looks across accounts; the territory block in 8.4; and the register in 10.8. That list is the whole of it, it is reviewed at every release of this policy, and it is shortened only by putting a control into service or by the requirement behind it being withdrawn, never by deleting a line from it.

Six items have left it that way rather than by anybody deleting a line: checkout and payment, accounts and sign-in, report production and delivery, outbound email, and, in this release, the export and the link.

What came with the export and the link, so this clause can be checked rather than trusted. You name the recipient and give us their address, we send them the link, and before their first view they confirm that address with a code – the same mechanism you sign in with. Every view is served by us and recorded, a link never outlives the ninety-day window, and revoking one stops the next request; there is no anonymous link to forward. Permission to create a link is asked for at the moment you create one, on its own, and can be withdrawn. Every export of a file is recorded as an event of its own. What none of that reaches is a file once it has left us, and 10.1 says so in its own words rather than in softer ones.

We will not sell a report about a natural person until every control in that list that protects that person is running.

Two things are outside that list and are not qualified by it. The prohibitions in this policy bind you from the moment there is a contract between us, whether or not the control that would detect a breach exists yet. And the commitments we make about our own conduct – what we refuse, what we delete, what we record, and how quickly we answer – bind us from the effective date. Where we cannot honour one, we change the sentence rather than leave it standing.

1.6 Which version applies. The version of this policy in force when you order governs that order and the report it produces, for the whole life of that report and after your 90 days end. We may change this policy for orders placed after the change. We will not apply a new prohibition, a new warranty or a new remedy to a report you have already bought. This is clause 17 of the Terms of Service applied to this document, and it is stated here as well because this is where the conduct rules and the consequences of breaking them are written.

2. Who a report may be about, and how that is established

2.1 A report may be about:

(a) a company or other organisation; or
(b) a natural person acting in a professional or commercial capacity in the matters analysed, whose professional role is on the public record, and only where 2.2 is satisfied.

2.2 A report about a person needs that person's agreement, given to us. Where the subject is a natural person, we will produce a report only where one of the following is true:

(a) the subject is you, and you have shown control of the email address or of the profile address the report is bound to; or
(b) the subject is somebody else, and that person has confirmed to us, by email, that they agree to the report being produced. We will write to them with a plain description of what the report is, who asked for it, what it will and will not contain, and how to refuse. Production will start only after they confirm.

Your own statement that you have the subject's permission is not a substitute for (b). We take that statement as well, and 2.4(g) says what it carries, but permission has to be given to us and we have to be able to show that it was.

2.3 If the person does not confirm. Where there is no confirmation within the window shown to you at checkout, the order is cancelled and refunded in full, automatically, without you having to ask. We will not tell you whether the request was read, declined or ignored, and a cancellation is not a finding about anyone. Sending the request is not a step you can skip, waive or pay to remove.

2.4 Each time you order a report about a natural person you warrant, and we rely on it, that:

(a) the subject is aged 18 or over;
(b) your interest is professional – investment, corporate development, partnership, commercial or competitive diligence, or an equivalent business purpose;
(c) there is no personal, family, domestic, romantic or former-romantic relationship between you and the subject;
(d) there is no personal dispute, harassment complaint, investigation or litigation between you and the subject, and no protective, restraining or non-molestation order made against you protects the subject;
(e) you have no reason to believe the subject has asked not to be researched;
(f) you are not buying the report to make or inform a decision about employment, credit, insurance or housing; and
(g) where the subject is not you, you have that person's permission to ask for a report about them.

2.5 One warranty, one source. This is the same warranty as clause 4.3 of the Terms of Service, and both are rendered from a single source so that they cannot drift apart. What binds you is the wording displayed to you at checkout and stored against your order. If any published copy of this warranty differs from that stored wording, the stored wording governs, the difference is a defect in our documents rather than a term of your contract, and we correct it.

2.6 How it is taken, and how it is recorded. The warranty will be presented at checkout as its own control, above the pay control, never pre-ticked, and never bundled with acceptance of the Terms of Service, with the Privacy Policy, or with any other confirmation. We will record against your order the exact wording shown to you as it was rendered, a version identifier for it, and the time you actioned it, and we will produce that record to you on request. Checkout will not open until that record can be written: a warranty we cannot produce afterwards is not a warranty.

2.7 What the warranty carries, and what we check. The warranty is given afresh on every order and is a condition of it. A false statement under 2.4(g) is a material breach: it ends the licence granted by clause 8 of the Terms of Service, it engages section 10 of this policy in full, 10.6 says what happens to the price, and if you are a business buyer it engages the indemnity in clause 13 of the Terms of Service. Nothing in 2.4 makes you liable to us for a fact about the subject that you could not reasonably have known, other than the fact of your own permission under 2.4(g), which is yours to know.

The check that matters is the confirmation in 2.2, and it is a real one: no report about another person is produced without it. Beyond that we do not verify most of 2.4, and we would rather say so than imply a check we do not run. A subject-eligibility check will run when you submit a brief, before we spend anything and before you are asked to pay. It will refuse a subject it cannot place on the public professional record, and it will not catch everything. Passing it is not a finding that your order was permitted, and it waives nothing.

``

3. Decisions a report must not be used for

3.1 The following applies to every report and is the most important line in this policy:

This report is not a consumer report. It must not be used to make decisions about employment, credit, insurance or housing. It is not produced to the accuracy standards those decisions require.

3.2 Those four categories cover, without limiting them: hiring, engagement, promotion, discipline or dismissal; credit, lending, guarantees, debt or collections; insurance underwriting, pricing or claims; and housing, tenancy or tenant screening. This clause expands the four categories named in 3.1. It does not state a different set from clause 9.2 of the Terms of Service, and neither document narrows the other.

3.3 A report must never be the sole or determining input into any decision about a person. Separately, and whether it is one input or the only one, a report must not be used in a decision that produces a legal effect for the person it is about or that similarly significantly affects them. That includes every decision within 3.2, and it includes decisions about benefits, professional licensing, education admission, immigration status, and whether to grant or withdraw access to a service. If you are unsure whether a decision is caught, treat it as caught.

3.4 Why these are bars rather than guidance. A report about a person is produced by an automated system from the public record, and no person reads it before it is delivered. If you take a decision with a report in front of you, the decision is yours alone, you are the decision-maker, and you may carry obligations under data protection law or other law that we do not carry for you.

3.5 Do not present a report as a background check, a screening report, a credit reference, or verification of anyone's identity, qualifications or history. It is none of those.

3.6 A report is not professional advice. What a report is, and is not, is in Report Accuracy and Public Data and AI Transparency and Limitations.

3.7 Where an order, the brief, the way you describe it or anything else known to us indicates a purpose caught by this section, we will refuse it, and where we learn of such a purpose after payment we will cancel the order and refund you in full. The confirmation in 2.4(f) is taken at checkout as its own unticked control and is a condition of every order. This is not a discretion we reserve; it is a refusal we owe.

``

4. Subjects we refuse

4.1 Minors. We will not knowingly produce a report about a person under 18, at any price, for any buyer, for any reason. If you have reason to think a subject may be under 18, do not order. Where the public professional record does not place a subject in adulthood, we will refuse rather than resolve the doubt in our own favour, and that refusal will run before payment is taken.

If a parent, a guardian, or the young person themselves tells us we have produced one, we act the same day. We will not ask them to prove the relationship, we will not ask for identity documents, and we will not argue about it. What we do, precisely:

(a) we end access to the report and disable every share link to it at once;
(b) we delete the report, the evidence behind it, the brief and the generated files from our live systems the same day;
(c) we delete the internal records of the automated calls made while that report was produced, rather than letting them run to their normal expiry;
(d) we remove the subject's name from the copy of the brief held with the accounting record, and hold that record without it from then on;
(e) we require the buyer to stop using the report, to delete every copy they hold, and to retrieve or destroy copies they supplied to anyone else. In this case alone the step in 10.3(e) is taken every time, is not discretionary, and applies whether or not the buyer was at fault;
(f) we add the subject to the list in 4.4 so that no further report about them can be produced; and
(g) we refund the buyer in full.

Two things we cannot reach, and we would rather say so than be found out. Ending access under (a) reaches every link, because we serve each view of a shared report ourselves and simply stop: from the next request the link is dead wherever the address has travelled. It does not reach a file the buyer exported before we acted, or what they wrote down or screenshotted while reading. A file that has left us is beyond deletion, beyond revocation and beyond expiry, (e) is the only lever there is on it, and we will not tell a parent, a guardian or the young person that copies have been destroyed when we cannot see that they have. Material deleted from live systems persists in backups until those backups expire on the schedule in the Data Retention notice; it is not restored to live systems in the meantime.

4.2 A person in a personal, family, domestic or intimate relationship with you, current or former. A confirmation under 2.2 does not make such an order permitted, because a confirmation given inside a relationship of that kind is not the protection this rule exists to give.

4.3 A person on the other side of litigation, a dispute, a complaint or an investigation involving you, and any person protected by an order made against you. A confirmation under 2.2 does not make such an order permitted either, for the same reason.

4.4 A person who has asked us not to produce reports about them. That route is in If a Report Names You.

We will not tell you, any other buyer, or anyone enquiring about somebody else, whether a particular person has used that route, and we will neither confirm nor deny it however the question is put, including where the question looks harmless. That refusal protects the person asked about, so it does not run against them: where a person asks about their own entry and we are satisfied that it is them, we tell them, as If a Report Names You sets out. Nothing in this policy limits any right a person has to be told what we hold about them.

4.5 A private individual with no professional public record. A thin record is not a coverage problem we solve by saying the record is thin. It is a subject we decline.

4.6 A person or entity designated under sanctions. See section 8.

4.7 We may refuse any subject. A refusal before delivery costs you nothing: see 10.6 and the Refund Policy. A refusal is never a way of keeping the price.

5. Purposes and conduct we prohibit

5.1 Do not use a report, any part of one, or the service, to:

(a) stalk, monitor, surveil or track a person, including a current or former partner, a family member or a colleague;
(b) harass, intimidate, threaten or humiliate a person, or join others doing so;
(c) dox a person: to compile, publish or pass on their home address, personal contact details, movements or family members;
(d) defame the subject, to state as a fact anything drawn from a report that you know or ought reasonably to know is untrue, or to repeat a finding after we have told you it has been suppressed, corrected or withdrawn;
(e) discriminate against a person on any protected characteristic;
(f) solicit the subject's customers, or use a report or any finding or score from it in advertising or comparative advertising. Who you may show a report to is governed by clause 8 of the Terms of Service and by nothing in this policy: this paragraph names no permitted recipient and widens clause 8 in no respect;
(g) assemble a profile of a person for any purpose in section 3;
(h) supply a report, or a finding or score from it, to any person outside the circle clause 8 of the Terms of Service permits, whether or not you tell them what it is and whether or not you accept responsibility for it yourself. If you want a third party to rely on an analysis of this subject, they need their own report;
(i) publish a report or any part of it, or put it where an audience wider than the licence permits can reach it; or
(j) attempt to change what a report says about anyone, including yourself, by publishing or supplying material written to be read by our system.

5.2 What this section never prevents. Nothing in 5.1, and nothing in clause 8 of the Terms of Service, prevents you from:

(a) making a disclosure that a law, a court, a tribunal, a regulator or a supervisory authority requires of you;
(b) reporting a suspected criminal offence or a suspected breach of law to a competent authority, or making a protected disclosure under whistleblowing law that applies to you;
(c) taking legal, accounting or insurance advice on a report, from advisers bound by their own duties of confidence; or
(d) showing a report to the person it is about.

Where you disclose under (a) or (b), disclose no more than is required of you, tell the recipient what a report is and what it is not, and give them the statement in 3.1. None of the above is a breach of this policy and none of it is a ground for anything in section 10.

5.3 What we do about 5.1(j) ourselves. That prohibition binds our customers. It does not reach a person who is not our customer, and material planted by such a person can reach a report. We do not treat a contract term as a control for that. Where a person a report names tells us that a statement about them rests on material planted or manipulated to be read by an automated system, we suppress that statement while we examine it, we examine where the evidence came from and not only what it says, and we tell the buyer that a statement has been suppressed pending review. That route is in If a Report Names You, it is open to anyone, and it needs no account, no fee and no particular form of words.

5.4 Who you may show a report to, the link, and the file. A report about you is yours: you bought it, it is your own record, and you may show it to anyone you judge fit, investors and a board included. A report about a company is not. It goes to your own people who need it for the decision it was bought for, and to your own professional advisers under a duty of confidence, and no further. Clause 8.3 of the Terms of Service states the rule in full and governs. This is a summary of it: 8.3 carries one further limb, for a buyer that is an investment firm, and where the two differ 8.3 is the answer.

A link is not a password. You name the recipient and give us their address, we send them the link, and before their first view they confirm that address with a code – the same mechanism you sign in with. Every view is served and checked by us and recorded against that link, it never outlives the ninety-day window, and revoking it stops the next request. There is no anonymous link, so passing the address on does not pass access on. Revoke one when the conversation it was made for is over.

The file is the opposite, and it is the sentence in this policy to read twice. Once you have exported it, we cannot recall it, revoke it, delete it or expire it. Send it to the people you meant to send it to, and treat every copy after that as one you answer for under 5.1(h) and clause 8 of the Terms of Service.

One case deserves naming because nothing in the product stops you. A company report can turn out to be about one living person – a sole trader, a one-person company, a named partnership – and that person is not our customer and agreed to nothing. Exporting or sharing such a report is permitted and it is entirely your decision; the paragraph above about a report about a company is what binds you, and it binds you at its narrowest there.

5.5 Access. Sign-in codes and sessions are personal. Do not share, sell or publish a sign-in code, and use one account. Signing in will be by a single-use code sent to the email address you used to order, so anyone who controls that mailbox will be able to reach your reports; keeping it secure is something we ask of you and cannot do for you. You are responsible for use of your account by a person you gave access to, and for use you could have prevented by taking reasonable care. You are not responsible for use by someone who obtained access without your knowledge and otherwise than through a failure to take reasonable care, and you are not responsible for anything done through your account after you have told us at [email protected] that you think someone else has access. Do not open a second account after we have refused an order, blocked a purchase or closed an account.

5.6 Do not misrepresent who you are, and do not order for a person whose identity you conceal from us.

6. What you submit to us

6.1 A brief will be short: the subject's name, a link identifying them or their organisation, and an optional free-text field of up to 600 characters headed "Anything else worth knowing".

6.2 That field will steer what we look for and which sections we go deeper on. It will never be treated as evidence, never quoted as a finding, never cited, never rendered on a shared view of a report, never printed in a file exported from one, and never served in the machine-readable copy of a report given to a recipient. The rule is upstream of all of those: what you write there never becomes a sentence in the document, so no surface that renders the document can carry it. If you tell us about an unannounced product or a funding position, that is an instruction about where to look. It does not become a sentence in the document.

6.3 One limit on that, and it is not ours to remove. Where the subject is a natural person, what you write in that field is information about them. If they ask us what we hold about them, we have to give them the text you wrote, because the right that entitles them to it is not something your contract with us can switch off. We will not tell them who you are. Write the field on that basis: if you would not want the subject to read it in your own words, put it another way or leave it out.

6.4 You warrant that you are entitled to give us everything you give us, and that doing so breaches nobody's rights and no duty you owe.

6.5 Do not put into a brief: information about a person's health, sex life, sexual orientation, racial or ethnic origin, religious or political beliefs, or trade union membership; biometric or genetic data; allegations, proceedings or records concerning criminal offences; anything held under a duty of confidence you are not free to waive; anyone's card details, password or government identifier; or material that is unlawful or infringes a third party's rights.

6.6 We do not want that material, and we would rather describe what will happen to it than assert that it cannot reach us. A brief containing it may be refused, the material may be removed, or the order may be cancelled and refunded in full. The control that keeps material of that kind out of what we store, rather than only out of what we publish, is applied at the point of retrieval and before anything is written to evidence storage. Clause 4.6 of If a Report Names You describes it from the subject's side, and it is in the list in 1.5 because it is not running yet.

6.7 6.5 is a restriction on you, not a permission for us. A report about a person is bound to the public professional record. The prohibition in 6.5 limits what you may send us; we do not rely on it as a basis for handling special categories of personal data or information about criminal offences, because no such basis would be open to a product like ours. What a report may contain about a named individual is in clause 3.3 of Report Accuracy and Public Data and clause 4.6 of If a Report Names You, and those limits bind the analysis whether the material came from you or from the open web.

7. Volume, automation and bulk ordering

7.1 We sell reports one at a time. There is no batch price, no volume tier, no bulk ordering route and no reseller programme, and we do not quote or negotiate one. An enquiry about volume, portfolio or batch ordering is refused, and the refusal is recorded with its date, because a recorded refusal is what shows we did not solicit the pattern this section exists to prevent. If a volume arrangement is ever offered it will be a separate written agreement carrying every restriction in this policy, including section 2, and none is in place.

7.2 Do not:

(a) order by automated means, or through any interface other than the one we publish;
(b) order at volume to assemble a dataset, a list, a directory or a competing product;
(c) order reports about the same person through more than one account;
(d) coordinate with others to order reports about the same person; or
(e) order a report about a person for someone whose identity you keep from us.

7.3 Volume, pattern and review. Orders naming natural persons are reviewed for pattern: how many distinct people one account orders about over a rolling period, how often the same person is named over a short period whoever placed the orders, and whether one buyer appears to be ordering through more than one account. Reaching a threshold is not by itself a breach and does not by itself stop an order: it means a person looks at the pattern, at the pattern rather than at the content of any report, and a review can lead to any step in 10.3, including refusal and a refund in full.

We do not publish the thresholds. A published number is an instruction on how to stay under it, and the people it would help most are the people this section exists to stop. The part of this review that looks across different accounts naming the same person is not running yet, and 1.5 lists it: until it runs, the route by which a pattern of orders about one person reaches us is section 11, and we would rather say so than let a figure imply a control we do not have.

7.4 There is no public interface for ordering programmatically, and we publish no terms for one. If one is built it will carry its own terms, the same rules about who a report may be about, and its own limits, and it will not open before the controls in this policy are enforced in code.

7.5 We may throttle, rate-limit or block automated access at any time and without notice.

7.6 The rules for automated access to this website and to the sample reports, including crawling, indexing, ingestion and bulk copying, are in the Intellectual Property notice, and nowhere else.

``

8. Sanctions, restricted parties and territories

8.1 Do not use the service, or anything we produce, to breach or to help anyone breach sanctions, export controls or trade restrictions.

8.2 Do not order if you, or a person you act for, is designated on a sanctions or restricted-party list that applies to us, or is owned or controlled by such a person, or if you are located in a territory subject to comprehensive sanctions. Clause 14 of the Terms of Service is where you give that representation and is the only place the applicable lists are identified. This policy states no list of its own and neither widens nor narrows that clause.

8.3 We may refuse or cancel an order where the subject of the report is a designated person or entity, and we refund in full. That is a fact about the subject, not an accusation against you. We do not query sanctions or watch lists as part of producing a report – Report Accuracy and Public Data says so – so this is a refusal we make when the position is known to us, not the output of a screen we run over every subject.

8.4 What we do, rather than what we ask you to promise. Checkout will not open until a block on billing addresses and card-issuing countries is configured for the territories we do not sell into, and until refusal or cancellation with a refund in full is recorded under 10.8 where that block is triggered. Our payment provider runs its own screening for its own purposes. That screening is theirs, it does not run on the subject of a report, and neither we nor you may treat it as discharging anything in this section.

8.5 Where the founder report is sold. Everywhere. No territory is excluded, and no product is available in fewer places than the others. Clause 2 is why that costs nothing: a report about a person is sold to that person and to nobody else, so we never supply one person's information to another. Nothing in this clause is a statement about any buyer or any subject.

``

9. Security research

9.1 Do not test, scan, probe or attack this service. In particular, do not attempt to reach another person's brief, order or report; do not attempt to defeat a share link, an expiry, an access control or a rate limit; do not attempt to extract our prompts or scoring internals; and do not degrade the service for anyone else.

9.2 Section 12 of the Security notice is our vulnerability disclosure policy. It states the scope, the conditions and the safe harbour, and it prevails over 9.1 for research that stays inside its conditions throughout. Nothing in this policy narrows it. Outside it, no permission to test anything is given by this document or by any other.

9.3 If you come across a vulnerability without looking for one, write to [email protected] with "security" in the subject line, stop there, and do not access, change, download or keep any data you were able to reach. We will not treat a report made in good faith on those terms as a breach of this policy.

9.4 We pay no bounty, and no permission we could give would extend to the providers we build on. Do not test them.

``

10. How we enforce this, and what happens

10.1 What we do not do. We do not read your report after it is delivered and we do not analyse what you do with it. Who you show it to we know in one respect only: you name the recipient of a link, we send it to them, and we record each view of it, because 10.2(b) says we do. Where a file goes after you export it we do not know and cannot find out.

A link we can end, because we serve every view of it ourselves. A file we cannot recall: it is on your machine and not on ours, and no clause of ours changes that. No person reads a report before it is delivered. Do not read this policy as an assurance that somebody is checking how a report is used: a seller who claims to police use and does not is worse placed than one who never claimed it.

10.2 What we look at, and what is recorded. Three different things, and we separate them because they are often confused.

(a) Before a report is produced, automatically. The consent step in 2.2, the eligibility check in 2.7, the do-not-report list in 4.4, and the volume and pattern thresholds in 7.3. No person is in that path.

(b) Recorded about your own account, including after delivery. That a sign-in code was issued and used, that a report was opened, that a file was exported from it, and that a link was created for a person you named, confirmed by them, viewed by them, or revoked, each with a time. These are records of access to your own account. They carry nothing about the content of a report and they are not observations of what you do with one. We keep them to secure your account, to answer your support questions, and to answer a payment dispute raised against a charge you made. The basis and the periods are in the Privacy Policy and the Data Retention notice, and the dispute use is governed by the Refund Policy. We say so here because logging what somebody reads without telling them would be worse than the logging.

(c) Looked at by a person. A pattern flagged under 7.3, anything raised with us under section 11, and anything raised by a person a report names.

None of that is monitoring of the content of a report or of what you do with one once you hold it.

10.3 What we may do. Depending on what has happened, we may:

(a) refuse a brief before you pay;
(b) cancel a paid order before delivery and refund in full;
(c) stop a report in production and refund in full;
(d) end online access to a delivered report, disable every share link to it, and delete it;
(e) require you to stop using a report, to delete every copy you hold, and to take reasonable steps to retrieve or destroy copies you supplied to anyone else;
(f) withdraw the licence granted by clause 8 of the Terms of Service;
(g) suspend or close your account and block future purchases;
(h) end the licence to a report whose payment has been reversed or reclaimed and not settled, under 10.9; or
(i) report the matter to an authority where we are required to.

10.4 Paragraph (d) and paragraph (e) do different work, and running them together is how a seller ends up promising what it cannot do. Under (d) we stop serving the report and every link to it, and that works: each view of a shared report is served by us, so from the next request the link is dead. Paragraph (e) exists for what (d) cannot reach – a file exported before we acted, and anything transcribed or screenshotted. It obliges you to stop using the report, to delete the file, and to take reasonable steps to retrieve or destroy copies you supplied to anyone else. It does not give us the ability to retrieve anything ourselves, and 10.1 says what we cannot do. Where a person a report names asks us what we have done, we will tell them that the links are dead, who each was issued to and when each was last viewed, that we have required you to stop using and delete the file, and whether you have told us that you did. We will not tell them the copies have been destroyed, because we cannot know it.

10.5 Proportion and notice. We use the least drastic remedy that answers the problem. Where a breach is a first one, can be put right, and does not look deliberate, we will tell you and give you the chance to put it right. We will act at once and without notice where a person may be at risk of harm, where the law requires it, or where the subject has objected.

10.6 Money. Before delivery you are refunded in full, always, and automatically: where we refuse a brief, where we cancel an order, where production fails, and where a consent request under 2.2 is not confirmed. You do not have to ask for any of those.

After delivery there is no refund as of right. The Refund Policy is the only place our refund position is stated, including the discretionary refunds we give, and if this clause and that policy ever differ, that policy governs. Two things belong here rather than there, because they are consequences of breach rather than of money:

(a) where we end your access to a delivered report because you gave a false warranty under 2.4(g) – you told us you had a person's permission and you did not – the licence ends and the price is not returned. That is the consequence we attach to that statement, it is the reason the statement is taken separately at checkout, and it is stated there in the same words; and
(b) where we act after delivery for any other reason, what happens to the price is decided under the Refund Policy and not under this clause.

We do not treat a refund decision as a general sanction for breaking this policy. Where a breach causes us loss we pursue that loss on its own evidence under clauses 12 and 13 of the Terms of Service rather than by keeping money you have paid. Your statutory rights, including any remedy where a report does not conform to what we described, are unaffected and are not what this clause is about.

``

10.7 What we will and will not tell you. We will always tell you that an order was cancelled and refunded. We may not be able to tell you why, where the reason would disclose information about another person. We will never confirm to you that a particular person asked us not to report on them, and 4.4 says what happens when that person asks us themselves.

10.8 We will keep a record of every brief refused, every order cancelled for cause, every report deleted for cause and every account closed, with the reason and the date. That record is kept for the period stated for it in the Data Retention notice and no longer, and that notice is the only place its period appears. It does not carry the name of a report subject: a refusal is recorded against the order and the reason, and where the reason concerns a person, against the identifier already held for that person and destroyed when that identifier is. Nothing kept under this clause outlives the record it relates to, and nothing kept under it is used to answer a question about a report or a person whose record has been deleted.

10.9 Non-payment. Your licence to a report is granted in consideration of payment for it. If that payment is reversed, withheld or reclaimed and the position is not settled, the licence to that report ends, whether or not the report is still in your account and however much of it you read. That is not a penalty and it is not a finding that you did anything wrong. Where you were entitled to your money back, the licence ends because the sale has been unwound. Nothing in this clause affects a statutory right, a refund you are owed, or your right to dispute a charge with your bank, and while a dispute is open we suspend access rather than delete anything, because a dispute may be resolved either way.

10.10 Liability and indemnity are in clauses 12 and 13 of the Terms of Service. Nothing here adds to either, and no limit in either reaches a person a report is about.

11. Reporting misuse

11.1 Anyone can tell us about a misuse of a report or of this service. No account, no fee, and no particular form of words: [email protected].

11.2 What helps: the report or the order it came from, the link if there is one, what happened, and a way to reach you. Tell us if you believe someone is at risk of harm and we will take that first.

11.3 We will acknowledge within two business days, and tell you the outcome where we can do so without disclosing information about another person. Where you tell us a person may be at risk of harm we treat the message as urgent: we act on it before we acknowledge it and we do not wait for the acknowledgement period to run. A business day is a day other than a Saturday, a Sunday or a public holiday in Estonia. This policy does not use the term "working day".

11.4 If a report names you, this is not the route you want. If a Report Names You is faster and more specific: it carries the routes to object, to have something corrected, to ask for deletion, to withdraw a confirmation you gave under 2.2, and to ask us not to produce a report about you in future. Nothing in this policy, and nothing in our contract with any customer, limits those rights.

11.5 We pay nothing for reports of misuse and we run no bounty. We will not act against anyone for telling us something in good faith.


This Acceptable Use Policy is part of the LeMans Labs legal set. Read it with the Terms of Service, which is the contract and governs the licence, liability and indemnity, and which also carries our provider identification and the address for notices; If a Report Names You, written for the person a report is about; Report Accuracy and Public Data and AI Transparency and Limitations, on what a report is and how it is produced; Intellectual Property, which governs automated access to this site; the Security notice, which carries the vulnerability disclosure policy; and the Refund Policy.