Safety · 8 min read · 2026-06-02
The Signup Process: Understanding Google OAuth and Your Privacy
A transparent breakdown of our secure signup process. Learn why we use Google OAuth and exactly what permissions we request to clean your inbox.
The Password Dilemma: Why Email Tools Historically Failed Security
Email is the master key to your entire digital identity. It holds password reset links for your banking accounts, confidential work communications, medical records, tax documents, and personal conversations. Entrusting a third-party software tool with your inbox is one of the most sensitive decisions you can make online.
In the early days of web software, third-party productivity tools required you to provide your actual username and password or generate an insecure "App Password." If that third-party service suffered a security breach, malicious actors could hijack your entire Google account, read all your private messages, change your security questions, and lock you out permanently.
At Smart Mailbox Cleaner, we believe that security and privacy must be foundational, not afterthoughts. That is why we never ask for passwords. Instead, our application is built entirely upon official Google OAuth 2.0 with PKCE (Proof Key for Code Exchange)—the gold standard in modern internet authorization.
In this transparent guide, we break down our exact signup process, review every single permission we request from Google, explain why it is needed, and highlight the critical capabilities we deliberately block.
What is Google OAuth 2.0 and PKCE?
Google OAuth 2.0 is an authorization protocol that allows you to grant a third-party application limited, revocable access to specific parts of your Google account without ever revealing your password.
When you log in to Smart Mailbox Cleaner:
- The Handshake: You click "Sign in with Google" and are redirected directly to
accounts.google.com, Google's secure authentication server. - PKCE Security Verification: Our application generates a dynamic cryptographic code verifier and challenge. This prevents authorization code injection attacks and ensures that only our authenticated frontend client can complete the login handshake.
- The Granular Consent Screen: Google displays our verified application profile and presents the exact list of permissions requested.
- Token Generation: When you approve, Google issues an encrypted, temporary access token and refresh token. This token permits our server to perform specific API tasks on your behalf, but can be revoked by you at any second with a single click in your Google Account security panel.
Granular Breakdown: What Permissions We Request and Why
Google groups API permissions into specific "Scopes." In accordance with the principle of least privilege, Smart Mailbox Cleaner requests the bare minimum permissions necessary to scan, categorize, and clean your mailbox:
+-------------------------------------------------------------------------+
| OAUTH SCOPES REQUESTED BY SMART MAILBOX CLEANER |
+-------------------------------------------------------------------------+
| 1. https://www.googleapis.com/auth/gmail.metadata |
| • Purpose: Fetches email headers (Sender, Subject, Date, Size). |
| • Privacy: CANNOT access body text or download attachments. |
| |
| 2. https://www.googleapis.com/auth/gmail.modify |
| • Purpose: Moves cleaned emails to Trash & restores them on Undo. |
| • Privacy: Used strictly for trash management and label adjustment. |
| |
| 3. https://www.googleapis.com/auth/drive.metadata.readonly |
| • Purpose: Queries overall storage quota breakdown (Gmail/Drive). |
| • Privacy: CANNOT read or download files stored in Google Drive. |
+-------------------------------------------------------------------------+
1. gmail.metadata (Email Header Analysis)
- What it does: Allows our scanning engine to read email message headers: the
From sender address, the Subject line, the date timestamp, file attachment size indicators, and system labels (e.g., Starred, Important, Inbox, Promotions). - Why we need it: This metadata powers our Smart Scan and AI Confidence Scoring. We need to know that an email is from an automated mailing list and is 2 years old in order to categorize it safely.
- Privacy Guarantee: Under the
metadata scope, Google's API strictly forbids access to the actual message body, HTML content, or file attachments. Even if our servers tried to read an email body, Google's API would instantly reject the request with an authorization error.
2. gmail.modify (Trash and Label Management)
- What it does: Allows our server to apply labels and move designated messages to the Gmail Trash folder.
- Why we need it: When you click Clean Selected during a One-Click Cleanup, we must send a batch command to Gmail instructing it to move those specific message IDs to Trash. When you click Undo, this permission is used to remove messages from Trash and reapply their original labels.
- Safety Restriction: We do not permanently delete (
messages.delete). We strictly issue move-to-trash commands (messages.trash), ensuring you retain a 30-day safety net.
3. drive.metadata.readonly (Quota Gauge Tracking)
- What it does: Allows us to read your Google Account storage quota numbers (e.g., 14.2 GB used of 15.0 GB total).
- Why we need it: Powers your dashboard's real-time storage gauge and fuels our Guardian Auto-Clean watchdog.
- Privacy Guarantee: We cannot inspect, read, or download your Google Docs, Sheets, photos, or Drive files.
What Smart Mailbox Cleaner CANNOT Do
To provide complete peace of mind, here is an explicit list of actions our application is architecturally incapable of performing:
| Forbidden Action | System Status | Reason |
|---|
| Reading Email Body Content | 🚫 IMPOSSIBLE | Denied by OAuth scope restriction (metadata only) |
| Viewing or Downloading Files | 🚫 IMPOSSIBLE | No attachment download permissions granted |
| Sending Emails on Your Behalf | 🚫 IMPOSSIBLE | Denied; no gmail.send scope requested |
| Accessing Google Contacts/Calendar | 🚫 IMPOSSIBLE | No Contacts or Calendar scopes requested |
| Changing Account Passwords | 🚫 IMPOSSIBLE | Third-party OAuth tokens have zero account admin access |
| Locking You Out of Google | 🚫 IMPOSSIBLE | Zero authority over Google Account credentials |
How to Audit and Revoke Access at Any Time
You remain in total control of your account at all times. If you ever wish to disconnect Smart Mailbox Cleaner and instantly invalidate our tokens, you can do so in seconds:
- Visit your Google Account security center at myaccount.google.com/permissions.
- Locate Smart Mailbox Cleaner under the list of third-party apps with account access.
- Click on the application and select Remove Access.
- Google will instantly destroy all active access and refresh tokens. Our servers will be completely blocked from making any further API calls.
Pro Tips for Vetting Third-Party Email Software
- Always Check the OAuth Consent Dialog: When authorizing any web tool, carefully read the permissions listed on Google's consent screen. If a cleanup app asks for
Read, compose, send, and permanently delete all your email, decline immediately! - Look for Metadata-Only Architecture: Legitimate storage cleaners only need email headers. Avoid tools that download your email bodies onto external proprietary servers.
- Verify Enterprise Review Status: Ensure the application has undergone Google's rigorous third-party OAuth app verification process and adheres to the Google API Services User Data Policy.
- Audit Your Authorized Apps Regularly: Review myaccount.google.com/permissions every six months and prune apps you no longer actively use.
Our Privacy Core Principle
"We only access email metadata — sender, date, size, labels. We never read email content."
Your personal privacy is our highest priority. Experience a clean, fast inbox without compromising your security. Sign up — your first cleanup is free at Smart Mailbox Cleaner and explore our transparent plans on our Pricing Page.
Related Reading
Frequently Asked Questions
Does Smart Mailbox Cleaner ever see or store my Gmail password?
Never. We use Google OAuth 2.0 with PKCE. Authentication happens directly on Google's encrypted servers (accounts.google.com). We never see, receive, or store your Google password or two-factor authentication credentials.
Can your software read the private text or body of my emails?
No. Our OAuth access is strictly limited to the gmail.metadata scope. Under Google's API architecture, this scope only provides message headers (Sender, Subject, Date, Size, Labels). Google strictly blocks access to email body text, HTML contents, and file attachments under this permission.
Why do you need the gmail.modify permission?
The gmail.modify permission is required to move emails into the Gmail Trash folder when you perform a cleanup, and to restore those emails back to their original labels when you click Undo. We never request the permanent delete (messages.delete) permission.
How can I revoke Smart Mailbox Cleaner's access to my Google account?
You can revoke access at any time by visiting your Google Account security settings at myaccount.google.com/permissions, selecting Smart Mailbox Cleaner, and clicking "Remove Access". This immediately invalidates our API tokens.
Is Smart Mailbox Cleaner compliant with Google's API User Data Policy?
Yes. Smart Mailbox Cleaner adheres strictly to the Google API Services User Data Policy, including the Limited Use requirements. We never sell user data, never transfer data to advertising brokers, and never use email metadata to train public machine learning models.
Try Smart Mailbox Cleaner free →