Security
Careful with what
you trust us with.
Your conversations hold your customers’ details. Here is how Mossbird is built to look after them.
Runs on Cloudflare
Mossbird runs on Cloudflare Workers, with data in Cloudflare D1 and files in Cloudflare R2.
Passwords are hashed
Passwords are hashed with PBKDF2 before they are stored. We never keep them in plain text.
HttpOnly sessions
Sign-in sessions live in HttpOnly cookies, which scripts running in the page cannot read.
Private file storage
Attachments are stored privately. Downloads go through signed links that expire.
AI takes only approved actions
The AI agent can only run the actions you approve, within the limits you set. Every step it takes is logged for your team to review.
Signed requests to your app
When an approved action calls your webhook, the request is signed with your workspace’s secret, so your app can check it came from Mossbird.
Audit log on Forest
Mossbird records administrative actions, such as who changed settings, deleted data or accepted charges. On Forest, admins can review that audit log in Settings.
Payments through Stripe
Checkout and the billing portal are hosted by Stripe; card details are entered on Stripe’s pages.
Compliance
Mossbird doesn't hold its own SOC 2 or ISO 27001 certification yet. It runs on Cloudflare, and payments are handled by Stripe; both maintain their own certifications, including SOC 2 Type II, and Stripe is certified to PCI DSS Level 1, so card details never touch Mossbird.
Report a security issue
Email support@mossbird.io. We'll confirm we've received it and keep you posted.
Data location, retention and deletion, and the providers we use, are in our Privacy policy. Questions in the meantime? Get in touch.