A single-user, personally operated job-application assistant. This page explains what data the application accesses, why, and how it is handled.
Effective 23 August 2026Operator Jared Adams (individual, personal use)Scope Google account integration
01What Jobpipe is
Jobpipe is a personal automation tool that helps one individual candidate — its operator — search for jobs, tailor application materials, and submit job applications on their own behalf. It is not a public product, is not offered to other users, and does not collect or process data belonging to anyone other than its operator.
02What it accesses in your Google account
Jobpipe requests one Gmail scope:
Scope
What it's used for
gmail.modify
Read recent messages, apply labels, archive messages, and send email — used narrowly for the three purposes below. This scope cannot permanently delete mail.
Within that scope, Jobpipe only ever does three things:
Reads a one-time verification code or link when an employer's application system (Greenhouse, Workday, and similar) emails one during account creation — so the operator's own automated session can complete a sign-up it started.
Sends one transactional notification to the operator's own address when an application needs a human decision it cannot make on its own (for example, a question with no pre-approved answer). No other outbound mail is ever sent, and nothing is sent to anyone but the operator.
Labels and archives high-confidence application-tracking-system mail so the operator's inbox stays organized. Jobpipe never deletes a message outright.
03What it does not do
It does not read, use, or store the content of personal or unrelated email — only messages it identifies as coming from a known application-tracking-system sender are ever inspected.
It does not share, sell, or transmit any Gmail data to a third party, advertiser, or any service other than the Google API itself.
It does not use Gmail data to train, fine-tune, or improve any machine-learning model.
It has no other users. It was built for, and is operated exclusively by, one individual for their own job search.
04Where data lives
All data Jobpipe reads or produces — job listings, application records, and the OAuth credentials themselves — is stored on infrastructure the operator personally owns and controls. Nothing is hosted by, or shared with, a third-party cloud service beyond the Google APIs Jobpipe calls directly.
Credential storage: the OAuth refresh token is held in a self-hosted secrets store (HashiCorp Vault) or an equivalent local, access-restricted file — never in source control, never in a shared or public location.
05Revoking access
The operator can revoke Jobpipe's access at any time from Google Account → Security → Third-party access. Revocation takes effect immediately; Jobpipe's verification-code and notification features stop working until access is granted again.
06Changes to this policy
If what Jobpipe accesses or does with that access changes, this page will be updated and the effective date above revised accordingly.