[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fB4s4Sf0IEiJLt3qjsbPzML5rSITM6JQG6_rAyPwGVGw":3},{"lesson":4},{"id":5,"slug":6,"article_id":7,"title":8,"body":9,"prevention":10,"framework_refs":11,"framework_notes":16,"status":21,"created_at":22,"published_at":23,"article":24,"tags":28,"podcasts":41,"controls":42},"95898417-9fd1-4887-95a2-956bf4669974","dating-site-publicly-exposed-sensitive-member-profiles-revealing-sexual-orientation-and-religion","cbb0fbd1-771a-4786-b4ad-7d374027324e","Dating Site Publicly Exposed Sensitive Member Profiles, Revealing Sexual Orientation and Religion","Social Garden AS published member profiles — including photos and personal information — on the public homepages of its dating platforms, indirectly disclosing users' sexual orientation and religious beliefs without obtaining valid consent. Under GDPR Article 9, these categories constitute 'special category' data requiring explicit, informed consent before any processing or disclosure. The failure stemmed from a design or configuration decision that treated sensitive profile data as publicly viewable marketing content rather than protected personal information. This matters because exposure of sexual orientation or religious beliefs can lead to discrimination, harassment, or physical harm for affected individuals. Regulators are increasingly enforcing strict accountability for special category data, making this a costly compliance and reputational failure.","**Immediate actions:**\n- Audit all publicly accessible pages and APIs to identify any special category personal data (sexual orientation, religion, health, etc.) currently exposed without explicit consent.\n- Remove or restrict access to any member profile content visible to unauthenticated or general users until a lawful basis is confirmed.\n\n**Design & consent improvements:**\n- Implement privacy-by-default settings so user profiles are private unless users explicitly opt into public visibility.\n- Enforce a consent management workflow that obtains explicit, granular consent before any special category data is processed or displayed, documenting the legal basis for each processing activity.\n- Conduct a Data Protection Impact Assessment (DPIA) before launching or modifying any feature that processes special category data.\n\n**Long-term governance:**\n- Train product, design, and engineering teams to classify data sensitivity during feature design, ensuring special category data triggers additional review gates.\n- Establish a regular review cycle for all data processing activities to verify ongoing compliance with GDPR Article 9 requirements.",[12,13,14,15],"GDPR Article 9","GDPR Article 5","GDPR Article 25","NIST SP 800-53 PT-2: Authority to Process Personally Identifiable Information",{"GDPR Article 5":17,"GDPR Article 9":18,"GDPR Article 25":19,"NIST SP 800-53 PT-2: Authority to Process Personally Identifiable Information":20},"Article 5 requires data to be processed lawfully, fairly, and transparently, and limited to what is necessary (data minimisation); publishing sensitive profile data publicly violated these foundational principles.","Article 9 prohibits processing of special category data — including sexual orientation and religious beliefs — without explicit consent, which Social Garden failed to obtain before publicly displaying member profiles.","Article 25 mandates privacy by default and by design, meaning the platform should have defaulted member profiles to private rather than making them publicly visible.","PT-2 requires organisations to establish and document a legal authority before processing PII, directly addressing the absence of valid consent for processing special category data in this case.","published","2026-11-16T17:22:10.592528+00:00","2026-11-16T17:22:10.545+00:00",{"id":7,"url":25,"slug":26,"title":27},"https:\u002F\u002Fgdprhub.eu\u002Findex.php?title=Datatilsynet_(Norway)_-_24\u002F01411-15&diff=53854&oldid=53850","datatilsynet-norway-24-01411-15-2d5f0e","Datatilsynet (Norway) - 24\u002F01411-15",[29,35],{"id":30,"name":31,"slug":32,"description":33,"color":34},"c0dcc566-3654-4d70-8ede-262a198e732f","Regulatory Compliance","regulatory-compliance","GDPR, NIS2, DORA, sector-specific violations","#ec4899",{"id":36,"name":37,"slug":38,"description":39,"color":40},"c8b843a5-d5a7-41d1-8d3b-cabded09d2ef","Data Protection","data-protection","Unencrypted data, missing DLP, poor classification","#3b82f6",[],[43,47,51],{"slug":44,"name":45,"problem":46},"cloud-security-posture","Cloud security posture management (CSPM and CNAPP)","Misconfigured cloud storage and over-permissive roles get caught before they leak.",{"slug":48,"name":49,"problem":50},"saas-security-posture","SaaS security posture management (SSPM)","Business apps like Microsoft 365 and Salesforce stop leaking through risky settings and connected apps.",{"slug":52,"name":53,"problem":54},"data-loss-prevention","Data loss prevention (DLP)","Sensitive data cannot quietly leave by email, upload, USB stick or AI tool."]