1. Scope and purpose
MossMail Windows Local is an email-to-OTP tool that lets an owner review messages from mailboxes they are authorized to manage and identify verification codes. The G1 website introduces MossMail and provides public product and privacy information; it is not a Web mailbox service.
The G1 website serves informational pages at only /, /privacy, and /styles.css. It has no signup or account forms, cookies, Web login or session, OAuth callbacks, mailbox APIs, Cloud Vault, or email/OTP processing. It contains no analytics or third-party scripts.
2. Windows edition
The Windows Local edition connects to Gmail through the Gmail API and to Outlook/Hotmail through Microsoft Graph. At the user's request, it reads messages from the connected mailbox and processes their content on the user's PC to display mail and identify OTPs. Provider credentials are handled by the Windows application and its local backend. Saved account metadata and OAuth credentials in the local Account Vault are protected using Windows DPAPI CurrentUser.
The Account Vault does not store message bodies or extracted OTPs. Windows Local processes requested message content on the PC; it does not send mail content to the MossMail Web service. The Windows Vault is separate from Web V1.
3. G1 public website
G1 is a public informational website introducing MossMail. It has no Web login, accounts, OAuth client or callback, mailbox connection or API, Cloud Vault, or mail/OTP processing. This describes the G1 website whether accessed as a local preview or after public deployment. The website itself does not request Google API data.
Railway HTTP/access logs: Railway documents HTTP/edge logs separately from application logs and describes request metadata that may be recorded. For any MossMail deployment, the actual fields collected, who can access logs, and retention depend on the active service configuration and Railway plan. This policy does not assert deployment-specific logging settings, access roles, or a retention period. See the Railway Logs documentation and HTTP logs reference.
4. Google API Services User Data
In Windows Local, the user-requested Gmail feature reads messages through the Gmail API so the app can display mail and identify OTPs. The G1 website makes no Google API requests. Google's API Services User Data Policy applies to data obtained through Google scopes. Its Limited Use requirements limit use to prominent user-facing features and restrict transfers and human access to specified circumstances.
Use, sharing, sale, and advertising: The Windows Local source reviewed sends Gmail OAuth and message-read requests to Google endpoints after user action; retrieved messages are returned to the local app for display and OTP identification. The inspected source does not forward Gmail message content to MossMail Web or an advertising/analytics service. No sale of Google user data or advertising use of Gmail data is implemented in the reviewed source. This source-code finding does not describe Google's own processing, other software on the device, or future MossMail versions.
The Windows Local Connect code reviewed requests https://www.googleapis.com/auth/gmail.readonly; the read path also accepts existing tokens with gmail.modify or https://mail.google.com/. The actual scope of a particular token depends on its grant. Google classifies gmail.readonly as a Restricted scope. Google's guidance describes verification requirements and a possible personal-use exception, and requires a security assessment for apps capable of accessing restricted-scope data from or through a third-party server. This policy does not claim that MossMail qualifies for an exception, that a particular token has a specific grant, or that a client has completed verification. The G1 website has no Google OAuth client. See Google's Gmail API scopes and restricted-scope verification guidance.
5. Retention, disconnect, and deletion
- Windows: saved OAuth credentials remain in the local DPAPI Account Vault until the owner removes them or deletes the Vault. Removing local credentials does not necessarily revoke provider-side OAuth consent; that can be managed in the Google or Microsoft account settings.
- G1 website: it has no Web accounts or mailbox features, so it does not create Web mailbox records or provide a mailbox-deletion workflow. Any platform logs are subject to the active service configuration and plan described above.
Any future Web mailbox release would need documented retention, deletion, and provider-consent handling before those features become available.
6. Contact
Privacy contact: haitt.tpl@gmail.com
This policy covers Windows Local and the G1 public informational website, whether viewed as a local preview or after deployment. It does not describe Web mailbox functionality.