SynapCTX is built for proprietary engineering systems. This page explains what the service processes, how organizations remain isolated, and which deployment model fits your requirements.
SynapCTX processes the repositories you explicitly connect, the code structure derived from them, agent retrieval requests, organizational memories your users choose to store, and the minimum account and usage data needed to operate the service.
Each connected organization is treated as an isolated tenant. Repository context, graph data, memory, credentials and usage are scoped to that organization throughout the service. Authentication never relies on the marketing-site account hint cookie; authorization is enforced by the console and service APIs.
Customers can disconnect repositories and request deletion of account or organization data. Trial and subscription states preserve indexed work as described on the pricing page; they do not silently convert customer content into public data or training material.
The managed service provides organization-level isolation on SynapCTX-operated infrastructure. Sovereign deployments use infrastructure dedicated to one organization and can be sized, located and operated around its requirements. Contact us for the exact architecture, support boundary and data-region needs.
Send security reports to security@synapctx.com. Include reproduction steps and impact where possible. Please do not access data that is not yours or disrupt the service while investigating.
Tell us your deployment, data-residency and assurance requirements. We will answer directly and document the agreed boundary.
Contact security