Privacy Policy — Apply Assistant
Last updated: 2025-08-01
Apply Assistant is a Chrome extension that helps you scan a company or job page you're viewing, draft a tailored cold-application email using an AI language model, and send or open that email through your own mail client or Gmail account. It also offers optional autofill for job-application forms and a personal, local tracker for the applications you've sent. This policy explains what information the extension accesses, what is stored only on your own device, what (if anything) is sent elsewhere, and why.
Overview
Apply Assistant is designed so that most of your data — your resume, your autofill profile, your application tracker, and your settings — stays on your own device in Chrome's local extension storage. Data only leaves your device when it's necessary to perform an action you explicitly requested, such as generating an email draft or sending mail through your own Gmail account. We do not sell your data, and we do not use your data for advertising.
Information We Collect
Stored locally on your device
The following information is saved using Chrome's built-in storage APIs
(chrome.storage.local / chrome.storage.sync). This storage lives in
your own browser — it is not a server or database that the developer operates or has access
to.
- Resume / profile: a freeform text summary of your background, and optionally an uploaded resume file (its name, file type, size, and content encoded as base64). This is used only to help the AI tailor drafts and score job matches, and is never automatically attached to any email that gets sent.
- Autofill profile fields: information you enter yourself — name, email, phone, location, LinkedIn/portfolio URLs, years of experience, notice period, and CTC — used only to fill in job-application forms when you click "Autofill".
- Your own Gmail OAuth tokens (access token, refresh token, expiry), only if you choose to connect your Gmail account directly. These tokens are exchanged directly between your browser and Google; the developer never sees or receives them. They're stored locally so the extension can send mail on your behalf.
- Apply Assistant Cloud sign-in session: a session token issued by our backend, along with your account email and plan tier, used to authenticate your future requests to the backend.
- Application tracker: a locally-stored list of jobs you've drafted or sent applications for (company, role, job URL, recipient email, status, notes, timestamps). This is a personal organizer feature only — it is never transmitted anywhere.
- Basic settings: which AI provider is active, your mailto/Gmail send preference, and the backend URL in use.
Sent to our backend / third parties
Data leaves your device only in the following specific situations:
- Drafting an email via Apply Assistant Cloud (the default mode): the scraped page text (job posting or company page), your resume/profile text, and your chosen tone are sent to the Apply Assistant backend, which forwards them to an AI language model provider (such as Groq) to generate the draft, then returns the result to you. The backend also tracks how many drafts your account has used per month, to enforce the free-tier monthly cap, along with your account email and plan tier.
- Sending mail via your connected Gmail account: the composed email (recipient, subject, body) is sent directly from your browser to Google's Gmail API using your own OAuth token. Our backend is never involved in this send.
- Signing in with Google (Cloud mode): Google verifies your identity (email address) via OAuth. Our backend never receives your Google password — only a short-lived authorization code, which is exchanged for a token.
- Community-verified HR emails (optional, opt-in, signed-in Cloud users only): if you actually send or compose an email to a company contact address, that address (and the company's email domain) may be reported to our backend to help other users find verified contacts at the same company. Only addresses you have actually chosen to use are ever reported — never every address a page scan happens to find.
- Standard request logs: our backend logs basic request metadata (timestamps, rate-limit counters) for abuse prevention and to enforce the free-tier monthly draft cap.
What we do not collect
- Browsing history outside of pages you explicitly scan with the extension.
- Your Google password (Google Sign-In never exposes your password to the extension or our backend).
- Payment information (the extension does not process payments).
- Any data from tabs you haven't actively used the extension on.
Permissions We Request and Why
| Permission | Purpose |
|---|---|
activeTab & scripting |
Read the content of the tab you currently have open — the job posting or company page text — only when you click an explicit action like "Scan this page". The extension never runs automatically or in the background. |
storage |
Save your settings and data locally on your own device (see "Stored locally" above). This is local browser storage, not a hosted database the developer can access. |
identity |
Support Google Sign-In so you can authenticate with Apply Assistant Cloud, and, if you choose, connect your own Gmail account to send email directly. |
sidePanel |
Let you optionally open the extension UI in Chrome's resizable side panel instead of the popup. This has no effect on what data is collected. |
Host permissions (domains the extension can talk to)
| Domain | Why |
|---|---|
api.groq.com |
The Groq AI API, used to draft emails when running in a "bring your own key" mode (not enabled by default — the extension normally routes drafts through our backend instead). |
localhost:8787 |
The Apply Assistant Cloud backend. During development this is localhost; in production it points to our hosted backend on Render. |
ja-extension-backend.onrender.com |
The production Apply Assistant Cloud backend — handles AI-drafted email generation, account authentication, and optional community-verified HR email lookups. |
gmail.googleapis.com |
Used only if you explicitly connect your own Gmail account (using your own Google OAuth credentials) to send email directly from the extension. |
oauth2.googleapis.com |
Google's OAuth token endpoint, used for both Google Sign-In (Cloud) and the optional Gmail connection. |
*.linkedin.com |
Allows the extension to read job-listing pages on LinkedIn when you are on linkedin.com and choose to scan or load companies from that page. |
Third-Party Services
Apply Assistant integrates with the following third-party services. Our use of them is governed by this policy, but once data reaches them, their handling of it is governed by their own privacy policies:
- Google (Sign-In and Gmail API) — used for authentication and, optionally, sending email through your own Gmail account. See Google's Privacy Policy: https://policies.google.com/privacy.
- Groq — an AI language model provider used (via our backend, or directly if you enable "bring your own key" mode) to generate email drafts. See Groq's Privacy Policy: https://groq.com/privacy-policy/.
Data Retention & Your Choices
Data stored locally on your device — your resume, autofill profile, application tracker, settings, and tokens — can be cleared at any time from the extension's own Settings page (for example, using "Remove resume"), by uninstalling the extension, or by clearing your browser's extension data.
For data held on our backend — your account email, plan tier, monthly usage counters, and any reported HR contact email addresses — you can request deletion at any time by contacting us at the email address below.
Children's Privacy
Apply Assistant is not directed at children under 13, and we do not knowingly collect data from children under 13.
Changes to This Policy
We may update this policy as the extension changes. The "Last updated" date at the top of this page reflects the most recent revision.
Contact Us
If you have questions about this policy or want to request deletion of backend-held data, contact us at anurazzz.mishra098@gmail.com.