From 74d8b13d2c0757b722604330147df0060b9c37fb Mon Sep 17 00:00:00 2001 From: puglieri <112409628+puglieri@users.noreply.github.com> Date: Fri, 18 Sep 2026 10:46:03 -0300 Subject: [PATCH 1/2] Update app.html.md --- adguard-mail.com/privacy/app.html.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/adguard-mail.com/privacy/app.html.md b/adguard-mail.com/privacy/app.html.md index 8e09b30..ba0a2b5 100644 --- a/adguard-mail.com/privacy/app.html.md +++ b/adguard-mail.com/privacy/app.html.md @@ -90,9 +90,13 @@ When managing aliases and recipients, including actions like creating, retrievin - **Alias ID**: The unique identifier, name, description, and status of the alias. Fields that may contain user-defined information about the recipient. - **Recipient ID**: The unique identifier, name, description, and status of the recipient. Fields that may contain user-defined information about the recipient. -- **Email address**: The email address associated with the recipient or alias. +- **Email routing metadata**: Information required to enable email forwarding and reply routing, including sender and recipient email addresses, alias addresses, message identifiers, delivery metadata, and timestamps. -Alias and recipient management involves data that directly identifies email addresses and associated users. While email addresses are considered Personally Identifiable Information (PII), they are essential for the functionality of the service. +Email addresses and related routing data may constitute Personally Identifiable Information (PII). However, processing this information is necessary for the operation of the service. + +To provide alias-based email forwarding and reply functionality, AdGuard Mail creates **encrypted** reply-routing metadata. The sender's email address, which is required for routing replies, is stored in this metadata in encrypted form and is not stored in plain text within reply mappings. This data is required for email forwarding, reply routing, processing delivery failures and spam complaints, sender blocking, troubleshooting, and abuse prevention. + +**When an account is deleted, associated reply-routing metadata is removed**. When an alias is deleted, certain technical records may be retained for a limited period to process delayed delivery notifications and are deleted afterward. ### Session and account access management From 6c28da5181600a004ca9d92ed5e4bcd1965353fb Mon Sep 17 00:00:00 2001 From: Elena Ter-Mikaelyan Date: Tue, 22 Sep 2026 16:18:39 +0300 Subject: [PATCH 2/2] Update adguard-mail.com/privacy/app.html.md --- adguard-mail.com/privacy/app.html.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/adguard-mail.com/privacy/app.html.md b/adguard-mail.com/privacy/app.html.md index ba0a2b5..f2628fc 100644 --- a/adguard-mail.com/privacy/app.html.md +++ b/adguard-mail.com/privacy/app.html.md @@ -94,7 +94,7 @@ When managing aliases and recipients, including actions like creating, retrievin Email addresses and related routing data may constitute Personally Identifiable Information (PII). However, processing this information is necessary for the operation of the service. -To provide alias-based email forwarding and reply functionality, AdGuard Mail creates **encrypted** reply-routing metadata. The sender's email address, which is required for routing replies, is stored in this metadata in encrypted form and is not stored in plain text within reply mappings. This data is required for email forwarding, reply routing, processing delivery failures and spam complaints, sender blocking, troubleshooting, and abuse prevention. +To provide alias-based email forwarding and reply functionality, AdGuard Mail creates **encrypted** reply-routing metadata. The sender’s email address, which is required for routing replies, is stored in this metadata in encrypted form and is not stored in plain text within reply mappings. This data is required for email forwarding, reply routing, processing delivery failures and spam complaints, sender blocking, troubleshooting, and abuse prevention. **When an account is deleted, associated reply-routing metadata is removed**. When an alias is deleted, certain technical records may be retained for a limited period to process delayed delivery notifications and are deleted afterward.