JOBI
JOBI - Don't apply more. Apply better.
Privacy Policy
This policy explains how the JOBI Chrome extension and dashboard handle your information.
Last updated
Scope
JOBI is a job-search assistant. It helps you save job postings, organize your application pipeline, analyze a posting, create application drafts, and fill fields only when you choose to use those features. This policy applies to the Chrome extension and the JOBI dashboard.
Information we handle
- Account information. Your Google sign-in identity, including your email address, display name, and authenticated account identifier.
- Job-page context. After you explicitly allow page access, the extension reads the active page's URL and title. When you request a page-based feature, it may read relevant job-posting text, page structure, application-form labels and values, and a screenshot of the current page.
- Career and application content. Information you choose to save or upload, including job records, job status, profile details, resumes, cover letters, notes, prompts, contact details, chat questions, and generated drafts.
- Service records. Data needed to operate the service, such as saved-job timestamps, membership state, and feature-usage or token-budget records.
JOBI does not request access to browser history, cookies, saved passwords, or Google data beyond basic sign-in identity. Password input fields are excluded from form-field collection.
Optional email recommendations, direct search and Chrome collection
When you enable JOBI recommendations, a personal receiving address accepts your job alerts and forwarded job emails through our receiving provider, Resend. Supported job links are separated, deduplicated and analyzed with your enabled profile sources. This uses your account's analysis allowance.
If you separately enable Chrome auto collection in the extension and grant Indeed/LinkedIn access, Firebase Cloud Messaging wakes JOBI when a posting needs browser access. While Chrome is open, JOBI opens one inactive job tab at a time, reads the job title, company, location and description, then sends that text to the JOBI backend and configured AI service. This does not collect your unrelated browsing history, screenshots or form answers. JOBI closes only its own inactive job tab; tabs you activate or navigate elsewhere are preserved.
When you enable Indeed direct search in My dashboard and request a search, JOBI stores your chosen keywords, location, radius, recent-posting period and search depth with your account. A compatible, enabled Chrome extension opens the requested search-result pages in inactive tabs and sends individual job links to the backend for duplicate checks. New postings use the same browser collection and analysis flow described above, within your selected depth and account allowance. The latest search progress is stored so you can check it or stop the run. Email collection and direct search have separate controls.
You can turn collection off in My dashboard or the extension. Login and security verification require manual action. Push delivery, browser connectivity and site access can delay processing. Failed retrieval is not charged as a successful analysis. Pending intake and billing receipts are normally retained for up to 90 days, and email processing receipts for 30 days; selected saved jobs remain until you delete them.
How we use information
We use the information above only to provide and maintain JOBI's user-facing features:
- authenticate you and keep your dashboard data associated with your account;
- save, display, update, and delete your job-search and profile records at your direction;
- analyze a job posting, answer your job-context questions, generate drafts, and suggest form values; and
- protect the service, enforce configured access limits, and resolve technical issues.
When information is shared
JOBI uses Google Firebase services for authentication, data storage, and callable backend functions. When you request an AI-assisted feature or enable automatic job recommendations, the relevant job-page context and enabled profile context are sent through the backend to the AI provider configured for JOBI, which may be Google Gemini, OpenAI, OpenRouter, or Skaia. These providers process that content to return the feature output you requested.
We do not sell your personal information or page-browsing data, and we do not use it for personalized, retargeted, or interest-based advertising. We do not transfer it for unrelated purposes.
Your choices and deletion
The extension asks for a specific page-access choice before it reads active-page metadata. You can use the extension's Stop access control at any time to prevent future page-context reads; this also clears the active page context used for new extension actions. You can delete saved jobs, profile records, prompts, and uploaded profile sources from the dashboard.
To request account-level deletion or ask a privacy question, contact the support address shown in the JOBI Chrome Web Store listing.
Chrome Web Store Limited Use
JOBI's use and transfer of information received from Chrome APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. Page context is used only for the features you request, such as saving, analyzing, discussing, or assisting with the current job page.