PostgreSQL Row-Level Security (RLS) & Multi-Tenant Isolation
Nsol Flow enforces multi-tenant boundary isolation at the database kernel level through PostgreSQL Row-Level Security (RLS). Rather than relying on application-layer query filters or software-level routing flags that can fail during high-concurrency operations, database policies enforce cryptographic boundaries on every row query and mutation.
Every operational table in our schema—including clients, leads, conversations, messages, appointments, and client_service_entitlements—has strict Row-Level Security explicitly enabled.
Session identity is anchored to signed cryptographic tokens. PostgreSQL evaluates auth.uid() = profile_id and containment subqueries. Cross-tenant leakage is mathematically prevented by the relational database engine.
PostgreSQL Canonical Isolation Policy Reference
-- Every query executes within strict tenant boundary containment
CREATE POLICY "tenant_isolated_leads_access"
ON public.leads FOR ALL TO authenticated
USING (
client_id IN (
SELECT client_id FROM public.client_members
WHERE profile_id = auth.uid()
)
)
WITH CHECK (
client_id IN (
SELECT client_id FROM public.client_members
WHERE profile_id = auth.uid()
)
);Cryptographic Encryption in Transit & At Rest
All communications between real estate clients, prospective home buyers, edge telecommunications nodes, and our core compute infrastructure traverse zero-trust encrypted networks. We implement enterprise cryptographic standards across every layer of the operational stack.
All web, webhook, and API endpoints enforce TLS 1.3 exclusively with Perfect Forward Secrecy (PFS). Legacy ciphers (TLS 1.0, 1.1, and insecure RC4/DES suites) are systematically blocked at edge gateways.
Underlying database volumes, read replicas, and object storage buckets housing call recordings and listing brochures are encrypted at rest using hardware-accelerated AES-256 GCM encryption.
Third-party carrier credentials (telephony carrier tokens, Voice API keys, Core CRM OAuth tokens, Resend keys) are encrypted via dedicated Key Management Services (KMS) and never surfaced in application logs.
Decoupled Provider Architecture & Uptime Invariant
Nsol Flow is engineered around a core architectural invariant: “If Nsol Flow experiences downtime, the brokerage’s business and lead conversion keep running uninterrupted.”
Form Studio intake forms submit directly to the platform’s global CDN edge infrastructure (Nsol Cloud Forms). Prospective client inquiries never pass through an intermediate bottleneck. If Nsol Flow web services are undergoing maintenance, inbound consumer inquiries are captured, tagged, and ingested into your CRM with 100% fidelity.
Sarah’s conversational AI prompts, property qualification criteria, and calendar booking webhooks are compiled and synchronized directly to Autonomous Voice and Core CRM Custom Values at configuration time. During live telephone calls, speech-to-text, LLM inference, and voice synthesis occur entirely on enterprise carrier voice meshes. Inbound or outbound calls never rely on synchronous HTTP calls to Nsol Flow servers during active conversations.
Zero LLM Model Training on Proprietary Brokerage Data
Luxury real estate brokerages handle high-value listing presentations, sensitive client financial disclosures, and proprietary geographic farming notes. Nsol Flow operates under a strict, non-negotiable contractual zero-training policy.
Brokerage listing brochures, client contact databases, agent notes, and conversation transcripts are NEVER used to train, fine-tune, or reinforce foundation models provided by OpenAI, Anthropic, Google, or any public open-source project.
All AI inference is executed exclusively through enterprise-tier commercial APIs governed by strict Zero-Data-Retention (ZDR) and Business Associate agreements. Prompt payloads are flushed from inference memory immediately upon token emission.
Voice AI Telephony Telemetry, TCPA & Consent Policies
Nsol Flow operates telecommunication services in strict adherence to Federal Communications Commission (FCC) guidelines, the Telephone Consumer Protection Act (TCPA), and state-specific two-party recording statutes.
Permissible Calling Time Windows & DNC Registry
Speed-to-lead automated call dispatches enforce local time-zone fences. Outbound voice dispatches are restricted between 8:00 AM and 9:00 PM in the prospect’s recipient area. Inbound DNC requests or “STOP” keywords trigger instant cryptographic opt-out tags across both platform carrier routes and CRM pipelines.
Two-Party Consent Recording Injections
When routing telephony to or from numbers registered in two-party consent jurisdictions (e.g. California, Florida, Massachusetts, Washington), Sarah autonomously injects verified call recording disclosures prior to initiating conversational intake questions.
Automated Audio Telemetry Lifecycle
Audio recording blobs and raw audio stream buffers are stored in encrypted tenant buckets. Tenants may configure automated TTL (time-to-live) retention windows (30, 60, or 90 days), after which underlying media is cryptographically overwritten and purged.
Support Mode Impersonation & Mutation Barriers (Phase 18)
Platform engineers, customer success personnel, and systems architects are structurally prohibited from accessing customer workspaces without formal client authorization. Nsol Flow implements the rigorous Phase 18 Support Mode specification.
Support Mode can only be initialized through an active, time-bounded support ticket created with explicit justification. Access expires automatically and cannot be held indefinitely.
Every support session initiates with strict mutation barriers in read-only diagnostic mode. Any state-modifying action requires explicit secondary dual-custody verification.
Every single view, query, and administrative interaction within an impersonation session produces an immutable, cryptographically hashed audit event record. Brokerage administrators receive full transparency reports showing who accessed what record and when.
Tenant Data Sovereignty & Carrier Asset Retention (Phases 16 & 17)
At Nsol Flow, brokerages retain full legal sovereignty and operational ownership of their data and telecommunication assets. We do not engage in proprietary data lock-in or asset confiscation.
Brokerages can export their complete operational database—including lead histories, notes, call logs, appointment schedules, and form funnel definitions—in standardized CSV (RFC 4180) and JSON formats with one click at any time.
If a brokerage pauses or cancels their subscription, their dedicated sovereign phone numbers and carrier routing identities are never destroyed. Assets enter a protected parking state with guaranteed 1-click port-out capability to any carrier.
Responsible Vulnerability Disclosure Program
We welcome collaborative security research from certified penetration testers, white-hat researchers, and engineering partners. If you discover a security vulnerability or anomalous behavior across our infrastructure, please notify our security team immediately at security@nsolflow.com. We pledge to acknowledge all vulnerability disclosures within 24 hours.