What is actually in place, and what is not.

Separation between publications

Every publication runs against its own database rather than sharing one with a tenant column. Requests are bound to a publication at the edge and that binding is carried through the request, so a query cannot accidentally read across the boundary.

Payments

Each publication connects its own Stripe account through Stripe Connect. Card details never reach us — the payment relationship is between the publisher and Stripe, and we hold identifiers rather than instruments.

Credentials

Sending-provider keys and integration tokens are encrypted at rest and scoped to a single publication. Assistant access mints short-lived credentials per request rather than storing long-lived admin keys.

Sign-in

Email and password, Google, and Microsoft. Staff accounts support two-factor authentication. Single sign-on is available on Business.

What is not in place

We are a new product. TribeTale has not completed a SOC 2 audit and does not claim one. It is built on Ghost, which has a long production history, but the multi-publication layer, the control plane and the integrations are ours and are new. Weigh that honestly against a vendor with years behind them.

If you are running a security review and need something specific, ask — we would rather answer a hard question than have you assume.