Application privacy
Privacy Policy
How Job Hunt Automation accesses, uses, stores, and protects Google Sheets data in its local, owner-operated workflow.
- Application
- Job Hunt Automation
- Operation
- Private and locally operated
- AI assistance
- Optional and disabled by default
Overview
Job Hunt Automation is a private, locally operated tool used by its owner to manage job opportunities in a Google Sheets workbook. It does not provide a public account, hosted job service, or automated application service.
Google Data Accessed
The application requests the following Google Sheets OAuth scope:
https://www.googleapis.com/auth/spreadsheetsThis permission allows spreadsheet reading and writing as described by Google’s authorization screen. The application code is designed to operate on the spreadsheet ID explicitly supplied by the owner, but the OAuth permission is not technically restricted to only that spreadsheet.
How Google Data Is Used
Google Sheets data is used only to support the owner-requested workflow:
- Create and validate the workbook structure.
- Add or update opportunity records.
- Preserve human-owned review fields.
- Maintain deduplication records and run logs.
- Generate dashboard information.
- Perform owner-requested backup and recovery operations.
Credential Storage
OAuth credentials are stored locally using Windows Credential Manager. The application does not intentionally write OAuth refresh tokens to ordinary JSON token files, application logs, this portfolio website, or a hosted application server. These measures reduce exposure but do not guarantee absolute security.
Local Data Storage
Workbook snapshots, pending recovery records, quota state, and sanitized operational logs may be stored on the owner’s computer. These local records support troubleshooting, recovery, and consistent scheduled runs.
Optional AI Processing
AI-assisted analysis is optional and disabled by default.
If the owner separately enables it, only permitted job-listing excerpts and owner-verified profile claims are submitted for analysis. OAuth credentials are never submitted to an AI provider, and general spreadsheet contents are not used as unrestricted AI context. The configured provider may be Gemini Free or an approved local Ollama model; provider-specific data policies apply when an external provider is used.
Google Workspace API data is not used to develop, improve, or train generalized or non-personalized AI or machine-learning models.
Data Sharing and Sale
The application does not sell Google user data, use it for advertising, or share it with data brokers. Google processes data as necessary to provide its services. If external AI analysis is separately enabled, the limited inputs described above are processed by the configured provider solely to provide the requested application feature and remain subject to that provider’s data policies.
Retention and Deletion
Locally stored operational data remains on the owner’s computer until the owner deletes it or removes it through normal local maintenance.
- Google access can be revoked through the Google Account security or connected-app settings.
- Locally stored Google credentials can be deleted using the application’s credential-removal feature.
- Local runtime snapshots and logs can be deleted by the owner.
- Revoking Google authorization and deleting local credentials are separate operations.
Security
The project uses data minimization, local credential storage, explicit activation gates, sanitized logs, and human review to reduce risk. No technical system can guarantee complete security or eliminate every risk.
Contact
Questions about this application or policy can be sent through the portfolio’s existing contact section.
Policy Changes
This policy may be updated as the application’s features or data practices change. The last-updated date on this page identifies the current published version.
Last updated