Complete documentation of what BHASM reads, how it is stored, what it never does, and your rights as a data principal.
Compliance here is not a checklist — it is architecture. Privacy obligations are enforced as hard constraints inside the governance engine, the same layer that controls urgency scoring and hold decisions.
Security questionnaires, DPAs and the full sub-processor list on request: hello@bhasm.ai
{{ r.fields }}
{{ r.note }}
{{ s.v }}
{{ n.body }}
All outreach stops. No campaign, no brief item, no autonomous send — until the complaint is resolved, and a cooling period runs after that. The relationship is worth more than the message.
Sending a promotional message to a customer with a failed payment creates regulatory exposure and destroys trust. BHASM treats this as an absolute block. No campaign setting lifts it.
{{ c.v }}
Every tenant is encrypted under its own key, derived from a single master via HKDF-SHA256. A compromise of one tenant key decrypts nothing else. Security questionnaires and DPAs on request.
This page publishes no availability figure. Nothing in the system measures availability today, so any figure printed here would have no instrument behind it. Ask for the agreement; that is the binding document.
Continuity plan, source-code escrow and second-party deploy options for enterprise tenants.
{{ p.v }}
{{ s.body }}
For security questions, data processing agreements or compliance documentation for your procurement team, write to us.
Autonomous sending stays off until you switch it on. That is the wall on every plan — not a tier, and not a setting we flip for you.