Who is responsible

Controller: Armando, the personal project owner.

Privacy contact: [email protected].

This is a personal-use automation for its owner, not a commercial service or public multi-user product.

Information processed

When the owner runs the workflow, it may process:

• Gmail account address and the OAuth credentials needed to connect the account;
• headers and message content from recent emails that match selected job-alert sender domains;
• job-listing details derived from those messages, including employer or title where available, dates, short descriptions and listing URLs; and
• workflow information such as run status, counts and the digest recipient address.

The workflow uses message content to identify and sort job alerts. It is not intended to extract unrelated Gmail content, but the Gmail search and message-fetch operations are performed by Google’s Gmail API under the permissions granted by the account owner.

Why and how the information is used

The information is used only to operate the owner’s job-search digest: locate relevant alerts, extract and deduplicate listings, apply simple keyword-based criteria, and email the resulting digest to the same Gmail account. It is not used for advertising, profiling for unrelated purposes, sale, or training machine-learning models.

The current automation reads matching emails and sends the digest. Although the OAuth setup currently requests a Gmail message-management permission as well, the script does not use that permission to change, label or delete messages.

Armand Job Tracker’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Where processing happens and who provides services

• Google: Gmail and the Gmail API provide the mailbox and email-delivery functions. Google’s Privacy Policy and the Google API user-data policy describe its handling of data.
• GitHub: the scheduled workflow runs on a temporary GitHub Actions hosted runner. The OAuth client credentials and refresh token are stored as GitHub Actions repository secrets. The script processes message data in memory during the run; it does not write message bodies to the repository or a separate database. Workflow logs may record operational details such as run status, counts and the digest recipient address. GitHub controls log and secret retention under the repository settings and its service terms; see GitHub’s Privacy Statement.
• Cloudflare: this informational website is delivered using Cloudflare Pages. Cloudflare may process standard connection and security data (such as IP address, user-agent and request metadata) to deliver and protect the pages. Cloudflare does not receive the Gmail message content through this website. See Cloudflare’s Privacy Policy.

These providers may process data in locations outside the European Economic Area. Their own privacy notices and contractual safeguards govern their services and any applicable international transfers.

Storage and retention

The workflow has no application database or mailbox archive of its own. Source emails remain in Gmail under the account owner’s mail settings. The generated digest is sent by Gmail and remains there until the owner deletes it. Message content is processed in the hosted workflow run and is not intentionally saved as a file by the script. GitHub Actions logs and repository secrets remain subject to the retention settings described above; the owner can delete workflow logs and remove secrets in GitHub. The owner can also revoke the app’s Google access in their Google Account.

Security and Google data

OAuth credentials are kept out of the source code and stored as repository secrets for the scheduled workflow. Access should be limited to the owner, credentials should not be shared, and the Google authorization should be revoked when it is no longer needed.

Google user data is used only for the features described here, with no sale or advertising use. Access can be withdrawn at any time by revoking the app’s access in the Google Account security settings. Revocation stops future Gmail API access, although emails already in Gmail and workflow logs remain until deleted under the relevant account settings.

Cookies and this website

These pages do not set advertising or analytics cookies, use tracking pixels, offer user accounts, or collect information through a form. No third-party fonts, images, analytics or scripts are loaded by these pages. The hosting and security provider may process technical request data as described above.

Your choices and rights

The tool is intended for its owner’s own account. The owner can stop scheduled processing, revoke Google access, delete the stored GitHub secrets, remove workflow logs, and delete Gmail messages or digests. If you have a privacy request about information described in this policy, contact [email protected]. Depending on the applicable law, rights may include access, correction, erasure, restriction, objection, data portability and withdrawal of consent. People in France may also contact the CNIL.

Changes and contact

This policy may be updated if the workflow or its data practices change. The current version will remain available at this address. Questions can be sent to [email protected].