Certified, not self-declared, what procurement actually requires
Third-party certification backs every claim: FERPA and COPPA compliance, iKeepSafe certification, and the Student Privacy Pledge, independently verified and publicly documented. Your technology review team gets documentation, not talking points. And because Bloomz has no advertising model, families are users, never the product.
Controls administrators actually hold, not assumed safe
Role-based permissions decide exactly who can message whom across district, school, classroom, and group levels. Moderation and quiet-hour policies keep communication professional, and staff never share personal phone numbers. Every message is archived for reference, records requests, and peace of mind, with no extra configuration.
Granular, role-based control across district, school, and class. Tap a role to see exactly what it can do. Try it.
Secure delivery and regional residency, where the law requires it
Report cards, IEPs, and sensitive notices route only to verified guardians over secure delivery, anchored to SIS identity, not self-asserted accounts. SSO keeps authentication on your identity provider. Regional data hosting is available where residency rules require it, already running in production internationally, including Singapore.
Report cards and IEPs delivered only to verified guardians, encrypted, logged, and audit-ready. Tap a document. Try it.
Uptime you can verify yourself, at status.bloomz.net
A public, independently hosted status page is live at status.bloomz.net: real-time status for every Bloomz service, an incident timeline the moment something's degraded, and a per-component uptime history that builds day by day rather than one blended number. It runs deliberately outside Bloomz's own app infrastructure, so it stays reachable precisely when the app isn't.
A live, independently hosted view of every Bloomz service, with 90 days of uptime history per component. Tap a category. Try it.
How this reinforces the Bloomz pillars
Connected across Bloomz
20 minutes with Bloomz
answers more than 20 pages ever could.
Bring your hardest scenario, a multilingual community, a PBIS rollout, a vendor consolidation, and we'll walk through the actual product.