Protected
Data protection depends on the controls supported by the deployed infrastructure.
Security and trust
Attendee data is limited to authorised access.
Attendee data is available only to authorised organisation members and authorised Bloomod personnel where operationally required. Data is protected in transit and at rest where supported by the deployed infrastructure.
Authorised
Organisation roles and operational need determine who can access attendee information.
Accountable
Important invite, consent and account activity can be recorded and reviewed.
Controls
What the security model requires.
| Control | Covers | Status |
|---|---|---|
| Transport protection | Application and provider connections | Infrastructure dependent |
| Data protection at rest | Sensitive attendee and Event data | Where supported |
| Organisation roles | Attendee and Event access | Required control |
| Operational access | Authorised Bloomod support and administration | Need-to-know |
| Planned API credentials | Future Business integration access | Planned |
| Sender identity checks | Connected providers and Business custom domains | Context-specific |
| Verification gate | Calendar automation for each Event | Event-scoped |
| Activity records | Important Event and account actions | Where implemented |
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 identity
Identity checks match the sending model.
Free uses a connected Google or Microsoft identity where applicable, or Bloomod-managed transactional delivery when available. Business custom domains, custom reply-to addresses and own SMTP require ownership and configuration checks.
- Free does not require a custom sender domain
- Connected provider identity applies where used
- Business custom domains require ownership verification
- Higher-volume limits require a separate operational review
Planned API controls
Integration access remains subject to review.
The Event API is not yet in production. The proposed Business model keeps invitation writes in a review queue and does not treat API access as permission for unrestricted sending.
Proposed control model
Planned- Created in app
- Event rules apply
- Created via API
- Review queue proposed
- Higher volume
- Separate approval
- Provider limits
- Always apply
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
- Apply access and infrastructure controls
- Enforce organisation roles
- Apply suppression and pacing
- Record important activity where implemented
You do
- Obtain and evidence consent
- Keep your member list current
- Protect account and integration credentials
- Approve only what you intend to send
Questions about data handling?
Write to hello@bloomod.com for current product access or policy information.