06 Security & ownership
Single-tenant Postgres in your own account and region. No shared multi-tenant tables, no model training on your data, and tested exit exports.
Architecture controls
Your own Postgres database in your own account and chosen region (Singapore, EU, UK, or self-hosted HK/on-premise): never mixed in shared multi-tenant tables.
The 5x6 Matrix plus Hard HR Lock enforces Postgres RLS before rows leave the database. Shared catalogue specs can cross brands while factory names, buy-prices, finance keys, and HR stay fenced off.
Test exact permissions on a live tender before inviting any salesperson, sourcing engineer, or contractor.
Staff run playbooks safely without overwriting house standards. Outbound connections are blocked from leaking OEM factories, margins, sister brands, or contacting DNC accounts.
Tokens are issued per user, never passed through to other services. Tools run parameterised queries with read-only defaults and rate limits.
Daily backups plus an independent nightly vault export tested at go-live. If you leave, you keep the database and schema files.
WhatsApp, WeChat/WeCom, and Telegram webhooks verify cryptographic signatures; email CC and forwards enforce DKIM/SPF against staff RLS, answer 1-to-1 to the sender (never reply-all), and require an Approve tap before canonical Postgres writes.
Voice notes, whiteboard photos, forwarded threads, Quote Shield flags, and agent drafts stay staged until an authorised owner taps Approve. Nothing enters canonical company memory silently.
Preview as staff
Test exact row visibility per role before inviting any salesperson, sourcing engineer, or contractor.
ROLE: OWNER
Rexel 28.5% gross floor · Dongguan Plant #2 US$1.31/m · Board & HR unlocked
Nothing withheld in Postgres
Contract & exit
Your company owns the Supabase / Postgres account and picks the region (Singapore, London, Frankfurt, or your own HK / on-premise server). Empra operates as named processor.
Client files, pricing rules, and conversations never train foundation models and never touch another client's project.
Standard DPA with 48-hour breach notification, minimal personal data by default, and no mainland personal data routed to Chinese desktop LLM connections.
Daily backups plus an independent nightly vault export tested before handover. If you leave, you keep the database and schema files.
Next