Cloaked Design System 4.5

Privacy that feels handled — and worth opening.

Cloaked lives in anxious moments — data leaks, identity exposure, a name where it shouldn't be. The 4.5 system is built to lower the temperature of those moments while feeling unmistakably premium: calm surfaces, focused attention, layered light and depth that signal visibility and protection, and motion that explains what the system is doing.

01

Calm & comforting technology.

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 Brand/300 Cloaked accent instead of a rainbow. The design doesn't shout because the situation is already loud.

Calm is not the same as quiet. The system fades into the background while still feeling intelligent and capable — the kind of competence that doesn't need to announce itself.

If the screen can lower your heart rate by one beat per minute, it's done its job.
02

Premium consumer experience.

Most privacy products look like enterprise software dressed in dark mode. Cloaked is closer to a modern consumer brand than a traditional cybersecurity product — the texture of an app you'd actually want to open, not one you tolerate when something goes wrong.

Premium, here, is restraint. Considered typography, generous spacing, surfaces and motion that feel built rather than assembled. Components arrive opinionated: dark mode, density settings, and theme switches are earned, not assumed. Consumer products people love don't tax their users with choice for its own sake.

03

Focused interfaces.

Anxious users scan, they don't read. If two things look equally important, they do neither. Less clutter, stronger hierarchy, intentional attention flow.

Every screen earns exactly one Brand/300 Cloaked 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 also a product discipline: if a screen feels like it needs two primary buttons, the screen probably needs to become two screens.

04

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.

05

Insight first.

Cloaked sits on top of a lot of numbers — broker counts, removal progress, exposure scores, breach timelines, account graphs. We don't ask users to read all of it. The default view is the conclusion, not the table.

One sentence that says what the numbers mean. One next step that follows from it. The raw rows, the per-source breakdown, and the underlying counts are still there, one tap away, for the user who wants to verify. Insight first; detail on demand.

The discipline is editorial. Before we show a number, we ask what it would change if the user saw it. If the answer is “nothing,” the number stays in the drawer.

06

Transparency & depth.

Privacy is, at its core, about visibility — knowing what's exposed, what's protected, what's moving where. The interface mirrors that idea. Glass, lighting, reflections, and layered environments are the visual grammar of seeing through and being protected — not decoration.

Depth has rules. Layers should feel earned: a clear surface in front of a soft scene, not stacked panels for their own sake. Light falls in one direction and stays consistent across a flow. Reflection and translucency belong to moments where the system is showing you something it has discovered or is actively shielding — never as ornament.

07

Motion with purpose.

Animation is the part of the interface that does the explaining. It shows where attention went, what the system noticed, and how one state became the next. Motion guides understanding and reinforces the sense that something intelligent is working on your behalf.

So we move with reason. Transitions follow the path the user's eye is already on. Entrances are soft, never theatrical. Loading states tell you what's happening, not just that something is. If an animation can be removed without losing meaning, it should be.