Legal
Privacy policy
Effective · Mossbird is a product of Simplisik LLC
This policy explains how Simplisik LLC handles personal information in connection with Mossbird: the website at mossbird.io, the dashboard at app.mossbird.io, the Messenger and embeds served from cdn.mossbird.io, the help centers at help.mossbird.io, the email we receive and send for customers at mossbird.email, and the account email we send from mail.mossbird.io (together, the “Service”).
The short version. We collect what we need to run Mossbird and nothing for advertising. We don’t sell personal information, we don’t use our customers’ data to train AI models, and our website counts visits with Google Analytics, with its advertising features off. When a business uses Mossbird to talk with its own customers, that business decides what is collected and we handle it on their behalf. This summary doesn’t replace the full policy below.
1. Who we are
Mossbird is a product of Simplisik LLC (“Simplisik,” “we,” “us”), based in Nashville, Tennessee. You can reach us at privacy@mossbird.io or by mail:
Simplisik LLCAttn: Legal
5510 Old Hickory Blvd, Suite B #32
Hermitage, TN 37076
United States
2. Our two roles
We handle personal information in two different capacities, and it matters which one applies to you.
- When we decide how information is used (we are the “controller” or “business”). This covers people who sign up for or use the Mossbird dashboard, billing contacts, people who visit mossbird.io, and people who email us or chat with us through our own Messenger.
- When we act for our customers (we are the “processor” or “service provider”). Businesses that use Mossbird (“customers”) put information into their workspaces, and their own customers and website visitors (“end users”) send information through the Messenger, embeds, help center and email. We call all of this “Customer Data.” The customer decides what is collected and why, and the customer’s own privacy notice explains it. We process Customer Data only to provide the Service to that customer, under our Terms of service.
If you are an end user of a business that uses Mossbird, please contact that business about your information. If you contact us instead, we will pass your request to them where we can tell which business it concerns, and help them respond.
3. Information we collect
This section covers information we handle as a controller.
Account and workspace information
When you create a workspace or accept an invitation, we collect your name, email address and password, the workspace name and, if you give it, your website. We store your password only as a salted PBKDF2 hash, never in plain text. We set the workspace’s time zone from your network connection at sign-up. We also keep your role, team memberships, availability (online or away) and notification preferences, and the email addresses of people you invite. Your name, initials and availability can be shown to your workspace’s end users in the Messenger, and your name appears on emails you send through Mossbird.
Your account information may also include a profile photo, if you add one in Settings → General. We crop it to a square and store a small copy. It is shown to your teammates in the dashboard and, in the Messenger, to your workspace’s end users when the Messenger shows its team’s faces and on your replies. So that it can load on your workspace’s website, it is served from an address that is hard to guess but doesn’t need a sign-in: anyone who has that address can view it. We keep it until you remove or replace it, or delete your account (section 11).
Billing information
Payments are handled by Stripe. You enter card details, billing address and tax ID on Stripe’s pages, and we never see or store full card numbers. We receive and keep your Stripe customer and subscription identifiers, plan, billing period, subscription status and renewal dates, and we fetch invoices from Stripe to show them in your settings. If your workspace pays for extra AI conversations, we send Stripe each month’s count and amount so it can invoice them.
Usage, device and security information
When you sign in, we keep a session record with when it was created and last used and your browser’s user agent. We use IP addresses to rate-limit sign-up, sign-in, password resets and similar requests, and to protect the Service from abuse. The sign-up and password-reset forms may use Cloudflare Turnstile to check that a person, not a bot, is filling them in: Cloudflare processes your IP address and information about your browser to run the check, and we send it your IP address when we verify the result. To apply a customer’s per-visitor and per-network AI limits and spam blocks in the Messenger and its help search, we keep a keyed hash of each visitor’s IP address (never the address itself) and daily counts of their AI use. We keep an audit log of administrative actions, such as who changed settings, deleted or exported data or accepted charges for extra AI conversations, along with counts of AI usage and operational logs. Our hosting provider, Cloudflare, processes network and request data such as IP addresses to deliver and secure the Service.
Integrations you connect
- Slack: the Slack workspace and channel identifiers, the bot token (encrypted at rest), who installed the app, and the names and email addresses of Slack users, which we use to match them to Mossbird teammates.
- Microsoft Teams: the Teams tenant, team and channel identifiers and names, and the name and email address or user principal name of Teams users, used to match them to Mossbird teammates.
- Intercom import: an access token (encrypted at rest), the email address of the Intercom admin who connected it, and the names and email addresses of Intercom admins, used to match them to Mossbird teammates.
Communications
When you email us or chat with us through the Messenger on mossbird.io or in the dashboard, we keep the conversation, your contact details, and anything you choose to share. Our own Messenger works the way it does for our customers (section 4) and may be answered by our AI agent (section 5).
Our website
www.mossbird.io uses Google Analytics to count visits and see which pages are read, with Google’s advertising features turned off. Google receives the pages you view, your IP address and your browser and device information. In the European Economic Area, the United Kingdom and Switzerland it runs without cookies; elsewhere it sets Google Analytics cookies (section 10). You can opt out with Google’s opt-out browser add-on. The pages also load fonts from Google Fonts, so your browser connects to Google, which receives your IP address and browser information. Both are covered by Google’s privacy policy. The tour of the app on our homepage is an interactive demo made with AtriumKit, another Simplisik product, and loads from atriumkit.com. It counts views and the steps reached, with a random visitor identifier kept in the browser’s local storage, as described in the AtriumKit privacy policy.
4. Information in customer workspaces
So that end users can see how Mossbird works, this section describes the Customer Data the Service handles. We process it on our customers’ behalf, as described in section 2. If a customer’s plan lapses, messages from end users still arrive and are stored in the workspace, so nothing they send is lost.
The Messenger and embeds on a customer’s website or app
- Visitor information: a visitor token kept in the browser’s local storage (not a cookie), the pages viewed (address, title and referring page), browser, operating system and language, and an approximate location (city and country) that Cloudflare derives from the IP address. The IP address itself isn’t stored on the visitor’s profile.
- App errors: unless the customer turns it off, the Messenger reports uncaught errors on the page (the error message, the top of the stack trace and the page address), so the support team and AI can see what went wrong.
- What the customer’s app sends: a customer can identify signed-in users with details such as a user ID, name, email, phone number, job title, company and other attributes, and send events about what they do in the app.
- What end users send: messages, attachments, ratings, survey answers, contact form submissions, and an email address if they ask for replies by email.
- Identity checks: before the AI agent takes certain actions, it may ask an end user to confirm their identity with a six-digit code sent to their email address, or with a single-use link.
Customers forward their support address to Mossbird. We receive those emails, including headers, attachments and the original message file, and store them in the customer’s workspace. We remove tracking pixels from incoming email and block its remote images unless a teammate chooses to show them. We send replies, reply notifications and identity codes and links on the customer’s behalf.
Help centers
Help centers publish the customer’s articles. We count article views without tying them to individuals, and record “Was this helpful?” votes.
Imports
If a customer imports from Intercom, we copy what they choose: contacts and companies, conversations (with their attachments) from the period they pick, which is the last 24 months unless they choose up to 10 years, help center articles, saved replies, tags and teams.
5. AI features
Mossbird’s AI agent answers end users from the customer’s help articles, drafts and summarizes replies for teammates, answers help searches, and groups unanswered questions into article suggestions.
- What the AI sees. To answer a conversation, we send the AI model the recent messages in the conversation, the end user’s profile and company details, their recent events and app errors, the page they are on and their device, the most relevant help articles and internal AI notes, and the workspace’s AI settings.
- Who runs the model. Requests go through Cloudflare AI Gateway to our AI model provider, OpenAI. OpenAI processes them to generate a response, and we ask it not to store responses for later use. Under its API terms, OpenAI doesn’t use this data to train its models and keeps it only for a limited time, generally up to 30 days, to monitor for abuse. Our AI gateway logs only metadata about each request, such as the model, token counts and timing, never the content of messages.
- No training on Customer Data. We don’t use Customer Data to train AI models, ours or anyone else’s.
- Transparency. The AI appears under the bird mark, not a human face, and says it’s an AI when asked. Answers show the help articles they used, and every turn, with the steps the AI took, is logged for the customer’s team. An end user can ask for a person at any time, and the AI hands the conversation to the team.
- Approved actions. The AI can take actions such as a refund only when the customer has set that action up, within the limits the customer chose, and only for an end user whose identity has been confirmed. The customer’s own systems carry out the action. Questions about a decision should go to that business.
6. How we use information
We use the information we control to:
- create and run your account and workspace, and provide the features you use;
- authenticate you, keep the Service secure, and detect and prevent fraud, spam and abuse;
- process payments, manage subscriptions and keep financial records;
- send service email, such as email verification, password resets, invitations, usage alerts, billing notices, data export links, and notices to workspace owners about incidents, planned maintenance, new service providers and changes to our terms;
- answer your questions and provide support;
- understand how the Service is used, in aggregate, so we can fix problems and improve it;
- comply with the law and enforce our terms.
We use Customer Data only to provide the Service to the customer it belongs to, which includes delivering messages, running the AI agent and workflows, search and insights, security, troubleshooting and support, and as the law requires. We don’t sell personal information, share it for cross-context behavioral advertising, or use it for advertising of any kind. We don’t currently send marketing email. If we start, we will send it only as the law allows, and every message will include a way to unsubscribe.
7. Legal bases (EEA and UK)
If you are in the European Economic Area, the United Kingdom or Switzerland, we rely on these legal bases for information we control:
- Contract: to provide the Service you signed up for, including account, billing and support.
- Legitimate interests: to secure the Service and prevent abuse, to understand and improve the Service, to respond to people who contact us, and to run our business. We weigh these interests against your rights.
- Legal obligation: to keep tax and accounting records and respond to lawful requests.
- Consent: where we ask for it. You can withdraw consent at any time.
For Customer Data, the customer is responsible for having a legal basis.
8. How we share information
- Service providers that help us run Mossbird, listed in section 9. They may use the information only to provide their services to us.
- Within a workspace. Customer Data is visible to the customer’s teammates according to their roles.
- Integrations a customer turns on. When a customer connects Slack or Microsoft Teams, new conversations appear in the channels they choose as cards showing the end user’s name (or email address) and company, the subject and first message, and who is handling it. The assigned teammate gets a direct message, and teammates mentioned in an internal note get the note as a direct message. When a customer sets up webhooks or approved actions, we send the event or action details, including the end user’s identifiers, to the addresses the customer chooses. These services handle the data under their own terms.
- Legal reasons. When we believe in good faith that the law, a court order or a valid government request requires it, or that it’s needed to protect the rights, safety or property of our users, the public or us. Where the law allows, we will tell the customer before disclosing Customer Data.
- Business transfers. If Simplisik is involved in a merger, acquisition, financing or sale of assets, information may transfer as part of that deal, and this policy will continue to apply to it.
- With your permission, or at your direction.
9. Service providers
These are the providers that process personal information for Mossbird:
| Provider | What they do | Data involved | Location |
|---|---|---|---|
| Cloudflare, Inc. | Hosting, database, file storage, real-time messaging, email receiving and sending, AI gateway, network security | All account information and Customer Data | United States and Cloudflare’s global network |
| OpenAI, L.L.C. | AI model provider | Customer Data sent with AI requests (section 5) | United States |
| Stripe, Inc. | Payments, subscriptions and invoices for Mossbird plans | Billing contacts and payment details; no Customer Data | United States |
| Google LLC | Web fonts for our website, dashboard, help centers and, unless the customer turns it off, the Messenger; analytics for our website | IP address and browser information of anyone whose browser loads the fonts, including end users; pages viewed and device information on our website. We send Google no Customer Data | United States |
We will update this list, and email workspace owners at least 14 days in advance, before a new provider starts processing Customer Data.
Services a customer chooses to connect, such as Slack, Microsoft Teams and Intercom, and the webhook and action endpoints a customer sets up, aren’t our service providers. We exchange data with them only at that customer’s direction (section 8), and they handle it under their own terms with the customer.
10. Cookies and browser storage
- Dashboard (app.mossbird.io): one strictly necessary session cookie that keeps you signed in. Scripts can’t read it (it is HttpOnly), and it expires after 30 days without use. The dashboard also keeps a few preferences in your browser’s local storage. It runs our own Messenger, so you can reach us from inside the dashboard: it tells us your name, email address and the workspace you have open, and keeps a visitor token in local storage like any Messenger (below). Signing out clears that token.
- Messenger and embeds: no cookies of their own. A visitor token is kept in local storage so the visitor’s
conversations are still there on their next visit, along with which surveys, announcements and help articles
they’ve answered, dismissed or rated, and the address of the workspace’s launcher icon so it shows straight away.
Calling
Mossbird.shutdown(), for example when a user signs out, clears the token. - Our website: Google Analytics cookies (
_gaand_ga_<id>, kept for up to 2 years) that tell repeat visits apart. Visitors in the European Economic Area, the United Kingdom and Switzerland get none: there, Google Analytics runs without cookies. We set no other cookies on our website. The homepage tour (from atriumkit.com) sets no cookies; it keeps a random visitor identifier in local storage to count views.
Cloudflare, which hosts and protects all of these sites, including the Messenger’s script and API, may also set
strictly necessary security cookies of its own: __cf_bm, which helps tell people from bots and expires
after 30 minutes without activity, and cf_clearance, after a security check is passed. They’re used
only to keep the Service secure, not for analytics or advertising, and Cloudflare says it doesn’t use them to track
people from site to site.
We don’t use advertising cookies, and the dashboard, Messenger and help centers use no analytics. Customers who add the Messenger to their sites are responsible for any notice or consent their local law requires for it.
11. How long we keep information
We keep personal information only as long as we need it for the purposes above:
| Information | How long we keep it |
|---|---|
| Account information | While your account exists. When you delete it, or ask us to, we remove it from our live systems within 30 days. |
| Your profile photo | Until you remove it or delete your account; we then delete it from our storage right away. Replacing it deletes the earlier photo. Copies that a browser has already loaded may stay in that browser’s cache for a while. |
| Sign-in sessions | Until 30 days after last use; expired sessions are deleted daily. |
| Password reset and email verification links | Deleted once used or expired. |
| Invitations | Deleted when they expire, 7 days after they’re sent, whether or not they were accepted. |
| Rate-limit records, which can include IP addresses | About one day. |
| Messenger page views, events and app errors | 90 days. |
| Abuse-protection records for the AI agent: daily AI usage counts per visitor and per network, and keyed hashes of visitors’ IP addresses (never the address itself) | Hashed IP addresses about two days, or up to 30 days when a teammate blocks a visitor’s network as spam (until it’s unblocked); daily counts 40 days. |
| Anonymous Messenger visitors (leads with no email address, no conversations and no survey answers) | Deleted, with their page views and events, after 90 days without activity, unless a teammate has blocked them as spam. |
| Identity check codes and links | Codes expire after 10 minutes and links after 24 hours; the records are deleted after 7 days. |
| Slack and Teams teammate matching | Slack: refreshed after 7 days, and deleted when Slack is disconnected or the workspace is deleted. Teams: refreshed after a day of use; deleted as soon as no Mossbird workspace is connected to that Teams organization any more (the workspace is deleted, its Teams channels are disconnected, or the app is removed from the team), after 7 days if no workspace connects it, and otherwise after 30 days without use unless the person is a teammate in a connected workspace. Both are also deleted when the matched teammate deletes their Mossbird account. |
| AI gateway request logs | Metadata only (model, token counts, timing, workspace and conversation identifiers), never message content. Kept for monitoring and cost tracking, and replaced as newer logs arrive. |
| Other Customer Data (conversations, contacts, emails, attachments, articles) | For as long as the customer keeps it in their workspace. When a customer deletes contacts, conversations or the whole workspace, we remove them from our live systems, usually within hours and always within 30 days. After a subscription or trial ends (an unpaid subscription counts as ended 14 days after its first failed payment), we keep the workspace for 30 days so the customer can come back or export its data. We then email its owners that it will be deleted 7 days later, and delete it on that date or the day after unless the customer has chosen a plan by then. Forest workspaces are never deleted this way; their order form applies. An owner can delete a workspace at any time. |
| Data exports a customer downloads | Deleted 7 days after they’re ready, when the emailed download link stops working too. |
| Records of notices we email to workspace owners | Who we sent each notice to and when: 3 years, or until that person’s account is deleted. |
| Billing and tax records | As long as tax and accounting law requires, generally 7 years. |
| Messages you send us | As long as needed to help you and keep a record, generally up to 3 years. |
Deleted information can remain in backups for up to 30 more days before it is overwritten. We may keep information longer when the law requires it or to resolve disputes, and we may keep aggregated information that doesn’t identify anyone.
12. Security
We protect information with measures that fit its sensitivity: encryption in transit, passwords stored only as salted hashes, HttpOnly sessions, private file storage with download links that expire, integration tokens encrypted at rest, signed requests to customers’ webhooks, and access limited by workspace role. Our Security page has more detail. No system is perfectly secure. If a breach affects your information, we will notify you and, for Customer Data, the affected customer without undue delay and as the law requires.
13. International transfers
Simplisik is based in the United States, and the Service is operated from the United States and wherever our service providers operate, including Cloudflare’s global network. When we transfer personal information from the European Economic Area, the United Kingdom or Switzerland, we rely on appropriate safeguards such as the European Commission’s Standard Contractual Clauses and the UK Addendum, as described in our Terms.
14. Your rights and choices
Depending on where you live, you may have the right to:
- access the personal information we hold about you and get a copy of it in a portable format;
- correct inaccurate information;
- delete your information;
- object to or restrict certain processing;
- withdraw consent where we rely on it;
- complain to your data protection authority.
You can change your name, profile photo and password in your account settings, remove your photo, and delete your account in Settings → General. Workspace owners can delete the whole workspace there, owners and admins can export the workspace’s data there in a portable format (JSON), and admins can remove teammates and delete contacts and conversations. To exercise any other right, or if you can’t use these settings, email privacy@mossbird.io. We will confirm your identity, usually by asking you to write from the email address on the account, and respond within 30 days, or sooner if the law requires. We won’t treat you differently for exercising your rights.
If your information is Customer Data, please send your request to the business that uses Mossbird. They can delete your contact record and conversations from their dashboard and export their workspace’s data themselves, and we will help them with exports and other requests.
15. US state privacy rights
Residents of California and other states with privacy laws have the rights in section 14, along with these disclosures about information we control, covering the past 12 months:
- Categories we collect: identifiers (name, email address, IP address, account identifiers); commercial information (plan and purchase history); internet activity (how you use the Service); approximate location; professional information (job title, company); and account sign-in credentials.
- Sources: you, your organization, your browser or device, our service providers, and integrations you connect.
- Purposes: those in section 6.
- Disclosures: to the service providers in section 9, for the business purposes described there.
- No sale or sharing: we have not sold personal information or shared it for cross-context behavioral advertising, and we don’t knowingly do so for anyone under 16. Because we don’t sell or share, a Global Privacy Control signal doesn’t change how we handle your information.
- Sensitive information: we use account sign-in credentials only to let you sign in and keep your account secure.
You can make a request yourself or through an authorized agent, whom we may ask for proof of authority. If we decline your request, you can appeal by replying to our decision. If we deny your appeal, you may contact your state attorney general.
16. Children
Mossbird is a service for businesses. It isn’t directed to children, and we don’t knowingly collect personal information from children under 16. If you believe a child has given us personal information, contact us and we will delete it.
17. Changes to this policy
We will update this policy when our practices change, and change the effective date at the top. If a change is material, we will tell workspace owners by email or in the dashboard at least 14 days before it takes effect.
18. Contact us
Questions or requests about privacy: privacy@mossbird.io, or write to us at:
Simplisik LLCAttn: Legal
5510 Old Hickory Blvd, Suite B #32
Hermitage, TN 37076
United States
See also our Terms of service.