Privacy Policy
This Privacy Policy describes what personal data Mossmoon collects when you use our website, dashboard, and API, why we collect it, who we share it with, and the choices you have. It applies to our always-on WhatsApp lines, the API, the dashboard, and the website at mossmoon.app.
At a glance
- We collect what we need to run the Services: account info, billing details (your full card number goes to our payment processor, never to us), usage and activity logs, and the content that passes through the API because of your use of it.
- We do not sell personal data, and we do not use the content that flows through our APIs to advertise to anyone.
- For WhatsApp message content and contacts, Mossmoon acts as a processor on behalf of the customer using the API; the customer is the controller.
- You can ask us to access, export, correct, or delete your data. See Your rights.
- Questions: [email protected].
Who this applies to
This Policy covers three groups of people whose data we may process:
- Account holders: the developers, agencies, and businesses with a Mossmoon account.
- End-Customers of WhatsApp Lines: individuals whose WhatsApp account is linked to a line that our customer provisioned (for example, an agency's client). Their phone number, profile name, and message content flow through the line on the customer's instructions.
- Message recipients and contacts: people who exchange messages with an End-Customer through a line, or who appear in the End-Customer's WhatsApp contacts.
- Website visitors: anyone who visits
mossmoon.app, whether or not they have an account.
Our role
Whether Mossmoon is the “data controller” or “data processor” (terms used in GDPR and similar laws) depends on the data:
| Data category | Mossmoon's role |
|---|---|
| Your account, login, billing, support correspondence, website and dashboard activity, telemetry of how you use the Services | Controller |
| WhatsApp message content, media, recipient phone numbers, contacts and profile details that pass through a WhatsApp Line you provisioned | Processor (you are the controller; the End-Customer and their contacts are the data subjects) |
| Operational logs (request metadata, IP addresses, timestamps, error traces) | Controller |
When we act as a processor, we only process data on documented instructions from you (the controller), as set out in these Terms, our API, and your configuration.
What we collect
You give us directly
- Account data: email address and password (stored only in hashed form by our authentication provider).
- Payment data: when you save a card or top up, you enter card details directly with our payment processor, Square. We never receive your full card number. We keep a Square customer ID and card token, the card brand, last four digits, expiry month and year, and transaction IDs, and we share your email address with Square.
- Support and sales correspondence: when you email us or use our contact-sales form, we keep your name, email address, and the content of your messages.
- Configuration: webhook URLs and secrets, line settings, logos you upload, credentials for integrations you connect (such as a GoHighLevel token, stored encrypted), and opaque identifiers you supply (e.g.
agency_external_user_id).
We collect automatically when you use the Services
- Website and dashboard activity: pages you view, links and buttons you click (including their text), time on page, scroll depth, the referring page, and campaign (UTM) parameters. We collect this for all visitors using a first-party cookie. If you later sign in, we link the activity from that browser to your account.
- API usage: each authenticated API request, including the endpoint, time, response code, and user-agent, linked to your account.
- Device and network data: IP address, user-agent string, and approximate location derived from IP (city, region, country).
- Cookies and similar storage: see Cookies.
We process on your behalf
- WhatsApp message content (text and media), sender and recipient phone numbers, delivery and read receipts, and group membership events.
- End-Customer details: the phone number and profile name of the End-Customer's WhatsApp account, any phone number you supply for the line, and the End-Customer's IP address when they open the connect page (used to route their line through their region).
- Contacts: the End-Customer's WhatsApp contacts and the public profile details WhatsApp exposes for people they message (name, “about” text, business profile, profile picture).
Why we use it
- To operate the Services: authenticate requests, keep WhatsApp Lines connected, route each line through its region, deliver webhooks, and sync with integrations you connect.
- To bill you: apply prices, run charges through the payment processor, maintain financial records.
- To support you: respond to inquiries, debug issues, and send service emails about your account (for example onboarding help, trial and billing notices, and line alerts).
- To keep the Services safe: detect and prevent fraud, abuse, spam, and security incidents; enforce our acceptable-use rules; protect users.
- To improve the product: analyze how visitors and customers use the website, dashboard, and API, including per-account activity, to understand where people get stuck and make Mossmoon better.
- To comply with the law: respond to legal process, prevent harm, exercise or defend legal claims.
We do not use the content of WhatsApp messages to train AI models, target advertising, or sell to anyone. We don't send bulk marketing email; if we ever do, we'll ask for your consent first and include an unsubscribe link. The one follow-up email we may send after signup (asking whether you need help connecting a line) has an unsubscribe link, and unsubscribing stops it and any similar email. Emails about your account, billing and lines are not marketing and keep coming.
We keep a record of the emails we send you. Outside the EEA, the UK and Switzerland, our emails also contain a tiny image that tells us when an email is opened, so we can see whether important notices (a failed payment, a disconnected line) reach you. We don't do this for recipients in those regions, or when we don't know where you are. Blocking images in your email app stops it.
Legal bases (GDPR)
If you are in the European Economic Area, United Kingdom, or Switzerland, we rely on the following legal bases under the GDPR:
| Purpose | Legal basis |
|---|---|
| Providing the Services to a customer, billing, support | Performance of a contract (Art. 6(1)(b)) |
| Security, abuse prevention, first-party website and product analytics, onboarding emails, business records | Legitimate interests (Art. 6(1)(f)) |
| Complying with applicable law, responding to legal process | Legal obligation (Art. 6(1)(c)) |
| Marketing emails, and anything else we say is consent-based | Consent (Art. 6(1)(a)), withdrawable at any time |
WhatsApp Line specifics
When you provision a WhatsApp Line for an End-Customer, we host a persistent connection to WhatsApp on their account so that inbound messages can be forwarded to your webhook and outbound messages can be sent through the API. To do that, we process:
- The End-Customer's WhatsApp phone number and profile name;
- Connection credentials used to keep the line authorized (stored on our servers; never exposed to you or any other party);
- Inbound and outbound message content and media, sender and recipient phone numbers, contact names and profile details as resolved by WhatsApp, and delivery / read acknowledgments.
The End-Customer's WhatsApp remains primary on their phone. They can disconnect the connection at any time from WhatsApp on their phone (Linked devices). A disconnected line stops processing messages until the End-Customer links it again, and is released automatically if it stays disconnected for more than 7 days during a paid month, or more than 24 hours otherwise (during a free trial or while a payment is failing).
When a line is released (by you, automatically, or by us), we log the connection out of WhatsApp, delete its connection credentials (with a weekly cleanup as a backstop), and stop processing new messages for that line. Message history and billing records for the line are retained as described in Retention.
Data retention
We keep personal data only as long as needed for the purposes we collected it for, or as required by law. Indicative periods:
| Data | How long |
|---|---|
| Account record | While the account exists. Deleted when you close your account, except records we must keep by law. |
| Billing records (top-ups, charges, tax records) | Up to 7 years, as required by financial / tax law. |
| WhatsApp message text, contacts, and profile details | While your account is active, so you can retrieve message history through the API. Deleted when you close your account or ask us to delete it. |
| WhatsApp message media (images, audio, files) | 30 days from receipt, then deleted automatically. |
| Contact profile pictures | While the related line records exist. |
| WhatsApp connection credentials | Only while the line is active; deleted when the line is released. |
| Webhook delivery logs (including payloads) | 90 days, then deleted automatically. |
| Website, dashboard, and API activity logs | 180 days, then deleted automatically. |
| End-Customer IP lookups from the connect page | While the account exists. |
| Records from our discontinued SMS number service | Kept with billing records. |
| Support and sales correspondence | As long as needed to help you and keep a record of our dealings, then deleted. |
| Security / abuse investigation records | As long as needed to investigate, prevent recurrence, and meet legal obligations. |
You can request earlier deletion as described in Your rights, subject to retention we're legally required to maintain.
Security
We implement reasonable and appropriate administrative, technical, and organizational measures to protect personal data, including encryption in transit (TLS), encryption at rest provided by our database and storage providers, hashed passwords, encryption of third-party integration tokens, database access controls, access to production data limited to a small number of named staff, and audit logging when staff view message content. API Keys are kept retrievable so you can view them in the dashboard.
No system is perfectly secure. You play a part too: protect your account credentials, rotate API Keys if you suspect compromise, and notify us at [email protected] if you discover a vulnerability or believe an incident has occurred.
International data transfers
Mossmoon is operated from the United States. Our application runs in the United States, our WhatsApp line servers run in Germany, and our service providers may also process data in the European Union, the United Kingdom, and other countries. Each line's traffic is routed through a network address in the line's own region. Where we transfer personal data from the EEA, UK, or Switzerland to a country that doesn't have an adequacy decision, we rely on appropriate safeguards such as the European Commission's Standard Contractual Clauses (and the UK addendum where applicable), along with supplementary measures as needed.
Your rights
Depending on where you live, you may have rights to:
- Know what personal data we hold about you and get a copy;
- Correct inaccurate or incomplete data;
- Delete personal data (subject to retention we're required to keep);
- Restrict or object to certain processing;
- Receive your data in a portable, machine-readable format and, where technically feasible, have it transmitted to another provider;
- Withdraw consent where we relied on consent;
- Lodge a complaint with your local data protection authority.
For data we process as a processor on a customer's behalf (WhatsApp messages and contacts), please contact the customer first; we'll support them in responding to your request. For everything else, including closing your account and deleting your data, email [email protected]. We handle these requests by email rather than in the dashboard, and we respond within 30 days. We may need to verify your identity before acting.
California (CCPA / CPRA)
If you are a California resident, the categories of personal information we collect, the purposes for which we collect each category, and the categories of third parties with whom we share each category are described in What we collect, Why we use it, and Who we share with.
We do not sell personal information and we do not share personal information for cross-context behavioral advertising as those terms are defined under the CCPA / CPRA. We do not knowingly collect sensitive personal information for the purpose of inferring characteristics about a consumer.
You may exercise your rights to know, delete, correct, and limit the use of sensitive personal information by contacting [email protected]. We will not discriminate against you for exercising your rights.
Children
The Services are not directed to children under 18 (or the age of digital consent in your jurisdiction, whichever is higher). We do not knowingly collect personal data from children. If you believe a child has provided us personal data, contact [email protected] and we will delete it.
Changes to this Policy
We may update this Privacy Policy from time to time. When we make material changes, we'll update the Effective Date at the top and, where reasonable, provide additional notice (for example, an in-product banner or an email to the address on your account). Continued use of the Services after a change takes effect means you accept the updated Policy.
Contact
Privacy questions and security disclosures: [email protected]. General support: [email protected].