BYE! 0.1.8 requests broad Gmail authorization, including the ability to permanently delete messages. This is more access than a Spam-only permission. Evaluate both what Google allows the app to do and how BYE! actually uses that access.
Google account permissions in the inspected code
| Scope | What it allows | Relevant BYE! use |
|---|---|---|
https://mail.google.com/ | Read, compose, send and permanently delete Gmail messages. | Calls that list messages and permanently batch-delete selected IDs. |
gmail.settings.basic | Manage basic mail settings, including filters. | Creates and removes sender filters. |
userinfo.email and userinfo.profile | Account email and profile information. | Sign-in and account identification. |
Google distinguishes the restricted full-mail scope from gmail.modify, which does not allow immediate permanent deletion bypassing Trash. A permission’s capabilities do not prove that BYE! uses every capability, but the breadth must be disclosed accurately. Google’s scope definitions.
Chrome extension permissions
The installed manifest lists storage, alarms, identity, identity.email and activeTab. It permits connections to Gmail/Google API and account domains, BYE!’s website and cdn.skypack.dev. The Gmail content script runs on mail.google.com. These browser permissions are separate from the Google account consent scopes.
What source inspection establishes about data flow
- BYE!’s extension stores account and token values using
chrome.storage.sync. It should not be described as local-only storage. - The extension sends account identifiers and OAuth access/refresh tokens to BYE!’s backend in its account-linking flow. The popup also reads linked-account token fields returned by that backend.
- Message-list and deletion requests in the inspected cleanup path go to Google’s Gmail API. This alone does not prove that all message content stays on the device across every product path.
- The extension registers an installation identifier and version with BYE!’s backend.
For questions about retention, deletion requests or service providers, contact support and consult the privacy policy. A Chrome Web Store badge or statement of Limited Use adherence is not a substitute for reviewing the scope of access.
Payments and privacy claims
Stripe processes paid upgrades. The trial ends on limited Free without a charge unless you separately choose and pay for a paid plan. Review checkout for paid renewal terms and the total charge. This does not mean BYE! holds no payment-related records. The public privacy policy describes data handling, but policy text is not a substitute for implementation evidence.
Before connecting or disconnecting
Review the actual consent screen. If Google shows an unexpected verification warning, stop and contact support for its current status. Signing out, revoking Google access, removing Gmail filters and deleting the BYE! account are different actions; do not assume that one performs all four. Review connected apps in your Google Account and your Gmail filters when stopping use.
BYE! is operated by Meow Catalog LLC and is not affiliated with Google. If you prefer not to grant another app this access, Gmail’s manual controls remain available. A custom script also requires account permissions and careful review; “script” does not automatically mean “safe.”
Evidence note: prepared by BYE!’s maker from installed extension 0.1.8 source on September 12, 2026. No production tokens or email contents were inspected. This source review is not an independent security certification.