Privacy should feel handled, not urgent.
Cloaked lives in anxious moments — data leaks, identity exposure, a name where it shouldn't be. Every decision in this system exists to lower the temperature of those moments: softer surfaces, literal language, one clear next step. This is the long-form reasoning behind every token.
Calm is the feature.
Our users come to Cloaked because something scared them. A data broker, a breach notification, a weird email from a stranger. The interface cannot add to that. Every pixel is doing emotional work before it does functional work.
That is why we lean on a cream canvas instead of stark white, 1.5px icon strokes instead of bold ones, rounded corners instead of sharp, and one Firey accent instead of a rainbow. The design doesn't shout because the situation is already loud.
If the screen can lower your heart rate by one beat per minute, it's done its job.
Say the real thing.
Most privacy products hide behind vague copy — “your data is safe,” “we've got you covered.” Users have been burned by that language for twenty years. They don't believe it anymore, and they shouldn't.
So we write the specifics. “Removed from 23 of 47 broker sites.” “Your address appeared on Spokeo 4 days ago.” The numbers aren't decoration; they're the only thing that rebuilds trust. Vague is the enemy. Concrete is the product.
One primary action per screen.
Anxious users scan, they don't read. If two things look equally important, they do neither. So every screen earns exactly one Firey button — the one thing we're asking them to do next. Everything else is tertiary, text-mono, or text link.
This is a design constraint but it's also a product discipline. If a screen feels like it needs two primary buttons, the screen probably needs to become two screens.
Data looks like data.
Cloaked shows people numbers that affect their real lives — breach counts, removal progress, exposure scores. Those numbers have to feel machine-generated, not marketing-generated.
That's what the mono typeface is for. Anything a computer counted gets STK Bureau Mono. It's a small signal that says “we didn't make this up.” Users can trust a number that looks like it came from a terminal more than one that looks like it came from a press release.
Good defaults, few knobs.
Privacy software has a long history of pushing the complexity onto the user — checkboxes, toggles, preferences, “advanced settings.” That's how people end up less safe, not more. Every option is a tax.
Cloaked components arrive opinionated. Dark mode, density settings, and theme switches are earned, not assumed. When we add a knob, we add it because there's evidence that the default genuinely harms a real group of users — not because a stakeholder wanted choice for its own sake.
Design disappears on purpose.
The best compliment a Cloaked screen can get is that nobody remembered what it looked like — they just remembered that the problem got smaller. We are not trying to be memorable. We are trying to be useful and then invisible.
This is why we resist trend-chasing. No glassmorphism, no AI sparkle effects, no neon gradients. The system is built to still feel right five years from now, on the day someone opens the app because the worst thing just happened.