Your inbox deserves care
PRIVACY &
DATA CHOICES.
MailBreather is available to invited Gmail testers at app.mailbreather.com. General public account access is not open. This draft describes the hosted test; remaining operational retention details and review requirements must be finalized before launch. It is not a claim of Google or Yahoo approval.
Who we are
The MailBreather Team maintains MailBreather, an independent email cleanup app. It helps users filter clutter, review a matching batch, and confirm which messages to move to Trash. Yahoo Mail support is planned and is not publicly available.
For help, privacy questions, or a request to remove app-held data, contact the MailBreather Team at support@mailbreather.com. Please do not send passwords, authorization tokens, or email contents that are not needed to explain your request.
What the website collects
This introductory website has no signup form, advertising trackers, analytics scripts, or mailbox connection. Render hosts this website and the connected Gmail app. The Gmail app runs in Render’s Oregon region in the United States. Render may process network and technical information, including IP addresses and request information, to deliver and protect the services. See Render’s privacy policy. The public website itself does not connect to your mailbox; invited testers connect through app.mailbreather.com.
What the connected Gmail app accesses
When you authorize the test app through Google, MailBreather receives authorization tokens, not your Google password. The app accesses:
- Your Gmail address to identify the active mailbox.
- Message identifiers, labels, sender information, subjects, dates, short snippets, and size estimates to filter messages, show previews, identify protected messages, and display recent cleanup activity.
- Message counts and labels to show categories and protection status.
- If you connect the storage monitor, your Google account’s reported storage usage and limit. These totals can include Gmail, Drive, and Photos.
The current Gmail connector requests message metadata and may receive short snippets. It does not download full message bodies or attachment files. MailBreather sends your chosen filters and cleanup requests to Google to perform the actions you confirm.
Why Google asks for these permissions
gmail.modify: finding and reviewing messages and moving confirmed batches to Trash. This permission also allows composing and sending email. MailBreather uses it for mailbox cleanup and does not compose or send email.https://mail.google.com/: optional permission required to permanently delete messages when you choose Empty Gmail Trash. This grants full Gmail access, including sending, although MailBreather uses it for cleanup.drive.file: optional permission used to request storage totals. This permission also covers Drive files explicitly shared with the app; MailBreather does not list or modify your Drive files.
Moving messages to Trash and permanently deleting them are separate actions. Permanent deletion cannot be undone. Google’s own retention rules govern mail in Trash and when storage totals change.
Storage and retention in the hosted test
Authorization tokens, mailbox sessions, cleanup previews, and up to 50 recent cleanup receipts are held in the app server’s memory. This version has no persistent mailbox database and does not write mailbox data or tokens to application files or create mailbox backups. A server restart clears these in-memory stores and signs users out.
- Mailbox sessions and tokens: sessions expire 24 hours after creation. Recent cleanup receipts are kept within that session.
- Sign-in requests: pending authorization state expires after 10 minutes.
- Cleanup previews: expire after 30 minutes; permanent-deletion previews expire after 5 minutes. Confirmed previews are consumed before cleanup begins.
- Expired records: the running app removes them during access and periodic cleanup approximately every minute. These are application-level deletion rules, not a guarantee of immediate physical memory erasure.
Switching or disconnecting removes the active server session, its stored previews, and pending permission-upgrade requests. An operation already in progress can still finish. Disconnecting does not cancel that operation or revoke Google’s authorization.
The browser stores a session cookie lasting up to 24 hours and a sign-in cookie lasting up to 10 minutes. Local storage holds your mailbox address as part of a key, the first recorded storage total, and its timestamp so the app can compare later readings. Those local records remain until you clear the site’s browser data, including after disconnect. Browser caching stores interface assets; the app’s service worker excludes mailbox API and OAuth responses. Displayed mailbox information also exists in page memory while the app is open.
The app emits startup and generic error messages to Render’s logs; its current logging statements do not intentionally include email contents or OAuth tokens. Render’s dashboard log retention depends on the workspace plan: 7 days on Hobby, 14 days on Pro, and 30 days on Scale or Enterprise. These dashboard periods do not describe all infrastructure or security records held by Render. The applicable workspace plan and provider-level retention arrangements must be confirmed before this draft becomes final.
Use, sharing, and human access
The app uses Google data for the cleanup and storage features you request. It has no advertising, data-sale, or AI-training integration. Google receives the API requests needed to perform those features. Render processes app requests and in-memory mailbox data as our hosting provider. GitHub stores application source code; the deployed source repositories do not contain mailbox data or user tokens. Any additional provider handling user data will be disclosed before it is used.
MailBreather’s proposed public data-use commitment is to follow the Google API Services User Data Policy, including its Limited Use requirements. Google data must not be sold, used for advertising, or used to train generalized AI models. Human access must be limited to circumstances permitted by Google’s policies, such as your explicit consent to investigate a support issue, security needs, or legal obligations. These commitments and the production implementation will be reviewed before this policy becomes final.
Your data choices
- Use the app’s Switch control to disconnect the current session.
- Remove the app’s access through your Google Account connections. Disconnecting in the current test app does not itself revoke Google authorization.
- Clear browser site data for app.mailbreather.com to remove the stored mailbox-address key, storage baseline, cookies, and cached interface files; close the app’s tabs to discard displayed page data.
- Email support@mailbreather.com to request removal of app-held data. Include the connected mailbox address so we can identify your request; we may need to verify that you control it. Do not include your password.
Removing app-held data does not restore permanently deleted Gmail messages or remove mail that still exists in your Google account.
Support messages
Messages sent to support@mailbreather.com are forwarded through Porkbun to a Gmail inbox monitored by the MailBreather Team. Porkbun and Google process the address, message, and attachments you send to deliver and store that correspondence. Support correspondence is separate from the app’s 24-hour session records. Its deletion schedule and any necessary security or legal retention exceptions remain to be finalized before public launch.
Changes before launch
We will update this draft as support, remaining retention details, and production account controls are finalized. Material changes to data access or use will be disclosed, and additional consent will be requested where required. Yahoo data practices will be documented before Yahoo connections are offered.