Case Study 01
Ephemeral
Secure investigative infrastructure for journalists, academics, and institutional auditors.
The brand
Technical and restrained. The direction was infrastructure from the start. The challenge was sustaining that register across a full landing page without it reading as cold or inaccessible.
The audience
Professionals for whom exposure has real consequences. The copy doesn't persuade, it qualifies. The reader should feel that Ephemeral was built specifically for how they work.
The work
A landing page and a crisis communications package covering three formats: public statement, journalist briefing, and internal communication. The same event, written from three different positions.
Ephemeral presentation
The landing
The headline, "The work remains. Not its traces," sets the product's core claim without explaining it. It assumes the reader understands the risk, which is the first qualification: if you need this explained, Ephemeral is not for you.
The structure follows the same logic. Each section advances a single argument rather than listing features. The stakes section exists to establish that the problem is infrastructural, not behavioral, before the product is introduced. By the time the reader reaches how it works, they already understand why it works that way.
The governance section does something specific: it converts trust claims into structural ones. "We cannot sell any data" is not a policy statement, it is a technical one. The distinction is the entire argument.
As a landing page, it reads like the product itself: contained, precise, and nothing left over.
View landing page
Ephemeral landing page
The crisis package
A crisis communications package is a test of register. The press statement and the media Q&A had to read as institutional without reading as evasive. The language is measured and precise: it confirms what happened, explains what the architecture allows, and stops there. No overclaiming, no deflection.
The internal memo was written for a different reader entirely. Where the press statement manages perception, the memo manages people. The tone shifts from formal to direct, from public to internal, without losing the same underlying restraint.
The decision across all three formats was to let the architecture do the work. Ephemeral doesn't need to argue that it protects users. It only needs to explain what the system is capable of producing, and what it isn't.
As a package, it reads like something that already existed before the crisis happened. Preparedness, not reaction.
View press statement View media Q&A View internal memo
Ephemeral crisis package