Privacy Policy

This policy describes what data Fulltime Job Applier collects, how we use it, and the choices you have. It applies to our websites (jobapplier.app and app.jobapplier.app) and our Chrome extension (together, the “Service”).

In plain English: the Service is an AI assistant that lives in your own Chrome browser and helps you complete job applications. It reads the page in front of you, fills application forms from your saved profile, drafts tailored answers, and takes page actions you ask for in its chat panel. It works only in your browser, only on the tab you open it on, and it fills only job applications — we do not apply to jobs from our servers, and you are the one who submits every application. We hold the minimum data we need, encrypt sensitive things, and never sell anything to third parties.

A small launcher control is present on every page; it reads nothing on its own. That control (a button, usually docked to the side of the page) lets you start the assistant from wherever you are — it does not watch your browsing, send anything to our servers, or read the page until you click it. The assistant becomes active on a tab only when you invoke it there — from that in-page button (which can fill the page immediately with one click), the toolbar button, the side chat panel, or the keyboard shortcut — and its access ends with that tab.

What it reads, and what it will do, are different questions. On the tab you opened it on, the assistant can read the page and answer your questions about it, whatever the page is — that is how it can tell you what a page is, whether a role fits you, or what a posting actually says. Filling, clicking and attaching happen only on job applications. It identifies applications by reading the page, not from a fixed list of websites, which is why it works on employers’ own career sites as well as on the large applicant-tracking platforms.

To answer you or fill a form, the extension sends our servers the text and form structure of that page — the questions, answer options, and field structure, and enough of the page’s visible text to understand what it is. We send only the page you have the assistant open on. We do not send your browsing history, your other tabs, or pages you have not opened it on. The resulting fill actions (typing, selecting, clicking) all happen locally, inside your own browser session.

How the assistant gets faster over time. The first time it meets a given question on a given employer’s form, it may need to think through the answer. To avoid re-doing that work for you next time — and for the next applicant who meets the same question — we retain the question’s structure (the question asked and the options a form offered, which are the same for every applicant) together with a short, de-identified sample of the kind of answer that resolved it. This shared recognition store is not linked to your account or identity, and self-identification questions (race, gender, disability, veteran status, sexual orientation) are always excluded from it. Because it isn’t linked to you, it also isn’t something an account-deletion request can reach or remove — deleting your account removes your profile, answers, and history, but not these de-identified, cross-user entries. Separately, we keep de-identified per-employer fill rules — which kind of profile fact drives which field, and which option text a form accepted — on the same basis.

Account data. Email address (your login), authentication tokens, and your plan. We do not ask for or store a phone number.

Profile data. Information you choose to provide so the Service can fill applications — name, contact details, work history, education, skills, work-authorization status, screening answers, and resume file.

Career-site credentials — none. The Service does not ask for, receive, or store the passwords you use on career sites. Where a site requires an account (for example some Workday employers), you sign in yourself in your own browser; the assistant waits. Your career-site credentials never pass through us.

Your Job Applier sign-in. To sign in to your own Job Applier account from the dashboard or from the extension’s side panel, you enter your email and password. They are sent directly to our authentication provider (Amazon Cognito) to obtain a session token; we do not store your password, and the extension keeps only the resulting session tokens, which are removed when you sign out.

What the extension reads from a page. Only on a page where you have asked the assistant to work — by clicking the launcher, opening the panel, or starting a fill. On any other page the only thing present is a launcher button, which reads nothing and sends nothing. When you do invoke it, we receive:

• the address of the job page, and the visible text of the job posting, capped at 6,000 characters;
• the structure of the application form — each field’s label, its type, and the answer options it offers;
• the values already in those fields, so the assistant does not overwrite or duplicate an answer you already gave, capped at 300 characters per field;
• the answers the assistant produces or you supply, and your chat messages about that application.

Diagnostic records — and what we deliberately do not keep. When a fill runs we record which fields the assistant found, what it decided for each, and whether the page accepted it, so we can tell a bug from a page we have not learned yet. We do not store a copy of the page: the page’s own HTML and the full text reading of it are used in the moment to check the assistant’s work and are then discarded, never written down. A page can contain far more than your application — anything already filled in, anything the employer shows about you — and the cheapest way to protect it is not to have it. If you report that the assistant failed on a page, we reproduce the problem on that page ourselves rather than reading a stored copy of yours.

Application history. Records of the applications you completed with the assistant — the jobs, the answers used, and timestamps — so you can review them on your dashboard. You can export or delete this any time.

What we don’t collect. No career-site passwords, no payment-card details (those go directly to our payment processor), no browsing history, no record of pages you did not invoke the assistant on, and no microphone, camera, location or contacts.

The Service gets better by remembering two very different things. We keep them separate on purpose, and the difference matters to you.

1. Your answers stay yours. The answers you give or approve — screening responses, cover letters, work-authorization answers, anything from your profile — are stored against your account and reused to fill your future applications. They are not shown to, or filled in for, any other user. They are deleted when you delete your account.

2. How a form behaves is not personal. When the assistant works out how to operate an unusual control — a custom dropdown, a date picker, a typeahead — we record the technique: the kind of widget, the sequence of clicks and keystrokes that worked, and how long to wait. This is a description of a website, not of you. It contains no answers, no profile data, and nothing that identifies you, and it is what lets the assistant fill that widget instantly for everyone afterwards instead of working it out again.

3. Questions, and short answers, may be pooled — read this one. When a question on an application is one the Service could not answer from your profile, we record the question text so we can teach the Service to recognise it next time. Alongside it we may keep a small number of short example answers (at most five, each 80 characters or less) that users have given to that same question, so we can tell what kind of answer it expects. These examples are stored without any link to the account that provided them — we cannot tell whose they are, and neither can anyone else — but because they are not linked to an account, they are not removed when an account is deleted. Treat a short free-text answer as something that may be retained in this de-identified form. We do not do this with your resume, contact details, work-authorization status, or any answer longer than 80 characters, and we never use it to fill another user’s identity, legal, or demographic fields — the assistant is prohibited from guessing on those for anyone.

You may provide work-authorization / immigration status so the Service can answer work-authorization questions on applications accurately. We treat this as sensitive personal information, use it solely for that purpose, never sell it, and never use it for any unrelated purpose.

If you tell the assistant instead of the profile page. People often give a salary expectation or their work-authorization status by typing it into the chat mid-application rather than filling it in beforehand. That is fine, and it is treated the same way — but it lands in one extra place: the conversation itself, which is kept for 12 months like any other chat. If you would rather it were not, delete that conversation from the chat list; the answer you saved stays on your screening answers page, where you can edit or remove it separately.

Demographic questions (ethnicity, gender, veteran and disability status) are treated the same way, and more strictly in one respect: the assistant will never guess an answer to one, never infer it, and never fall back to “prefer not to say” on your behalf — that is an answer, and only you get to give it. These answers are never pooled across users.

We use your data to operate the Service: filling forms at your direction, tailoring cover letters and screening answers to specific jobs, answering you in the assistant’s chat, surfacing your application history on your dashboard, supporting your account, and improving how reliably the Service fills forms. We do not sell your data.

Job recommendations. We also use your profile, the jobs you have applied to, and the answers you have given to work out what kind of role suits you, so we can suggest jobs worth applying to. This is a use of your own data for your own benefit; it is not shared with employers, and it does not make decisions about you — it only orders a list of suggestions you are free to ignore. If you would rather we did not, email us and we will turn it off for your account.

AI providers. Free-text answers (cover letters, “why this company” responses, chat replies) are generated using AI. Only the context needed for each generation — the relevant question, the page’s form structure, and the relevant parts of your profile — is sent to our AI providers.

Zero data retention at the provider. Our AI provider processes each request under a zero-data-retention agreement: it keeps nothing after the response is returned, and may not train on it. That commitment is contractual with the provider rather than a per-request toggle, so we state it plainly here rather than implying a switch you could inspect. We send inference to one provider, not to a routing marketplace that could place your request with an endpoint under different terms.

We do not train general-purpose AI models on your data. Nothing the extension collects from your pages, and nothing from your profile or your answers, is used to train a general-purpose model, ours or anyone else’s. The learning described above is a lookup table of questions and form techniques, not a model trained on you.

We rely on a small number of service providers: our AI model providers; our payment processor (Razorpay, which handles card details and recurring charges — we never receive your full card number); cloud hosting (United States); and email/SMS delivery for verification codes. Each is bound to use your data only to provide their part of the Service.

Data is stored in the United States and encrypted at rest using industry-standard key management. Career-site credentials are never stored anywhere — we simply do not have them. Only authenticated requests carrying your token can read or write data attributed to you.

We hold two different kinds of data, and they have different lifetimes. A nightly job deletes anything past its window automatically — you do not have to ask.

Deleted on a schedule. Conversations you have with the assistant in the side panel are kept for 12 months from the last message in that thread, so your chat history stays available while you are job hunting — and you can delete any conversation yourself, at any time, from the chat list in the panel. Records of AI calls made on your behalf keep their accounting (which model, how many tokens, what it cost) for 90 days, but the text inside them — the prompt summary, the model’s reply and the results of the tools it used — is erased after 30 days, because a cost question needs the numbers and not the words. The per-run fill diagnostics tied to your account — what the assistant saw on the form, the answers it wrote and the actions it took — are kept for 90 days. Crash reports and model-comparison logs are kept for 90 days. Raw browser diagnostic logs are kept for 30 days.

Kept until you remove it. Your profile, your saved answers to application questions, and your application history are not deleted on a timer. They are what let the assistant fill the next application correctly without asking you the same questions again, so deleting them silently would degrade the service you paid for. They are removed when you delete the individual record, or when you ask us to delete your account.

After account deletion. We remove all rows associated with your user id within 30 days, and encrypted backups may retain copies for up to 90 days before being expired. Two things survive, and we would rather name them than let you discover them:

• Plan and payment records. Records of subscriptions, charges, refunds and usage are retained as financial records where the law requires us to keep them. Those rows keep only an account identifier — no name, email, or application content — and are still included in any copy of your data you request.
• De-identified question and form knowledge. The pooled question text, the short example answers described above, and the widget techniques carry no link to any account, so there is no way to find and remove “yours” — deletion works by account id and these rows have none. They are also not returned by a data export for the same reason. If this concerns you, avoid typing anything into a free-text application field that you would not want kept in de-identified form.

Export. Download a copy of your profile, application history, and any answers you have given from the dashboard at any time.

Delete. Delete individual records (a saved answer, a resume, an application) yourself from the dashboard at any time. Deleting your entire account is handled by our team rather than a self-service button, so a deleted account can’t simply be recreated to restart a free trial — email admin@jobapplier.app and we process it promptly. See “How long we keep data” above for exactly what is removed, when, and the categories that aren’t reachable by an account-deletion request.

Pause or stop. The assistant acts only when you start it, and you can stop it at any time using the Stop button in the extension or the Cancel button in the dashboard.

EU/UK and California residents. Standard GDPR / CCPA / CPRA rights apply: access, correction, deletion, objection to processing, and portability. Send requests to admin@jobapplier.app. The Service targets US-based users.

Job Applier's use and transfer of information received from Google APIs to any other app will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. Specifically:

• We use the data we collect only to fill job application forms at your direction and to show you your own application history.
• We do not sell it.
• We do not transfer it to third parties except as needed to provide the Service (the sub-processors listed above), or where the law requires it.
• We do not use it for advertising, and we do not build advertising profiles from it.
• We do not allow humans to read it, except with your explicit consent, for security purposes, or to comply with the law.

The extension does not attempt to solve CAPTCHAs or bypass any anti-automation measure. Where a career site presents one, the session pauses and you complete it yourself.

The Service is not directed at children under 16 and we do not knowingly collect their data. If you believe a minor has signed up, contact us and we will delete the account.

If we discover unauthorized access to your data, we will notify affected users by email within 72 hours of confirming the incident.

When we make material changes we will update this page and bump the version shown at the top. If you are an active user we will also email you and re-prompt for acceptance the next time you sign in.

The data controller for the Service is Subdrive Car Rentals Private Limited (CIN U63120TS2025PTC194096), operating as Fulltime Job Applier.
1-4, Sagar Canal Bridge, Kappalabandam, Kallur, Khammam 507209, Telangana, India
admin@jobapplier.app