Data transparency

Privacy Policy

Effective date: October 24, 2026

AI Job Hunter is a personal automation project run by an individual operator. It uses n8n and connected services to organize job-alert messages for the operator's own job search. It is not offered as a public service.

1. Google data accessed

With permission granted through Google OAuth, the automation uses Gmail API access to retrieve messages matching a configured job-alert search or label. It may receive email fields such as sender, subject, message identifier, text, HTML, and job links. The Gmail permission scope may technically be broader than the subset of messages processed by this workflow.

2. Purpose and use of data

The automation parses job-alert messages, extracts details such as employer, role, location, and job URL, checks for duplicates, and evaluates job opportunities against the operator's preferences. It can obtain additional publicly available job description details from linked vacancy pages. AI-generated matching assessments assist the operator's own review; they do not make employment decisions.

3. Where data goes

• n8n (self-hosted): orchestrates workflow execution and may retain execution data and diagnostic logs, according to its configuration.
• OpenAI API: may receive extracted job details or vacancy descriptions for AI-assisted evaluation. The workflow is not intended to send unrelated personal email content for evaluation.
• Google Sheets: may store job details, links, evaluation results, and processing statuses for tracking and deduplication.
• Telegram: may receive messages containing selected job details and evaluation summaries.
• Gmail / Google: remains the source of the original authorized messages and associated account data.

Use of these third-party services is also subject to their respective privacy terms. The site itself is static and does not collect Gmail data from visitors.

4. Retention and deletion

Original messages remain under the account owner's control in Gmail. Extracted results and processing records may remain in Google Sheets, Telegram, and n8n execution history until the operator deletes them or the applicable service's retention settings remove them. There is no guaranteed automatic deletion period unless configured in those systems.

5. Security and access

The automation connects to Gmail using Google OAuth rather than requesting the user's Google password. Access to the n8n workflow and connected services is intended for the operator. As with any online integration, security depends on the configuration and access controls of the services involved.

6. Sharing and advertising

Google user data is used only for the workflow functionality described above and is not sold or used to target advertising. Data may be transmitted to the integration services named in Section 3 to perform the requested job matching and notification functions. The automation is not intended to make Google user data available to unrelated third parties.

7. Control and revocation

The Google account owner may revoke the application's access through Google Account third-party connections. The operator can also disable the n8n workflow and delete stored results from the connected services, subject to those services' capabilities.

8. Questions and changes

Questions about this personal automation can be directed to the application support email shown on its Google OAuth consent screen. This policy may be updated to reflect changes in connected services or data handling practices; updates will be published here with a revised effective date.