Extension privacy

JobClock extension privacy

This policy describes the data handled by the JobClock Chrome extension, when access happens, and the controls available to you.

Last updated 21 July 2026

01

Single purpose

The JobClock extension helps a signed-in JobClock user preview the active job listing, save it to their application pipeline, and update stages for recent applications. It does not collect page content in the background.

02

What the extension accesses

Page access happens only when you open the extension on a normal HTTP or HTTPS page. It may read the active page URL and title, plus visible or structured job details such as the job title, company, location, salary, and description.

The extension also handles your personal extension token, recent applications returned from your JobClock account, and application stage changes that you explicitly submit.

03

Storage and transfer

Your extension token and transient popup state are stored locally in Chrome using chrome.storage.local. The extension does not expose an editable server address.

The token, active page URL and title, and extracted job content are sent over HTTPS only to jobclock.michaelogunjimi.com. The extension itself does not send this information directly to other domains.

The JobClock service may send relevant job content to your user-configured AI provider to turn the page into a structured preview. Those providers process data under their own terms and your account configuration.

04

Retention and your controls

Opening a preview does not add the job to your account. Job information is persisted to your JobClock account only after you select Save to JobClock.

Saved application data remains in your account until you update or delete it. You can delete saved applications in JobClock, and you can use Revoke Token in JobClock settings to stop an existing extension token from authorizing future requests. Remove or replace the token in the extension to clear the locally stored credential.

05

Sale and advertising

Extension data is not sold or used for advertising. It is used to provide the preview, save, recent-application, and stage-update features requested by the user.

06 · Permissions

Why Chrome permissions are needed

activeTab

Temporarily accesses the tab where you opened JobClock so it can identify the active page.

scripting

Runs the packaged JobClock extractor on that active tab to read job details.

storage

Stores your extension token and short-lived popup state locally in Chrome.

Access to jobclock.michaelogunjimi.com

Allows API requests only to jobclock.michaelogunjimi.com for previews, saves, and stage updates.

07

Contact

JobClock is published by Michael Ogunjimi. Questions about this policy or the extension can be sent to support@jobclock.michaelogunjimi.com, or raised through the public JobClock support page.