Privacy Policy

AI connectors

When you connect an AI assistant to Trackly, including OpenAI (ChatGPT and Codex), Anthropic (Claude), Meta (Muse), and other MCP-compatible clients, Trackly receives the requests and tool calls that assistant makes for you. Data received through these connectors is used to provide the features you request. We do not sell it, and we do not use it to train AI models.

MCP usage analytics are a separate record of that activity. As described in Analytics & Session Recording, those traces may be kept for up to 12 months to operate, debug, and improve Trackly. They are not a copy of your résumé, profile answers, or application notes. Meta Muse does not write those MCP usage analytics. Its connector traces are described in Meta Muse.

You can disconnect an assistant or revoke its access at any time. That stops the assistant from making further requests to your Trackly account. Disconnecting does not delete your account, saved jobs, or profile. For a connection other than Meta Muse, MCP usage analytics already collected also remain until they expire under Data Retention & Deletion. You can ask us to delete analytics data by emailing [email protected].

Deleting your account from Settings removes the connector refresh tokens, authorization codes, and consent records stored for that account, together with the account data described under Data Retention & Deletion. You can also request deletion by emailing [email protected].

Meta Muse

This section applies to a Meta connection to Trackly at https://mcp.usetrackly.app/api/plugin/trackly/mcp or https://mcp.usetrackly.app/api/plugin/trackly/muse/mcp. It does not change how Trackly handles any other AI connector, including OpenAI (ChatGPT and Codex) and the general MCP endpoint.

When you disconnect a Meta connection, Trackly deletes that connection’s connector data: its OAuth grants, tokens, consents, and Muse MCP traces. Disconnecting does not delete your Trackly account or your saved jobs. For a Meta connection to https://mcp.usetrackly.app/api/plugin/trackly/mcp, this applies when the connection uses Meta’s Muse OAuth callback.

For requests to https://mcp.usetrackly.app/api/plugin/trackly/muse/mcp, diagnostic metadata contain only account and connection identifiers, the connector resource, processing purpose, request type, and timestamp. They do not contain tool arguments, resume or profile text, or request bodies. Trackly uses a 30-day retention period from collection, with automatic periodic cleanup of expired records and earlier deletion when you disconnect the connection or delete your account.

Restricted disaster-recovery backup copies may remain until they expire through backup rotation. They are not used for ordinary connector operations. This 30-day limit applies to diagnostic metadata; your account, profile, and saved jobs follow the account data rules under Data Retention & Deletion.

Muse connector traces are used only to operate and debug Trackly. Those traces are not used to improve Trackly or to train models. A job status change can still send a usage analytics event when usage analytics are on. Meta prohibits other uses of Muse connector data. The retention period stated for MCP traces and other product analytics events does not describe these Muse connector traces.

Analytics & Session Recording

Trackly and its service providers collect identified usage analytics and session recordings to operate, debug, and improve the free product. When you are signed in, these records may be linked to your Trackly account.

We record sessions of some Trackly product surfaces. Recordings may capture readable on-screen text and your interactions there. Input values, including passwords, are masked. Request headers and bodies are not recorded.

The existing /onboarding, /profile, /chat, /inbox, /connector, and /settings surfaces are excluded from session recording and product event capture. These routes contain onboarding, application-profile and résumé management, AI prompts and AI-connection readiness, and account settings.

For MCP usage, Trackly may collect granular tool activity, structured job-search usage, selected fields from public results, agent-intent categories, runtime details, outcomes, timing, and sanitized failure details. MCP usage analytics do not include résumé text, profile answers, demographic or work-authorization answers, or application notes. Trackly may still process that information within its systems when needed to provide and optimize your job-search agent; it is not copied into MCP usage analytics.

Before MCP authentication, Trackly may collect anonymous initialization, tool-discovery, and setup-failure activity. After successful authentication, that activity may be associated with the authenticated MCP session.

Before you sign in on the Trackly macOS app, Trackly may collect a limited set of anonymous app-launch, distribution-channel, sign-in-attempt, sign-in-failure, invitation, and access-check lifecycle events. This activity uses a temporary identifier that is not saved or linked to your account, excludes free-form text and identifying data, and stops when you turn off usage analytics.

Visits to our public marketing pages may also be recorded before you sign in. These anonymous recordings are kept separate from authenticated product analytics until you sign in.

Usage analytics are on by default. You can turn off future collection at any time using Share usage analytics in Account Settings. Turning it off takes effect for future capture; traces already collected remain until they expire under the retention periods below. We do not use third-party advertising trackers. Authentication tokens are stored locally on your device.

Referral-enabled sharing

If we make referral-enabled job sharing available, this section applies when you choose to create a referral-enabled link. Sharing helps keep Trackly accessible. Growing through personal recommendations helps us rely less on paid advertising and supports our goal of keeping Trackly free or low cost.

When you create a referral-enabled link, we associate it with your account and record qualifying referrals. This helps us understand what brings people to Trackly and recognize those contributing to its growth. We record the link, the job it shares, the original link creation time, your identity and account association, and qualifying referral actions. Your identity is not shown in the public link preview or on the public job page.

This limited referral attribution is part of the sharing feature and operates separately from optional usage analytics. Turning off general analytics does not disable it. Merely using Trackly does not create referral attribution; creating the link is the specific action. Recipients retain applicable privacy rights. Any permissions required to measure recipients still apply. This exception does not authorize unrelated browsing, recordings, or marketing.

Identifiable referral records may remain after you delete your account, but for no more than 12 months from the original link creation time. Later clicks, referrals, or account deletion do not restart that clock. By that deadline, we delete identifiable referral records or permanently remove every connection to your identity. Anonymous aggregate totals may remain; a random ID that can still be connected to you is not anonymous. You can exercise applicable privacy rights or make a request by emailing [email protected].

Data Retention & Deletion

MCP traces and other product analytics events are retained for up to 12 months. Session recordings are retained for 30 days from capture, then deleted. Muse MCP traces are not included in that period. They are described in Meta Muse.

You can delete your account at any time from Settings. When you delete your account, your profile, preferences, saved jobs, tracking history, analytics profile, and session recordings are permanently removed. The limited identifiable referral records described in Referral-enabled sharing are an exception and may remain for no more than 12 months from the original link creation time, including after account deletion. You can also request deletion of your analytics data and recordings at any time by emailing [email protected].

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.

Outside the active Berkeley Haas 12Twenty admin tab used for user-initiated actions, the extension does not access any other browser tab, bookmark, history entry, or download. It does not request the cookies permission and cannot read or write the cookie store directly. It does not install a persistent content script.

Chrome Web Store disclosure and permissions

Beyond the two host permissions above, the extension requests the storage permission for its own local settings and workflow state. The scripting permission lets the extension run a packaged function in the active Berkeley Haas 12Twenty admin tab for user-initiated employer lookups and draft creation, so those requests use the administrator’s existing signed-in page context. It does not install a persistent content script or download executable code. It also requests the Chrome identity permission solely to open and complete the optional Trackly Google Sign-In flow through Chrome’s extension redirect. The Chrome identity permission does not grant access to your Google contacts, calendar, or password. The extension does not request the separate identity.email permission.

Google Sign-In shares your name and verified email address with Trackly so Trackly can verify the account you selected, confirm access to this extension, and issue your personal Trackly credential. Trackly does not use the Chrome identity permission for advertising or unrelated browser activity. The use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements.

Google Sign-In and Trackly credentials

Google Sign-In is optional. Manual trk_ API keys remain fully supported, including for existing installations, and you do not need to switch an existing manual connection to Google. You may also continue to paste and use a manual key on a new installation.

If you choose Google Sign-In, Trackly creates a personal, full-access trk_ API key for this installation. It is a normal Trackly credential that can access the Trackly account data and actions available to a full-access API key; it is not limited to 12Twenty posting. The extension stores that managed key locally in the same credential slot used for manual keys and sends it as a Bearer credential when calling Trackly.

When the extension 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

Extension settings and workflow state live in chrome.storage.local on your device. Trackly receives the Google authentication exchange, sanitized support diagnostics, and the Trackly API calls described above. The locally stored items are:

• Your Trackly API key and saved 12Twenty options, including owner, relationship-manager, contact, and posting defaults.
• For a Google-managed connection, locally stored identity and authentication metadata: authentication mode, your Trackly account identifier and verified email address, an installation identifier, and credential schema/version details.
• Draft sessions: the in-progress review queue of jobs you have synced from Trackly but not yet pushed.
• Trackly sync state, including the sync cursor and per-draft preference snapshot references.
• Posted-job history and deduplication safeguards that prevent accidental duplicate work.
• 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.
• A separate random diagnostics installation identifier, the local sanitized diagnostic event queue, and diagnostic delivery state.

Sanitized support diagnostics

Sanitized support diagnostics are sent to Trackly by default to help diagnose extension failures. You can stop future uploads in Options by turning off Send sanitized diagnostics to Trackly for support. The API key is used only as the authorization header and is not included in the diagnostic payload.

These automatic remote uploads include sanitized operation events, extension version, timestamps and reason, and a separate random diagnostics installation identifier. Events can include bounded job and workflow context such as job title, company and domain, posting and Trackly URLs, salary, location and classification data, draft field values, review messages, and error text. When the Options setting is enabled, uploads also include a sanitized settings summary with feature flags and owner, relationship-manager, and company-default option IDs. They exclude email addresses, passwords, cookies, the Trackly API key, Google identity metadata, authorization codes, and PKCE verifiers. Server-side copies follow the product analytics retention and deletion practices described above.

Switching accounts and local-data boundaries

When Google Sign-In changes the Trackly identity, or the previous identity cannot be confirmed, the extension clears only Trackly-derived drafts (including their preference snapshot references) and sync cursor after the new credential is stored. This prevents one person’s Trackly feed or preferences from carrying into another person’s connection.

Your 12Twenty settings, posted history, employer ledgers, and deduplication safeguards remain on this device. Unrelated local state also remains. Suggested roster setup fills only blank 12Twenty fields after you confirm it; choosing Google Sign-In does not overwrite populated 12Twenty settings.

What is not done

• No third-party analytics, telemetry, or error-reporting SDK. The first-party sanitized support diagnostics described above can be turned off in Options.
• 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.
• When you choose Download diagnostics in Options, the extension creates a user-requested local JSON support artifact. This local diagnostic export is distinct from the automatic remote uploads described above. It excludes your email address, installation identifier, API-key prefix, authorization code, PKCE verifier, and the API key itself, and preserves the existing diagnostics format.
• 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

“Disconnect Google” revokes that managed key before clearing it from this browser. If revocation temporarily fails, the extension keeps the connection so you can retry. A separately warned local-only override can remove the local credential while leaving the managed server key active. Removing a manual API key from this browser does not revoke it on Trackly because a manual key may also be used elsewhere.

Uninstalling the extension removes its locally stored data from Chrome, but uninstalling the extension may not revoke a managed key on Trackly. Use “Disconnect Google” before uninstalling when possible, or revoke the credential through Trackly. Until it is revoked, the server-side managed key may remain active even though it is no longer stored in this browser.

Clearing or changing a Trackly credential does not automatically remove the retained 12Twenty settings and safeguards described above. To remove all local extension state, uninstall the extension through Chrome. Uninstalling still cannot guarantee server-side managed-key revocation, so disconnect Google first when possible.

Chrome Extension: Trackly Apply

This section applies to the Trackly Apply Chrome extension, a separate extension from Trackly → 12Twenty above. It fills supported Greenhouse, Ashby, and Lever job-application forms from your Trackly profile and resume library, on job postings you open yourself. The extension itself never submits an application. Submit is clicked on the employer’s own site, by you after you review the filled form. The web-app feature Apply for me, described below, is separate: there a Trackly team member submits the application.

Trackly offers the extension through the Chrome Web Store. Until that listing is public, Trackly staff load the extension in Chrome’s developer mode from a file. A build loaded that way does not update itself, and Google has not reviewed it.

What the extension accesses

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

• https://closeai.mba/*: the Trackly backend API, used to read your saved profile, resume, and application setup, and to send verification hashes and unanswered-field requests as described below.
• The Greenhouse, Ashby, and Lever job-posting and application pages the extension can read and fill:
  • https://boards.greenhouse.io/*
  • https://job-boards.greenhouse.io/*
  • https://jobs.ashbyhq.com/*
  • https://jobs.lever.co/*
  • https://jobs.eu.lever.co/*
  Apart from the two optional hosts in the next item, the extension requests access to no other site; it can open Trackly pages on usetrackly.app in an ordinary tab or sign-in window for setup and account connection.
• Two more Greenhouse hosts are declared as optional_host_permissions, so Chrome does not grant them when you install the extension:
  • https://job-boards.eu.greenhouse.io/*
  • https://job-boards.anz.greenhouse.io/*
  When you click Fill this form on one of these hosts, the extension asks Chrome for access to it, and Chrome asks you to allow it. If you decline, nothing is read, sent, or filled. If you allow it, the extension adds its content script to that host, and removes it again if you withdraw access.

On those application pages, the extension reads the form’s own field labels, help text, and option lists so it can match them to your saved profile, and it reads the posting’s URL, job title, company, and location so it knows which job you are applying to. When you click the employer’s Submit button, it also reads the values you typed into the fields described under “Answers saved when you submit” below. It does not read any other tab, and it does not install a content script outside the hosts above. Its bundled content script loads automatically on those five hosts when the page becomes idle, adds the Trackly launcher, and installs listeners for the submit-time capture described below. On the two optional hosts it adds that script only after you allow access.

The manifest’s externally_connectable entry lets pages on usetrackly.app send the extension a message. The extension answers only one of them, the Trackly admin page for Apply for me requests (https://usetrackly.app/admin/assist-requests, top-level frame), and refuses every other page. That page can ask for the extension’s version, or offer it an Apply for me request. The extension accepts an offer only when the signed-in account is already known to be a Trackly staff assist admin, a status it read earlier from the Trackly backend, so an ordinary account’s extension refuses it. An accepted offer expires within 30 minutes, opens the job posting in a new tab, and fills nothing until a staff member clicks in the extension’s side panel.

Extension permissions and Limited Use

Beyond the host permissions above, the extension requests the storage permission for the local settings and in-progress fill state described below. The scripting permission lets the extension place values into the application form on the current tab after you click Fill this form or a related action in the extension and, for Trackly staff testing the extension, while the panel stays open on that application, place an answer a Trackly team member has provided to a question sent from it (marked for review, as described below). This value-placement code does not run on page load. No executable code is downloaded. The activeTab permission lets a click on the extension’s toolbar icon, which opens the side panel, resolve to the tab you are viewing, without standing access to your browsing history. The identity permission opens Trackly’s sign-in page in a separate Chrome sign-in window through Chrome’s extension redirect, for the Connect Trackly account flow, which links the extension to your Trackly account; it does not grant access to your Google or Apple contacts, calendar, or password. Trackly does not use the Chrome identity permission for advertising or unrelated browser activity. The sidePanel permission shows the extension’s panel beside the page; it grants no access to page content. Trackly’s use of all information this extension collects or receives — including sign-in information, your profile and resume data, the form and posting content described in this section, and the answers saved when you submit — adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements.

Connecting your account opens Trackly’s sign-in page (Google or Apple) in that separate Chrome sign-in window. On success, Trackly exchanges the result for a personal trk_ API key, which the extension stores locally and sends as a Bearer credential on the calls described above. The extension never sees your Google or Apple password. The connection request also carries a random installation identifier the extension generates, so Trackly can tell this installation’s key from others.

What Trackly does when you click Fill this form

When you click Fill this form, the extension reads your saved application profile — your name, contact details, your resume file, and (only with the applicable separate consent) work-authorization and optional EEO answers — and types them into the employer’s application form in that tab. Each fill tells Trackly which employer (the job board’s company identifier) and which posting country the form belongs to, so the right saved answers come back. When the fill belongs to an application batch you started in Trackly, the extension also sends a verification hash that identifies the page and tab being filled — never the answers themselves. It does not send the employer form’s contents to Trackly, with the exceptions described below: for a question your profile cannot answer, it sends that question’s label, options, help text, and whether it is required, never an answer; with optional AI assistance, it sends a separate set of question wording and choices; and when you click the employer’s Submit button, answers you typed into unanswered fields that match a reusable profile question are saved to your Trackly profile so later applications can reuse them. EEO or self-identification answers, work-authorization answers, legal attestations or consents, passwords, file uploads, and free-text questions that have no matching profile question are never saved this way (see “Answers saved when you submit” below).

In this build an ordinary account does not send unanswered questions to a Trackly team member. A tester answer queue and a pasted-grant assist mode exist only for Trackly staff, and both stay hidden unless the Trackly server grants the signed-in account that staff capability. For a staff account, the extension sends the field’s label, option list, help text, and whether it is required for a field that the profile cannot answer (not an answer, since none exists yet), along with the job posting’s URL, ATS, company, and job title, so a Trackly admin can help. EEO, self-identification, and legal-attestation questions are never included in this admin-help request. A work-authorization question is included in an admin-help request only if the account has given the separate recruiting-data consent described below; otherwise it is also withheld from admins.

If you separately enable AI assistance, the extension sends a separate set of unanswered question labels, options, and help text to Trackly’s AI service. This set is not limited to the questions eligible for admin help: an unrecognized question can include wording about self-identification, work authorization, or consent. The same request carries the job posting’s title, location, and description (the description cut to 12,000 characters, the title and location to 300 each) and your local calendar date, which the service uses to date a signature or count a notice period. This sends the question’s wording and choices, not an answer you entered, together with the posting’s text. If Trackly accepts the AI request, it can use permitted profile facts and evidence from your selected resume to draft an answer. Before an AI answer is filled, a second, independent AI checks it against your own sources: the permitted profile facts, your selected resume, and the posting. An answer that check rejects is not filled. The check also covers every EEO answer, including an answer you saved earlier. Answers saved when you submit (below) are sent to your Trackly profile. AI assistance is optional, and you can fill from your saved answers without enabling it.

Answers saved when you submit

When you submit an application, the extension reads the values you typed into form fields that match a reusable question in your Trackly profile (for example willingness to relocate, years of experience, or your LinkedIn or portfolio link) and that your profile had no answer for, and saves them to your profile. It never saves EEO or self-identification answers, work-authorization answers, legal attestations or consents, passwords, file uploads, or free-text questions that have no matching profile question. The panel lists every answer it saved. You can switch to one-click saving in the extension’s settings, and edit or delete any saved answer at usetrackly.app/profile.

Consent, EEO answers, and work authorization

The extension shows a fill notice summarizing this section and asks you to agree before its first fill, and again whenever that notice changes. EEO and self-identification answers (for example gender, race, veteran, or disability status) are filled only with a separate consent, distinct from the agreement above: either the demographic-data consent you give in Trackly Apply setup, which is saved to your Trackly profile, or a per-application allowance you give in the extension for one application only. The per-application allowance is stored only on your device and is never sent to Trackly or to any admin. Filling saved work-authorization and eligibility answers requires the separate recruiting-data consent you control in Apply setup. That consent also determines whether an unanswered work-authorization question can be sent to a Trackly admin for help, where the staff-only question queue described above is in use. The separately enabled AI question path is described above.

In the staff-only tester answer queue described above, a question your profile could not answer is sent to Trackly and may be answered by a named Trackly team member so the fill can be completed. That admin sees your account profile (name, contact details, work history, and other saved profile answers, but never your EEO or self-identification answers), your parsed work history, and your resume text — not the resume file itself. Access to answer these requests is limited to Trackly staff who are signed in with a named Trackly admin account and whose sign-in is current within the last 24 hours; every answer is marked for your review before you submit the application. Trackly submits an application for you only when you ask for it with Apply for me, described below.

Apply for me

Apply for me is a feature of the Trackly web app, offered to accounts Trackly has enabled for it, and is not part of what the installed extension does for ordinary users. It is optional and works one job at a time. Nothing is submitted unless you click Apply for me on that job. The first time you use it in a browser, Trackly shows what the team member will be able to see and asks you to confirm; after that, one click sends the request. You can cancel a request while it is still waiting. A named Trackly team member, signed in with a named Trackly admin account whose sign-in is current within the last 24 hours, then fills in and submits that application on the employer’s site, using the Trackly Apply extension with your saved profile and resume; the extension does not submit by itself, and the team member clicks the employer’s Submit. While they work on it they can see your contact details, address, work authorization answers, salary expectations, employment status and resume. They never see your demographic (EEO) or self-identification answers. Trackly admins who work the request queue see your name and the job you asked for. Only the team member who has taken your request can open the rest, and only while they hold it; each time they open it is recorded, and their access ends when the request is closed. You get an email when the application was submitted or could not be completed, and the job moves to Applied in your tracker when it is done.

What is stored locally

Extension settings and in-progress fill state live in chrome.storage.local on your device. The locally stored items are:

• Your Trackly API key and account status.
• A random installation identifier, generated by the extension and sent to Trackly when you connect your account.
• Your selected resume and a cache of your resume list.
• The in-progress fill report, checklist, and any fill error for open application tabs.
• Answers captured from a form when you submit — and whether they were saved to your profile — while the application tab remains open. This state can be cleared when the tab closes, the browser restarts, the application changes or reloads, your account changes (including sign-out), or the bounded local cache evicts an older entry. Staff answers and fill reports can also remain in this local state until those cleanup events; they have no guaranteed 14-day local expiry.
• Your Apply setup state and the consent version you last agreed to.
• AI-drafted answers awaiting your review, when AI assistance is enabled, and its own consent version.
• Your separate, per-application EEO consent. This value stays on your device only; it is never sent to Trackly.

What is not done

• No auto-submission. The extension can only place values into the form and scroll the employer’s own submit control into view; it never clicks or triggers submission itself.
• No third-party analytics, telemetry, or advertising SDK, and no targeted advertising use of any permission.
• No remote-hosted code. All extension logic ships inside the downloaded .zip.
• No sale or rental of your data, and no transfer of it beyond what this section describes: the Trackly backend and the service providers that host and operate it (see Data Sharing above), the employer’s own application form when you direct a fill, and (only if you enable it) Trackly’s AI service, which runs on third-party AI model providers acting as Trackly’s service providers.

Retention, disconnect, and uninstall

Trackly’s server-side records of unanswered-question requests and the team’s answers (created only by the staff-only answer queue) are permanently deleted by an hourly cleanup after the request reaches 14 days from its original send time. This does not erase copies already downloaded into the extension or placed in an employer’s form. Resume files and application-profile answers are retained as part of your Trackly account and are permanently removed, along with the rest of your account data, when you delete your account (see Data Retention & Deletion above).

AI assistance requests are not saved as records of their own. Trackly does not write the questions, the posting text, or the AI’s answers or checks to its database, and its server log line for each request holds counts and codes only, never a question, a profile value, or drafted text. Trackly’s call ledger keeps token counts, cost, timing, and your account ID for each AI call, with no content; the ledger is deleted after 90 days by default and when you delete your account. Trackly has not set, in its own systems, how long the AI model provider keeps what it is sent.

“Disconnect” in the extension revokes your personal trk_ API key on Trackly before clearing it from this browser, if you connected through sign-in; if this browser still holds a manual trk_ key from an earlier version of the extension, removing it from this browser does not revoke it on Trackly, because the same key may be used elsewhere.

Uninstalling the extension removes its locally stored data from Chrome, but does not by itself revoke a key you connected through sign-in. Disconnect first when possible, or revoke the credential through Trackly. Deleting your Trackly account removes your resume, application-profile answers, and any unanswered-question requests not yet deleted from Trackly’s account storage. It cannot remotely erase copies already stored in an installed or offline extension, or data already placed in an employer’s form or submitted to an employer. To remove local extension data, disconnect when possible and uninstall the extension through Chrome; employer-held copies follow the employer’s policy.

Government and third-party data requests

This applies to every request for Trackly user data, not to one connector or product. Trackly reviews each government, law-enforcement, or third-party request for legal validity. Where appropriate, we challenge requests that are overbroad or legally deficient. We disclose only the minimum data the law requires. We notify the affected user before disclosure unless notice is legally prohibited or there is an emergency. Send requests to [email protected].