Seeker Agent · Privacy & security
Your career information. Your applications. Your decisions.
Seeker Agent fills in employer application forms for jobs you choose. AI requests are built from a reduced copy of your information, and the final submit waits for you.
Limited beta. Not publicly available.
How it works
Four steps from match to decision
- 01
Choose a job
Start from a role you matched on Seeker. The agent works only on employers' own application pages and won't sign up for job boards.
- 02
Prepare the application
The agent opens the form in a browser on Seeker's machine. Known steps run as ordinary code. AI reads unfamiliar pages and drafts open-ended answers.
- 03
Verify information
Name, email, phone, address and links come from your account, your Application details, or a saved answer that passes a format check. AI never writes them; unverified fields stay empty.
- 04
Review and approve
You check drafts and the finished form. The agent stops at the final step and waits for your decision.
Data flow
Designed around data minimization
Your information crosses two boundaries: into Seeker, and out to an AI provider or an employer. Each destination receives a different subset.
- What you supply
- Your résumé file, the profile from your analysis, Application details (phone, location, links, work authorization), saved answers, and a self-identification preference. The résumé file also stays in this browser until you remove it.
- What Seeker keeps to prepare it
- Seeker's servers hold your analysis, Application details, saved answers and your 24 most recent runs. While an application runs, the agent holds a working copy of your profile, résumé and employer session, then keeps a minimal record.
- What may reach an AI provider
- Page structure, the question, the job, and the parts of your profile a draft needs. Details are in the next section.
- What is entered on employer sites
- Name, email, phone, location, links, work history and the résumé file for the job you chose. Work history is copied as written unless a field needs a shorter version, which you approve first.
AI assistance
AI with boundaries
Seeker Agent sends individual requests to Anthropic models. Each one is built from a reduced copy of the context, with unneeded values hidden by default.
01
Complete application context
02
Minimized relevant context
03
AI assistance
One request, one task
What a request can include
- Reading a page: field labels, required marks, control types and the options offered.
- Drafting an answer: the question, the job, your target role, work history, education, skills, projects, and up to 12 of your saved answers, not filtered by relevance. Your name, email, phone and links are not included.
- Matching a saved answer: the question, its choices, and up to five saved answers that look related. If none do, no request is made.
What is held back
- Contact details while the AI navigates a page. It sees placeholders such as
{{email}}; the agent types the real value. - Passwords, verification codes, card and bank numbers, SSNs, dates of birth, passport and licence numbers, shown only as
[redacted]. - Values the site pre-filled, shown only as filled. Cookies, session tokens and sign-in links. Self-identification answers and other users' data.
Work history and saved answers are personal information, and they are sent when a draft needs them. Pattern rules for secrets can't recognize every format on every site, so hiding by default is the main protection. Anthropic processes requests under its API terms.
Submission control
You're in control of what gets submitted
Preparing an application and submitting it are separate actions. The agent can fill every field. Only your approval, given for that specific application, lets it submit.
- No standing permission. No setting turns approval off, and an approval is never restored after a restart.
- Layered safeguards. Independent checks block an unapproved submit, including inside the page, so pressing Enter or a page script can't send the form. They are tested against saved Workday, Greenhouse, Lever and Ashby pages.
- Declining ends the task. Nothing else is clicked.
- Beta: submission is blocked. Seeker's website refuses final-submit approvals for now. The agent prepares the application and stops.
These layers reduce the risk of an unintended submit. They are not a guarantee.
Retention
Your information has a lifecycle
Each kind of data follows its own rule. When an application ends, the agent removes its working data on a schedule and keeps a short record.
- 1 Information provided
- 2 Active application
- 3 Task finished
- 4 Temporary data cleanup
Passwords you type
For an employer sign-in
Kept only in memory for that application.
Employer sign-in session
Cookies and site storage in your agent browser profile
Wiped when the application ends, unless Stay signed in is on. That is an agent setting in the beta, off by default, and not yet on the website.
Application working data
Profile copy, form values, work history, step details, résumé copy, captures
Removed 24 hours after the application completes or is cancelled, or 7 days after it fails so you can still apply by hand.
Minimal application record
Employer, job title, link, status, dates, outcome, AI calls and cost, counts
Kept as your history until you ask for it to be deleted.
Remembered answers (agent)
Answers reused on later applications
Only if Remember my answers is on: an agent setting in the beta, off by default. When off, answers are used for that application only.
Website and device copies
Résumé on this device, Application details, saved answers, 24 recent runs
Kept until you remove them or ask us to. Run history keeps only your 24 most recent runs.
Diagnostic captures
Raw page captures, off by default
Owner-only access. Deleted after 7 days unless held as evidence for an incident.
If a run is interrupted
After a restart, the agent resumes recent unfinished tasks, checks what the employer kept and redoes only what is missing. A pending question comes back; an approval does not. If Seeker can't confirm an application arrived, it says so instead of guessing.
Deleting your data
Email support@seekerscore.com. One request removes all your agent data, including application records, saved answers and your browser profile. If you're in the Agent beta, you'll also find the résumé on this device and your saved answers in Settings.
Before you submit
Employers' systems often save drafts as a form is filled in. Fields the agent entered may stay with the employer even if you never submit, under that employer's privacy policy.
Security
Security principles
- Isolated agent storage
- Agent data is readable only by the agent's own system account. Profiles and saved answers are separated per user.
- Passwords handled once
- Agent-created passwords are stored encrypted and handed over once through a pickup that expires after 48 hours if unclaimed. They are not emailed or logged. Seeker keeps the username, not the password, to avoid duplicate accounts.
- Your identity accounts stay yours
- Seeker refuses to pass a password to a Google, Apple or Microsoft sign-in page.
- Self-identification is never inferred
- Gender, race, veteran and disability answers come only from your stated preference, and are not kept with saved answers.
- Shared links omit your résumé
- Results links show others the analysis without résumé details. Only your account or uploading browser sees the full view.
- A browser that keeps little
- The agent's browser keeps no form-entry history, saved addresses, cards, passwords or browsing history. Agent logs rotate daily and are kept 14 days.
- Email goes to your account
- Follow-up reminders require sign-in and go only to your account's address.
Not finished yet
- The agent runs as one supervised service for a small beta. Isolation for many concurrent users is not complete.
- Password reset has been tested on practice pages, not on a real employer site.
- Automatic cleanup covers applications that ended after it went live. Older records are being cleaned up after review.
- Remember my answers and Stay signed in can't be changed on the website yet, and deletion has no self-service button.
FAQ
Questions
Does my résumé reach a server?
Yes. Seeker's servers analyze it, the agent receives a copy for each application you start and removes it with that application's working data, and it is uploaded to the employer you apply to. A copy also stays in this browser until you remove it.
Can the agent submit without me?
Submitting requires your approval for that specific application, and the beta blocks final submission entirely.
Can an employer keep what the agent typed?
Yes. Many application systems save drafts as you go, so entered fields may be kept even if you never submit. The employer's privacy policy governs that data, and Seeker can't delete it. Contact the employer to remove a draft.
Does Anthropic keep my data?
Requests are processed under Anthropic's API terms. Seeker doesn't control their retention.
How do I delete my agent data?
Anyone can email support@seekerscore.com. One request deletes your applications and their data, saved answers, employer-account records, pending password pickups, uploaded résumés, captures and your agent browser profile. During the beta, Seeker staff run it for you, once no application is in progress. There is no self-service button yet. If you're in the Agent beta, you'll also find controls in Settings: remove the résumé on this device under Application details, and delete saved answers under Saved application answers, which clears Seeker's copy and the agent's. Account and résumé analysis data are covered by the Privacy Policy.
This page covers Seeker Agent. The Privacy Policy covers the rest of Seeker. Questions or deletion requests: support@seekerscore.com. Updated .