Your archive,
under your control.

Information accessed and collected

The tool reads job identifiers, employer and role names, posting URLs, application stages, and application dates from the owner's shared Google Sheets tracker to identify postings to archive. Read-only tracker snapshots can also contain other tracker fields, such as notes and contacts; those snapshots remain private.

When enabled for a permitted source, it captures publicly accessible job-posting content as screenshots and visible text. It stores source URLs, timestamps, capture outcomes, file checksums, Google Drive file and folder identifiers, and processing state to organize archives and recover interrupted uploads.

Google OAuth credentials, including a refresh token, are used to maintain the authorized Drive connection. The tool requests only the https://www.googleapis.com/auth/drive.file scope for this connection, not unrestricted Google Drive access. Sheets access uses separately granted service-account permissions.

How information is used

Information is used to identify applied jobs, preserve posting details, organize the owner's private archive, avoid duplicate captures, verify file integrity and private access, and diagnose or recover failed processing. The archive uploader does not use Google user data for advertising, sell it, or send archive content to an AI model.

Job Scraper Archive's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Storage, access, and service providers

Archive files are uploaded to the owner's Google Drive. Private working copies, tracker snapshots, capture state, upload journals, and credentials are stored on an AWS Lightsail server. Local authorization credentials and development or verification artifacts may also be kept on the owner's computer.

Google and Amazon Web Services process this information to provide their storage, API, and hosting services. Access is limited through the owner's Google permissions and private operating-system file permissions. The uploader verifies owner-only permissions on its Drive objects and does not create public sharing links. The operator can access the private information to maintain the tool.

This public website is hosted on Cloudflare. It uses no site-added analytics, advertising scripts, cookies, or forms. Cloudflare may process ordinary connection information, such as IP addresses and request metadata, to deliver and secure the website under its privacy policy. Visiting this website does not authorize Google access.

Retention and deletion

There is currently no active automated deletion schedule. Stored files and records remain until the owner removes them or the operator deletes them. Any source-specific retention requirements must be resolved before enabling capture for that source.

To remove archive content, delete the relevant files or archive folder from Google Drive and empty the Drive trash as appropriate. Corresponding local and server copies, journals, indexes, snapshots, and any backups must be removed separately by the operator. Deleting a Drive file does not automatically delete those other copies.

Revoking Google access

The owner can revoke authorization through Google Account connections. Revoking access stops future authorized API access once existing access tokens expire or are invalidated; it does not delete files already saved. The operator can stop processing immediately by disabling the worker and remove stored credentials separately.

Contact and changes

For questions or deletion requests, contact James McFadden using the support email displayed in this app's Google authorization details. This tool is maintained for the operator's personal use and is not a public account-registration service.

Changes to data practices will be reflected on this page with an updated effective date.