MsgMesh Privacy Policy

We collect data to provide and operate the Service, analyze traffic, and measure advertising performance:

• Account data: your email and hashed password, or identity data returned by Google or Telegram when you choose third-party sign-in. The Telegram ID and username are used to verify your identity; for accounts signed in with Telegram, we also use that ID as the recipient for verification codes and service notices.
• 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.
• Advertising measurement data: The website and the panel’s Plan and Billing pages use a Google Ads tag that may send visited pages, ad click identifiers, IP addresses, and browser or device information to Google to measure advertising performance. When you return to the panel after successful payment, we also send the checkout’s transaction identifier, amount, and currency to measure purchase conversions; this does not include your email, tenant ID, or message content.
• Technical logs: standard logs that may include IP addresses and timestamps for security and operations.

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. Accounts signed in with Telegram have no email address, so verification codes and service notices are sent via Telegram instead.

We also use the Google Ads tag to measure ad-driven website visits, interactions, and purchase conversions.

Signed-out Matomo analytics are anonymous and cookie-free. Signed-in Matomo 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.

We use the following third parties to operate the Service and measure advertising performance:

• Resend: account verification and notification email.
• Google / Telegram: identity verification when you choose third-party sign-in. When a new account is created, we attempt to send a registration notice to the operator’s Telegram: email for email or Google sign-up, or a Telegram sign-in identifier when a new Telegram account has no email. Delivered notification copies are not automatically removed by the Service’s account-deletion process. For accounts signed in with Telegram, we send you verification codes and service notices (such as usage reminders) through the Telegram bot (@alderflux_bot). Message content (which may include usage figures, plan and billing status, and the topic names and webhook URLs you configure) is sent to and stored by Telegram, remaining in your conversation with the bot; we do not retract or delete messages already sent. Delivery is on a best-effort basis and is not guaranteed.
• Google Ads: The website and the panel’s Plan and Billing pages load a Google tag to measure advertising performance. It may use advertising cookies and send website visit, ad click, device-related data, and purchase conversion data (transaction identifier, amount, and currency) to Google. See How Google uses information from partner sites or apps and Google’s Privacy Policy.
• 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.

Our self-hosted Matomo analytics uses the privacy settings below. These settings apply only to Matomo, not to the Google Ads tag described below:

• No Matomo tracking cookies: Matomo analytics does not place tracking cookies on your device.
• IP anonymization: IP addresses recorded by Matomo are anonymized.
• Do Not Track (DNT): Matomo does not track visits when your browser sends a DNT signal.

The website and the panel’s Plan and Billing pages also use a Google Ads tag (gtag.js) to measure advertising performance and purchase conversions. The Google tag may read or write advertising cookies to record ad clicks and subsequent visits; Google’s policies govern its processing and retention of data. You can block or clear cookies in your browser settings and manage advertising preferences in Google My Ad Center. Matomo’s cookie-free, IP anonymization, and DNT settings do not automatically apply to the Google tag.

The Service may also use essential cookies or similar technologies to maintain sign-in sessions. These essential cookies are used only to provide the Service, not for cross-site tracking or advertising.

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. Database backups are kept on the Service host for approximately 14 days. Copies uploaded to Cloudflare R2 are configured for automatic deletion 90 days after creation; actual cleanup may be slightly delayed. 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.

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, verification codes and service notices via Telegram, or registration notices, or when traffic is proxied through an edge network, limited related data (such as your email address, Telegram sign-in identifier, or notification content) may be processed outside Taiwan by Resend, Google, Telegram, or Cloudflare, subject to their respective privacy policies. The Google Ads tag may also transfer website visit, ad click, device-related data, and purchase conversion data outside Taiwan for Google to process and retain under its policies. In addition, two categories of data are stored outside Taiwan on an ongoing basis: (1) database backups uploaded to Cloudflare R2 object storage by a daily scheduled job, 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). Messages sent to you via Telegram are also stored by Telegram (see Section 3); their retention period is not controlled by the Service. 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.

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, or security 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.

Database backups created before deletion may still contain your data. As described in Section 5, they are configured for automatic deletion 90 days after creation; actual cleanup may be slightly delayed. The Telegram registration notice described in Section 3 and messages already sent to you via Telegram are also not automatically removed by the account-deletion process.

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.

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.

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].

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.

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.

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