Security

Security and data handling

Braze access is read-only: every call is a server-side HTTP GET. SendSight does not send, create, update or delete anything in Braze.

What data we handle

Canvas and campaign structure, message templates and content blocks as authored, and aggregate daily metrics.
Segment names and IDs, plus aggregate size estimates. No segment membership or individual users are stored.
Custom attribute names and types and custom event names, without user values.
Optional bounce and unsubscribe endpoints return email addresses. We count them in memory and store only the totals, never the addresses.
We store the names and email addresses of your own users who sign in to SendSight.

Data handling

Storage:Supabase (PostgreSQL) on AWS us-west-2, encrypted at rest, with row-level security. Braze keys are stored in Supabase Vault; every key read is logged.
Retention:Synced data is deleted within 30 days of pilot or account end, or on request, with written confirmation. Database backups roll off within 7 days, so backup copies are gone well inside that window.
Transmission:TLS 1.2+ in transit.
Access:Row-level security limits every query to the workspaces a user belongs to.
Sign-in:Google, a passwordless email link, or Okta / SAML SSO. For SSO organizations, SSO can be enforced as the only sign-in method, including for MCP and API tokens. Okta SCIM provisioning is supported: unassigning someone in Okta ends their SendSight access within seconds. No passwords are stored.

API security architecture

Braze calls are read-only and run server-side.

Braze reads

Every Braze call is a server-side HTTP GET. No Braze call sends, creates, updates or deletes.

Supabase Vault

The Braze key is kept out of the browser, purged when the connection is removed, and every read of it is logged.

Client control

You can disable or delete the Braze key in Braze to stop access immediately.

Current security controls

Infrastructure

  • ✓Supabase (PostgreSQL) on AWS us-west-2, encrypted at rest
  • ✓All data transmitted over TLS 1.2+
  • ✓Row-level security limits queries to the workspaces a user belongs to

Access control

  • ✓Row-level security limits every query to the workspaces a user belongs to
  • ✓The client can disable or delete its Braze key at any time, immediately terminating access

AI features and MCP

What reaches an AI model, and who controls it.

In-product AI runs on models served through Amazon Bedrock in US Regions only. In-product calls do not go to model providers' own APIs.
Journey and template content is sent for categorization, summaries, findings and drafting. Email addresses are removed before every AI call; Liquid tags remain unrendered.
Bedrock does not use inputs or outputs to train models or share them with model providers. Zero data retention is configured. SendSight does not train models on customer data.
The MCP server lets each person use their own MCP-compatible AI assistant with their SendSight login and workspace permissions. Content returned goes to the tool they connect under their own agreement with its vendor. MCP writes stay inside SendSight and never change Braze or send a message.

Audience Insights

A separate Braze data flow that requires your approval before it is enabled.

AI Audience Insights is in early access. Audience volume and trends (segment sizes over time) come from the same read-only Braze key, with no person-level data.
Per-person views need a Braze Currents connector that you create and control, pointed at storage you own, with email, phone and IP removed by Braze before export. That part stays off until you enable it, and we provide the fields, storage and retention design in writing for approval first.

SOC 2 approach

We don't have a SOC 2 report yet. Our controls are designed against the SOC 2 Trust Services Criteria.

IT security FAQ

Do you have SOC 2 certification?

We don't have a SOC 2 report yet. Our controls are designed against the SOC 2 Trust Services Criteria.

How can we verify you will only read data?

For Braze, every call is a server-side HTTP GET. The published permission list contains no write or messaging scopes. You can disable or delete the key in Braze at any time.

Who has access to our data?

Your own team sees only its SendSight workspaces; row-level security limits every query to the workspaces a user belongs to. See our Privacy Policy for subprocessors.

How do we give you the API key?

The Braze key is stored in Supabase Vault, never sent to the browser, and purged when the connection is removed. Every read is logged.

Can we revoke access at any time?

Yes. You can disable or delete the Braze key in Braze at any time, immediately terminating SendSight's access.

Need a custom security review?

Book a call to discuss your security requirements.

Book a demo

See your whole program today

Connect a read-only API key and see one of your own journeys mapped live in minutes. No card, no sales call, no setup.

  • Broken link alerts
  • Anomaly alerts
  • Unlimited drafts
  • MCP access for agents