Privacy settings grouped by functional area with plain-language descriptions

Privacy settings that users cannot find or understand are functionally absent. GDPR Art. 7(3) requires withdrawal of consent to be straightforward — a single flat list of 40 settings with technical labels like 'behavioral_targeting_v2' does not meet that standard. Poorly organized settings also increase support burden and erode trust: users who cannot find a control assume the platform is hiding it. GDPR Art. 25 (privacy by design) requires that controls be accessible and meaningful, not merely present.

Group privacy settings into functional sections — Profile Visibility, Communication, Data & Analytics — and write plain-language descriptions for each toggle. Avoid technical labels in the UI. In src/app/settings/privacy/page.tsx:

<section aria-labelledby="profile-visibility-heading">
  <h2 id="profile-visibility-heading">Profile Visibility</h2>
  <p>Control who can see your profile and posts.</p>
  <SettingToggle
    id="profileVisibility"
    label="Profile visible to"
    options={['Everyone', 'Followers only', 'Only me']}
    description="Who can view your profile page and basic information."
  />
</section>

<section aria-labelledby="data-heading">
  <h2 id="data-heading">Data & Analytics</h2>
  <p>Control how your usage data is collected and used.</p>
  <SettingToggle
    id="analyticsOptIn"
    label="Send anonymous usage analytics"
    description="Helps us improve the platform. No personal data is shared."
  />
</section>

Test the settings page with actual users unfamiliar with the platform — if they cannot find a specific control within 30 seconds, the organization needs revision.