Designing for Privacy in an Increasingly Public World

Robert Stribley, a digital designer with two decades in the field, argues that designers should treat privacy as part of the experience they build. He frames privacy as control over personal information and explains why the stakes have grown, pointing to data breaches, identity theft, facial recognition built from publicly posted photos, and tracking of health-related browsing that became more sensitive after abortion rights changed in the United States.

The middle of the talk covers dark patterns, interface tricks that steer people into choices they did not intend. Examples include a pre-selected recurring donation, opt-out buttons that shame the user, and contact-importing prompts that send invitations to a person's friends. He reviews apps and services that made activity public or intrusive by default, and compares the EU's GDPR, which requires opt-in consent, with the American opt-out approach. He also notes that a few ordinary data points can identify someone even without obvious identifiers.

The closing section offers practical guidance: make privacy the default, avoid dark patterns, explain data use in plain language at the moment of collection, place privacy controls where people can find them, and warn users before changing their settings. He also suggests that designers push back on clients by framing privacy as a matter of reputation, legal exposure and cost. The takeaway is that privacy by design is a practice teams can adopt now, not only a legal requirement.