Privacy Policy

ByeMail is a Chrome extension that helps users analyze and clean Gmail by detecting newsletters, promotions, repetitive senders, large messages, and unsubscribe links.

Information We Access

• Gmail message metadata such as sender, subject, date, snippet, message ID, size estimate, and unsubscribe headers.
• Gmail profile email address, used to identify the connected account and generate email aliases.
• Local extension settings, scan metrics, automation rules, saved scan history, and background job status.
• Website email input fields, only to fill aliases such as user+example.com@gmail.com.

ByeMail does not intentionally read full email bodies unless future versions explicitly add that feature and request the required permission.

How We Use Information

• Detect newsletters, promotions, and repetitive senders.
• Display scan results and local metrics.
• Move selected Gmail messages to Trash or archive them when requested by the user.
• Open unsubscribe links exposed by Gmail headers.
• Run local user-created automations.
• Fill website email fields with a Gmail plus-address alias based on the current website domain.

Local Storage

ByeMail stores data locally in the browser using chrome.storage.local, including OAuth access token metadata, connected Gmail email address, scan results, scan history, cumulative metrics, automation rules, background cleanup job status, and theme preference.

Data Sharing

ByeMail does not sell, rent, or share user data with advertisers or third parties. ByeMail does not use an external backend server in this MVP.

Gmail Permissions

ByeMail requests Gmail permissions to read message metadata and modify messages by archiving or moving them to Trash. ByeMail does not permanently delete Gmail messages.

Email Alias Feature

When a user visits a website with an empty email field, ByeMail may fill it with an alias based on the connected Gmail address and website domain.

user@gmail.com + example.com -> user+example.com@gmail.com

Users can edit or remove the filled value before submitting any form.

User Control

• Remove the extension from Chrome.
• Clear extension data from Chrome settings.
• Revoke Google OAuth access from their Google Account.
• Avoid using cleanup or automation actions.
• Edit email aliases before submitting forms.

Security

ByeMail stores data locally and uses Chrome extension APIs for authentication and storage. No system is guaranteed to be perfectly secure, but ByeMail avoids external data collection in this MVP.

Children's Privacy

ByeMail is not intended for children under 13 and does not knowingly collect data from children.

Changes

This policy may be updated as ByeMail changes. The effective date will be updated when material changes are made.

Contact

For questions about this Privacy Policy, contact the developer or publisher of ByeMail.