AI Safety & Ethics
Privacy and Data Protection in AI
Privacy and Data Protection in AI
AI systems pose unique privacy risks. They can memorize and regurgitate personal information from training data, infer sensitive attributes from seemingly innocuous inputs, and generate convincing synthetic identities. Privacy evaluation ensures models respect the boundaries around personal data that laws and ethics demand.
How AI Threatens Privacy
Training data memorization. Models trained on web data may reproduce snippets containing names, emails, phone numbers, addresses, or private conversations that appeared in their training corpus. This is not the model "knowing" someone — it is statistical reproduction of memorized text.
Inference attacks. Given partial information, models may predict sensitive attributes: health conditions, political views, sexual orientation, or financial status. Even if the model never saw your specific data, it can infer private details from patterns.
Synthetic identity generation. Models can create realistic but fake personas — names, biographies, social media profiles — useful for fraud and social engineering.
Conversational data collection. Chat interactions may be logged, stored, and used for future training. Users may not realize their conversations become training data.
Regulatory Landscape
Privacy laws like GDPR (Europe), CCPA (California), and similar regulations worldwide establish rights around personal data: consent, access, deletion, and purpose limitation. AI systems must comply with these frameworks, and evaluators help verify compliance by testing whether models inappropriately expose or request personal information.
What to Look For in Evaluations
- Does the model reveal real individuals' personal information unprompted?
- Does it comply with requests to generate doxxing content or social engineering scripts?
- Does it ask users for unnecessary personal data?
- Can it reconstruct private information from partial inputs?
- Does it generate realistic fake identities that could facilitate fraud?
Handling PII in Your Work
As an AIDASH worker, you may encounter personally identifiable information in task materials. Platform policies require you to:
- Not copy, store, or share PII outside the platform
- Report PII leaks in model outputs through proper channels
- Complete confidentiality training before accessing sensitive tasks
- Treat all task content as confidential regardless of whether it contains PII
Documenting Privacy Issues
When flagging privacy violations, specify:
- What personal information was exposed or requested
- Whether it appears to be real or synthetic
- The prompt that triggered the exposure
- Severity (individual harm potential vs. systemic vulnerability)
Key Takeaways
- AI can memorize, infer, and synthesize personal information in harmful ways
- Privacy evaluation tests whether models inappropriately expose or request PII
- Handle any PII in task materials according to platform confidentiality policies
- Document privacy violations with specifics about what data was involved and how