ARES

ARES Privacy Policy

Last updated: October 4, 2026

ARES stores profile details, application settings, chat memory, recent activity and fortune-reading history locally on the user's computer, subject to the user's choices.

Anonymous usage metrics and crash diagnostics are sent only with express consent. ARES does not send chat content, file names or paths, profile details, fortune content, passwords or microphone recordings as diagnostic data.

Microphone audio is processed temporarily only for speech recognition and is deleted after processing. Users can withdraw consent, erase local metrics, clear chat memory and export their data from Settings > Privacy.

Google User Data

ARES accesses Gmail only after the user explicitly completes Google's OAuth consent flow. The Gmail integration uses Google authorization data only to provide the mail features requested by the user, such as reading, sending and managing Gmail messages.

OAuth authorization data, including access and refresh tokens, is stored locally on the user's device in ARES credential storage so that the Gmail account can remain connected. ARES does not use Gmail message content or Google OAuth tokens for advertising, profiling or diagnostic telemetry, and does not intentionally upload them to an ARES-operated cloud service.

For performance and mail-safety purposes, Defender-clean message bodies may be kept in a local, Windows DPAPI-protected cache. This cache is non-authoritative and does not store attachment file bytes.

Google user data retention

ARES does not apply a fixed server-side retention period to Google user data because the Gmail integration is local to the user's installation. OAuth credentials are retained locally only while the Gmail account remains configured in ARES. Local cached mail data is kept only as an operational cache and may be invalidated or purged during normal cache maintenance.

Google user data deletion

Users can delete Google user data held by ARES by removing the Gmail account from ARES Mail Center. Removing the account deletes the local account authorization credential for that account and purges the corresponding secure local mail-body cache. A new OAuth authorization is required before ARES can access that Gmail account again.

Users may also revoke ARES access at any time from their Google Account permissions. Revoking access prevents further Google API access until the user explicitly authorizes ARES again. Data retained independently by Google is governed by Google's own privacy policies and account controls.

Third-party services

Spotify, Perchance, radio, podcast and user-opened streams are subject to the respective third parties' privacy policies and terms.