Legal
Privacy Policy
Last updated: October 28, 2026
This policy explains what data Climbr collects, why we collect it, and what we do with it. We aim for short and honest — if anything is unclear, email support@climbrhq.com.
1. What We Collect
Account information. Email address, full name (if provided), and authentication identifiers from Google or Apple when you sign in with them. If you sign in with Apple and choose Hide My Email, we receive an Apple private relay address instead of your real email address.
Profile and preferences. Your selected field, IT specialization, experience level preferences, job type preferences, and email notification preferences.
Home address. A home address is optional. If you add one, in Settings or in the iPhone app, we store it to fill job applications that ask for it.
Resume and career data. The contents of any resume you upload, paste, or build with our guided flow, including work history, education, skills, certifications, and projects.
Other people's details you choose to save. If you save an emergency contact or professional references in Settings, we store what you give us about each person: their name, how they relate to you, and their phone number and email address. We keep these encrypted, show them only to you, and use them only to fill the matching emergency-contact or reference boxes on applications you choose to fill. We never contact these people. Only list someone who is comfortable being listed; you can delete an entry yourself in Settings, or email support@climbrhq.com and we will remove it.
Application data. Jobs you save, mark as applied, advance through interview stages, or annotate with notes.
Target companies. Companies you choose to track and any career page URLs you add.
Usage data. Basic logs of pages visited, API requests, and error events for debugging and improving the Service. We use product analytics (PostHog, served through our own domain; Vercel) to understand usage, and the Meta Pixel + Conversions API and Google Ads conversion measurement to measure and optimize our advertising — these may share a hashed identifier (such as a hashed email), an ad click identifier, and conversion events (such as signup, starting a checkout, or subscription) with Meta or Google, including from our servers. We never share your resume, application data, or message content for advertising.
Payment data. If you subscribe, Stripe processes your card on our behalf. We never see or store your card number — only a customer ID and subscription status returned by Stripe.
Survey responses. If you respond to an optional Climbr survey, we store your answers, along with a salted, one-way hash of your IP address (never the address itself) and your browser's user-agent string, used to limit and look into abuse of the survey. If you're signed in, or you respond through a personal survey link we emailed you, your answers are linked to your account; otherwise your response is anonymous. For the business survey, we also store your organization name, contact name, and work email only if you check the box asking us to follow up — we don't save them even if you typed them in unless you check that box. When you open a personal survey link we emailed you, we record that it was opened and when, linked to your account. We store nothing else about that visit (no IP address or browser details), keep at most five of these records per day per person, and delete them with your account.
Email delivery events. Our email provider tells us when an email to you bounces or is marked as spam, and when a survey or announcement email was delivered. We record these events — the type of event, which email it was, the provider's message ID and a one-way hash of your address, never the message contents — linked to your account when we can match it. If an email bounces permanently or you mark it as spam, we pause all non-essential email to that address, so we don't keep emailing an address that can't or doesn't want to receive it.
2. Why We Collect It
We use your data to:
- Authenticate you and maintain your account
- Show you job openings relevant to your field and preferences
- Generate AI match scores, tailored resumes, and interview prep specific to your background
- Send you notifications you've opted into (job matches, target company openings)
- Process subscription payments and provide billing receipts
- Detect abuse, fix bugs, and improve the Service
We do not sell your data. The contents of your resume, applications, and messages are never used for advertising. We do use limited site-usage signals (such as which pages you visited and which ad or link brought you here) to measure our own ads and show them to people who visited the site, as described in Section 5.
3. Who Sees Your Data
Your data is shared with the following service providers (called "subprocessors", except Cerebras) strictly to make the Service work:
- Supabase — hosts our database and authentication. Your account, resume, and application data live here.
- Vercel — hosts the web application.
- Anthropic (Claude) — processes the text you give our AI features (your resume, job descriptions, LinkedIn profile text you paste or link, job offers you ask us to review, and your mock-interview answers) and, if you provided them, your self-attested security-clearance details (level, polygraph, status), citizenship, and work authorization, to generate match scores, tailored resumes, cover letters, interview prep, and our other AI features. It also reads scanned or photographed resumes you upload so we can pull out the text, drafts answers to application questions when you ask it to, powers the Climbr AI chat, and helps us sort and answer messages you send our support team. It also reads the text of application questions (never your personal details) so the extension and app can tell what they ask.
- Cerebras — runs an open-source AI model for us. We use it for most of our match scoring and resume tailoring, and for resume feedback, skill-gap and LinkedIn checks, detecting your field and skills, and reading job postings. It receives your resume text, the job posting, the LinkedIn headline and About text you paste into our LinkedIn checker, and — if you provided them — your self-attested security-clearance details, citizenship, and work authorization, your skills, and any answers you give to tailoring's accuracy questions.
- Amazon Web Services (Amazon Bedrock) — runs some of the same AI models for us (Anthropic's Claude and the open-source model Cerebras runs). We use it for part of our match scoring, including overnight scoring of new jobs for you, and it may also handle some of our resume features, such as tailoring, cover letters, the resume builder, and reading the work history in your resume. When Cerebras can't handle a request, it may also handle LinkedIn checks, detecting your field, job insights and role tips, reading job postings in our extension, and sorting the recruiter emails you forward to us. For those it receives the same data Cerebras would, plus the text of those emails. It receives the same kinds of data as above for the requests it handles, including your resume text, the job posting, the application questions you ask Climbr AI to answer and the parts of your details they need, your answers to tailoring's accuracy questions, what you enter in our resume builder, and — if you provided them — your self-attested security-clearance details, citizenship, and work authorization, and your skills. It also reads the text of application questions (never your personal details) so the extension and app can tell what they ask. AWS may handle these requests in data centers outside the United States. For all three AI providers: we send each one the data the feature you're using works from, and that can include the contact details at the top of your resume.
- Apify — if you give us your LinkedIn profile address instead of pasting your profile, Apify fetches that public profile for us. We send it only the address.
- Stripe — processes payments. They receive only what's needed to bill you.
- Resend — delivers email notifications.
- Twilio — delivers SMS notifications (when SMS is enabled).
- RapidAPI / JSearch — provides the job listings shown in your feed. We do not send them anything about you; we only retrieve listings.
- Google — if you sign in with Google, Google sees that you used your account to access Climbr.
- Apple — if you sign in with Apple, Apple sees that you used your Apple Account to access Climbr. If you chose Hide My Email, the emails we send you go through Apple's private relay service.
We do not share your personal data with anyone else, except: the analytics and advertising measurement described in Section 1; when you choose to send it yourself (for example, when you fill in an employer's application with Climbr and submit it); when required by law (subpoena, court order); or to protect the rights and safety of users or the public.
4. How Climbr Uses AI
Climbr runs on AI. Reading your resume, scoring jobs against it, tailoring it to a posting, and writing cover letters are done by AI models run by outside companies. AI is part of how the Service works, so there is no separate AI switch or consent screen: by creating an account or using Climbr (on the website, in the iPhone app, or in the browser extension) you agree to what this section describes. If you do not agree, do not use Climbr, or delete your account.
- What we send. Depending on the feature you use: your resume text (including the contact details at the top of it, or the image itself if you upload a scan or photo), your profile and preferences, and the job descriptions you look at. If you have added them, also your self-attested security-clearance details, citizenship and work authorization, your skills, and your answers to tailoring questions. Anything you paste into an AI feature (for example LinkedIn text, a job offer, or an interview answer) is sent too.
- Who receives it. Anthropic, Cerebras, and Amazon Web Services (Amazon Bedrock). Each one gets the data the feature you are using works from. Section 3 above lists what each provider receives and what it does for us.
- Why. To read your resume and pull out your work history, to score how well jobs match you, to tailor your resume to a posting, to write cover letters, and to power the other AI features you choose to use, such as interview prep and resume feedback. Some of this runs in the background, for example scoring new jobs against your resume overnight. AI output can be wrong, so you review it, and Climbr never sends anything to an employer unless you choose to apply.
- What is never sent to an AI provider. Your passwords (your Climbr password, and any job-site sign-in you keep in the browser extension, which stays on your device), and the answers in your private answers vault and your voluntary self-identification answers (gender, race, veteran status, disability). The vault holds sensitive application questions such as criminal history, drug screening, non-compete agreements, visa type, salary expectations, and references. Your card number goes to Stripe, never to us or to an AI provider.
- How long it is kept. Climbr keeps your resume and the AI results (match scores, tailored resumes, cover letters) in your account until you delete your account. After you delete your account there is a 30-day grace period, then your personal data is permanently deleted from Climbr. Each AI provider handles what it receives under its own terms, which Climbr does not control. We do not sell your data, and your resume is never used for advertising.
- How to delete it. You can delete your account at any time from Settings → Data & privacy on the website or Me → Delete account in the iPhone app, or by emailing support@climbrhq.com.
5. Cookies and Local Storage
We use cookies set by Supabase to keep you signed in — these are essential for the Service to function.
If you reach us through a Meta (Facebook/Instagram) ad, the Meta Pixel may set cookies (such as _fbp and _fbc) used to measure ad performance and attribute conversions. You can limit this through your browser settings and your Meta ad preferences.
When our Google advertising tag is enabled, Google may set cookies used to measure ad performance and for remarketing. You can limit this through your browser settings and your Google Ads Settings.
We may use your browser's local storage to temporarily hold a resume you built before signing up, similar short-lived signup carry-over (like a plan you picked before creating an account), and a record of which ad or link first brought you to the site (so we know which of our marketing actually works). You can remove this at any time by clearing your browser storage.
6. Your Rights
You can:
- Access your data by viewing it in your account at any time.
- Correct your data by editing it through the relevant page (resume, onboarding, applications, companies).
- Delete your account yourself from Settings → Data & privacy (or by emailing support@climbrhq.com). Deletion is scheduled with a 30-day grace period — sign back in any time during it to cancel — after which your account and personal data are permanently erased. Deleting also cancels any active subscription. A few records are anonymized rather than deleted (see Data Retention below), and we may retain limited records where required by law or to prevent fraud.
- Export your data by emailing support@climbrhq.com with a request. We'll provide it in a machine-readable format within 30 days.
- Opt out of email notifications using the toggle in your dashboard notifications panel.
If you are in the European Union, the UK, or California, you have additional rights under GDPR / UK GDPR / CCPA, including the right to lodge a complaint with your local data protection authority.
7. Data Retention
We keep your data while your account is active. When you delete your account, it enters a 30-day grace period during which you can undo it by signing back in; after that, your personal data is permanently deleted. Some records are anonymized rather than removed — support conversations and ad-conversion logs are kept with your identifying details stripped out — and we retain limited records where required by law or to prevent trial abuse (such as consent logs and payment-method fingerprints). Some anonymized usage data may be retained for analytics. Backup snapshots may persist for up to 90 days before being overwritten. Automatic fill summaries from the iPhone app are deleted after 180 days; reports you send with 'This didn't fill right' are kept until you delete your account.
8. Security
Your data is transmitted over HTTPS. Database rows are protected by row-level security so that only you (and our backend service role used for legitimate operations like sending you a daily digest) can access them. We follow industry-standard practices to protect your data, but no system is perfectly secure. If we ever discover a breach affecting your data, we will notify you within 72 hours of becoming aware.
9. Children
Climbr is not intended for children under 16. We do not knowingly collect data from anyone under 16. If you believe a child has provided us data, email support@climbrhq.com and we will delete it.
10. International Transfers
Climbr is operated from the State of Maryland, United States. If you use the Service from outside the United States, your data will be transferred to and processed in the United States and other countries where our subprocessors and Cerebras operate.
11. Text Messaging (SMS)
If you opt in to receive text messages from Climbr, the following applies to that program:
- What you'll receive: account and job-match notifications (e.g., new jobs matching your profile, openings at companies you track, and application or account updates).
- How you opt in: by entering your mobile number and checking the unchecked-by-default SMS consent box on our text-alerts page or in your account settings. Opting in is optional and is not a condition of signing up for, purchasing, or using Climbr — every feature works without text messages.
- Message frequency varies based on your activity and preferences.
- Message and data rates may apply.
- Opting out: reply STOP to any message to unsubscribe at any time, or HELP for help. Opting out of SMS does not affect your email notifications.
We do not share or sell your mobile number, or your SMS opt-in consent, to any third party or affiliate for their own marketing or promotional purposes. Your mobile number is used only to deliver the Climbr messages you requested, including through our SMS provider (Twilio), which sends them solely on our behalf.
12. Browser Extension
If you install the Climbr browser extension, the following applies in addition to the rest of this policy:
- What it reads. On the supported job boards and applicant-tracking systems — the current list is published at climbrhq.com/extension — when you are viewing a job posting, the extension reads the public posting on that page — its title, company, and description — to score it against your résumé. If a board changes its layout so the posting can't be read cleanly, the extension reads the visible text of that posting (capped) so Climbr can pull the title, company, and description out of it. On those boards' application pages it also reads the application form's field labels and types, so it can fill fields with your saved data and flag the ones it isn't sure about. On a few of those systems the application form is embedded in a frame served from the same vendor's own domain; the extension reads that frame too, solely to fill the form you are completing.
- On other websites. The extension has permission to run on every website, and by default it checks the pages you open — in any tab — to see whether each one is a job posting or a job application. The check happens on your computer. It looks only at that page's own content: its text, layout, and web address, including any job-posting data built into the page (for example, whether the page has a job title and description, or a résumé upload box). It doesn't read what you've typed into form fields. It stops right away on pages it should stay out of: common email, document, payment, banking, and social sites (such as Gmail, Outlook, Google Docs, PayPal, several major banks, Facebook, and Reddit), pages whose address looks like a login, checkout, account, or admin page, and any page showing a password box. The check itself sends nothing to Climbr or anyone else, and the extension does not save a record of which pages it checked (only a running count of the pages it flagged, shown on the extension's settings page). If a page only might be a job page, the extension just shows a small "?" on its toolbar icon and reads nothing more. If a page is clearly a job posting or application and you are signed in to Climbr, the extension opens on that page by itself. Before opening, it checks with Climbr that you are signed in; that request contains nothing about the page. Once open, it works exactly as it does on the supported boards: it reads the posting and sends it to Climbr for your match score, and on an application form it reads the form's field labels (see "What it sends us" below). You can also open it on any page yourself by clicking "Open Climbr on this page" in the extension's toolbar menu.
- Turning it off. Click the Climbr icon in your browser's toolbar and switch off Autofill on other sites. If you are signed out, use the same switch on the extension's settings page (right-click the Climbr icon, then Options). Despite its name, this switch turns off everything described in the bullet above — the check, its "?" badge, and the automatic opening — not just autofill. The extension keeps working on the supported boards, and "Open Climbr on this page" still works when you click it. To hide Climbr on a single site, click the eye-slash icon ("Don't show Climbr on this site") on the Climbr panel. The panel stops appearing on that site, and if the site is not one of the supported boards, the check and the automatic opening stop there too. On a supported board, hiding the panel does not stop the extension from reading and scoring the postings you view there. You can undo this on the extension's settings page. To stop the extension from running on a site at all, use Chrome's own extension settings ("Site access").
- How it signs you in. The extension uses your existing Climbr login (your session cookie). It never asks for or stores your Climbr password.
- What it keeps on your device. So it doesn't have to re-download everything on every page, the extension keeps some of your own data in your browser's extension storage on this computer:
- The résumé file you picked for autofill. It is held in temporary browser memory that is cleared when you close the browser, and reused for no more than 10 minutes (your main résumé) or 24 hours (a tailored one).
- The job postings you viewed recently (title, company, description, and web address) and their scores: up to 20, for 7 days. This lets a score follow you from a posting to its application form.
- Where you are in an application you are filling, including which fields it filled (cleared when you close the browser).
- Which résumé you last chose.
- Any changes you make to your autofill details inside the extension.
- Your extension settings, such as the sites you muted.
- A short troubleshooting log of up to 20 recent times its panel covered a button on a page (the site name, the time, and the button's text).
- Only if you add them: sign-in reminders for job-application sites (the email or username you used there and, if you choose, a password). The password is shown masked, and none of it is ever sent to Climbr. The extension does not encrypt them separately, so anyone who can use your browser profile could reveal them.
- Assisted autofill. When you click Autofill, the extension fills application fields with the data you saved in Settings → Autofill — contact details, links, and, only if you chose to provide them, your mailing address, work authorization, security clearance status, and voluntary self-identification (gender, race/ethnicity, veteran status, disability). It only ever replays exactly what you entered — it never guesses or infers these answers — and it shows you what it filled so you can verify before submitting. If you saved an emergency contact or references, the extension fills them only into the boxes asking for them, and marks each one so you can check it before you submit.
- Cookie notices. On job pages, the Climbr extension may decline or hide a site's cookie notice for you. It never accepts cookies on your behalf.
- What it sends us. When the extension is open on a job posting — on a supported board, on another site where it opened by itself, or where you opened it — the posting's title, company, and description are sent to Climbr to generate your match score (processed by our AI providers, as described in Section 3); if the posting couldn't be read cleanly, the visible posting text is sent so we can extract it (also processed by our AI providers). On job postings and application pages, the page's web address and title may also be sent to Climbr to match the page to a job already in your account. When you are signed in, the extension also tells Climbr the site name (never the full page address) of each page where it runs, what kind of page it is (for example, a posting or an application), and whether its panel appeared; this is linked to your account in our product analytics (PostHog), along with when you last used the extension, so we can find sites where it fails to show up. We also record de-identified diagnostics — the site's domain and which extraction method worked, with no identifier tying it to you — so we can tell when a site changes its layout and fix it. When you click Save, that posting is added to your feed and tracker. When you click Tailor my résumé, the posting is sent to Climbr to produce a tailored version of your résumé (processed by our AI providers), which is saved to your account. When you click Draft from my résumé on an application question, that question and the posting are sent to Climbr and, together with your résumé, processed by Anthropic to draft an answer that you review and edit before using. When you click Save for reuse on an answer, that question and your answer are stored in your Climbr account so the extension can offer them back to you when the same question appears again. You can view and delete any saved answer at any time in Settings → Autofill.
- Reading application questions (Pro and Elite). When you fill an application and Climbr can't tell on its own what a question is asking, only the words of the question and its answer choices are sent to Climbr, where Anthropic's Claude (run for us by Amazon Web Services, or by Anthropic directly) says which kind of question it is. Nothing you saved or typed is sent with it: not your résumé, your saved answers, or your memory. Questions about race, ethnicity, gender, sexual orientation, disability, veteran status or age are never sent. The box is still filled only from what you saved, is marked "Check this", and Climbr never submits an application for you. We keep what a question means, not who asked it, so the same question isn't sent again, and we count how many questions each account sends a day to keep the feature within its limits.
- What it never does. It never submits an application for you, never fills a field or sends a posting for tailoring or drafting without your action, never fabricates an answer, and never sells or shares your browsing.
13. iPhone App
If you use the Climbr iPhone app, the following applies in addition to the rest of this policy. The app uses the same Climbr account as the website, so what this policy says about your account, résumé, matches, and applications (Section 1), about the AI providers that process some of it (Section 3), and about your saved memory and fill summaries (below), applies in the app too.
- Signing in. You can sign in with your email and password, with a code we email you, with Sign in with Apple, or with Google. With Apple, we receive an identifier from Apple, the name you choose to share (Apple shares it the first time only), and either your email address or, if you choose Hide My Email, an Apple private relay address. With Google, you sign in on Google's own page in your phone's secure browser sheet, and we receive an identifier and the basic details Google shares, such as your name and email address. Climbr never sees your Apple or Google password. We use this only to sign you in and to find or create your Climbr account. The app keeps your signed-in session (a token, not your password) in the iPhone Keychain, on that device only: it is not synced to iCloud Keychain.
- What the app keeps on your phone. Besides the session above, the app saves a few things in its own storage on your phone, under your account:
- Your job-site accounts note: for each employer where you made an account or signed in while applying with Climbr, the site's address, the employer's name, the job system it uses, whether it signs people in with a password or an emailed code, whether the sign-in was seen or is waiting for you to confirm your email, the first and last day, and how many times Climbr filled a form there. It never holds a password, a code, a cookie, a session token, your email address, or anything typed on the employer's page. It stays on this phone and is not sent to us. In the app you can remove any employer from the list; that clears only our note, and your account with the employer stays until the employer closes it.
- Your field answers (for example license, certification, or shift details you gave for your line of work). They are saved on the phone first, then sent to your Climbr account when the app can. This phone's copy is removed when you sign out or delete your account.
- Where you are in setting up your profile: the step you reached, the choices you made (such as your field and the roles you want), and any name, email address, or city you corrected on the "check your details" card. Your résumé itself is not kept on the phone.
- Where you are in the daily loop: which matches you have looked at or hidden today, your weekly plan, follow-ups you logged, and applications Climbr filled that you have not yet told it whether you submitted. So your matches show without a connection, the app also keeps a copy of your latest matches (at most 50, without the job descriptions); it is removed when you sign out or delete your account.
- A short record of which jobs and sites an autofill was already counted for in the last 24 hours, so one application is not counted twice; a count of how many fill summaries the app sent today, so it stays inside the daily limit (a number for each day, with no form content); and a few display settings, such as that you have seen a tip; the count is removed when you sign out or delete your account.
- Anything you typed in the app and did not save yet (for example half of an answer) is kept in the app's memory only, never written to storage, and is cleared when you sign out or close the app.
- Fill with Climbr, inside the app. The app opens an employer's application page in its own built-in browser. Nothing is filled until you tap Fill with Climbr. When you do, the app reads that page's form (its field labels, field types, and questions) in the browser on your phone, then types into the form only the details from your Climbr account that the form asks for, for example your name, contact details, and links, and it can attach your résumé file. It fills a question that asks for something you saved under Your answers only with exactly what you saved, and marks it for you to check. That can include questions about pay, availability and screening, and voluntary self-identification (gender, race or ethnicity, veteran status, disability), and, where you saved one, work authorization or sponsorship. If you did not save an answer, or the app is not sure a question means the same thing, it leaves the question for you. It does not guess. On a form with several pages it can press the page's own Next or Continue button on a page in the middle, and it stops on the last page: it never presses Submit, Apply, or Send, and it never submits an application for you. You review the form and tap the employer's own Submit yourself. To do this the app downloads your autofill details and your résumé file from your Climbr account into the phone's memory for that fill; it does not save them to your phone's storage. The form itself and what is typed into it stay on your phone: the app does not send Climbr the form's contents or anything it typed, except that, if you have turned on Climbr AI answering a form's questions (next item), it sends the wording, kind and choices of the questions still left empty. What it does send is described under "Fill summaries" below. When you tap Fill, the app also tells Climbr that one autofill was used (and, if you turned on Climbr AI answering a form's questions, those questions, as the next item describes), so your account's weekly count stays right.
- Reading application questions (Pro and Elite). When you fill an application and Climbr can't tell on its own what a question is asking, only the words of the question and its answer choices are sent to Climbr, where Anthropic's Claude (run for us by Amazon Web Services, or by Anthropic directly) says which kind of question it is. Nothing you saved or typed is sent with it: not your résumé, your saved answers, or your memory. Questions about race, ethnicity, gender, sexual orientation, disability, veteran status or age are never sent. The box is still filled only from what you saved, is marked "Check this", and Climbr never submits an application for you. We keep what a question means, not who asked it, so the same question isn't sent again, and we count how many questions each account sends a day to keep the feature within its limits.
- Fill summaries. After a fill, the app sends Climbr a summary of how that form went, so we can find forms the app fills badly and fix them. The summary holds the employer site's address (its host and page path, never the part after a question mark), the job system it runs on, the app version, each page's heading, the label and type of each box, whether the app filled it or left it for you, and whether the page required it; for a box it filled, what kind of saved information it used (for example, your degree or a saved answer), never the information itself; for a box it left, why (for example, you had no saved answer for it); and counts of how many boxes it filled. It never includes anything that was typed into a box or anything you saved. Our servers refuse a summary that contains text that looks like an email address, a phone number, a link or a long number. Each summary is linked to your account. We keep these automatic summaries for 180 days and then delete them. The app sends at most 20 a day per account.
If a form looks wrong, you can tap This didn't fill right and the app shows you the report before it is sent. It is the same kind of layout report, but it lists every box on the page (label, type, whether required, and what Climbr did with it), never what was typed. We keep these reports you choose to send until you delete your account.
- Your memory and Climbr AI. In the app you can save things for Climbr AI to remember about you: jobs you have held, skills (with where you used each one), short stories in your own words, and certifications or licenses (the name, who issued it, the year, an expiry if it has one, and whether it is current, expired or in progress). Climbr does not save certificate, license or ID numbers; the app asks you to leave them out, and our servers turn away text that looks like one. Your security clearance is not a separate copy: it is the clearance answer you already gave under Your answers. When Climbr AI asks about a skill or credential and you answer "not yet", we remember that for 90 days, so it does not ask again right away, and then it may ask again. When your résumé lists a certification with no date on it and an application asks whether you hold it, Climbr never decides that from the résumé: whenever the entry is a plain certification name, the app asks you, once, before anything is filled, and otherwise the question stays empty. We work out which certification to ask about on our servers, from your résumé, and the question goes only to your phone; that question is not passed to an AI provider. If you answer "Yes, I hold it", we save it as one of your own credentials, with its name and no year until you add one, and Climbr AI may then use it to answer that question on later applications, marking the answer for you to check; it is not copied into your certifications list unless you later add a year to it. If you answer "Not yet", we remember that for 90 days and leave that question empty. You can change or delete either answer in Your memory at any time, and deleting your account deletes them. Everything you type into memory is stored encrypted in our database (AES-256-GCM, with a key kept on our servers, not in the database), so a copy of the database on its own would not show it. Our servers do decrypt it to show it to you and, if you allow it, to use it. Memory is only ever what you typed or said yourself.
Climbr AI uses your memory only if you allow it in the app. If you have not chosen, or you choose Not now, memory is not used by AI and is not copied anywhere. If you allow it: skills you saved are also added to your Skills list, and credentials you saved to your certifications list, which Climbr uses to score jobs against you (those lists are part of your profile and are not separately encrypted); and when you tailor a résumé, Climbr sends our AI providers (Section 3) the names of your saved skills that the job posting mentions and the saved credentials that fit that job, but not the notes you wrote next to a skill. A tailored résumé lists what it used from your memory. You can change or delete any item, or reset all of memory, in the app. The Climbr AI chat is a separate feature: your messages go to Anthropic to be answered, Climbr does not keep the text of the conversation on its servers, and the chat does not read your memory. Deleting your account deletes your memory.
- Climbr AI answering a form's questions. This is separate from the fill above, and it is off unless you have said yes when the app asked whether Climbr AI may use your memory and fill in questions. When it is on and you tap Fill with Climbr, the app also sends Climbr the questions on the page that are still empty: their wording, the kind of box, the answer choices, the heading of the section they sit in, whether they are required, and their maximum length. The request has no field for what you typed or what is already filled in. To begin with, Climbr passes a question to an AI provider only if it is one of these: a question about your education (your degree level, field of study, school, or graduation year; a question that names two degrees, such as a bachelor's and a master's, is answered only if both are in your details); a question about a certification or licence you hold (a certification that appears on your résumé without a date is never counted as held: the app may ask you first, as described under Your memory and Climbr AI); a question about how many years of experience you have in a named skill, tool or field (such as sales, nursing or Python; not how long you have lived or worked somewhere); a question about which tools or skills you have used, or whether you have experience with one (such as "Which EDR tools have you used?" or "Do you have experience with Splunk?"), which is answered only with a tool or skill that your résumé or your saved skills and jobs name, and is left empty otherwise (it is never answered No just because something is missing; it is answered No only when a skill or job you saved says you never used it); or a "why this company" or "tell us about yourself" question, an essay answer of a plain kind (a time you led or solved something, why we should hire you, your proudest accomplishment, or anything else), or a cover letter, which it drafts for you to check. An essay question about diversity, legal or personal information, family, health, politics or your personal life is not passed on. Every other question is left empty for you and is not passed on; for example, where you have worked or your current employer, pay, work authorization, sponsorship, citizenship or security clearance, gender, race, veteran or military status, disability, health, age, religion, criminal history, family or relationships, personal documents (such as an ordination, firearms, liquor or birth certificate), the faith of a school, scholarships and financial aid, references, other people, a degree you are still working on or an expected graduation date, the agreement and consent boxes, and file uploads. A question that mixes one of the four kinds above with something else (including a health, addiction, pay or background-check word), a question written as a negative, a question longer than 200 characters, a question whose wording holds an email address, a link, or a long number, and a question about a certification, school, or subject that is not in your own details are not passed on either. Which questions are passed on is decided from the wording by rules in our code, so a question worded in an unusual way could be judged wrongly. For the questions that are passed on, Climbr reads from your account the text of your résumé, what you told Climbr AI in your memory (your jobs, skills, certifications and stories; from each story only the sentences that say what you did yourself are used, and a plan, a hope, a number you were unsure of, something a teammate or manager did, and anything you took back are left out before anything is sent; a story is used only for the "why this company", "tell us about yourself", essay and cover-letter questions), and sends them, cut down to the lines each question needs (see below), with those questions to Anthropic (Claude), which writes an answer for each question it can support from what you gave it, or none. Before anything is sent, Climbr masks the name, email address, phone number, web addresses, street addresses and postcodes, and ID numbers (such as a passport, licence, candidate or registration number, or any long mix of letters and digits) it recognises in that text, including phone numbers written with letters and email addresses written out in words, drops the address and place lines at the top of your résumé, and masks the names of other people it recognises (a reference, a manager, a family member), so the provider does not receive them, and a masked value is never put into an answer. The rules cover address and phone shapes from many countries but they are rules, not a promise: a detail written in an unusual way, or a nickname, could still get through. Only the lines a question needs are sent: for a degree question your education lines, for a certification question your certification lines, for a years question your job headings, the lines that name the skill and your memory items about jobs, for a question about a tool or skill you have used your job headings, the lines under them, your project lines, your skills lines and your saved skills and jobs, and for a "why this company" or "tell us about yourself" question, an essay answer or a cover letter your work, education, certifications and skills, and your saved stories (cut as described above). The volunteer, awards, interests, activities, affiliations, memberships, personal and references sections of your résumé are never sent, whatever the question. Lines about you rather than your work (leave, your own health or surgery, immigration or work-authorization status, security clearance, veteran status, a union, a membership in a group or a faith, a spouse or caregiving, a native language, a date of birth, marital status) are also taken out before anything is sent. That is a short list of wordings in our code, not a promise: a line worded in another way can still go with the rest. Some requests go to Amazon Web Services (Amazon Bedrock), which runs Anthropic's Claude for us, instead of to Anthropic directly. When a "why this company" question or a cover letter is passed on, Climbr also looks up the job posting you are applying to, but gives the provider only the company's name and the job title, not the description. Your saved answers (Settings → Autofill), the answers you keep under Your answers in the app, your private answers vault and your self-identification answers are never read for this, and the AI never sees them. Before an answer reaches your phone, Climbr's own server checks it against your résumé and your memory, not only the part the AI pointed to (a very long résumé or a very large memory is cut at a fixed length, and what is cut is neither sent nor checked). The answer must quote your own words. A certification is filled in only if your details hold a record of it that is current (a saved credential marked active, or a résumé line with a past date, or an expiry date that has not passed) and nothing else in the line, such as an expiry date that has passed or a note that it lapsed, is pending, or is in progress; a question that asks for a current, valid or active certification is answered only if the record shows an expiry date that has not passed (or the word lifetime) or is a saved credential marked active, and a year of issue alone is not enough; a program, a residency, a bridge course, a permit or an apprenticeship is not a certification. A degree is filled in only if its record has a finished date in the past that can be read; a date or note it cannot read leaves the box empty, an honorary degree does not count, a minor is not read as your field of study, and a graduation year is the year the record ends. Years of experience are counted only from the dates of your full-time jobs, one job at a time and never added up, and only where the job shows you did the thing (a word that only describes something else, such as the "sales" in "sales tax analyst" or the "cybersecurity" in "cybersecurity posters", does not count), a job whose own line says it ended (laid off, quit, contract ended, position eliminated) is not counted to today even if its dates say Present; a part-time, per-diem, relief, student, internship, co-op, assistantship, adjunct or volunteer job is not counted (when the job's own heading, or the one or two short lines directly above its dates, says so), and a range or "about" in the question is answered only if your figure fits it. If another line you wrote contradicts an answer, the box stays empty. If your saved details do not support an answer, the box stays empty. Every answer comes back with the part of your details it was taken from, so you can check it. A "why this company" or "tell us about yourself" answer, an essay answer, and a cover letter are drafts, written only from your own résumé and memory: each sentence either says you want to join the company or the role, or states something one record of your own details says. A draft never states your religion, nationality, race, sex, orientation, disability, health, veteran or military status, age, family or immigration status as a fact about you, and it does not name a faith group as your employer or school. It may name a military branch as an employer when your résumé says you worked there (for example "I worked as a logistics specialist in the U.S. Army"), but it never states that you are a veteran. A number, a percentage or a length of time in a draft must be written the same way in a record of yours, a sentence about the present is made only about a job with no end, and a sentence never carries what you did at one job over to another. It calls you only by a job title or credential of your own, never by the job of people you managed or served, and a line that says someone else did something to you (such as "trained by" or "applied for") is never used as something you did. It does not say you love, like, enjoy, are motivated by or are passionate about something, or that you have always felt so, unless your own memory says so. The draft is flagged for your review, it never contains a signature or your name, and the check refuses a sentence that says or suggests you worked for that company, were hired by it, or hold its job title, though an unusual wording could still slip past it, which is why you review every draft. You still review the form and press the employer's own Submit yourself. Climbr keeps a short record of each run: when it ran, your account, the app's run number, the kind of employer site (such as Workday) and the main web domain of the page it was on, whether a job posting was used, whether Anthropic or Amazon Web Services handled it, which model, how the run ended, which kinds of question it answers on that run, how many questions were on the page and how many were passed on, how many it answered, drafted, or left empty and why, which checks turned an answer down, how many boxes of each kind there were, which topic groups were kept away from the AI, which kinds of your details (résumé or memory) backed the answers, how many tokens it used, how long it took, and what the run cost. For each question on the page the record also holds the question's wording as the employer wrote it, with numbers, email addresses and links hidden and anything that looks like your name, contact details, address or text from your résumé taken out (only the question itself is kept, and a wording that looks like pasted text is kept only as a mark), the kind of question it is, whether it was filled, drafted, or left empty, and which kind of your details it came from or why it was left empty, so that Climbr can see which questions it fills and which it leaves for you and improve. It does not keep your answers, the quotes behind them, or any text from your résumé or memory in that record. Climbr keeps these run records until you delete your account. You can turn this off at any time by choosing Not now in the app, and your fills keep working without it.
- More answers you can save. Under Your answers you can also save, only if you choose to: the countries you are a citizen of now, and any you held in the past; your pronouns; whether you served in the U.S. military, the branch, and the month you left; whether you can perform the essential functions of a job with or without reasonable accommodation; your work schedule (shifts, days, weekends, holidays, overtime, rotating shifts) and whether you can work in an office or travel for team events; your GPA and test scores (SAT, ACT, GRE); and driving details (whether you have a valid license and since which year, whether you have reliable transportation and auto insurance) and your English level. Citizenship, pronouns, military service, the essential-functions answer, your schedule, your grades and scores, and the license year are stored encrypted in the same way as your memory; the remaining short choices are stored as plain labeled values in your account's private answers store, readable only through your account. The app fills a matching question on an employer's form with exactly what you saved and marks it for you to check; Climbr AI never reads these answers, and fill summaries never contain them. You can change or delete any of them under Your answers.
- Boxes you tick that Climbr remembers. When you tell Climbr to remember a box you ticked on an employer's application, for example that you read its privacy notice or that your application is true, Climbr saves that employer's name, the exact words of that box, a fingerprint of those words, the date, and whether you said yes in the app or in Chrome. It does not save your name, a signature, or anything you typed. On that same employer's later forms, if the words are exactly the same, Climbr ticks the box again and marks it for you to check. If the words change by even one character, or the form is a different employer's, it does not tick it, and it never submits anything. If a box is about you personally, such as a statement about your history or an opt-in to messages, Climbr can tell you to check it carefully. Climbr does not save words that contain your name, a date you signed, or an email address, phone number or link. You can see and remove what Climbr remembers yourself, and it is deleted with your account.
- Employer sign-in pages. If an employer's page asks you to sign in or create an account, you do that yourself. Climbr never types, reads, or stores your password for an employer. When you tap Type my email, the app types your Climbr account email into the page's email box and nothing else. The employer's page receives what is typed into its own form, and whatever you submit goes to the employer, whose own privacy policy covers what it does with it.
- The app's browser. Like any browser, it stores cookies and other site data from the employer sites you open in it on your phone, so you may stay signed in to an employer between visits. Climbr does not read or copy them, and deleting the app removes them. If an employer's upload field offers Take Photo, iPhone asks for your permission to use the camera, and the photo goes only to that employer's form. The app can open only web pages (https) in this browser.
- Adding a résumé from your phone. If you choose a résumé file from your phone, it is sent to Climbr to read your contact details and work history and to build your matches, and, like a résumé you upload on the website, a scan or photo may be read by an AI provider (Section 3).
- Deleting your account in the app. In the app, go to Me → Delete account and type your account's email to confirm. If you signed in with Apple, you confirm with Apple once more so Climbr can revoke its Apple sign-in tokens. Deletion works as described under Your Rights above: it is scheduled with a 30-day grace period, you can undo it by signing back in and tapping Keep my account, any subscription is set to cancel, and after the 30 days your account and personal data are permanently erased. The app also removes its job-site accounts note, its copy of your field answers, and its other saved notes (your setup progress, daily-loop state, and the saved copy of your matches) from the phone, and signs you out.
- What the app does not do. As of this version the app contains no advertising or third-party analytics code, and it does not ask for your location, your contacts, or permission to send notifications. We do not sell your data.
14. Changes to This Policy
We may update this policy from time to time. When we do, we will change the “Last updated” date at the top of this page.
15. Contact
For privacy questions or requests, email support@climbrhq.com.
See also our Terms of Service.