Privacy Policy
Last updated: August 28, 2026
MemoryCV is operated by TwinBruhs LLC. Here’s what we collect, the providers that process it on our behalf, and how to get your data out or delete it. It applies alongside the Terms of Service.
What we collect
Everything below is data you give us to build your career memory; we do not buy data about you or track you across other sites.
- Account details: your name, email address, and password. The password is stored only as a salted hash, never in plain text.
- Career history facts you add through text chat, voice conversations, or career memory editing: roles, projects, skills, education, credentials, and preferences.
- Links you choose to make between a skill and the work that demonstrates it, picked from your own career facts. These are candidate-provided examples; we never present them as employer-verified.
- Voice intake audio and the conversation transcripts derived from it.
- Resume files (PDFs) you upload for fact extraction.
- Content the product derives from your facts: generated resumes, grounded application materials, job-match scores, and application records. An application record can include status and timeline events, private notes and contacts, submitted material, and the source and time you confirm.
- Immutable application evidence snapshots: the exact stored job and resume versions, selected export check evidence, and bounded copies of the career-fact excerpts, generated artifacts, and contact involvement needed to show what you say was submitted. Private jobs you capture also retain their owner-scoped company identity and assignment history.
- Bounded export check reports for resume exports, including the format, an exact file fingerprint, recovered-field counts, and any issue codes, short labels, or bounded expected-content excerpts needed to explain a missing or reordered result. We do not store the exported file or its recovered full text.
- If you connect the Chrome extension: the account-bound connection record; the current job page URL and title; job title, company, description, location, work setup, employment type, source, canonical, and apply links; observation time and extraction method; your edits to those fields; and explicit save, generation, Application Assist, and submission-confirmation actions. The extension does not collect general browsing history, cookies, sensitive or manual form entries, screenshots, or raw page HTML; if you explicitly choose “Read this page with AI”, or use a grounded Application Assist feature on a form whose job the companion cannot otherwise identify, the visible posting text (with form fields, hidden content, and page chrome removed) is sent once for extraction and is not retained.
- If you ask the agent to fill an application for you: a record of each hosted-browser session, and a per-turn history of the run covering why it stopped, the kinds of actions it took, how many protected questions it declined to touch, and the AI budget it used. These hold no field values and no screenshots.
- If you turn on alerts in Settings: the Web Push subscription your browser issues, which is a delivery endpoint, its two encryption keys, and your browser user agent. It is what lets us send an alert to that device.
How we use it
Your data is used to run the product: extracting career facts, generating resumes that stay grounded in those facts, matching you against job postings, and tracking your applications. We do not sell personal data and we do not use it for advertising.
AI processing
Fact extraction, resume generation, job matching, and the Chrome extension’s page-read fallback are performed by external AI APIs (Anthropic for text processing and page-read extraction, OpenAI for embeddings, and Mistral for Application Assist field classification). Under those providers’ API terms, API inputs and outputs are not used to train their models by default. Their published standard API terms may retain inputs and outputs for up to 30 days for service and abuse-monitoring purposes, subject to our account settings, a different agreement, or legal requirements. Voice conversations are handled by ElevenLabs, which processes the audio and produces the transcripts we extract facts from.
When you ask the agent to fill an application for you, MemoryCV opens the employer’s site in a hosted browser run by Browserbase. Your selected resume file is staged into that browser for the upload field, and the answers you approved are typed into the form there. The model steering the run (Anthropic, or Google Gemini on deploys using that model) sees screenshots of the form, so those images can show the answers already typed. The agent never answers demographic, disability, veteran-status, or background-check questions.
Chrome extension
MemoryCV Companion installs with access to https pages so it can spot job postings and application forms wherever you browse, with no per-site setup. That detection runs entirely on your device: it looks for a posting in the page and keeps a short-lived note, per tab, of which job that tab was reading. The note stays in Chrome session storage, is never sent anywhere on its own, and is deleted when the tab closes or the browser exits. Nothing is sent to MemoryCV unless the side panel is open for that window or you take an explicit action, and nothing is saved to your account except by your explicit actions: generating a tailored resume, saving a job for later, using a grounded answer, or confirming a submission.
On application forms, the companion identifies form fields without reading what you have typed into them. An answer is stored only when you explicitly ask MemoryCV to remember it, limited to work authorization, sponsorship, compensation, relocation, and availability questions, and you can view and delete remembered answers from the panel at any time. The companion never reads demographic, disability, veteran-status, or background-check questions, and it never submits an application for you.
Before you save, the extracted job fields are sent to MemoryCV so Anthropic can extract requirements and OpenAI can embed those requirements for comparison with the connected career memory. This pre-save check does not create a saved job. The extension gets at most 24 requirement rows and evidence snippets capped at 140 characters, without career memory fact identifiers or raw facts.
Chrome local storage holds one scoped connection token and an isolated workspace for each open Chrome window. Depending on the current step, a workspace can contain page and job fields, observation metadata, bounded requirement and evidence rows, the saved job reference, current application stage, and resume-generation progress or destination path. Closing a window deletes its workspace. The token can save and score jobs, generate for the connected career memory’s own captured jobs, project career-memory-safe Application Assist details, export a selected resume for attachment, author grounded answers, save and manage the remembered answers described above, and confirm submission evidence. It cannot perform general application-stage writes, list or read career memory facts, resume text, application notes or history, billing, settings, or other account data.
Chrome Web Store Limited Use
MemoryCV Companion’s use of information received from browser permissions complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. We use and transfer that data only to provide or improve the companion’s disclosed job-fit, capture, generation, and tracking purpose. We do not sell it, use it for personalized advertising or credit decisions, or let people read it except with your specific consent for support, when needed for security or law, or as aggregated and anonymized data for permitted internal operations.
Providers that process your data
We use a small set of service providers. Each receives only what its column describes, only to provide that service.
Anthropic
AI text processing
Career facts, resume text, uploaded resume content, and job-posting text when you ask MemoryCV to extract, compare, generate, or revise content (Claude API). When you ask the agent to fill an application, it also receives screenshots of that form as images, which can show the values already typed into it.
OpenAI
Vector embeddings
Career-fact, job-posting, and extracted requirement text converted to embeddings for search, matching, and extension fit checks.
Mistral
Extension field classification
Value-free application-form field descriptors when the Chrome extension classifies fields for Application Assist (Mistral API). Not retained.
Role classification and agent steering
Job-posting and role text when a role family is classified (Gemini API), and, on deploys that run the agent on Gemini, screenshots of the application form being filled.
Browserbase
Hosted browser
When you ask the agent to fill an application, it drives the employer's site in a Browserbase-hosted browser. That browser receives the answers typed into the form, such as your name, email, and phone, plus the resume file staged for the upload field.
Tavily
Live job search
Your search terms when a live web search backs up the job catalog. Nothing from your career memory or resume.
ElevenLabs
Voice conversations
Your microphone audio and the resulting conversation transcripts during voice intake.
Stripe
Billing
Name, email, and payment details if you start a paid subscription. We never see your card number.
Apify / Fantastic Jobs
Job-posting and company data
Nothing about you. They supply the public job postings we match your career memory against, and licensed public company profiles (size, industry, ratings) fetched server-side by company identifier, never with your career memory or resume.
Brandfetch
Company logos and firmographics
When a catalog job or company page shows a Brandfetch logo, your browser requests it directly from Brandfetch's CDN using the company's public domain. Brandfetch may receive that domain and ordinary request metadata sent with the request, such as your IP address, browser user agent, and referrer. Private jobs you add do not use Brandfetch logo hotlinks. Separate server-side company enrichment sends public company domains, not your career memory or resume.
Cloudflare
Sign-in bot check
On sign-up and sign-in, your browser loads the Turnstile challenge from Cloudflare, which receives ordinary request metadata such as your IP address and browser user agent to tell people from bots.
Resend
Email delivery
Your email address, and for an application alert the company and job title it is about, to deliver account and alert email.
Sentry
Error monitoring
Error names, messages, and stack frames with the route and method they came from. No request bodies, headers, cookies, or user identifiers.
PostHog
Product analytics
Pages you open and clicks inside the app, tied to the analytics cookie described below. A named profile is created only once you sign in. We do not record your screen.
Railway
Hosting
Request data (such as IP address) as the platform serving the app, and the career memory, job, resume, and application data stored in managed Postgres.
Cookies
We set a single essential session cookie so you stay signed in. We also set one first-party analytics cookie, ph_<project>_posthog, holding an anonymous device identifier and PostHog’s own session state; it expires 365 days after your last visit. Those analytics requests are sent to a MemoryCV path on this domain and forwarded to PostHog. There are no advertising cookies. Some catalog job and company pages make the direct Brandfetch logo request described above; MemoryCV does not use that request for analytics or advertising.
Retention
Your data is kept for as long as your account exists. Facts, resumes, and applications you delete inside the product are removed from your career memory. A confirmed submission is historical evidence: deleting or editing a source fact or resume does not silently rewrite the bounded copy already frozen in that application snapshot. Those copied excerpts remain until you delete the containing application or your account. Working resume export check reports are shorter-lived: we keep no more than the newest three for the same document version and analysis method, and delete all such working reports after 30 days. Facts extracted from an uploaded resume wait for your review: if you never accept that review, we delete the extracted review facts and the upload record after 30 days. A Chrome extension token expires after 90 days and can be revoked sooner in Settings. Disconnecting the extension clears its token and all panel workspaces from Chrome. Uninstalling clears the extension’s local data and permissions. Saved jobs, resumes, and application records remain in your MemoryCV account until you delete the relevant record or account. Providers listed above retain data under their own published policies. For voice intake that includes transcripts held by ElevenLabs.
Deleting your account
You can delete your account yourself at any time from Settings. Deletion cancels active billing first, then removes your application evidence in an explicit order before removing your account and its remaining data: facts, voice transcripts, uploaded files, resumes, resume export check reports, owner-private job and company records, extension connections, job matches, applications, hosted-browser sessions and agent run history, registered alert devices, sessions, and any subscription.
Access and export
You can download a machine-readable JSON copy of your data yourself at any time from Settings. For help with an export, or to ask what we hold about you, email support@memorycv.com from your account address.
Changes to this policy
If this policy changes, we update this page and the date at the top. Material changes will be flagged in the product before they take effect.
Contact
Privacy questions go to support@memorycv.com.