Security & Anonymity
Buyer↔seller anonymity is Keralora's core product guarantee, not a feature toggle. It is enforced by three independent technical walls — a breach requires all three to fail at once.
- Wall 1 — Application-layer scoping
- Your browser never talks to our database directly. Every read and write passes through a server-side access layer that explicitly scopes queries to your own account, and buyer-facing responses are built from types that structurally cannot contain a seller's identity — a leak would be a compile-time error, not a runtime hope.
- Wall 2 — Database row-level security
- Row-level security is enabled and enforced on every table in our database, independent of the application code above it. Buyer-visible seller data exists only as database views that omit identity columns entirely — the underlying tables grant buyers nothing at all.
- Wall 3 — Document and identity redaction
- Sellers appear to buyers only as a codename (e.g. SELLER-KL-001), never a company name. Buyer-facing invoices, packing lists, and lab certificates are generated from templates that cannot hold a seller's legal name or address. Uploaded files are stored under randomly generated keys, never a party's name.
Platform hardening
Every request carries a strict Content-Security-Policy with a fresh per-request nonce, HSTS, and standard security headers. Sensitive actions — bid submissions, quote requests, document downloads, payment webhooks — are rate-limited. Dependencies are audited on an ongoing basis, and every production build is scanned to confirm no credential or secret ever reaches code sent to your browser.
Reporting a vulnerability
If you believe you've found a security issue, please email us — we take every report seriously and will respond promptly.