Privacy policy

PostPush Local Cleaner · Updated 2026-11-11

PostPush Local Cleaner is a personal utility run by its operator on a Windows computer. This policy describes the program’s Gmail integration and these two information pages.

Google data accessed and its purpose

The program verifies the connected Gmail address, searches for PostPush notifications, and reads matching messages, including their headers, body text and HTML, message identifiers, dates and labels. It processes this information locally to recognize supported offers, determine the author payment, preserve uncertain messages and avoid repeating an action.

The program requests the gmail.modify permission. This is a broad permission to read and modify Gmail data. The program’s implemented mailbox actions are reading messages and moving individual qualifying messages to Trash. It only selects clearly recognized offers below USD 50 before commission; it keeps offers at or above USD 50 and ambiguous messages. It does not send mail, permanently delete mail or empty Trash.

Processing and sharing

The computer connects directly to Google’s authorization services and the Gmail API over HTTPS. Mailbox processing runs locally, without Codex, AI model calls or an application cloud backend. The program does not send Gmail message content to the hosting service for these pages, to an AI service or to another third-party processing service.

Google data is used only for this mailbox-cleaning function and its local operational history. The program does not sell this data or use it for advertising, profiling or AI training.

PostPush Local Cleaner’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Local storage and protection

OAuth tokens are stored locally and encrypted with Windows Data Protection API (DPAPI), using the current Windows user’s protection context. This token protection does not encrypt the separate local operational reports.

Local reports and history can contain the mailbox address, message identifiers, dates, recognized payment amount, decision reason, short normalized offer evidence, offer links, content hashes and operation results. New reports do not store complete message bodies. The program also reads existing local history to protect previously processed or restored messages; existing history is preserved.

Tokens and operational records remain on the operator’s computer until the operator removes them. There is no automatic retention period. Access to that computer and any copies or backups is controlled by the operator.

Revoking access and removing data

To revoke Gmail access, open your Google Account, go to its third-party connections, select PostPush Local Cleaner and remove its access. The program will no longer be able to use that authorization to access Gmail.

Revoking Google access does not remove local reports or restore messages already moved to Trash. Contact the operator to request removal of locally stored tokens or records, or to ask about a prior action. Use the operator’s support contact shown on this application’s Google consent screen.

These information pages

These two static pages contain no analytics code, tracking pixels, forms, cookies, external fonts or external scripts. They do not receive Gmail credentials or message content. The hosting provider may process IP addresses and request metadata in its own service and security logs; those records are separate from the local cleaner.