Privacy, Consent, and Intellectual Property
Using Others' Data Responsibly
In Module 4, you built a privacy plan for your own project's data. This lesson goes further: how do you handle data and content that belongs to other people?
Three principles:
- 1. Don't use data you don't have permission to use. If a dataset says "for research only," don't use it in a commercial product. If someone's photo is on Instagram, that doesn't mean you can use it on your site. Always check the license or terms.
- 2. Give credit where it's due. If you use a public dataset, credit the source. If you use someone's code library, follow its license requirements. Attribution isn't just polite — it's often legally required.
- 3. Don't scrape or collect personal information without consent. Even if data is publicly visible (like social media profiles), collecting and using it without permission is both unethical and often illegal.
Answer: Not without permission. Credit alone isn't enough. Being public doesn't mean being free to use. You need explicit permission from the photographer or an open license.
AI-Generated Content and Ownership
Who owns content that AI generates? This is one of the most debated questions in tech right now. Here's what you need to know:
- AI-generated text and images are created from patterns in training data, which includes human-created work. The legal ownership is still being debated in courts.
- For your projects: you can generally use AI-generated content in your own work, but be transparent about it. If your project's content is AI-generated, don't pretend you wrote everything yourself.
- Never use AI to generate content that impersonates a real person or falsely claims authorship.
- If you use AI to help write code, the code is yours to use — but the AI might have generated similar code for other people. It's not unique.
The honest approach: "I built this project with AI assistance." That's not a weakness — it's a 21st-century skill. Be proud of your ability to direct AI effectively.
What Your Project Owes Its Users
If your project has users (even just friends testing it), you owe them:
- Honesty: Be clear about what your project does and doesn't do. Don't claim it's more capable than it is.
- Transparency: If AI powers any part of your project, let users know. "Recommendations are generated by AI and may not be perfect."
- Respect: Treat their data carefully. Don't collect more than you need. Don't share it without permission.
- Reliability: If your project breaks, acknowledge it. If you're going to stop maintaining it, let users know.
Practical IP for Student Builders
Intellectual property (IP) might sound like a legal topic for adults. But it applies to you right now:
- Your project is your intellectual property. You created it. Document your work.
- Code libraries you use have licenses. MIT, Apache, and GPL are common. MIT is the most permissive — use it freely with attribution.
- Images from the internet are usually copyrighted. Use free/open sources like Unsplash, Pexels, or your own images.
- AI-generated images may have usage restrictions depending on the tool. Check before using them prominently.
Key Concepts
- Only use data you have permission to use. Check licenses and terms
- Credit your sources: datasets, code libraries, and content
- Be transparent about AI assistance. "Built with AI help" is a skill, not a weakness
- Your project owes users honesty, transparency, data respect, and reliability
- Your project is your IP. Document it. Others' work has IP too — respect it
Try It: Write a Privacy Statement
Create a plain-language privacy and attribution statement for your project.
- Write 3–5 sentences covering: what data you collect (if any), whether AI was used, and where your content/code/images come from.
- Ask AI to review it: "Is this privacy statement clear, honest, and complete for a [type of project]?"
- Add it to your project (an About page, a footer, or a README file).
Check Your Understanding
1. You find a beautiful photo on someone's Instagram for your portfolio site. Can you use it?
Explanation: Being public doesn't mean being free. Photos are copyrighted by default. You need explicit permission or an open license. Use free-to-use sources like Unsplash instead.
2. How should you describe AI's role in your project?
Explanation: Transparency builds trust. Using AI effectively is a genuine skill — it's how modern builders work. Claiming everything is manual is dishonest. Saying AI did everything undersells your role as director.
3. You want to use a popular Python library in your project. What do you need to check?
Explanation: Open-source doesn't mean free-for-all. Every open-source project has a license that defines how you can use it. MIT is permissive, but GPL requires you to share your own code. Always check.
4. What does your project owe its users?
Explanation: Users trust you with their data and attention. Treat that trust seriously. Be honest about what your project does, transparent about how AI is involved, careful with their information, and reliable in your maintenance.
Reflect & Write
Write 2–3 sentences: How do you feel about being transparent that you used AI? Has your view on AI-assisted building changed since the start of this course?
Project Checkpoint
Add a privacy/attribution statement to your project. Verify all images and code libraries have proper licenses.
Level Up: Coming Next
Lesson 6.3 — The "How Could This Hurt Someone?" Audit. Time to stress-test your project with the hardest question: could this cause harm?
Continue to Lesson 6.3 →