Min Message Forwarder

Data practices

Privacy policy

Effective 19 November 2026

This policy describes Min Message Forwarder, an owner-operated personal utility, and its public information website.

Information the service accesses

The service accesses the monitored Google account's basic identity, Gmail message metadata, matching email contents and attachments, and Google Chat spaces and messages. The Google permissions allow read access across the authorized account; the service's own sender and time rules determine what is forwarded. Email metadata is checked before matching email bodies are downloaded. Chat messages sent by the monitored user and messages before initial activation are excluded from forwarding.

Why the information is used

Information is used to identify eligible messages, produce forwards, prevent duplicate delivery, recover from interruptions, and maintain the owner's authorized connections. Message contents are not used for advertising, sold, or used to train AI models. No AI model processes messages in this service.

Where messages are sent

Eligible messages are sent to the owner's configured destination mailbox through a separate authorized Gmail sender. Email forwards contain readable text and the original email file, which can include attachments. Chat forwards contain text, original message data, and any available attachment links or metadata; the service does not copy Chat attachment files. The sending and receiving providers process and retain those emails under their own policies. The owner controls the forwarding destination through service configuration, not through message text.

Storage and retention

Google Cloud hosts the service. Google Secret Manager stores authorization credentials. Firestore stores processing cursors, identifiers, timestamps, and delivery status. The service does not intentionally store message bodies in Firestore or application logs. Processing metadata currently has no automatic deletion schedule. Cloud infrastructure can retain event metadata and operational logs according to its configured retention policies.

Message contents pass through the service during processing. Delivered copies remain in the sending and receiving accounts until those account owners delete them, subject to their providers' retention practices.

Permissions and security

The monitored account grants read-only Gmail and Google Chat access and basic identity access. This connection cannot send, change, or delete work messages. The separate sending account grants Gmail send access and basic identity access, without inbox-read permission. Google's send permission is not restricted to a particular recipient; this service's configuration fixes the destination.

Credentials are kept separately from the public website. Google Cloud access controls restrict service invocation and access to stored credentials. The service checks the authorized account identities and granted permissions when refreshing access.

Stopping access and requesting deletion

The owner can pause the service and revoke its connections in Google Account settings. A send already in progress may finish. Revoking authorization prevents continued access as Google invalidates the relevant credentials; pausing the service stops new processing. The owner can separately remove stored cloud credentials and processing metadata. Removing the connection does not delete copies that were already delivered.

For questions or requests concerning access or deletion, use the operator's support email shown on the app's Google authorization screen. The operator can address service-held records; requests about copies in other people's mailboxes may require contacting their account owners or providers.

This information website

This static website does not access Gmail or Chat, collect message contents, provide a sign-in form, or run advertising or analytics scripts. The hosting provider may process technical request information, such as IP addresses, to deliver and secure the website.

Google API data

Min Message Forwarder's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Changes

Changes to these practices will be reflected on this page with an updated effective date.