| UI or UX | UI + UX - Durable privacy-control surface for account, product, device, app-access, activity, visibility, and sharing settings | UI + UX - Dedicated user or app configuration management surface | UI + UX - Persistent hub for communication, consent, topic, privacy, language, and personalization choices | UI + UX - Specific opt-in decision for optional data use, participation, communication, sharing, or training | UI + UX - Contextual operating-system or browser permission request for device resources, powerful browser features, private user data, or local capabilities | UI + UX - User or administrator workflow for selecting, preparing, securing, downloading, transferring, and verifying data export packages |
| UI guidance | Render privacy settings as a returnable control surface with current effective values, privacy categories, data types, app or service access, account/device/product scope, source of truth, managed or unavailable reasons, last updated status, and save or immediate-apply feedback. | Render settings management as a durable configuration surface with a clear Settings or Preferences entry point, grouped categories, current values, setting descriptions, ownership or scope labels, dependencies, save or immediate-apply behavior, status feedback, search or section navigation for larger sets, and reset or restore defaults where appropriate. | Render a preference center as a returnable hub with categories for communications, channels, topics or interests, notification delivery, privacy and data sharing, cookie or tracking consent, personalization, language or locale, required messages, managed values, source-of-truth status, and save feedback. | Render a consent prompt as a focused opt-in decision that names the requester, purpose, data involved, optionality, benefit, consequence of declining, withdrawal route, and consent record before the user chooses. | Render a permission request as a contextual feature gate that names the resource, user action, immediate benefit, system prompt timing, available choices, and fallback before invoking the OS or browser permission prompt. | Render data export as a job-based workflow with export scope, data categories, format, destination, estimated size, preparation status, expiry, security requirements, and download or transfer actions. |
| UX guidance | Use privacy settings when users need to inspect and change ongoing privacy posture for saved activity, profile visibility, app access, device permissions, data sharing, ad personalization, location, connected apps, or product privacy dashboards. | Use settings management when users need to review and change persistent app, account, workspace, notification, privacy, display, integration, or system behavior outside the immediate task flow. | Make the effective result clear before and after save: what changes now, what stays required, which rows are policy-managed, which external system owns the value, and where users can withdraw consent or unsubscribe. | Use consent prompt when the product needs the user to knowingly agree to a specific optional data-processing purpose such as marketing, research participation, AI training, personalization, partner sharing, or sensitive-data use. | Use permission request when a feature needs operating-system or browser authorization for resources such as location, camera, microphone, photos, contacts, notifications, Bluetooth, clipboard, motion sensors, or other powerful features. | Use data export when users need a portable copy of personal, account, workspace, product, activity, or organization data for reuse, compliance, migration, backup, or review. |
| Good UI | An account privacy dashboard groups Saved activity, Profile visibility, Ad personalization, Connected apps, Location history, Device permissions, and Data deletion, with current values, scope labels, last updated times, and unavailable reasons. | A notification settings page groups channels, quiet hours, digest frequency, and workspace scope; each row shows current value, effect, dependency, and whether changes save immediately. | A customer account preference center shows Email, SMS, Push, Topics, Cookies, Data sharing, Language, and Required service messages, each with current status, scope, and last saved time. | An AI writing tool asks whether the user wants workspace snippets used to improve future suggestions, shows included data types, keeps the default off, and records the consent version after opt-in. | A field service app asks for location only when the user taps Start route, explains that current location will verify arrival, then opens the system permission prompt and offers manual address entry if declined. | A privacy dashboard lets a user choose activity, profile, files, messages, and billing categories, shows JSON or CSV availability, requires reauthentication, creates archive EXP-2048, then shows download expiry and checksum. |
| Bad UI | A single Privacy mode switch claims to turn everything off but leaves ad personalization, public profile visibility, connected apps, and activity retention unchanged. | Users change the wrong scope because local, account, workspace, and organization settings look identical. | A single Receive updates switch hides whether it controls marketing email, SMS, push, product notices, analytics consent, or service messages. | A modal says By continuing you agree to personalized offers and partner sharing, with a large Continue button and a small privacy policy link. | An app asks for location, contacts, photos, and notifications on first launch before the user knows why any resource is needed. | The export link stays valid forever, exposes sensitive files to the wrong account, and is presented next to Delete account as though export deletes data. |
| Good UX | A user pauses saved activity, clears search history for a date range, disables ad personalization, hides birthday visibility, revokes a connected app, and sees which values apply immediately versus after sync. | A user turns off weekly digest emails, sees the setting save immediately, keeps urgent security emails enabled, and understands the workspace-level override. | A user turns off promotional email, keeps outage SMS and account security email, changes language to Spanish, withdraws ad personalization, and sees which transactional messages remain required. | A user consents to a beta research study, sees what data will be reviewed, receives a saved confirmation, and later withdraws from the account privacy page with the same purpose label. | A user denies precise location, chooses approximate location instead, and the app still shows nearby pickup points with lower accuracy. | A user requests a machine-readable archive, sees which data categories are eligible for portability, waits for preparation, downloads the package before expiry, and gets a manifest listing omitted records. |
| Bad UX | A user withdraws a consent prompt, but privacy settings still show personalization enabled because the source of truth and sync state are hidden. | A user changes a privacy setting thinking it affects only one project, but the value applies to the whole account. | A user opts out of marketing email but continues receiving promotional SMS because the channel matrix was hidden. | A user clicks Next to finish onboarding and unknowingly opts into marketing because the consent copy was bundled into the terms paragraph. | A user denies microphone access and the app loops the same system prompt every time they tap anything in the support screen. | The manifest lists raw sensitive values instead of safe category and count information. |
| Best fit | Users need ongoing control over personal data collection, saved activity, visibility, app access, device permissions, connected services, data sharing, or personalization. | Users need to inspect and change persistent app, account, workspace, privacy, notification, display, integration, device, or system behavior. | Users need to revisit and change communication, consent, topic, personalization, privacy, channel, language, or data-sharing choices. | The product needs a user's active agreement for optional data use, marketing, research participation, personalization, partner sharing, AI training, or sensitive-data processing. | A feature needs operating-system, browser, or device authorization to access location, camera, microphone, photos, contacts, notifications, Bluetooth, clipboard, motion sensors, storage access, or another powerful feature. | Users need to download or transfer a copy of account, workspace, personal, product, activity, or organization data. |
| Avoid when | The task is a first-time opt-in to one optional purpose; use consent prompt. | The task is a one-time transaction, submission, setup wizard, or onboarding flow. | The product only needs a small app setting unrelated to communications, consent, or personalization. | The choice is only about non-essential cookies or device storage; use cookie banner. | The decision is consent to optional data use rather than access to a device or browser resource. | The user is importing records into the product; use bulk import. |
| Required state | Privacy settings overview with categories and current effective values. | Settings overview with categories and current values | Overview with preference categories and current effective status | Pre-consent state with optional processing off and the core task still understandable. | Contextual request state tied to the user action that needs the resource. | Eligible data categories and unavailable categories state. |
| Accessibility burden | Use clear headings, labels, descriptions, and status text for each privacy category and control. | Use headings, section labels, fieldsets, and persistent labels so settings groups and controls have clear programmatic names. | Group categories with headings, fieldsets, legends, and persistent labels that name the affected channel, purpose, topic, source, and scope. | Associate every checkbox or toggle with a complete purpose label and consequence description. | Use a labelled region or dialog title that names the resource and feature, such as Allow location for route check-in. | Use persistent status text for queued, preparing, ready, partial, failed, expired, and downloaded states rather than relying on a spinner or toast alone. |
| Common misuse | Replacing privacy settings with a privacy policy link or legal notice. | Using settings as a dumping ground for unrelated navigation, billing, help, profile setup, onboarding, or destructive account actions. | Using one master preference switch for communication, privacy, cookies, topics, and required messages. | Treating continued use, scrolling, closing, or inactivity as consent. | Asking for multiple resources at launch before the user has attempted the relevant feature. | Confusing export with delete account, privacy preference changes, migration import, or audit-log investigation. |