Resources
Recordings and guidance, in one place.
Webinar recordings and application material, collected so you do not have to hunt through social media for them.
Resources
Webinar recordings and application material, collected so you do not have to hunt through social media for them.
Guidance
Chatbots like ChatGPT are designed to continuously learn and improve their responses from user input. While providers claim that sensitive data is filtered or anonymized, there is no absolute guarantee that your information will be fully deleted from storage systems.
Cybersecurity experts warn: there are five categories of information you should never enter into chatbots. Why? Because during model training, system bugs, or even hacking attempts, this data could be misused.
1. Personal Identity Information
National ID numbers, passport details, driver’s licenses, addresses, phone numbers, or dates of birth should never be shared. Even simple combinations like your name and city of residence can be enough for attackers to piece together your identity.
2. Medical Test Results and Health Records
Chatbots are not bound by strict healthcare privacy laws. Sharing lab results or medical history — especially alongside identifying details — can expose sensitive personal data. Beyond privacy risks, such information could potentially be used against you in contexts like insurance or employment. Keep medical data within secure, official healthcare systems.
3. Financial and Banking Information
Bank account numbers, credit card details, financial reports, or investment records are highly sensitive. Even a screenshot of a transaction slip can provide attackers with clues for phishing or identity theft. Chatbots are not designed to safeguard financial assets, so never input this type of data.
4. Confidential Work or Organizational Data
Drafting emails or reviewing project code with a chatbot may seem convenient, but it risks leaking proprietary information. Corporate documents, internal communications, or source code often carry significant commercial value. Even small fragments can give competitors or attackers critical insights. Always use sample or non-sensitive data instead.
5. Passwords and Usernames
Passwords are the keys to your digital life. Chatbots are not secure vaults, and even a single entry could remain in system logs. Always rely on password managers or encryption tools specifically designed for security. Never trust a chatbot to store or protect your digital keys.
How to Protect Your Information
Use Temporary Chat Mode: Like incognito browsing, this prevents conversations from being stored. Ideal for sensitive or experimental queries.
Delete Previous Conversations: Clear your history after sessions. Some services retain data for up to 30 days, so manual deletion matters.
Leverage Anonymization Tools: Use anonymization tools or privacy‑focused services that route your requests through secure channels, making it harder to track or link queries back to you. Services like Duck.ai anonymize requests, making user tracking nearly impossible.
Be Careful with File Sharing: Never upload personal documents, IDs, or corporate files. Even harmless-looking files may contain hidden metadata that reveals private details.
Raise Awareness: Many leaks happen due to ignorance. Educate colleagues and family about what should never be shared with chatbots. A shared culture of security is the best defense.
Practice Data Minimization: Always ask yourself: Do I really need to share this? If not, avoid it. Less data means less risk.
Verify Links and Outputs: If a chatbot generates a link, check its authenticity before clicking. Suspicious or unknown links can be phishing traps.
Conclusion: Protecting personal information in chatbots depends less on the tools themselves and more on your own awareness. By using temporary chat, deleting history, anonymizing requests, minimizing data, and staying alert to files and links, you can significantly reduce risks and keep your privacy intact.
This version keeps your original structure but integrates the complementary points directly into each item, making it clear, narrative, and practical.
Would you like me to now adapt this into a LinkedIn‑ready post (shorter, punchier, with hashtags) so you can share it with your Morning Team followers?