Protected
Attendee names and email addresses are encrypted at rest and in transit.
Security and trust
Attendee information stays private to the event owner.
You control the attendee records for your events. Names and email addresses are encrypted in transit and at rest; only the event owner can view them, and Bloomod cannot read them.
Owner-only
Event owners alone can view sensitive attendee information. Bloomod cannot view it.
Accountable
Important invite, consent and account activity can be recorded and reviewed.
Controls
What is in place, and what it covers.
| Control | Covers | Status |
|---|---|---|
| Encryption in transit | All API and application traffic | In place |
| Encryption at rest | Attendee names, email addresses and invite content | In place |
| Owner-only access | Attendee names and email addresses | Enforced |
| Scoped API keys | Programmatic access, separate test and live | In place |
| Sender verification | Sending identity and domain | Required |
| Verification gate | Calendar automation for each event | Verified only |
| Event automation control | Each event’s calendar invitation workflow | Owner controlled |
| Activity recording | Event, verification and account events | In place |
This page describes the security model of the product as designed. It is not a certification claim. For current compliance documentation, write to hello@bloomod.com.
Sender verification
Only you can send as you.
Verification proves the sending identity belongs to your business. It is what allows invites to carry your organiser name — and what stops anyone else from doing so.
- Domain ownership confirmed before sending
- Sending identity tied to a verified business
- Volume increases gated on verification status
- Unverified accounts limited to low daily volume
Approval gate
The API cannot bypass a person.
A campaign created programmatically returns 202 Accepted and waits, exactly like one created in the interface. There is no flag that skips approval, because a flag that skips approval is the feature that causes incidents.
Approval required
Always- Created in app
- Approval required
- Created via API
- Approval required
- Scheduled campaign
- Approval before queue
- Series update
- Approval required
Your responsibilities
Shared model, stated plainly.
Platform security is ours. Consent and content are yours. Neither of us can cover the other's half.
Bloomod does
- Encrypt and store records
- Enforce roles and scopes
- Apply suppression and pacing
- Record account activity
You do
- Obtain and evidence consent
- Keep your member list current
- Protect your API keys
- Approve only what you intend to send
Questions about data handling?
Write to hello@bloomod.com for current product access or policy information.