Security

This is how things stand today, and we revise it when they change. A security page that describes controls not yet built would be the worst overclaim we could make.

What this site collects

Very little. There is no account, no analytics script and no cookie. The scan and the assessment take a web address and multiple-choice answers, and keep the result under a random link for 30 days by default. Reminders keep an email, domain, due date and page; plan requests keep a website, note and optional reply email, without IP addresses. The details, including browser storage and provider prompts, are on the privacy page.

Controls that exist now

Modest, because the site is modest. These are the controls that apply to the public site and the requests and results it stores.

Perplexity Sonar receives public company details, site excerpts and evidence prompts, and buyer questions in the live assessment; Gemini is paused in production. “Polish copy” sends its template to Perplexity only on click. Paid calls share a daily rupee budget and cost log, with 7-day evidence/draft caches and 24-hour run reuse. Background lookups update and re-score saved results while keeping the first snapshot. An installation-only baseline-signing-key contains no customer data and cannot extend result expiry. “Check live URL” is limited to the company host or its www alias; peer refresh/save reads respect robots.txt and client/company limits.

TLS on every route, with HTTP redirected to HTTPS.
The scan and the assessment read public pages of the named site as FoundronicsAssessmentBot. Private and internal networks, link-local and cloud-metadata addresses are refused, every address a name resolves to is checked, redirects are checked again and limited to five, and each request has a time limit and a size limit. Checks are rate limited for each visitor.
Credentials are kept only in environment configuration, never in the repository.
A scan for secrets over the staged changes and the whole tree, run before every release.
Main content is rendered on the server. No third-party script runs here.
Checks on dependencies and types, in the same gate that can stop a release.

Controls that land with the assessment workflow

These remain planned controls, not a description of the current file-based assessment workflow.

Row-level security, and checks that know which customer a record belongs to, on every customer record.
Retrieved text and model output are treated only as data. Instructions found inside a crawled page are quoted as evidence and are never carried out.
A record of events when privileges change and whenever anything is published.
A person must give approval before any result about a company is published.

Reporting an issue

If you find a weakness in this site, please report it to us before you disclose it. Our security.txt, at /.well-known/security.txt, points here. Use the human contact route on the corrections page.

A published result about a company is a different kind of matter: corrections covers that.