Outreach privacy policy

Information the workspace uses

• Google identity: name, email address, verified-email status and Google account identifier, used to authenticate the owner.
• Gmail information: the connected mailbox address, verified sending identities, and message identifiers, recipients, senders, dates, subjects and message content used to check previous contact, detect replies, bounces and opt-outs, and maintain the activity timeline. Gmail read permission can access the mailbox; the application's queries focus on the outreach workflow.
• Professional prospect information: organization names, publicly available business contact details, research sources, opportunity hypotheses, draft messages, notes and recorded outcomes.
• Operational information: session cookies, authorization credentials, activity records and hosting/error logs used to operate and protect the service. Infrastructure logs may contain technical request information such as IP addresses.

Why Gmail permissions are requested

The Gmail connection verifies the authorized owner. Gmail read access supports prior-contact searches, sender verification and reply checks. Gmail send access supports sending exact messages approved by the owner or automatically approved under an outreach rule set explicitly authorized by the owner. Connecting Gmail or granting permission does not approve messages or enable sending; the application also requires message and schedule approvals, an enabled sending configuration and an unpaused queue.

Reply, bounce, decline and opt-out records stop further automated follow-ups. A do-not-contact list helps prevent repeated unwanted contact. Google API information is used for these visible workspace features, not for advertising, sale to data brokers, credit decisions or training general-purpose AI models.

Storage and access

The application runs on the owner’s Mac. Prospect, message and activity records are stored in a local SQLite database with local backups. Provider credentials and OAuth tokens are encrypted using macOS Keychain-backed storage. The application’s local HTTP service is restricted to its desktop window; external provider connections use HTTPS. No Gmail password is requested or stored. Historical hosted records remain in the retired cloud workspace for recovery; new desktop activity is not synchronized there.

Access to the desktop data depends on the Mac account and its filesystem protections. Authorized administrators may access historical cloud records for recovery or deletion. Exported files and backups need the same care as the original records.

Sharing and exports

Google processes information to provide authentication, Gmail, hosting and storage. When an approved message is sent, its recipient receives that message and the sender details. The owner can export professional contact records and prepare private review documents; exported copies are managed separately from the application database.

The running outreach application does not transmit Gmail content to an external AI service. Access by a person assisting with a specific review or support task requires the owner's authorization, except where needed for security or required by law. The workspace does not sell Google user data or share it with advertising platforms.

MehrLogic Outreach's use of Google API information follows the Google API Services User Data Policy, including its Limited Use requirements.

AI-assisted public research

The desktop uses local Ollama inference by default. Brave Search can receive public organization names and locations to find official websites. Free public directories supply candidate listings; an optional MapQuest fallback searches for nearby businesses when the primary directory fails. Retrieved websites are checked before their text is used as evidence.

If the owner selects Gemini or enables cloud fallback, public organization details, retrieved website text, proposed introductions and published professional contact information may be sent to the Gemini API. Gmail messages, mailbox history, private notes, generated sender footers and authorization credentials are excluded from model input.

Research, drafts and usage estimates are stored locally. The owner can authorize automatic review and scheduling, with checks for published contacts, prior correspondence, accuracy and suppression status. Standard follow-ups may reuse the original approval after fresh correspondence checks. The owner can pause all processing and sending in the desktop app.

Retention and deletion

Prospect, message and activity records remain in the workspace until the owner or an authorized administrator removes them. There is currently no automatic retention purge. Suppression records are retained to respect opt-outs and prevent repeated outreach. Desktop records and backups stay on the Mac. Historical cloud logs follow the project's retention settings.

For access, correction or deletion requests, contact hooman@mehrlogic.com. Deletion is handled by the owner or an authorized administrator; the console does not currently provide a self-service deletion control. Requests involving suppression records are reviewed so that removing other data does not restart unwanted contact. Deleting workspace records does not remove messages from Gmail, recipients' mailboxes or separately exported copies.

Disconnecting Google and stopping outreach

The owner can pause outbound activity in the console and revoke the connection through Google Account connections. Revocation stops future API access once existing authorization expires or is rejected; it does not automatically delete previously stored workspace records. Closing the desktop application stops its local processing; it does not revoke Gmail authorization. Contact the owner to request removal of stored credentials and records.

Recipients can reply “no thanks” or otherwise request no further contact. A recorded opt-out suppresses future outreach. No-bounce status is not treated as proof that a contact address is verified.

Changes and contact

This policy describes the current outreach application. Its effective date will change when the policy is updated. A new use of Google information requires an updated disclosure and any required consent before that use begins.

Questions: Hooman Pegahmehr, MehrLogic — hooman@mehrlogic.com.