Information LensMail accesses
After sign-in, LensMail may access Microsoft account profile information and Outlook message metadata, message bodies, recipients, folders, attachment names and sizes, Focused Inbox classification, read state, follow-up flags, conversation identifiers, and drafts required for the feature the user chooses. Attachment content is not downloaded or edited by LensMail.
Delegated permissions are openid, profile, offline_access, User.Read, Mail.ReadWrite, and Mail.Send.
Optional contacts and My LensMail
Updated October 17, 2026 for the 3.0.1 submission candidate. 3.0.0 remains the public Hub release until the update is approved. In 3.0.1, users can save reply titles/text/categories/favorites, local contact names/email addresses/favorites, and an optional signature on their device. These are not automatically uploaded to Outlook or a LensMail service.
Outlook contact access is optional and separate from email. Viewing requests delegated Contacts.Read; explicitly enabled editing requests Contacts.ReadWrite. That Microsoft permission also allows deletion, although LensMail does not offer Outlook contact deletion. LensMail accesses the personal default Contacts folder, showing contact names and email addresses for recipient selection. Contacts without email addresses are omitted. Other contact folders, the company-wide directory, and the phone's address book are not requested.
Contact results stay in the running interface unless the user chooses Keep locally. Only an explicit Save to Outlook creates or updates a Microsoft contact. Existing secondary email addresses and other contact fields are preserved. Declining contact consent does not disconnect email or prevent local contacts. Optional contact access and refresh tokens are stored separately from working email sign-in, scoped to the account and connection.
How information is used
Mailbox information is used only to display and manage the signed-in user's Outlook mailbox. User-requested reading, organization, draft editing, and explicitly confirmed sending are sent directly to Microsoft Graph. Save to Drafts does not send. Review & Send displays the saved draft and requires a separate affirmative confirmation. Contact information is used for the contact and recipient actions the user chooses. LensMail does not sell personal information, use mailbox or contact content for advertising, or train AI models with that content.
Storage and data flow
The public Client ID, tenant selection, access token, refresh token, and account label are stored in the installed app's local Even Hub/WebView storage. LensMail also stores user-saved personal phrases and hashed draft-ID send-attempt records locally, scoped to the signed-in account. Saved phrases contain the text the user deliberately saves; send-attempt records help avoid duplicate sends and do not store the email body. LensMail does not ask for a Microsoft client secret. Other mail content is held only as needed in the running interface; LensMail has no application database or developer-operated mail backend.
Microsoft sign-in uses static pages at https://auth.lensmail.net. LensMail sends short-lived PKCE context to the start page in a URL fragment, which is not transmitted to the hosting server. The start page holds it in tab-scoped session storage and gives Microsoft only a random state value. The callback exchanges Microsoft's authorization code in the user's browser, clears the temporary state, and returns the result to the local app. The host has no persistent token store.
Optional website analytics
The public pages at lensmail.net use Google Analytics 4 only after a visitor selects Allow analytics. If permission is granted, Google Analytics may process the page URL and title, referring page, browser and device information, approximate location derived from the network address, and ordinary page-view or interaction data. LensMail does not provide Google Analytics with mailbox content, Microsoft account details, authorization codes, access or refresh tokens, typed setup values, or a LensMail user identifier.
Analytics is not loaded on auth.lensmail.net, so the Microsoft sign-in start and callback pages are outside this measurement. Google Signals, advertising storage, ad personalization, and user-provided data collection are disabled. LensMail uses measurement ID G-N8DF75RR1W.
The choice is stored in the browser's local storage. When analytics is allowed, Google Analytics may set first-party cookies such as _ga. A visitor can continue using every public page after choosing No thanks, can reopen Analytics settings at any time, and can withdraw permission; LensMail then disables analytics and attempts to remove its analytics cookies. Browser Global Privacy Control or Do Not Track signals keep analytics off. Previously collected aggregate records may remain subject to Google Analytics retention and deletion controls.
Voluntary project support
The LensMail website links to Eddie Rivera's Buy Me a Coffee page for optional contributions. The button artwork is hosted by LensMail, so viewing a LensMail page does not contact Buy Me a Coffee. Buy Me a Coffee receives information only after a visitor deliberately follows the external link and then processes any payment under its own privacy policy and terms. LensMail and Wevem MSP do not collect or store payment-card information. Information a supporter chooses to provide through Buy Me a Coffee, together with contribution records made available to the page owner, is handled through that service. Contributions do not affect app features or support eligibility.
External services and security
The installed LensMail app uses the declared Microsoft identity, Microsoft Graph, and LensMail callback origins, and can open the public setup guide at lensmail.net. The product site's optional website analytics are not included in the installed app or callback. It uses Authorization Code with PKCE, validates OAuth state, limits callback age, and restricts callback returns to local LensMail origins. Microsoft and Even Realities process information under their own terms. Google processes consented public-site analytics under its Privacy Policy. Use of LensMail is also governed by the LensMail Terms of Service.
User choices and deletion
Users can clear Graph setup and locally stored sign-in information in LensMail, uninstall the app, and revoke consent through Microsoft. Personal phrases can be edited or cleared in the companion phrase list. Clearing sign-in removes cached authentication and the running mailbox view; saved phrases and send-safety records are separate account-scoped local records and may remain until cleared through the app or platform storage controls. Removing local records does not undo a sent, moved, or deleted message. Mailbox actions already completed remain subject to Microsoft and organizational retention policies. Website visitors can change their separate analytics choice with the Analytics settings control displayed on public LensMail pages.
Saved items, devices, and permission removal
In 3.0.1, saved replies, local contacts, and signature preferences are scoped to the current account, tenant, and Client ID in local Even Hub/WebView storage. They are not cross-device sync or a cloud backup. Users can edit or remove saved replies and local contacts and clear or disable a signature in My LensMail. The old personal-phrase record is retained during migration for rollback. Signing out or disconnecting contacts does not delete the saved library. App/platform storage controls or uninstalling may remove local data, depending on the platform's behavior; keep irreplaceable text elsewhere. Local app storage is not a promise of hardware-backed encryption and depends on the security of the phone and Even platform.
Disconnect contacts clears the optional local contact connection, not Microsoft's consent record. Users can revoke Microsoft consent through account permissions or their administrator. An Outlook contact already saved remains in Microsoft until changed there; removing a local copy does not delete it. The 3.0.1 saved-library controls replace the older phrase-list management interface.
Children and changes
LensMail is intended for Microsoft 365 account holders and is not directed to children under 13. Material policy changes will appear on this page with a revised effective date.
Contact
Privacy, feedback, and support inquiries: support@lensmail.net.