
ASEM Desktop
ASEM Desktop Privacy Policy
This policy describes data handling in the optional Mailboxes module of ASEM Desktop for Windows and the controls available to users.
Responsibility and scope
EURL ASEM, identified in the official website’s legal notice, operates the professional ASEM Desktop application and manages ASEM accounts and permissions. For questions or requests about your data, contact direction@asem-medical.com. Official details are available on the ASEM contact page.
The ASEM account and professional services are separate from a connected Gmail account. This policy covers the Gmail module and does not replace the policies for other ASEM applications.
Data accessed and purposes
With your permission, the module accesses the mailbox identity, sender and recipient addresses, headers, messages, conversations, attachments, folders, labels and drafts needed for the visible mail features.
Data is used to read and search email, compose, reply, send, synchronise drafts, manage stars and labels, organise, archive and move messages to Trash. Recipients you choose receive the messages and attachments you send.
The initial gmail.modify permission does not allow permanent deletion. The optional permanent deletion action in Trash separately requests the broader mail.google.com permission and an irreversible confirmation for the specific message.
Google authorisation and session persistence
Connection uses OAuth in your system browser. ASEM Desktop does not collect your Google password. You select the account and grant permissions on Google screens.
Access and refresh tokens maintain and renew the session. Storing them does not guarantee a permanent connection: Google may limit, expire or revoke authorisation, and a new sign-in may be required.
Local storage, cache and safeguards
Account associations, tokens, metadata, cached content and local drafts are stored on your computer in an AES-256-GCM encrypted vault, separated by ASEM identity. Its key is protected by Windows secure storage. Locally retained draft attachments are encrypted as well.
The persistent cache is limited to 1,000 messages and saved state to 64 MiB. It supports resuming work; no fixed automatic deletion period is promised. Signing out of the ASEM account hides session data but retains the vault for signing back in with the same identity.
Files you choose to save in your folders remain ordinary files subject to Windows protections; they do not automatically receive vault encryption. Application isolation does not protect against another person with the same Windows rights or administrator rights. Protect your Windows session and keep the computer up to date.
Communications, recipients and Limited Use
The module communicates directly with Google services over HTTPS for Gmail and OAuth. The ASEM backend does not receive Gmail messages, their attachments or OAuth tokens from this module.
Remote images load only after you choose to allow them; their host may then receive your IP address and technical request details. External links open after confirmation and are governed by the visited service’s policies.
Google data is used only to provide the visible mail features chosen by the user. It is not sold or used for advertising, commercial profiling or training artificial intelligence models. ASEM does not provide centralised human access to Gmail messages; only share the specific information you intend to disclose when contacting support.
ASEM Desktop’s use and transfer of information obtained through Google APIs complies with the Google API Services User Data Policy, including its Limited Use requirements. Changes in handling must be disclosed before any new use of this data.
Removal, revocation and data requests
Remove from this PC deletes the chosen account association, tokens, cache and local drafts from ASEM Desktop. It does not delete your Google account or messages held by Google, and does not automatically revoke Google authorisation. Files you saved separately remain in their folders.
You may revoke ASEM access in your Google account’s third-party connections. Local removal does not promise forensic erasure of old disk blocks or your personal backups.
To request information, exercise control or report a data issue, contact direction@asem-medical.com and identify the account and data concerned. Never send passwords, OAuth tokens or unnecessary mail content.