Privacy Policy

Chrome Extension — Trackly → 12Twenty

This section applies to the Trackly → 12Twenty Chrome extension, which is distributed as an Unlisted extension on the Chrome Web Store and is used by Berkeley Haas Career Management Center (CMG) administrators to mirror Trackly job postings into the 12Twenty career platform.

What the extension accesses

The extension communicates with exactly two hosts, declared in the extension manifest as host_permissions:

• https://closeai.mba/* — the Trackly backend API, used to list new job postings and read their details.
• https://mba-haas-berkeley.admin.12twenty.com/* — the Berkeley Haas 12Twenty admin tenant, used to look up matching employers, create new employer records when none match, and post job drafts.

The extension does not access any other host, browser tab, bookmark, history entry, or download. It does not request the cookies permission and cannot read or write the cookie store directly. It has no content scripts. The only permission it requests beyond host access is storage, for its own popup and service-worker state.

Authentication

The extension uses your existing browser sessions. When the extension calls Trackly, it sends your Trackly API key (entered once in the extension’s Options page and stored locally via chrome.storage.local). When it calls the 12Twenty host, the browser itself attaches any session cookies you already have for that host — the same way any web page makes a credentialed request — so 12Twenty recognizes your already- signed-in admin session. The extension never reads, copies, or stores those cookies and never asks for, stores, or transmits either platform’s password.

What is stored locally

All extension state lives in chrome.storage.local on your device. Nothing is sent to a Trackly-controlled server other than the API calls listed above. The stored items are:

• Your saved options (Trackly API key, 12Twenty owner / relationship- manager defaults, posting defaults).
• Draft sessions — the in-progress review queue of jobs you have synced from Trackly but not yet pushed.
• A bounded ledger of employers you created during the current install, used to keep create operations idempotent.
• A small autocomplete cache of recently looked-up employer names. No bundled employer database ships inside the extension package. The cache is populated lazily from 12Twenty’s own autocomplete API as you use it.

What is not done

• No third-party analytics, no telemetry, no error reporters.
• No remote-hosted code. All extension logic ships inside the uploaded .zip and is what is reviewed by Google.
• No targeted advertising. No browsing history collection. No data sold or rented to third parties.
• The extension does not see, store, or transmit any 12Twenty student data. It only reads and writes employer records and job postings within the Berkeley Haas tenant your admin session already has access to.

Uninstall & data removal

Uninstalling the extension from Chrome removes every locally stored item above. There is no server-side account or profile to delete. If you want to clear extension state without uninstalling, open the extension’s Options page and use the “Clear local data” control.