Transparent data practices for Gmail outreach and utilities
MMBS is designed to use data only for the features a user chooses to run. MMBS does not sell user data.
Introduction
This Privacy Policy describes the data MMBS may collect, use, process, store, or transmit when users visit the website, install the Chrome extension, connect Gmail, use campaign tools, or process files with the email, PDF, and image utilities.
Information Collected
Depending on the features used, MMBS may process:
- Google account profile details returned by OAuth, such as name, email address, and profile image.
- Gmail authorization tokens required to provide authorized Gmail sending and account features.
- Campaign inputs such as subject lines, email body content, recipient lists, merge fields, scheduling settings, and tracking preferences.
- Operational records such as send status, open events, click events, delivery attempts, errors, queue status, and dashboard activity.
- Browser-local preferences such as theme selection, connected account display state, and utility settings.
Gmail OAuth Usage
MMBS uses Google OAuth only for authorized Gmail-related features selected by the user. Gmail access is used to connect the user's Gmail account, display connection status, and send or support campaign workflows through the Gmail API where permission has been granted.
MMBS does not use Gmail access to sell user data, build unrelated advertising profiles, or access Gmail content outside the authorized MMBS sending and campaign features.
Email Processing
Email addresses, recipient rows, merge fields, subjects, and message bodies are processed to prepare, preview, schedule, send, analyze, and report on user-requested campaigns. Users are responsible for making sure recipient data is collected and used lawfully.
File Uploads
Files uploaded through MMBS features are used only for the selected workflow, such as extracting contacts, processing PDFs, reading campaign inputs, or preparing utility outputs. Uploaded or selected files are processed temporarily for the requested action and are not sold.
PDF/Image Utilities
The PDF and image utilities are designed to run client-side in the browser where applicable. Some advanced or server-assisted features may send files or derived content to the MMBS backend only to complete the requested processing task.
Analytics
The website may be prepared for lightweight analytics, search indexing, webmaster verification, and platform monitoring. MMBS avoids heavy tracking on legal pages and uses operational campaign analytics only to provide reporting features such as opens, clicks, send status, and dashboard summaries.
Cookies
MMBS may use browser storage, local storage, or cookies for authentication state, user preferences, session continuity, security, and product functionality. Users can control cookies and storage through browser settings, but disabling them may limit some features.
Security
MMBS uses reasonable technical and organizational safeguards to protect product data, including HTTPS-based services, authorization boundaries, server-side API controls, and limited feature-specific processing. No internet service can guarantee absolute security.
Third-party Services
MMBS may interact with third-party services that support core functionality, including Google OAuth, Gmail API, hosting providers, database services, browser APIs, and optional analytics or webmaster tools. Those services may process information under their own policies.
Data Retention
MMBS keeps operational data only as long as reasonably needed to provide product features, maintain security, troubleshoot issues, comply with legal obligations, and support campaign reporting. Temporary utility files should not be retained beyond the processing purpose unless required for the selected feature.
User Rights
Users may request access, correction, deletion, or clarification about personal data processed by MMBS. Availability of specific rights can depend on location, applicable law, and the technical state of the requested data.
Contact
For privacy questions, data requests, or Google OAuth verification inquiries, use the protected support email.