{"id":30984,"date":"2026-10-15T15:21:06","date_gmt":"2026-10-15T14:21:06","guid":{"rendered":"https:\/\/www.kaspersky.co.uk\/blog\/?p=30984"},"modified":"2026-10-15T15:21:06","modified_gmt":"2026-10-15T14:21:06","slug":"creating-resume-with-ai-safely","status":"publish","type":"post","link":"https:\/\/www.kaspersky.co.uk\/blog\/creating-resume-with-ai-safely\/30984\/","title":{"rendered":"How to improve your resume with AI without exposing your data"},"content":{"rendered":"

Finding a job these days is playing on hard mode. You send your resume to a company, and a couple of minutes later, an automated rejection lands in your inbox. And then it happens again. And again. Sound familiar?<\/p>\n

In this post, we look at how recruiting platforms work from the HR side. We also show how to use AI safely as a copy editor so you can prepare a resume for recruiters without turning it into a lifeless pile of keywords. At the end, we share a ready-made prompt to help you improve your resume\u2019s structure and content.<\/p>\n

Protecting your data<\/h2>\n

Before you give your resume to a chatbot, remove all sensitive information: your name, phone number, home address, email, company names, and scans of documents. Any language model you chat with can sometimes memorize personal information contained in their training data. That means there\u2019s always a chance the AI may accidentally \u201clearn\u201d to give your data to other users<\/a>. On top of that, even the biggest services aren\u2019t immune to glitches and leaks. For example, last year a researcher found a bug in Meta AI that let users gain access to other people\u2019s conversations with the chatbot by changing their request ID<\/a>.<\/p>\n

The ability to read other people\u2019s chats sometimes isn\u2019t even a bug. For example, it recently came to light that Grok users who clicked the Share chat<\/em> button to send a conversation to a friend or to themselves were also allowing<\/a> search engines to index that conversation. As a result, thousands of conversations ended up in public view. These included personal data, requests to come up with complex passwords, complaints about health problems, trade secrets, and other information the chat owners clearly never meant to publish.<\/p>\n

So before you use any chatbot, first check its privacy policy, and then go to the settings to turn off all the features you don\u2019t need. Most importantly, turn off training the AI on your requests. And remember the golden rule: don\u2019t send an AI anything you wouldn\u2019t be okay with seeing on the internet.<\/p>\n

If you work with sensitive information all the time, the safest option is to run language models locally right on your own computer. We previously explained how to do this, using DeepSeek as an example<\/a>. The same approach works with any other open-weight model.<\/p>\n

Finally, don\u2019t feed your personal data to chatbots from unknown developers that promise to write you a flawless resume. Often, these are just slick wrappers around popular models. And you probably won\u2019t ever find out who actually gets access to your data, where it\u2019s stored, or what happens to it next.<\/p>\n

Malicious actors can use this information for follow-up attacks. For example, they can send fake interview invitations and attractive job postings<\/a> that match your work experience and career interests a little too well. From there, the scam can go in many directions: a malicious file disguised as a job invitation, a link to a phishing page that steals your account, a request to install \u201ccorporate software\u201d or to continue the chat in a messaging app, and so on.<\/p>\n

When choosing an AI tool, ask yourself these questions:<\/h4>\n