Privacy Policy

Client Hunter is a private, single-owner client outreach and Gmail workflow application operated by MMS Studio. This policy explains how Client Hunter accesses, collects, uses, stores, protects, retains, deletes, and shares information when its owner connects Gmail, email providers, Telegram, browser extensions, or authorized AI clients.

Information we process

The application may process owner account details, authentication and security events, lead and contact records, outreach content, Gmail message metadata and bodies, draft and sent-message state, provider identifiers, and operational logs. It also stores configuration values and encrypted provider credentials required to operate enabled integrations.

How we access Google user data

Client Hunter accesses Google user data only after the owner affirmatively authorizes the application through Google OAuth. It requests the Gmail modify permission and receives Gmail message and thread content, headers, participants, labels, draft and sent state, provider identifiers, history identifiers, and verified Send-As addresses needed for the features described below. The application stores an encrypted refresh token so authorized background synchronization can continue until access is revoked or disconnected.

How we use Google user data

Client Hunter uses Gmail data only for owner-facing features: synchronizing email conversations into the dashboard, preserving thread context, creating or updating owner-requested Gmail drafts, sending drafts approved by the owner, changing read state, matching replies to lead records, stopping follow-up sequences after a reply, and displaying synchronization health. It does not use Gmail data for unrelated profiling, advertising, credit decisions, or data brokerage.

How we store and protect Google user data

Gmail message content and metadata needed for the dashboard are stored in the configured PostgreSQL database. Google refresh tokens are encrypted with AES-256-GCM before storage; access tokens are transient and are not exposed through the user interface or MCP. Owner sessions use secure HTTP-only cookies, MCP credentials are stored as non-reversible hashes, and scoped authorization, input validation, sanitization, and audit records protect access.

How we share or transfer Google user data

Google user data is transferred only when required to operate features deliberately enabled by the owner. This may include the application host and database processor, Google APIs, and an AI or automation service that the owner explicitly connects and grants a mailbox-related scope so it can provide the visible drafting or synchronization feature. Client Hunter does not sell Google user data, share it with data brokers, or use it for targeted, personalized, retargeted, or interest-based advertising.

Google Workspace data and AI models

Client Hunter does not use data obtained through Google Workspace APIs to develop, improve, or train generalized, non-personalized, or shared artificial intelligence or machine-learning models. An owner-authorized AI client may process selected email content only to provide the owner-requested, user-facing drafting or mailbox workflow at that time.

Service providers

Data is disclosed only to processors needed to operate enabled features, such as the application host, database provider, Google APIs, selected email providers, Telegram, and AI services explicitly connected by the owner. Each provider handles data under its own terms and privacy policy. The owner controls which integrations and MCP permissions are enabled.

Retention and deletion

Records remain until the owner deletes them, requests deletion, or an operational retention rule removes them. Disconnecting Gmail or revoking Google access deletes or invalidates the stored Google credential and stops future Gmail API access. Previously synchronized business records may remain so the owner retains outreach history until the owner deletes them or requests their deletion.

Your choices

The owner may disconnect Gmail, revoke MCP and browser-extension sessions, revoke active owner sessions, suppress contacts, and disable providers from the application. Google permissions can also be removed from the Google Account security settings.

Google API Services User Data Policy

Client Hunter's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Changes and contact

This policy may be updated as the service changes. Material updates will receive a new effective date. Questions or deletion requests can be sent to contact@sabbirmms.com.