Security and trust
Security built into every step.
Your attendees trust you with their details, and you trust us with them. Bloomod encrypts sensitive data, keeps every workspace separate and sends only to attendees who have confirmed their email.
Encrypted
Attendee email addresses and calendar connection tokens are encrypted at rest, and all traffic uses HTTPS.
Passwordless
Sign in with a one-time email code, Google or Microsoft. There are no passwords to steal or reuse.
Isolated
Every Event and attendee belongs to one organization, and is only reachable through that organization’s membership.
Controls
How Bloomod protects your data.
The controls in place today, in plain language.
| Control | What it does |
|---|---|
| Passwordless sign-in | One-time 6-digit codes are stored hashed, expire after 10 minutes and lock after 5 wrong attempts. Google and Microsoft sign-in use expiring, single-use state checks. |
| Encryption at rest | Attendee email addresses and calendar access and refresh tokens are encrypted. Duplicates are detected with a keyed hash, without reading the address. |
| Encryption in transit | The workspace is served over HTTPS, with HTTP Strict Transport Security. |
| Workspace isolation | Every request is resolved through your active organization membership. An organization ID sent from a browser is never trusted on its own. |
| Roles | Billing and calendar integrations can only be managed by members whose role allows it. |
| Single-use verification links | Links are stored hashed and work once. Opening a link changes nothing; the attendee must confirm, which protects against link scanners. |
| Separate calendar access | Calendar permissions are granted separately from sign-in. Sign-in tokens are never reused for calendars, and disconnecting a calendar revokes its tokens. |
| Rate limiting | Sign-in, registration forms, verification and sending are rate limited to slow down abuse. |
| Browser protections | Forms are protected against cross-site request forgery, and security headers limit framing and content sniffing. |
| Signed webhooks | Payment notifications are accepted only with a valid signature. |
| Activity records | Important actions on each Event are recorded in its activity log. |
| Session control | Sign out every other session from Settings, or delete your account and workspace. |
This page describes Bloomod’s security controls. It is not a certification claim. For questionnaires or compliance documentation, write to [email protected].
Responsible sending
Only people who confirmed get an invitation.
Unwanted calendar invitations harm attendees and sender reputation. Bloomod is built so that automated sending reaches only confirmed, expected recipients.
- Automated invitations go only to verified attendees
- Malformed, duplicate and blocked addresses are caught early
- Delivery is paced and can be stopped at any time
- Bloomod SMTP domains are verified through DNS before use
Sender identity
- Google or Microsoft calendar
- Your connected account
- Email on Seed
- Bloomod’s sending domain
- Bloomod SMTP
- Your DNS-verified domain
- Calendar provider limits
- Always apply
Shared responsibility
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 sensitive data and secure sign-in
- Keep each workspace separate
- Send only to verified attendees, with paced delivery
- Record important Event activity
You do
- Collect attendees lawfully, with consent
- Invite only people who expect to hear from you
- Keep your team’s access up to date
- Protect your email and calendar accounts
Security, answered.
Something not covered here? Write to [email protected].
What attendee data does Bloomod store, and how?
Attendee email addresses and the calendar tokens used to send on your behalf are stored encrypted at rest. Attendees belong to the event where they registered, inside your own workspace.
Can another organization see my attendees?
No. Every event and every attendee belongs to one organization's workspace, and workspaces are isolated from each other. The infrastructure is shared; the data is not.
How do people sign in to Bloomod?
Passwordless: an email one-time code, or Google or Microsoft sign-in. There is no password on the account, so there is no password to leak, reuse or phish.
Why does Bloomod insist on verifying attendees?
Because an automated calendar invitation writes into someone's calendar. Each attendee confirms their address through a single-use link, and only confirmed addresses receive automated invitations. Unverified attendees stay saved with the event and are never auto-invited.