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. Until you confirm it, the detected company, role, and canonical job URL are held only in browser session storage and are cleared when the browser restarts. 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.

Friends

Creating or accepting a friend invite requires permission to share new applications with that friend: company, role, and a supported public job-posting link. Earlier applications, notes, salaries, locations, account details, and exact timestamps stay private. Removing a friend stops access through ApplyQuest; it cannot erase information they already saw or copied.

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 private recommendations and, when native Jobs is enabled, let you save, compare, dismiss, or mark recommendations applied. An authorized agent can also preserve identities, deduplicate listings, and synchronize 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. In the friend beta, public participation can show your handle, companion, rank, score, streak, goals, milestones, and application totals. It does not publish company, role, job link, location, salary, notes, contacts, email, account details, exact event times, private sources, or deleted-application metadata.

Product growth and advertisement links

ApplyQuest uses aggregate account, tracker activity, and application totals to understand product growth. The private owner dashboard does not display names, emails, individual application counts, or individual histories. Application-stage ranges use the optional broad-market contribution setting, contributor thresholds, and delayed publication described below.

We count accepted advertisement-link requests in anonymous daily totals for each campaign, including repeat visits. Opening a tagged advertisement link sets a first-party cookie for up to 30 days to remember the first campaign opened in that browser. The server stores a hash of that random token, the campaign, and its arrival time; expired visit tokens are removed by scheduled cleanup. If you create an account in that browser during the window, the campaign is associated with the account to calculate aggregate signups and first-application activation. This association is deleted when the account is deleted. Anonymous daily arrival totals and previously released stage ranges remain. Campaign reports do not contain personal application details, IP addresses, browsing histories, or advertising-platform identifiers.

Optional Quest Groups

Quest Groups are private, invitation-based groups. Before someone joins, a person with a valid invitation link can see the group name, the inviter's handle, the member count, and the current members' handles.

After you join and accept the group sharing terms, active group members can see your handle, companion, leaderboard points, application counts, weekly goal progress, and streak. Named activity shows only your handle, company, role, application stage, and a broad time bucket such as today, this week, or earlier. It does not show application notes, contacts, compensation, job links, location, private sources, or exact event times.

Group sharing covers future eligible activity. You can separately choose whether to include eligible history when joining. Leaving a group or being removed stops the group view from returning your shared entries, but it cannot make another member forget information they already saw.

Optional delayed market totals

The Share broad market totals setting can contribute eligible company, role, stage, and matched public-listing facts. ApplyQuest does not put your name, full application, exact time, notes, salary, private source, or application history into an aggregate release.

ApplyQuest publishes ranges instead of exact counts and releases a bucket only after at least five distinct people contribute to it. Releases use completed hourly windows and remain at least one full hour behind current activity. The contributor threshold may be higher when the participating population grows.

Turning this setting off or deleting your account excludes your data from future releases. Prior releases are immutable and are not recalculated or withdrawn, so a contribution that was already included cannot be removed from that released range. These controls reduce disclosure risk but do not guarantee anonymity.

Optional external AI interview guides

If you choose to generate an interview guide while an external AI provider is configured, ApplyQuest sends these application fields: company, role, official listing URL, location, work arrangement, and current application stage. A generated request identifier, the configured model, and guide instructions may also be sent as operating metadata. The provider may use limited web search to research current public information about the employer and role.

ApplyQuest does not send the provider your account email, handle, private application notes, recruiter context, contacts, compensation, full process history, other applications, or your ApplyQuest application identifier. ApplyQuest stores the returned guide and bounded usage information needed to deliver and account for the feature. If no external provider is configured, the external guide request fails closed rather than sending data elsewhere.

Use, sharing, and retention

• We use job-search data only to provide ApplyQuest features, measure aggregate product growth, 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 in the active service until you delete or correct them, subject to the retention limits below.

Your controls

You can leave optional features off, discard any unsynchronized extension capture, unlink a browser, revoke agent or device access, change public participation, stop future aggregate contribution, leave a Quest Group, export your private applications as CSV, or delete your ApplyQuest account.

Self-service account deletion is available in Settings. It requires an acknowledgement and a separate final confirmation before ApplyQuest consumes the protected deletion request. Confirmed deletion removes the account and its linked active-service data, including the private tracker, profile, settings, Group memberships and owned Groups, connected agents, browser connections, and sessions.

Limited security, audit, backup, or legally required records may remain for their applicable retention period. ApplyQuest does not publish a fixed deletion schedule for those retained copies during this beta. Previously released aggregate ranges remain under the immutable-release rule described above.

Friend-beta support

ApplyQuest does not yet publish a support email, support form, or browser-store support channel. To contact the person who gave you access, reply to the private message that contained your invitation for help with login problems, deletion failures, incorrect records, privacy questions, or feature failures. Do not send sign-in codes, passwords, private invitation links, or unnecessary application details in a support message.

Account deletion remains self-service in Settings and cannot be completed by sending a support message. Read the friend-beta support guide before reporting a problem or suspected privacy issue.

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.