Email Checker
Data handling

Privacy policy

This policy describes how Email Checker accesses and uses data for its owner's private email-assistance workflow.

Data accessed

With the account owner's Google authorization, the integration accesses Gmail message metadata, senders and recipients, subjects, message bodies, thread context, labels, and attachments required for a task. Basic Google account information is used to identify the authorized account. The current Gmail permission is read-only.

Purpose and use

Data is used to search and summarize email, understand conversations, identify relevant follow-up work, prepare owner-reviewed suggestions, and retain useful task knowledge. This permission does not authorize sending or changing email. Email content and attachments are treated as untrusted input, not as permission to execute instructions.

Where processing happens and data sharing

The integration runs on an owner-controlled computer. Selected message content, attachment data or task context may be transferred to configured AI or processing providers, including OpenAI and services reached through OpenRouter, when needed to fulfill the owner's tasks. The providers actually used depend on runtime configuration. Such providers may apply their own security and retention policies. Data is not sold or used for advertising. The application does not use Google user data to train general-purpose AI or machine-learning models.

Human access is limited to the owner and any people the owner specifically authorizes for the work. This public website contains application information only; email content, attachments and OAuth credentials are not published here.

Storage, retention and deletion

OAuth credentials are stored in a protected credential store on the owner's host, separately from task knowledge. Working copies, summaries and task records may be retained while needed for approved work. Audit metadata and useful procedural knowledge may be retained longer. Cleanup currently requires owner-directed or manual action; automated retention enforcement is not yet enabled. No fixed automatic-deletion deadline is promised by this policy.

The owner may request removal of local task data through the support contact on the Google consent screen. Third-party copies, provider logs, backups and indexes may require separate handling and may follow different retention periods. Deleting a local copy does not guarantee immediate deletion from every third-party system. Gmail originals are not deleted by this read-only integration.

Control and revocation

The owner can revoke access at any time in Google Account connections. Revocation stops subsequent authorized API access but does not automatically erase copies previously created for tasks. To request deletion or ask questions, use the application support email shown on Google's consent screen.

Google API data

Email Checker's use and transfer of Google API data must comply with the Google API Services User Data Policy, including its Limited Use requirements.

Website and service infrastructure

This information site uses no application analytics scripts, forms or embedded tracking. Cloudflare serves the site and may process technical request information such as IP addresses under its own service policies. Other service providers used by the email workflow apply their respective policies.

Changes

This policy will be updated when the application's actual permissions or data practices change. Last updated: October 24, 2026.