Information the extension reads
When you use Job Log on an open job page, it reads that tab’s URL and visible text, then detects the job title, company, and source. The text passed to its extraction step can contain up to 6,000 characters from the page, including surrounding page content. Job Log uses this information to prepare a row for your spreadsheet.
On LinkedIn, the extension can also request job details from LinkedIn’s own API using your active LinkedIn session. To make that request, it reads LinkedIn’s JSESSIONID cookie as a request token and sends the request back to LinkedIn. If it gets confirmed job details, it uses the title and company from that response. If details cannot be confirmed, it may use the AI extraction flow described below.
Google account and Sheets access
Job Log requests the Google Sheets OAuth scope https://www.googleapis.com/auth/spreadsheets. Google describes this as permission to see, edit, create, and delete all your spreadsheets. This permission is broader than the one spreadsheet you enter in Job Log. The current extension code directs its Sheets requests to the spreadsheet ID you configure; the OAuth grant itself is not limited to that file.
Within that spreadsheet, Job Log reads sheet names and week or progress values. It writes application rows with the date, company, week, role, job link, initial status, and source. Its settings can also update your weekly goal and add week rows, formulas, validation, and formatting in the progress sheet.
For sign-in, the extension receives a Google access token and caches it in browser extension storage. One of its sign-in flows also requests the email scope. Job Log may ask Google for the connected account’s email address, then display and save that address locally as an account label and sign-in hint.
Gemini and Groq
You provide a Gemini or Groq API key in the extension settings. When page details need extraction, Job Log sends a prompt containing page text, detected title and company, and source to the service you selected. If it cannot get a usable result, it may try the other service if you also configured that key. The relevant API key is sent to its provider to authenticate the request.
Confirmed LinkedIn details do not go through this AI extraction step. The current extension code does not send data read from Google Sheets to Gemini or Groq. Those providers process requests under their own terms and retention practices, which Job Log does not control.
Where data is stored and for how long
- Chrome Sync storage: Gemini and Groq API keys, spreadsheet ID, selected AI provider, weekly goal, and selected week are stored with
chrome.storage.sync. Depending on your browser settings, Chrome may sync them across your signed-in browsers. - Local extension storage: Google access tokens and expiry times, the connected email when available, cached week names, and dismissed update notices are stored with
chrome.storage.local. The token is replaced or refreshed when needed; signing out clears the cached token and email. - Your Google Sheet: Application rows and progress data are stored in the spreadsheet you chose, in your Google account.
Job Log has no automatic deletion schedule for saved settings or spreadsheet rows. They remain until you change or remove them, or the relevant browser or Google storage is removed. Retention by Google, Gemini, Groq, LinkedIn, GitHub, and the website host follows those services’ own policies.
Service providers, transfers, and analytics
The extension sends Sheets requests directly to Google, may send page text to Google Gemini or Groq as described above, and may request LinkedIn job details from LinkedIn. It also checks a public update notice hosted by GitHub when its popup opens. That check makes a normal network request to GitHub; it does not include a job record or an API key in the request made by Job Log.
The inspected extension code contains no Job Log backend, analytics SDK, advertising tracker, or mechanism that sends spreadsheet contents to the developer. Job Log does not use Google API data for advertising or to train AI models. Its use of information received from Google APIs is limited to the user-facing spreadsheet features described here, in line with Google API Services’ Limited Use requirements.
This public website is hosted on Vercel. Serving a page sends normal request information, such as an IP address and browser headers, to the host. The website code has no sign-in, form submission, analytics script, tracking pixel, or application cookie. The extension does not create tracking cookies; it reads the LinkedIn cookie described above only to request LinkedIn job details.
Security
Job Log makes its external API and update requests over HTTPS. Google access tokens are cached in Chrome’s local extension storage, while API keys are stored in Chrome Sync storage. The extension does not add its own encryption layer to those stored values. Protect access to your browser profile and to the API keys you provide.
Your controls and deletion
You can edit or delete saved applications directly in your Google Sheet. The extension’s Disconnect control clears its cached Google token and saved account email, but it does not delete the spreadsheet or the settings stored in Chrome Sync. To withdraw the underlying Google OAuth grant, remove Job Log’s access in your Google Account connections.
Job Log does not currently include a one-click control to erase all extension settings. Removing the extension or clearing its browser extension storage affects local copies; settings synced through Chrome may also need attention in your Chrome sync settings. For help with deletion or questions about data handling, email eduardoemanuelcf@gmail.com.
Changes and contact
If Job Log’s data practices change, this page will be updated with a new date. The developer of Job Log can be contacted at eduardoemanuelcf@gmail.com.