Your application hunt stays under your control.

What the extension examines

After you enable application detection, the extension can examine the current page URL, page title, primary heading, canonical job link, site name, and up to 4,000 characters of visible page text on supported Greenhouse and Lever pages. This information is used only to recognize a likely job listing or submission confirmation.

The extension does not read passwords, form-field values, cookies, browsing history outside its supported job sites, email, attachments, or complete page HTML.

Browser-local application inbox

A detected application is shown for review before it enters the browser-local application inbox. A confirmed local capture contains the company, role, canonical job URL, listing platform, observation time, and random capture identifiers used to prevent duplicates.

Local captures remain on that browser until you discard them or ApplyQuest confirms that your agent already synchronized the exact capture. Removing the extension clears its browser-local storage according to your browser's extension-data behavior.

Account linking and synchronization

Linking the extension is optional. When linked, ApplyQuest stores a revocable device credential in extension storage and returns your account email for the linked-status display. Receipt checks send only bounded capture identifiers and cryptographic fingerprints to https://applyquest.quest so exact accepted captures can be cleared locally.

The extension cannot create application records or award leaderboard points. When you copy its agent prompt, the selected capture details enter your clipboard. Your chosen agent and the ApplyQuest CLI then show the proposed records and synchronize them only through the audited account workflow.

On the My Quest page at https://applyquest.quest, the extension can return the same bounded capture prompt to that first-party page after the page proves it belongs to your linked account. Preview domains and unrelated websites cannot request this prompt.

Website records and public activity

Private job-queue records can include official listing links, company and role, industry, location, work arrangement, posted or expected compensation, listing and discovery dates, recommendation scores, match confidence and reasons, status, and audit information. ApplyQuest uses them to show your read-only queue and let your authorized agent preserve identities, deduplicate listings, and synchronize only new or changed recommendations.

Private application records can include job links, stages, process history, location, compensation, notes, contacts, and audit information. ApplyQuest uses them to provide your tracker, exported CSV, progress totals, and fraud-resistant audit history.

Public leaderboard totals do not expose your private tracker. Company and role appear in public activity only after version-1 consent. Job link, location, and expected salary appear only after the separate version-2 application-details consent. Notes, email, account details, exact event times, and deleted-application metadata remain private.

Use, sharing, and retention

• We use job-search data only to provide ApplyQuest features, maintain security, prevent duplicate records or scoring, and respond to support or legal requirements.
• We do not sell personal information, use it for targeted advertising, or allow unrelated human review.
• Service providers may process data only as needed to host and deliver ApplyQuest under their applicable safeguards.
• Account records remain until you delete or correct them through the authorized workflow, subject to limited security, audit, backup, and legal retention.

Your controls

You can leave the extension unlinked, discard any unsynchronized capture, unlink a browser, revoke agent or device access, change public-activity consent, export your private applications as CSV, or delete your ApplyQuest account. Store-listing support channels can be used for privacy questions and deletion help.

Security and changes

ApplyQuest uses HTTPS, scoped credentials, server-side ownership checks, bounded requests, replay protection, and privacy-specific data projections. No system can promise absolute security. Material policy changes will be posted here with a new effective date, and extension permissions that materially expand access require browser review and user approval where applicable.