All documentsCompliance · Version 1.12

Sourcing and compliance statement

What is collected and how, what is never collected, opt-out and governance.

1. Summary

The company-signals products (Marketing stack, Hiring, Intent, Announcements and scale, Filings and records, and the Market series aggregated from them) are built only from public, first-party information: what companies publish on their own websites, in their public DNS records, on their newsroom pages and feeds and on the job boards they publish for distribution; public regulatory filings; open reference data for company identifiers and facts; and public web traffic data for a website's monthly traffic tier. Open data is used under its licence, and any credit a licence asks for is delivered with the data. No data is bought from, or collected from, any platform, social network, marketplace or data broker, and no personal data is delivered.

2. How we collect

  • Identified. Every request names our crawler, FokalsBot, and links to a public page that explains what it reads and how to opt out.
  • Permission-respecting. robots.txt is read and obeyed before every request, including crawl delays. A site's opt-out takes effect within a day. Where a publisher of open data turns crawlers away in its robots.txt but invites downloads of that data in the same file, we download as the file invites.
  • Polite. One request at a time per host, with pauses between requests; most sites are read once a day to once a week.
  • Public only. No sign-in, no forms, nothing behind a login or paywall.
  • English only. A website whose homepage is not in English is read in the English version the page itself declares or links, on the same rules as every read, at most two addresses. Without one it is not read beyond the homepage, and nothing of the page is kept; it is asked again a month later. How the language is judged is in METHODOLOGY.md section 4.2.
  • Blocked reads. When a site's network protection refuses the direct read (an HTTP 401, 403 or 429, or a challenge page), the page may be fetched through a proxy address or a third-party fetching service. The crawler's identity does not change, robots.txt is read and obeyed on that path as on every other, and no challenge is solved by us. A site that refuses on every path is recorded as refusing and asked again a month later. Sites read this way are read less often.
  • AI files. Beside the homepage, the crawler asks for the llms.txt file at a website's root, on the same rules as every read, and records what the site's robots.txt says to AI crawlers and the content signals it states, from the copy it reads to obey the file. A site's stated stance towards AI is delivered as part of its technology stack (METHODOLOGY.md section 5.1).
  • Pricing pages. When a homepage links a pricing page on the company's own website, that page is read now and then, on the same rules as every read, and what it shows (plans, prices, how they are charged) is compared with its last reading (METHODOLOGY.md section 5.4).
  • Discovery. Candidate websites come from links on pages we read, public lists of the most-visited websites, open web data, the job boards companies publish, open directories of business places, and open company and securities lists. Each candidate is read once, on the rules above, and checked before it becomes a company in the index.
  • Announcements. A company's newsroom or press page (when its homepage links to one) and the RSS or Atom feeds its homepage declares are read on the rules above, at most three per company, daily to every three days. Each announcement is kept as a title, a date, the address of the original and an excerpt of at most 1,200 characters of the company's own text, with its event type.
  • Public records. Regulatory filings are read within the regulator's published fair-access rules, identifying the business and a contact address in every request: private capital raises, and for listed companies their current reports, the employee count stated in their annual reports, the reports their insiders file when they trade the company's shares, the statements of anyone holding more than five per cent of them, and the structured financial statements they file. Filings of earlier years are read back the same way, at a share of the same pace, and kept beside the filings read as they are published, each marked as read back.
  • Open data. Open reference data for company facts and identifiers, and public web traffic data for the monthly popularity bucket of each website, worldwide and by country, used under their licences and delivered with the credit they ask for in the licence notices.
  • Open web measurement crawls. Public crawls that test website home pages each month record the technologies each page uses; only which technologies were detected on a company website in each month is kept, never the pages, their files or anything about their visitors. The source is credited in the licence notices.

3. What we do not collect or deliver

  • Personal data. Contact details in job descriptions (email addresses, phone numbers, personal profile links) are removed before storage. The individuals named in regulatory filings (officers, directors, promoters, sales recipients, signatories) are never read. In an insider's trading report or a large holder's statement, a person who files is kept by their role only (director, officer with the title the filing gives, owner of more than ten per cent, holder): their name, address and filer number are never stored, and the reference that tells two of their reports apart is particular to one company. An organisation that files (a fund, an adviser, a company) keeps its name.
  • Small sites that may belong to individuals. Websites, postings and signals are delivered only for companies in our index; a brand's site that we cannot tie to a company is read for internal quality work only and never delivered.
  • Employers' text. Job descriptions are used to derive structured fields and are not delivered.
  • Websites in other languages. A website with no English homepage and no English version is neither stored nor delivered, and a company whose websites are all of that kind is left out of every product. The list of listed securities is not filtered by language.
  • Visitor data. We read what a site publishes, not who visits it. The products contain no cookie, device or visitor-level data of any kind; the traffic tier is a monthly rank bucket of the website as a whole, from data published under an open licence.
  • People in announcements. A leadership change (a press release, or a listed company's current report) is kept as the company's dated statement with the excerpt the company published. The role concerned (chief financial officer, head of sales, board) is labelled; the person is not stored. No profile of a person is built, no person is tracked from one company to another, and no social network is read.
  • Sales representatives. What we publish about a sales organisation is what the employer advertises: roles, segments, pay ranges, quotas, ramp and lead mix as stated in its own postings. We collect no ratings, reviews or reports from employees, and no attainment or earnings figures.

4. Intent data

Intent scores and signals hold public information only, as every Fokals dataset does. They are not built from the browsing behaviour of people, bidstream data, cookies or any consumer data.

5. Material non-public information

All inputs are public at the time they are observed. We do not receive information from insiders, from companies under confidentiality, or from any non-public source. The trading reports of a company's insiders are public filings, read once the regulator has published them.

6. Opt-out and removal

A site owner can stop FokalsBot with robots.txt (User-agent: FokalsBot / Disallow: /). A company can ask for its information to be removed by writing to the contact address on the crawler page.

7. Governance

Collection rules are enforced in code, in one component that every request passes through. Labels and scores are written under named versions of their definitions, verified on every run. Daily and weekly outputs are written once and never rewritten. AI-written company briefs are marked as such and carry the facts they cite; they are our assessment of public facts, not statements about any company's plans. This statement, an overview of the methodology, the data dictionary, the API reference and the crawler page are published on the Fokals website; the full methodology is shared with clients and with teams evaluating the data.