Information we process
- Account information: your email address, name and, when provided by a sign-in service, profile image and account identifier. Sign-in uses email links, configured Google sign-in, or a separately provisioned review-account password. Passwords and API keys are stored as hashes; authentication tokens are used to maintain approved access.
- Connection information: the assistant’s OAuth client identity, the permissions you approve, consent records and refresh/access credentials.
- Job-search inputs: the filters your assistant or browser sends, such as role, seniority, broad hiring region, technology and salary preference. The MCP API has no input for full chat histories, resumes, precise GPS locations or government identifiers.
- Usage and security information: daily job and request counts, API-key request times, session IP addresses and user-agent information. Hosting infrastructure may also process IP addresses, request paths and operational errors.
- Optional features: email addresses and search preferences for job alerts, issue reports you submit, and correspondence you send to support. Saved jobs and tools that use browser storage remain in that browser. The free tools run in your browser unless you choose an AI action: then the text in that tool is sent to our AI provider, Anthropic (Claude), to generate the result. Anthropic does not use it to train models, and PickedJobs does not store it. We keep only a record of the run (tool, time, size and cost) and a credit count per account, or per browser for the free guest try, using a random browser cookie. Guest saved searches stay in browser storage; signing in merges them into your account. Signed-in saved searches and their optional email-alert preferences are stored with your account and available across devices. Alerts go only to your verified account email.
Why we use it
We use this information to sign you in, operate the job board and assistant tools, enforce account allowances, send requested sign-in links and job alerts, investigate errors and abuse, respond to support requests and honor your privacy choices. The application records daily usage totals rather than a per-account history of MCP search text.
We do not request or reconstruct your full assistant conversation. Your assistant chooses which tool arguments to send. Keep requests limited to the details needed for a job search; do not send passwords, API keys, health information or unrelated personal data as search text.
Who receives information
The assistant you authorize receives job results and your account’s remaining allowance. OAuth identity scopes may also allow it to retrieve your name and verified email address. Those providers handle your conversations and linked-account information under their own policies.
Our hosting, database, search and infrastructure providers process data to operate the service. Cloudflare handles network delivery and cached assets. Configured email delivery uses AutoSend. Google receives information when you choose Google sign-in. Anthropic receives the text in a free tool when you choose an AI action there. The website uses our Umami analytics instance to measure pages, search filters, visible job listings, employer-link clicks, feature use and page performance. Signed-in activity can be associated with your internal account identifier across visits. Separate server counters measure application-link redirects and assistant/API requests; they do not include assistant conversations or search text. Authentication tokens, email addresses, resumes and private tool inputs are excluded from analytics. Session replay recording is not enabled. The browser analytics script is not part of MCP tool responses.
PickedJobs does not have a tool that sends your information to an employer or submits a job application. Following an application link takes you to the employer or its applicant-tracking service, where its privacy policy applies. Support correspondence is handled through our email provider. We do not sell account information.
Retention
Account profiles, daily usage records and account-linked authentication records are retained for the lifetime of the account and until a verified deletion request is completed. An assistant’s consent and refresh access are removed when you disconnect it. API-key records are removed when you revoke a key. Some expired authentication records may remain until cleanup or account deletion; token expiration is an access limit, not a promise that every database record has already been erased.
Website sessions normally expire after seven days, sign-in links after fifteen minutes, and MCP access tokens after one hour. Refresh access can be renewed while the connection remains approved. These expiry periods do not prevent you from revoking access sooner.
Email alert subscriptions remain until unsubscribed or deleted; queued and delivery records support sending and troubleshooting those alerts. Browser-only collections remain until you remove them or clear the browser’s site data. Infrastructure logs, support correspondence and backup copies may be retained separately for operational, security or legal purposes; email us for current provider-specific retention details or a deletion request.
Your choices
In Account settings, view usage, disconnect assistants and revoke API keys. Disconnection blocks new MCP requests immediately; requests already in progress may complete. Manage saved searches and their alert preferences in Saved. Removing an account search also removes its alert and queued deliveries. You can unsubscribe using an email management link while keeping the saved search. To stop browser analytics requests, use your browser’s tracking/content controls. Clearing site data removes browser-only saved collections and signs you out.
For access, correction, export or deletion, contact [email protected] from your account email. We verify ownership before taking action. Account deletion removes account-linked profiles, grants and usage records from the active service; some records may need separate handling, and backups or legally required records may remain until their retention periods end. Information already received by an assistant provider is governed by that provider’s controls.
Contact and changes
Send privacy questions to [email protected]. We update this page when the service’s data practices change and show the effective date above. The assistant guide explains connection permissions and usage.