Privacy Policy — AEGIS

Last updated: 12 November 2026

This Privacy Policy describes how AEGIS (the "App"), a desktop application for Windows 10/11, processes your personal data, pursuant to Regulation (EU) 2016/679 (GDPR).

AEGIS is software distributed by Alessio Scionti (Private individual, non-commercial activity), referred to below as the "Owner", and is available at https://ascodenext.it.

1. Data controller

• Name: Alessio Scionti
• Status: Private individual, non-commercial activity
• VAT number / tax code: Not applicable — private, non-commercial activity
• Registered address: not stated (activity carried out on a private basis)
• Privacy contact: alessioscionti@gmail.com
• Website: https://ascodenext.it

2. The fundamental principle: AEGIS has no servers

AEGIS is a desktop application installed on your own computer. There are no AEGIS servers that store your data.

When you connect your Google account, the App:

• authenticates directly with Google, from your computer, using the OAuth 2.0 desktop application flow (authorization code + PKCE, with a temporary callback server on 127.0.0.1);
• queries the Google APIs directly, always from your computer;
• never transmits emails, metadata or tokens to any server operated by the Owner or to third parties.

The only communication with the Owner's infrastructure is the download of the installer and app updates, which take place through the normal distribution channel.

As a result, the data read from your Google account never travels through the Owner's systems and is not visible to the Owner.

3. What data is processed

3.1 Data from the linked Google account

During authentication, Google communicates to the App:

• your email address;
• a unique identifier for your Google account.

This data is used solely to show in the Settings screen which account is connected and to let you disconnect it. It is stored locally on your computer.

3.2 OAuth credentials

The App stores in the Windows Credential Manager, and not in readable configuration files:

• the refresh token needed to renew access;
• the optional client ID / client secret of the OAuth client (when not bundled with the installer).

The access token is not persisted to disk: it remains in an in-memory cache until it expires, and is released when the app closes.

3.3 Gmail data

With the gmail.readonly scope, the App is able to read from your Gmail mailbox. In practice, the App performs a single operation: reading the INBOX label, to obtain:

• the number of unread emails;
• the total number of messages in the Inbox.

The App does not read, open, copy, store or display the content, subject or attachments of any email. The widget shows only a count and a link to open Gmail in the browser.

3.4 Local technical data

The App stores locally, on your computer, widget configuration (position, appearance, display preferences) and technical operation logs. These do not contain any of your email data.

4. Requested OAuth scopes

The App requests the following OAuth 2.0 scopes:

• openid
• email
• https://www.googleapis.com/auth/gmail.readonly

The openid and email scopes are used to identify the connected account. The gmail.readonly scope allows the sole reading of the Inbox label for the unread email count.

The App does not request write, send or modify scopes: it does not read, modify, send or delete emails, does not access contacts, calendar, files or other data in your Google account. It does not request Google Drive, Google Calendar or Google Chat scopes either.

5. Purposes and legal bases

The explicit consent given on Google's OAuth consent screen constitutes, for Google data, the legal basis for processing: you may revoke it at any time as described in section 8.

6. How we handle Google data: compliance statement with Google policies

The use of data received through Google Workspace scopes is carried out solely to provide you with the Gmail widget's functionality, visible and prominent in the app interface.

The Owner expressly declares that:

• your data is not sold, transferred or rented out to third parties, advertising platforms, data brokers or information resellers;
• your data is not used to serve advertising, including interest-based advertising, retargeting or behavioural profiling;
• your data is not used to determine creditworthiness or for lending purposes;
• your data, including in aggregated, anonymised or derived form, is not used to train, create or improve artificial intelligence or machine learning models intended for other users or for general-purpose services. The App does not use language models and does not generate automatic summaries of email content;
• your data is not transferred to third parties except: (a) to provide or improve features requested by you with your consent; (b) for security purposes and abuse investigations; (c) to comply with applicable law; (d) as part of a merger, acquisition or sale, with your explicit prior consent;
• no person working for the Owner, its contractors or its sub-processors may read the contents of your emails. The App has no servers: the data stays on your computer and is not technically accessible to the Owner;
• your data is not used for behavioural profiling for advertising purposes or for business-intelligence purposes.

This use complies with the Google API Services User Data Policy, including its Limited Use Requirements, and with the Google Workspace Developer Policy.

7. Where data is stored and for how long

All data stays on the user's computer. There is no server-side database.

• Refresh token and OAuth credentials: Windows Credential Manager, for the duration of the connection. They are destroyed on disconnection or credential removal.
• Access token: memory only, for the duration of the app session, never written to disk.
• Emails and Gmail metadata: read on demand when the widget refreshes, processed in memory and not retained. The App keeps no copies, archives or persistent caches of email content.
• Account data (connected email): stored locally in the app's local settings, for the duration of the connection.
• Local technical logs: kept for as long as needed for diagnostics, and in any case for no longer than 12 months.

On disconnecting the account, or removing the credentials, the related local data is deleted by the app. Since the Owner receives and stores no data whatsoever, there is no data to delete server-side.

8. Revoking access and disconnecting

You may revoke the access granted to AEGIS at any time:

1. from within the app, in Settings → Google → Disconnect; to also delete the stored tokens use Remove credentials;
2. from your Google account settings at https://myaccount.google.com/permissions, by selecting AEGIS and revoking access.

Revocation is immediate: the App can no longer query the Google APIs and the widget returns to the "not connected" state.

For assistance, write to alessioscionti@gmail.com.

9. Security

The Owner applies appropriate technical and organisational measures:

• OAuth tokens are stored in the Windows Credential Manager, never in plain-text configuration files;
• the access token remains in memory and is never written to disk;
• the authorisation flow uses PKCE (S256) and a random state, with a temporary callback server on 127.0.0.1 closed at the end of the exchange;
• API access takes place exclusively over HTTPS (TLS);
• no email data is transmitted to third parties nor stored on servers.

10. Transfers outside the EEA

Because the App communicates directly with Google, any transfers outside the EEA are those made by Google to its own infrastructure, under the adequacy mechanisms and safeguards provided for in Google's terms of service (for example European Commission adequacy decisions and Standard Contractual Clauses).

The Owner transfers no personal data outside the European Economic Area, because no data is received.

11. Your rights

You may exercise at any time the rights provided for by Articles 15-22 GDPR: access, rectification, erasure, restriction, portability, objection and withdrawal of consent, as well as the right to lodge a complaint with the supervisory authority.

To exercise them, write to alessioscionti@gmail.com with the subject "GDPR request — AEGIS". The Owner responds within one month of receipt, extendable by two further months in the case of complex requests, with notice accordingly.

For rights relating to data held by Google, you can use the controls available in your Google security page.

You may also lodge a complaint with the Garante per la protezione dei dati personali, Via di Boccea, 180, 00187 Rome (www.garanteprivacy.it) — e-mail: protocollo@gpdp.it — or with the competent authority in your country of residence.

The Data Protection Officer (DPO) is: not appointed. For any request you can write to alessioscionti@gmail.com.

12. Changes to this notice

This notice may be updated to reflect changes in law, technology or organisation. The version in force is always published on this page with the date of the last update. In the event of material changes, users will be informed through the app or by a prominent notice on the app's page.

13. Contact

• Privacy and DPO: alessioscionti@gmail.com
• Website: https://ascodenext.it
• App terms: Terms and Conditions — AEGIS

For any request about your data, write to alessioscionti@gmail.com.