Built for agency, legal, and enterprise due diligence.
This page is maintained by Montjoy Synapse to answer common security, privacy, and infrastructure questions from prospective partners and their technical reviewers. It describes controls that are currently enabled in the platform — not a third-party certification.
Postgres Row-Level Security (RLS) on every tenant table
Every user-owned table in the Montjoy Synapse database enforces Postgres Row-Level Security policies scoped to auth.uid(). Tenants cannot read, insert, update, or delete records they do not own. Public reporting surfaces are mediated by explicit SECURITY DEFINER RPCs that project only non-PII columns.
Zod-validated inputs at every server boundary
Every server function is defined with createServerFn and an .inputValidator() step backed by Zod. Untyped payloads are rejected before touching the database, and validation errors are surfaced without leaking schema internals.
Role separation via a dedicated user_roles table
User roles are never stored on the profile row. They live in a dedicated user_roles table and are checked through a has_role security-definer function that prevents recursive policy evaluation and privilege-escalation attacks.
Isolated tenancy for uploads and documents
Documents uploaded on the Account page use a private storage bucket with per-user RLS on every read, write, and list operation. Agency workspaces enforce the same isolation between clients through the agencies / agency_clients relationship.
AES-256-GCM at rest for integration secrets
OAuth tokens and API credentials stored for Google, OpenAI, and Perplexity integrations are encrypted at rest with AES-256-GCM using a server-only integration key. Secrets are never returned to the client.
SOC 2-aligned operating controls
Montjoy Synapse operates against a SOC 2-aligned control set: least-privilege access, audit logging on privileged operations, background security scans, and vendor review for every subprocessor. Formal SOC 2 attestation is on the current roadmap; a full subprocessor list is available on request.
Requesting deeper documentation
Agency partners, procurement teams, and enterprise security reviewers can request our detailed architecture overview, subprocessor list, incident-response summary, and current DPA. Reach out through the FAQ or your Montjoy Synapse account contact and we will respond within one business day.
Shared responsibility: Montjoy Synapse operates the platform controls above. Customers remain responsible for account credential hygiene, user provisioning inside their workspace, and the accuracy of content they publish through the platform.