MsgMesh Privacy Policy

Effective date: 2026-07-25 · Last updated: 2026-09-13 (Public Beta)

MsgMesh ("the Service") is a hosted, multi-tenant persistent event bus built on Kafka and remains in public beta.

This Policy explains what personal data we collect, how it is used and protected, and your rights. Questions may be sent to [email protected].

1.What Data We Collect

We collect only the data necessary to provide and operate the Service:

  • Account data: your email and hashed password, or identity data returned by Google or Telegram when you choose third-party sign-in.
  • Service data: messages and event content, topics, hashed API keys, and usage metering such as message, delivery, operation, and byte counts.
  • Billing data: plan and subscription status, payment-provider customer/order/subscription identifiers, prepaid balance, and ledger entries. Polar processes full payment-card details; our servers do not store full card numbers.
  • Analytics data: privacy-first self-hosted Matomo data, including a pseudonymous tenant ID after sign-in.
  • Technical logs: standard logs that may include IP addresses and timestamps for security and operations.

2.How We Use Your Data

We use the data described above to provide and operate the Service; enforce quotas; calculate explicitly enabled overage; maintain prepaid balance; manage subscriptions, payments, and refunds; send verification and service notices; secure and improve the Service.

Signed-out analytics are anonymous and cookie-free. Signed-in analytics use a pseudonymous tenant ID for product-funnel analysis; we do not use it for advertising or cross-site tracking.

We do not use message and event content beyond operating and securing the Service, and do not sell personal data for advertising. For third-party personal data in your content, we process it on your instructions solely to deliver and retain it; you remain responsible for a lawful basis.

3.Third Parties and Data Processors

We use third parties only as needed to operate the Service:

  • Resend: account verification and notification email.
  • Google / Telegram: identity verification when you choose third-party sign-in.
  • Cloudflare: CDN, DNS, edge networking, and offsite backup storage.
  • Sentry: error tracking.
  • Polar: as Merchant of Record, processes subscription and top-up checkout, card details, tax, receipts/invoices, and refunds. It receives email, billing, and order data needed for a transaction. We retain Polar customer/order/subscription identifiers and billing outcomes, not full card numbers.

Except as described above, where required by law, or to protect the legitimate rights of the Service and users, we do not share personal data with other third parties.

4.Cookies and Analytics

We care about your privacy. Our website analytics use a self-hosted Matomo instance, deliberately configured with privacy-first settings:

  • No tracking cookies for analytics: our website analytics do not place tracking cookies on your device.
  • IP anonymization: IP addresses recorded for analytics are anonymized.
  • Respecting Do Not Track (DNT): if your browser sends a DNT signal, our analytics will not track you.

However, the Service may use cookies or similar technologies that are strictly necessary for features such as keeping you signed in (for example, session cookies). Such strictly necessary cookies exist only to provide the Service and are not used for cross-site tracking or advertising.

5.Data Retention

We retain data only as needed for the purposes in this Policy. Free retains messages for 3 days; Paid retains them for 30 days, after which they are deleted automatically. Account and billing data is retained for the life of the account and as needed for legal, tax, refund, dispute, and security obligations; data no longer needed is deleted or anonymized. Technical logs are kept for a reasonable security and operations period.

During beta we may reset test-environment data, so do not keep your only or critical copy on the Service.

6.Where Your Data Is Stored

Your personal data and service data are primarily stored and processed in Taiwan. However, when you use third-party sign-in, when we send you emails, or when traffic is proxied through an edge network, limited related data (such as your email address) may be processed outside Taiwan by Resend, Google, Telegram, or Cloudflare, subject to their respective privacy policies. In addition, two categories of data are stored outside Taiwan on an ongoing basis: (1) daily database backups uploaded to Cloudflare R2 object storage, containing your email address and your hashed password and API keys — encrypted in transit but not separately encrypted at rest; and (2) system error reports sent to Sentry (United States). Neither offers a choice of region; if other cross-border transfers become necessary for operational reasons in the future, we will update this Policy and take appropriate safeguards.

7.Your Rights and How to Exercise Them

You may request access, correction, deletion, or deletion of your account by emailing [email protected]. We may verify your identity first, and may retain data required for legal, billing, refund, dispute, security, or operational obligations.

Accepted account-deletion requests deactivate the account immediately; data not requiring retention is permanently deleted or anonymized after 30 days. You may request restoration during that period; after it, deletion is irreversible.

8.Data Security

We take reasonable technical and organizational measures to protect your data, including:

  • encrypting data in transit using TLS;
  • storing passwords hashed with argon2id and API keys in hashed form, never in plaintext;
  • applying necessary access controls and monitoring to our systems.

Please note that no method of transmission over the Internet or method of storage is completely secure. The Service is currently in beta, and we cannot provide any absolute guarantee of data security or service availability. Please keep your account credentials safe and avoid storing your only or highly sensitive data on the Service.

9.Important Public Beta Notice

The Service remains in public beta and is provided as-is, with no SLA or guarantee of availability. We may reset test-environment data, so do not store your only or critical copy here. Free remains free; Paid and top-ups accept payment. We will make reasonable efforts to give advance notice of changes to plans, beta billing rules, or retention periods.

10.Children

The Service is designed for developers and teams and is not directed at children. We do not knowingly collect personal data from children or anyone below the applicable age of consent. If you believe a minor submitted data without appropriate consent, email [email protected].

11.Governing Law, Jurisdiction, and Severability

This Policy, and any dispute arising out of the Service or this Policy, is governed by the laws of the Republic of China (Taiwan), with the courts of Taiwan as the competent forum. If any provision of this Policy is held to be invalid or unenforceable by a court of competent jurisdiction, the remaining provisions shall remain in full force and effect, and the affected provision shall be interpreted, to the extent permitted by law, in a manner that most closely reflects its original intent. We strive to follow applicable personal-data protection principles; however, this Policy does not constitute a claim of certification under any particular regulation.

12.Changes to This Policy

As the Service evolves—particularly during beta—we may revise this Policy from time to time. For material changes, we will post a notice on our website (msgmesh.alderflux.com) or notify you by other appropriate means. The revised Policy takes effect on the effective date stated in the notice; your continued use of the Service after the change takes effect constitutes acceptance of the revised Policy.

13.Contact Us

For questions about this Policy, personal data, or your rights, email [email protected]. We will respond within a reasonable time.

This document reflects MsgMesh's policy during public beta and may be updated as the Service evolves; changes will be posted on this page. In case of any discrepancy between the Chinese and English versions, the Chinese version prevails.