How MessageOS.ai protects data, controls access, and responds to security reports.
This page is maintained by MessageOS.ai to answer common security and privacy questions about the MessageOS platform and the Ezra agent. It describes current, enabled controls and is not an independent certification.
MessageOS.ai runs on managed cloud infrastructure with backend services hosted on enterprise-grade providers. Application data is stored in managed Postgres with encryption at rest and encryption in transit (TLS) for all client and server traffic.
RCS delivery is integrated with the Google RCS Business Messaging ecosystem and is architected for deployment across major U.S. carrier networks.
MessageOS.ai processes two categories of data on behalf of business clients: (a) conversation content exchanged between an end user and a client's verified RCS agent, and (b) operational metadata such as event timestamps, delivery status, and attribution tokens.
Client and end-user data is processed to deliver the messaging service. For the full description of collection, use, and retention, see our Privacy Policy.
MessageOS.ai relies on a limited set of vetted subprocessors for hosting, database, email delivery, and AI inference. A current subprocessor list is available on request for prospective and existing enterprise clients.
Request the list: security@messageos.ai
Retention windows are defined per data category and documented in the Privacy Policy. End users may exercise access, correction, and deletion rights by contacting us directly.
Privacy requests: privacy@messageos.ai
We welcome responsible disclosure. If you believe you've found a security issue in the MessageOS.ai platform, please email us with a clear description, reproduction steps, and any supporting evidence. Please do not test against production data belonging to third parties.
Security contact: security@messageos.ai
MessageOS.ai secures the platform, the hosting environment, and the Ezra agent runtime. Business clients are responsible for the accuracy of the messaging content they configure, obtaining appropriate consent from the end users they message, and managing their own users, credentials, and integrations. End users are responsible for the security of their own devices and messaging accounts.
MessageOS.ai builds toward the security expectations of the Google RCS Business Messaging ecosystem and U.S. carrier partners. For DPAs, security questionnaires, or specific compliance documentation required for a procurement review, contact security@messageos.ai.