Privacy

Your account. An email address, and your name and sign-in identity from Google or LinkedIn if you sign in with one. Passwords, when you use them, are handled by our authentication provider and never reach our servers.

What you enter. Applications, companies, roles, contacts, interactions, notes and reminders: the working record of your search.

Job descriptions you paste. When a career site won't let Artemis read a posting and you paste its text instead, we read that text to fill in the role. The posting taken from it joins the shared index like any other posting; the text you pasted is kept with that request, on your account. Copy just the posting: a page can also show things like your name if you were signed in there.

Documents you upload. Résumés and cover letters, in private storage scoped to your account. Other users cannot read them; access is enforced by the database, not only by our application code.

Voluntary self-identification. If you choose to fill in demographic fields for application forms, they are stored under their own access rules and are never included in any request to an AI model. Declining is a stored answer in its own right; it is not the same as leaving the field empty.

The Artemis extension for Chrome is not in the Chrome Web Store yet. A small group of early testers uses it now, and this section describes what it does for them. It is optional: it reads the job posting you are looking at and fills in the application form with you. It is the part of Artemis that runs inside other companies' websites, so it is worth being precise about where it runs and what it moves.

Where it runs. The application systems employers use: Greenhouse, Lever, Ashby, Workday, Workable, SmartRecruiters, Oracle and Oleeo. LinkedIn. A set of job boards, where it only reads the posting you are looking at: Handshake, Indeed, Glassdoor, ZipRecruiter, Monster, Dice, Built In, SimplyHired, Simplify, Welcome to the Jungle, Levels.fyi, Wellfound, WayUp, RippleMatch, Jobright, Y Combinator's job pages, USAJOBS, Idealist, The Muse, eFinancialCareers, and school career centres on Symplicity and 12twenty. And the hosts Artemis itself runs on: this website, where the extension picks up your sign-in so you never type a password into it, our API, and our own database project. That list is compiled into the extension, and Chrome lists it under the extension's site access. It does not run on any other site unless you turn it on for that site, one site at a time, in Chrome's own prompt, and you can switch a site off again in the side panel.

What it reads from a posting. The role title, employer name, description text, location and posting date: the employer's own listing, and nothing of yours. That posting is sent to us and joins a shared index used by everyone, which is why it must contain no personal information; the same posting captured by two different people is one record. This includes postings on pages that need a sign-in, such as a school's career centre; only the posting is taken, not anything about you on that page.

The addresses it sends. When you open a job posting on one of the sites above while signed in, the extension sends that posting's address to us to check whether it is already in your tracker, so the panel can show its status. When a posting's own Apply button takes you to an application page, that page's address is saved on your tracker row for the job, so it is recognised next time. It never sends the address of a search or results page, or of any other page, and it does not read your browsing history. The lookup does not add anything to your account; a posting becomes part of your tracker only when you save it or apply.

What it types into a form. Your profile answers and the résumé you picked. It fills what it can match with confidence and lists what it could not, so you finish those fields yourself. The résumé file is downloaded from your private storage into the extension and attached to the employer's form; it goes to that employer, as it would if you had attached it yourself. Assisted is the default: Artemis fills, you read the form, and you press submit. Auto-submit is a setting you choose, and in that mode the extension also presses submit; that is the only way anything in Artemis submits an application for you. It never signs in to an employer's site for you.

Forms on job boards. The extension fills no form on a job board, with one exception: on RippleMatch's own posting page, when you press Autofill, it fills your name, email, phone and work-authorization answers from your profile. It leaves the résumé upload, the account password, consent and marketing boxes, the other questions and the Submit button to you, even when you have chosen Auto-submit.

Demographic questions are left blank by default. Employers' forms often ask about race, gender, sexual orientation, veteran status and disability. Artemis fills those only if you turn self-identification on yourself. While it is off, those values are stripped inside the extension's background worker and never reach the page at all: the protection is that they do not travel, not merely that a field is skipped.

People you save from LinkedIn. When you ask it to save a contact from a LinkedIn profile, the extension reads the name, headline, employer, location and profile address shown on that page and stores them as a contact under your account. That is information about someone else; it is kept for you alone and never shown to other users. It fills no forms on LinkedIn.

What stays on your computer. The extension keeps your settings, your sign-in tokens and a short local history of what it did in your browser's own extension storage. Chrome extensions have no encrypted storage, so anyone with access to your computer profile could read it, the same as your saved passwords. Removing the extension removes all of it. Deleting your Artemis account does not reach this copy, because it lives on your machine, not on our servers, so uninstall the extension as well.

Usage events. The extension sends us three usage events: a form finished filling (how long it took, how many fields it wrote, and whether you or Artemis was going to press submit), a tailored résumé copied, and an AI intro copied. They carry ids, counts and those fixed labels only: no page text, no addresses of pages you visited, nothing you typed. They are on by default. To turn them off, open the extension's Settings and switch off “Share how you use Artemis” under Privacy & data; nothing else changes when you do. The events appear in your data export, and if you delete your account they are kept without your id, as product totals. That switch covers what the extension reports on its own. What the service itself does for you, such as saving a job or drafting a letter, is recorded on our side whether the switch is on or off, and is described under “What we store”.

Limited use. What the extension reads from the pages you visit is used only to provide the features described here. We do not sell it, we do not use it for advertising, we do not build a browsing profile from it, and we do not use it to train generalised AI models. The extension reads a page only when that page is on one of the sites listed above or a site you turned it on for. The extension's use of information it collects adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Connecting Gmail or Outlook is optional, and you can disconnect either at any time. Outlook support is still in testing. We ask for the narrowest permissions that do the job rather than the broad ones:

• gmail.readonly / Mail.ReadWrite: to log mail to and from people in your contacts, and to read job-related messages so we can suggest tracker updates. On Outlook it is also how a follow-up you approved is saved as a draft just before it is sent.
• gmail.send / Mail.Send: to send a follow-up you reviewed and chose to send.
• calendar.events / Calendars.ReadWrite: to create an interview or coffee-chat event you asked for. On Outlook, the same permission is how we read your week when proposing times.
• calendar.app.created: to make one calendar of our own, so an invitation nobody has answered yet can sit there instead of on a calendar you already keep. It reaches no other calendar.
• calendar.freebusy: to read your free and busy blocks on Google Calendar when proposing times. It returns availability, not event contents.

Logged mail keeps its subject, not its text. When a message to or from someone in your contacts is logged on their timeline, we keep its subject line and date.

Job-related mail is read on our servers, and a short excerpt is kept. Suggesting an update, such as moving an application to Interviewing when an invitation arrives or adding the recruiter who wrote to you as a contact, needs more than a subject line. So for messages that first match on their sender and subject, the text is fetched into memory on our servers and checked against a fixed list of phrases. Nothing in your tracker changes until you confirm a suggestion. For each suggestion we keep the subject, up to the first 500 characters of the message, the sentence the suggestion is based on, the sender's address and when it arrived, so you can see why it was made. That record is visible only to you, is included in your data export, and is covered by account deletion below.

What reaches our AI provider. The text of your messages is not sent to an AI model. The subject lines of mail logged with a contact can be, when you ask for a follow-up draft to that contact or a summary of them, and they go through the same redaction as every other AI request. We have built an optional check that would send a short, redacted excerpt of an already matched message to our AI provider to confirm a suggestion; it is switched off.

Limited use of Google user data. Artemis's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Gmail or Calendar data to train generalised AI or machine-learning models, we do not sell it, and we do not transfer it except as needed to provide the features you asked for or as required by law.

AI features, such as fit checks, résumé tailoring, cover letters, follow-up drafts, interview prep and filling a posting from a link, use a third-party language model. Three things about that are worth stating plainly.

Personal details are removed before the request leaves us. Before anything goes to an outside AI model we strip email addresses and phone numbers and mask the names we know about (yours on your résumé, the recipient's on a draft), then put them back in the answer. A name that appears only inside text you typed is not detected automatically yet.

Our current model provider operates in China. Redacted request text is processed there. We are building toward running the model on our own infrastructure, which ends that transfer; until then, this is how it works and you should know it.

Ask Artemis keeps a conversation for 90 days. Ask keeps each question and its answer for 90 days, then deletes them. You can delete a conversation at any time, and deleting your account deletes all of them. Deleting a conversation also deletes the AI requests Ask made for it; the counts we keep for usage limits stay. A question goes to the model provider above with email addresses and phone numbers removed.

Matching by meaning runs on hardware we operate. To compare your background with job postings, the text of your profile, your résumé entries and your interview stories is turned into numerical vectors by a model running on a computer Artemis operates. That text is not sent to an outside provider for this, and it is not logged or kept on that machine; only the vectors are stored with your account, and they are deleted with it.

We do not use your data to train models unless you turn that on. That setting is off by default. We keep the text of AI requests and responses, except Ask's (above), so we can debug and improve prompt quality, and that retention is separate from training consent. Deleting your account removes the link between you and those stored requests; the text itself carries the same redaction the request did, and we keep it, because being able to look at a bad answer months later is how it gets fixed.

Job recommendations are computed from what you have told us: the skills in your profile, which Artemis can read out of your résumé, the industries, levels and locations you set as preferences, and the industries and companies of the applications you already track. A fit score compares a posting against your profile and résumé and shows you which factors drove it, so the reasoning is inspectable rather than a black box.

Job postings themselves are collected from employers' public career sites and are shared across all users; they contain no personal information of yours. Your profile is never exposed to other users, and we do not show your activity to employers.

Résumé tailoring and cover-letter drafting read the résumé you select plus the posting you are applying to, with personal details redacted before the request leaves us, and return a draft only you see. We keep the request and response text so we can debug and improve quality.

We use a small number of service providers, each for one job: application and database hosting, authentication and file storage, the AI model provider described above, Google and Microsoft for the integrations you connect, and a payment processor if you subscribe. We do not sell personal information, and we do not share it for advertising.

You can download a copy of your records from Settings at any time. You can also delete your account yourself from Settings. Deleting takes effect at once, and you have seven days to undo it. After those seven days the account is queued for permanent removal, apart from the redacted AI request text described above (Ask's is deleted with the account) and the records of what happened in the product (usage events and an audit log), which are kept without your account attached. If you want us to confirm that your account has been removed, email us at the address below.

Disconnecting Gmail, Outlook or your calendar in Settings deletes the access tokens we hold, so we can no longer reach that account. You can also remove Artemis's access from your Google or Microsoft account's security settings.

Data is encrypted in transit and at rest. Per-user isolation is enforced in the database itself, so a bug in our application code cannot expose one user's records to another. Access to production data is limited to what operating the service requires.

Questions, requests for a copy of your data, or anything you think this page gets wrong: tpk5369@psu.edu.

See also our Terms and Pricing.