Privacy Policy
1. Who this applies to
Job Collector Gmail Read Only is a private, single-user job-search management tool operated by Stratus Insights LLC for the owner's personal use. It has no other users, no public accounts and no advertising.
2. Google user data we access
- The application requests only the Gmail scope
gmail.readonly, which allows reading email in the owner's Gmail account. - Read-only authorization has been granted. A minimal recruiting-mail read check and a refresh-token verification have completed.
- Recruiting-mail tracking and the Pending Updates queue are disabled until this disclosure is published and the owner enables scanning.
3. How data is or will be used
- The only purpose is to identify job-search progress in the owner's own email, relate it to positions already in the owner's tracker, and propose updates for the owner to confirm.
- Google user data is not used for advertising and is not sold.
4. Local recruiting-mail tracking — JC-GMAIL-TRACKING-V1
Read-only Google authorization and minimal mail-reading and token-refresh checks have completed. Tracking remains off until this disclosure is published and the owner enables it. The feature reads only job-related candidates for positions already applied to in the owner's existing tracker. Local rules identify Interview, Rejected, Under Review or Offer and abstain on ambiguous job matches. They do not use an external AI model.
Email bodies, subjects, sender addresses, attachments and snippets are not persisted by the tracking feature. Message text is processed only in local memory; Attachment download endpoints and remote email images are not accessed; non-text MIME parts are not decoded. No private mail content is sent to external AI services.
When enabled, the local queue stores an opaque queue identifier, Gmail message identifier, existing tracker job identifier, proposed status, message received time, queue creation and decision times, fixed matching-reason codes, rule version and a hash of the expected tracker progress. Deduplication stores hashes derived from message and job identifiers plus processing times; incremental cursors store job references and scan times. These records are saved only in a private local file under the application's credential directory, protected with 0700 directory and 0600 file permissions and the computer's FileVault. They are not protected by Keychain or application-level encryption.
Pending and decided queue records are deleted after 30 days. Deduplication hashes are deleted after 90 days. Retention cleanup runs whenever the enabled worker scans and when the owner accesses the tracking controls; if the computer is off or the application is stopped, cleanup waits until the next such execution. Incremental scan cursors remain until reset or deletion. The application does not include these Gmail-derived files in its application backup routines. Operating-system backups and filesystem snapshots, if any, follow the owner's separate settings; deletion is not a promise of forensic secure erasure.
Pending Updates are displayed only through the owner's existing protected Job Collector interface. Google provides OAuth and the Gmail API. Cloudflare Access and Tunnel carry authenticated traffic to that interface, including minimal queue metadata, but no email body, subject, sender address or snippet is exposed by this feature. Grist runs locally on the same computer, not Grist Cloud. Only after explicit confirmation does the application write the proposed application status and its normal status-change audit record to the local tracker. It does not store Gmail message identifiers or email text in Grist and never automatically changes the tracker.
The owner can pause or resume tracking. Authorization failure safely pauses scans without stopping the existing job collector. Delete derived data pauses tracking and removes the local queue, deduplication records and cursors without changing Gmail messages or existing tracker history. Resuming after deletion can rebuild suggestions from the owner's still-existing Gmail messages. Deleting derived data does not revoke Google authorization or delete the separately stored OAuth credentials. The owner can revoke access at https://myaccount.google.com/permissions and request local credential removal. Confirmed tracker history is not erased by derived-data deletion.
The application does not send, delete, move or mark Gmail messages as read, does not sell Google user data, does not use it for advertising and adheres to the Google API Services User Data Policy, including the Limited Use requirements.
5. Google API Services User Data Policy
The use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
6. Changes and contact
We will post changes to this page and update the date above. Contact: partnerships@stratusinsights.co.