Data CloudArchitect (Hardest)enrichmentethicsthird-party-data
Design ethical use policy for third-party enrichment in Data Cloud
Real World Scenario
Marketing purchased demographic enrichment feed; privacy office questions lawful basis and accuracy for credit-adjacent attributes.
Expected Answer
• Legal review per enrichment vendor and attribute category
• Document purpose limitation — no re-use for undisclosed decisions
• Accuracy sampling and opt-out propagation to enriched attributes
• Prohibit sensitive category enrichment where regulated
• Transparency in privacy notice about third-party data sources
• Technical isolation of enrichment streams for easier removal
• Annual vendor reassessment and contract alignment
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Legal review per enrichment vendor and attribute category. Document purpose limitation — no re-use for undisclosed decisions. Pick based on your integration pattern and team capability. Third-party data is liability inventory — architects catalog what enters unified profile and why. Document the decision in an ADR and align with enterprise standards.
Architect Perspective
Third-party data is liability inventory — architects catalog what enters unified profile and why.