MergeMind
Security & trust

What's implemented, what's planned — no in-between

We'd rather tell you exactly what's real today than let you assume more. Every claim below is checked against the running platform, not copied from a template.

MergeMind does not currently hold SOC 2, ISO 27001 or any third-party security certification. The controls below are implemented in the running platform; formal certification is on the roadmap and prioritised by real enterprise demand. If a certification is a hard requirement for your evaluation, tell us in a Build Review — it shapes what we prioritise next.

Controls

Implemented today, checked against the code

Authentication & access control

Zero-Trust gateway

Implemented

A single gateway validates the JWT once, then signs and injects identity headers (HMAC + timestamp). Downstream services verify the signature — they never parse a JWT themselves.


Multi-factor authentication

Implemented

TOTP-based MFA with backup codes, alongside SSO and invite-based provisioning.


Token security

Implemented

JTI blacklisting, one-time refresh-token rotation and bulk session revocation.


RBAC + ABAC authorization

Implemented

50+ fine-grained permissions across 4 platform roles, plus an attribute/ownership policy engine (owner-only, roles, time and IP ranges, deny-overrides).


SSO / SAML for enterprise

Planned

Available today; SCIM 2.0 provisioning for automated user lifecycle management is in active development.

Tenant isolation

Tenant context from a verified header only

Implemented

The tenant a request operates on is resolved from the gateway-signed header, never from a client-supplied body field — so a tenant ID can’t be spoofed by the caller.


Enforcement at the data layer

Implemented

Every service scopes reads and writes to the caller’s tenant at the data-access layer — enforced, not left to per-endpoint convention.


Scheduled data purge

Implemented

Tenant offboarding includes a scheduled data-purge path for GDPR-style deletion requests.


Dedicated / VPC / self-hosted deployment

Planned

Full infrastructure isolation for a single tenant — available as part of the Dedicated Enterprise engagement.

Data protection

Encryption in transit

Implemented

All traffic to the platform is served over HTTPS/TLS.


Payment data

Implemented

Card and payment details are handled by our PCI-compliant payment processors (Razorpay, Stripe) — MergeMind does not store raw card data.


Published data-residency options

Planned

A formal published policy on where tenant data is stored, with regional options, is not live yet — available on request for engaged prospects today.


Published backup & disaster-recovery runbook

Planned

Backups exist operationally; a formal, externally published RPO/RTO commitment is on the roadmap.

Audit & observability

Transactional outbox to an immutable audit trail

Implemented

Domain writes emit through a transactional outbox to Kafka, so an event is never published unless its transaction committed — feeding a searchable, immutable audit store.


Distributed tracing & metrics

Implemented

Request tracing (Jaeger), metrics (Prometheus/Grafana) and structured logs on every service — not just uptime pings.


Per-tenant audit export

Planned

Self-serve export of a tenant’s own audit history via the console is planned; available on request today.

Compliance roadmap

Certifications & formal programs

SOC 2 Type I / II

Planned

ISO 27001

Planned

Formal subprocessor list & DPA template

Planned

Published vulnerability disclosure program

Planned

Found a security issue?

We don't yet have a formal bug-bounty program, but we take reports seriously and respond fast. Email hello@mergemind.co with details — please don't open a public issue or post the finding publicly before we've had a chance to respond.

Evaluating MergeMind for a real deployment?

Tell us your security and compliance requirements in a Build Review — we'll tell you honestly what's ready today and what isn't.