A clear view of what Mail Audit uses—and what it does not store.

Mail Audit needs limited account and email metadata to create a tracking record, connect that record to the sender, detect supported image-load events, and display the result in the extension and dashboard.

• The text or HTML body of tracked emails in the Mail Audit database.
• Email attachments.
• Your Gmail password.
• Unrelated browsing history outside the extension's disclosed Gmail purpose.
• Credit-card information, because Mail Audit currently does not directly collect payment details.

The Chrome extension runs on Gmail so it can detect a compose window, identify the sender, recipient, and subject, insert the invisible tracking image, display tracking indicators, and show supported open status information.

Access should remain limited to the permissions necessary for these user-facing features. The extension should not use Gmail access for unrelated purposes.

Google sign-in is used only to authenticate your Mail Audit website account. The Chrome extension does not request Gmail API read or send scopes and does not receive your Gmail password.

Email tracking is added through the Gmail compose interface after you choose to send, while account access remains managed by Google sign-in.

• An open event is generated when the tracking image is loaded.
• Some email providers proxy, cache, preload, or block images.
• Multiple image loads may create multiple events.
• A missing open event does not prove that the message was not read.
• Users remain responsible for providing notices or obtaining consent where required.