WatchMail Privacy Policy
Last updated: April 8, 2026. This policy is for general information and is not legal advice. Have your counsel review it before you rely on it commercially.
This policy describes how m23n (“we,” “us”) intends to handle information when you use WatchMail, our email experience for Apple Watch and Wear OS. WatchMail is under active development; features, data practices, and this policy may be updated before or after public release. By using WatchMail when it is available, you acknowledge the then-current version of this policy.
Email providers: WatchMail is designed to work with mailboxes hosted by third parties (for example Google, Microsoft, or your employer’s IT provider). Those providers’ privacy policies and terms apply to your account, message storage, and their servers. We do not replace or control your email provider’s systems.
1. Who we are
For privacy requests and questions, contact us at support@m23n.com.
2. Categories of information (anticipated)
The list below describes categories of information that may be involved depending on how WatchMail is implemented and which features you enable. Not all categories may apply in early releases.
2.1 Account & credentials
- Mailbox access: To read or send mail, WatchMail may need to store or refresh credentials, OAuth tokens, or app-specific passwords using secure storage on your devices (for example the system keychain). We aim to minimize what passes through our infrastructure.
- Identifiers: Device or installation identifiers may be used to associate your watch and phone, validate subscriptions, and support sync.
2.2 Message content & metadata
Depending on architecture, message bodies, headers, attachments metadata, and thread structure may be processed on your devices and, only where necessary for the feature you use, on servers we operate. We intend to favor on-device processing and short-lived server processing where feasible.
2.3 Phone ↔ watch sync
On Apple platforms, we may use Watch Connectivity (or similar) to sync account state, preferences, and data the app needs to show mail on your watch. On Android/Wear OS, comparable OS-level sync mechanisms may be used.
2.4 Push notifications
If you enable notifications, a device token for your platform’s push service (for example APNs or FCM) may be processed so we can notify you about new mail or important events you configure.
2.5 Purchases & subscriptions
If WatchMail offers in-app purchases, transaction and entitlement data may be processed by Apple, Google Play, and/or providers such as RevenueCat, according to their policies and only as needed to validate access.
2.6 Analytics & diagnostics
We may use analytics and crash reporting (for example Firebase Analytics and Crashlytics) to improve stability and understand aggregate usage, subject to platform rules and your device settings.
3. How we use information
- Provide WatchMail features you choose to enable
- Keep your watch and phone experience in sync when applicable
- Validate subscriptions and prevent abuse
- Improve the product, secure our systems, and fix bugs
- Comply with law and respond to lawful requests
4. Retention & deletion
We keep information only as long as needed for the purposes above or as required by law. When WatchMail is broadly available, we will describe practical deletion and export options in-product and update this policy as needed. Until then, contact support@m23n.com for questions about development builds.
5. Children
WatchMail is not directed to children. Do not use WatchMail in a way that violates your email provider’s rules or applicable child-privacy laws.
6. Changes
We may update this policy as WatchMail evolves. We will post the current version on this page and may provide additional notice for material changes (for example in the app or by email where appropriate).
7. Related policies
Our website and WristChat (Slack) are covered by a separate policy: Privacy Policy (WristChat & m23n.com).
TeleWatch (Telegram) is covered by: TeleWatch Privacy Policy.
