WhatsApp Chat Sync to Gmail

Last updated: July 8, 2026

Summary

This app copies WhatsApp chat exports that you provide into your own Gmail account. It runs entirely on your device. There is no backend server, no account system, no analytics, and no advertising — the developer never receives, stores, or has access to your messages, your Gmail data, or your Google account.

What data the app accesses

To do its one job, the app requests three Google OAuth scopes:

gmail.insert — lets the app add new messages to your mailbox. It cannot read, modify, or delete any mail already in your account.
gmail.labels — lets the app create and apply a label (e.g. WhatsApp/Mom) so synced chats are organised.
userinfo.email — lets the app show which Google account is currently connected.

The app never requests permission to read your existing mail, contacts, or any other Google data.

Where your data goes

Nowhere but your own device and your own Gmail account. The WhatsApp export file you share or import is copied into the app's private storage on your device, parsed there, and sent directly from your device to Google's Gmail API over HTTPS — there is no intermediate server operated by the developer that your messages, attachments, or OAuth tokens ever pass through.

The app keeps a small local database on your device (message hashes and sync status) purely to avoid re-sending the same message twice. This database never leaves your device. Deleting the app removes it.

How your data is protected

Because the messages you sync are sensitive personal data, the app is built so that this data is exposed to as few systems as possible:

Encrypted in transit. Every network request the app makes — the OAuth sign-in and every Gmail API call — goes directly to Google over HTTPS (TLS). Your messages, attachments, and access tokens are never sent over an unencrypted connection.
No developer server, ever. There is no backend operated by the developer. Your data travels only between your own device and Google's own servers, so there is no third-party system that could store, log, or leak it.
Credentials stay on your device. The OAuth access and refresh tokens are cached only in local app storage on your device (auth/token.json on Windows; app-private storage on Android). They are never transmitted anywhere except to Google's own OAuth endpoints to obtain access.
Minimal local footprint. The only thing the app keeps is a small on-device database of message hashes and sync status, used purely to avoid re-sending the same message. It contains no message content and never leaves your device.
You control access and can revoke it instantly. Access is limited to the narrow scopes listed above and can be withdrawn at any time (see the next section), which immediately invalidates the stored tokens.

Because your data lives only on your own device and in your own Google account, we recommend protecting both with the usual safeguards — a device lock/OS-level encryption, and two-step verification on your Google account.

Account connection & revoking access

You can disconnect the app at any time from within the app itself (Settings → Disconnect), or by visiting your Google Account's third-party access page and removing "WhatsApp Chat Sync to Gmail" from the list. Revoking access does not delete anything already synced to your Gmail — those are ordinary emails in your mailbox and are yours to keep or delete like any other message.

Third parties

None. The app does not share, sell, or transmit any data to any third party. The only network calls it makes are to Google's own OAuth and Gmail API endpoints, directly from your device.

Changes to this policy

If this policy changes, the updated version will be published at this same address with a new "Last updated" date.

Contact

Questions about this policy or the app can be raised as an issue on the GitHub repository.