How Konyx keeps a person in charge of every send, isolates each company, and records what happened.
AI reads and drafts; it never sends. Every RFQ waits for a named person who holds the permission to open it, review the exact email, acknowledge the review and press Send.
Related: One RFQ to all the vendors · Autonomous purchasing
Source: Engineering Action Plan — decision log, 15 Sep 2026 · Checked 26 October 2026 · Version 2 · control.person-presses-send
Drafting an RFQ and sending it are separate permissions, checked in the API on every request — not in the screen. An employee who cannot send escalates by design, not by convention; calling the endpoint directly is refused.
Related: Roles and permissions · An employee who may raise a request but not send an RFQ
Source: Engineering Action Plan — §3.1 · Checked 26 September 2026 · Version 1 · control.permissions-on-every-call
Every state change is written in the same transaction as the change itself, by the one function allowed to change a status, and the log is append-only at the database level. The trail cannot disagree with what happened because nothing else can write either.
Related: The activity log · Can we see who did what?
Source: Engineering Action Plan — §3.7 · Checked 26 September 2026 · Version 1 · control.append-only-audit
A Konyxion — a vendor Konyx found on the web — is never emailed until a person picks it and checks the address on the send screen. That one gate is the quality gate, the deliverability gate and the legal gate.
Related: Konyxions — vendors found on the open web
Source: Engineering Action Plan — §3.4 · Checked 7 October 2026 · Version 2 · control.discovered-vendors-reviewed
Row-level security is forced on every tenant-scoped table and the application connects as a role that cannot bypass it. Two automated checks fail the build if a table lacks its policy or a query bypasses the scoped accessor, and a live test proves a cross-company read is refused. Konyx staff use the same permission wall, never a database console.
Related: How is our data kept separate from other companies'? · The shape of the system
Source: Engineering Action Plan — §3.1 · Checked 26 September 2026 · Version 1 · control.tenant-isolation
The Terms of Service and Privacy Policy are published at konyxai.com/terms and konyxai.com/privacy. Everyone creating a company or signing in to the company app ticks a box agreeing to both, and the version each person agreed to, and when, is recorded against them and in the activity log. The Terms set out how plans bought online are billed, renewed, changed and cancelled; card payments are taken by Stripe and card details never reach Konyx. The Cookie Policy at konyxai.com/cookies lists every cookie: one keeps a person signed in (7 days), one carries a sign-up to payment (up to a day), and Google Analytics' own only while analytics is switched on.
The sign-up, sign-in, activation and password-reset forms refuse to go on without the box, and so does the API behind them. When the terms change, the next sign-in asks again.
Konyx does not sell personal information or use it for advertising. Google Analytics runs on the site and the company app only when switched on, with advertising features off; it receives page paths with record numbers blanked, counts and choices, and the person and company as internal codes — never names, emails or what anyone typed. It never runs on the vendor quote link, or when the browser sends Global Privacy Control.
- Terms of Service
- https://konyxai.com/terms
- Privacy Policy
- https://konyxai.com/privacy
- Cookie Policy
- https://konyxai.com/cookies
- Recorded per person
- terms version agreed to
- when
Related: Each company is isolated in the database · Where does Konyx run? · Which AI models does Konyx use, and what sees our data?
Source: konyxai.com — /terms, /privacy and /cookies · Checked 15 October 2026 · Version 3 · control.terms-and-privacy
A company and its owner come into being in one of two ways: Konyx staff create them from the console, which emails the owner a temporary password, or the buyer signs up online, confirms their email with a six-digit code and chooses their own password. Nothing can be signed into that a person did not deliberately create, and every credential has one auditable origin.
Related: The shape of the system
Source: Engineering Action Plan — decision log, 15 Sep 2026 · Checked 26 October 2026 · Version 2 · control.no-default-accounts
One backend owns the database, the sessions, the permissions, email and AI, and cannot be reached without a key the browser never holds. The web applications are database-free: the browser calls their own backend, which forwards to the API with that key and the person's session. Sessions live in an httpOnly cookie; the token never appears in a response body.
Every route that can be abused is rate-limited in the database, so every instance sees the same count: sign-in, activation, RFQ sending, AI requests, web vendor search, the vendor quote link, imports and the rest. State changes are refused unless the request came from the application's own origin. Security headers are set on every response; secrets live in a managed secret store, not in code.
Related: Where does Konyx run? · Each company is isolated in the database
Source: Engineering Action Plan — decision log, 16 Sep 2026 · Checked 26 September 2026 · Version 1 · control.architecture
Each call to a model is recorded with who made it, which task and prompt version, and what it cost, and is shown per company and platform-wide. Each extracted field keeps its state, its evidence and the call that produced it, so the answer to why did it say that is always on file.
Related: What the AI does, and what it never does · Which AI models does Konyx use, and what sees our data?
Source: Engineering Action Plan — §3.8 · Checked 26 September 2026 · Version 1 · control.ai-provenance
A vendor's reply is written by someone outside the company, so nothing in it is trusted: every event from the mail provider is signature-checked and refused if it is old, mail is counted and capped before it is read, a message is only ever shown as text, unsafe file types are never kept, and the model that labels a reply can answer with one word from a fixed list and nothing else.
Limits apply per reply address, per company, per sender and overall; past a limit a message is not fetched, kept or passed on, and the RFQ's log says so once. A duplicate delivery changes nothing.
Files a vendor attaches are downloads, never opened in the page, and the browser is told not to guess their type. Programs, scripts, web pages and macro-enabled documents are refused, and so is the original of a message that carried one.
The copy emailed to the buyer sets the vendor's words apart from Konyx's own, warns when the sender is not one Konyx holds for that vendor or failed its mail checks, and is marked so that it cannot loop back in or set off an automatic reply.
A reply is stored in the company's own data like everything else: another company cannot see it, its files or its original.
- Daily limit per reply address
- 25 emails
- Hourly limit per sender
- 40 emails
- What a model may add
- one label from a fixed list
Related: Vendor replies by email, on the RFQ · Each company is isolated in the database · Every model call is recorded · An audit trail that cannot drift
Source: konyx-api — email/inbound.ts, core/inbound-mail.ts, webhooks · Checked 2 October 2026 · Version 1 · control.outside-email