Security & data

Security posture, including the parts that are missing

Most vendor security pages list capabilities and omit gaps, which makes them useless for the person doing the review. This one states what the system actually stores and enforces today, marks pilot-scoped items as such, and lists the gaps in their own section so you can find them without reading between lines.

Every capability on this page carries its real status: shipped code, work we do inside a pilot, or a design we have not built yet.

What is stored

Live todayModel-call records: timestamp, actor, source, operation, provider, model, token counts, latency, estimated cost and a JSON extras field. These come from the router we run on our own AI spend.
Live todayExposure-check scans: the submitted URL and host, the findings, the score, locale and user agent, plus a hashed client IP — raw IP addresses are not stored for scans.
Live todayContact submissions: the email or Telegram handle you type, your message, the page it came from, UTM parameters, and the submitting IP, which is kept for abuse control.
Live todayCustomer production prompts and responses are not stored, because the product does not sit in front of customer traffic yet.

Retention and deletion

Live todayThere is no automated retention window in the codebase today: scan, lead and call records are kept until deleted. We would rather say that than publish a policy nothing enforces.
Live todayDeletion on request: email us and we remove the rows — scans by report link, leads by the address you used.
Pilot scopeRetention rules bound to a pilot — window, scope and who may export — are agreed as part of that pilot.

Keys and BYOK

Live todayProvider API keys live in server-side environment configuration and are never shipped to the browser. The exposure check exists partly because this is the mistake we most often find in other products.
Design intentA customer-facing key vault, per-lane key scoping and rotation workflows are design. There is no BYOK storage in the product today.

Access control

Live todayStaff and superuser roles gate the administrative surfaces, and those surfaces are kept out of the public navigation rather than merely unlinked.
Design intentPer-customer RBAC, SSO and SCIM provisioning do not exist yet. If your procurement requires SSO today, we are not the answer today.

Audit trail

Live todayEvery model call writes a structured record; the full field list, with each field marked shipped or design, is published on the evidence page.
Design intentTamper-evident storage — hash-chained records where a silent edit breaks the chain — is designed and not built.
Pilot scopeScoped evidence packs are assembled inside a pilot; there is no export button in the product.

Abuse controls

Live todayRate limits per endpoint: contact submissions are capped per hour per client, and the exposure check is capped tighter because it fetches a URL you supply.
Live todayForms carry a honeypot field; submissions that fill it are accepted silently and stored nowhere.
Live todayScan findings redact the secrets they detect, so a shared report link does not become the leak.

Transport, storage and hosting

Live todayAll traffic to the site and API runs over HTTPS.
Live todayA single hosted deployment in the EU backs both the site and the API today.
Live todayThere is no application-level field encryption: data sits in the database protected by host and access controls, not by per-field cryptography.
Pilot scopePrivate deployment and data residency in a region of your choice are pilot-scoping conversations, not switches.

Known gaps, stated plainly

If one of these is a blocker for your review, you have learned it here in a minute instead of three calls in.

No SOC 2 attestation.
No PII or secret filtering in the model path — the only automated output check looks for refusals and absurd lengths.
No policy engine, so no record carries an allow / redact / block decision.
No tamper-evident storage and no evidence-pack export.
No automated retention or deletion schedule.
No customer key vault, no SSO, no SCIM.
No gateway in front of customer production traffic — governed lanes are design intent.

SOC 2

SOC 2 is on the roadmap and not attested. We will not describe ourselves as certified, compliant or audited before an auditor says so in writing, and we would rather lose a deal than be quoted otherwise in your report.

Questions a security review asks

Where is our data hosted?

In a single hosted deployment in the EU covering both the website and the API. Multi-region and customer-chosen residency are pilot-scoping topics, not existing configuration.

Do you train models on anything we send?

No. We do not train models at all. Content sent to a third-party provider through our own router is subject to that provider's terms — and today the product does not process customer production traffic in the first place.

Can we get our data deleted?

Yes. Email us with the report link or the address you used and the rows are removed. Because there is no automated retention job, deletion is a request rather than an expiry today.

What does the exposure check send to your servers?

The URL you submit. The server fetches that page and stores the host, the findings, the score, your locale and user agent, and a hashed IP. It does not store your raw IP address.

Do you have SOC 2 or ISO 27001?

Neither, today. SOC 2 is on the roadmap. If your procurement blocks on an attestation, that is a legitimate reason not to buy from us yet, and we will say so on the call.