AetherMail Ultimate Privacy Policy
How AetherMail Ultimate by AL-JABAREEN handles email, account and license data. Last updated: 2026-10-22. This policy covers the current Windows version under development and testing.
Publisher and scope
AetherMail Ultimate is a desktop email client developed by AL-JABAREEN. This page covers email processing within the application, connections to email providers, and communication with Sentinel Pro for the application account, licensing and security. This policy does not imply that Google or Microsoft integration has received public-release approval; both integrations remain under preparation and validation. Product page: https://hub.aljabareen.com/aethermail-ultimate Contact and privacy requests: support@aljabareen.com. Do not include passwords, access tokens or recovery keys in support requests.
Data processed and its purposes
Mail account data includes the email address, display name and server settings, plus a mail password for password-based accounts or OAuth authorization tokens for supported accounts once enabled. The application uses these to connect to the account you choose to add. OAuth authorization takes place with the provider; the application does not ask you to enter a Google or Microsoft password in its own form. Message data includes senders, recipients, subjects, message contents, attachments, drafts and outbox state. It is processed to provide the reading, receiving, local search and sending functions you request. Application account and licensing data includes registration and sign-in data, a device identifier, activation details and entitlement status. It is sent to Sentinel Pro to authenticate the user, validate licensing and apply security policies. The application account is separate from added email accounts.
Storage, protection and recipients
Messages, settings, drafts and the outbox are stored locally in the application's data files on your Windows device. The current message database is not fully encrypted; protecting the Windows account, disk and backups matters. Mail credentials and authorization tokens are kept in a separate vault encrypted using available Windows protection, rather than storing passwords in the interface's localStorage. Credential encryption does not mean the entire message database is encrypted. Mail engines connect directly to the selected provider using supported encrypted connections. Sending transfers the message and attachments to the mail provider and recipients you select as part of the sending function. Mailbox contents and mailbox passwords are not sent to Sentinel Pro as part of application license validation. Google, Microsoft, Hostinger or your custom provider process data under their own policies and account terms. Copies of messages may remain on provider servers, with recipients and in backups you create.
Google data and Limited Use
When Google integration is made available, use and transfer of Google account data are limited to authorized, user-facing functions and must comply with the Google API Services User Data Policy and its Limited Use requirements. We do not sell users' email data or use it for advertising or training general-purpose AI models. The current mail engine does not send Gmail contents to an AI service. Review the permissions shown by Google before authorizing access. Publishing this policy alone does not establish approval: the integration and its scopes must complete the applicable Google review before we advertise general commercial availability.
Retention, revocation and deletion
Local data remains in the application's data directory until removed locally. Removing an account in the interface or uninstalling the application is not a guarantee that every message, credential and backup is erased. For complete local-removal guidance or requests concerning application-account data held by Sentinel Pro, contact support@aljabareen.com; account ownership verification may be needed. Support does not remotely erase messages on your device without a clear action from you. OAuth authorization can be revoked in your Google or Microsoft account settings. Revocation stops the application's access but does not automatically erase previous local copies or recipients' messages. Deleting provider-held messages is governed by the provider's functions and policies. Access tokens may expire or be revoked for security reasons and are renewed when permitted by the provider; authorization is never promised to be irrevocable.
Support and policy updates
If you choose to send a diagnostic report or screenshot to support, review it and remove private messages, passwords and tokens before sending. Do not place sensitive information in public channels. Changes are published here with an updated date. A new processing path, AI integration or cloud backup of mailbox contents requires corresponding disclosure, interface and permission updates before activation. This policy describes the current version and does not present planned features as enabled. Last updated: 2026-10-22. Contact: support@aljabareen.com.