A misread screen is an incident.
369 HERTZ · CREATIVE TECHNOLOGY STUDIORECORD 001 / HOME
We design and build interfaces for products where data handling is the hard part. Research through merged code, in one set of hands.
Q·01
“Is this for us?”
If your interface is where an exposed record or a bad configuration starts, yes.
Products that expose complex systems to expert users have to make real technical state readable. Regulated environments are the sharpest version of this problem, and they are where the track record runs deepest. Research, design, and front-end engineering stay in the same hands from start to finish; back-end, infrastructure, and the decisions only your team can make stay with your team.
Data governance & privacy01
Consent, retention, and access rules an admin has to read right the first time.
Fintech02
Permissions, audit, and money movement with no ambiguity.
Health03
Consent and record access under HIPAA-grade scrutiny.
AI tooling04
Dataset, evaluation, and model-behavior surfaces experts trust.
Robotics & telemetry05
Live operational state where a misread is a physical event.
Developer tools06
Dense technical surfaces for users who notice everything.
Q·02
“What do we actually get?”
Work taken as far as it needs to go, through to production code most studios can't ship.
Findings land in the form that fits: a report, design files, a prototype, a spec. When the interface should ship, the engagement ends as tested TypeScript merged into your repository, reviewed by your engineers, in your CI, under your standards.
One thread from research to merge: the person who watched the session writes the component.
HOW ENGAGEMENTS RUN
Q·03
NAMES WITHHELD BY AGREEMENT“Who have you worked with?”
You won't find client names here. Neither will anyone find yours.
Discretion is policy, not inexperience: engagements aren't published, pitched, or hinted at. What we can show is the shape of the work.
HOW CONFIDENTIALITY IS HANDLED
Q·04
“Will this survive our security review?”
The paperwork is ready before anyone asks.
Vendor diligence shouldn't slow the engagement down. Everything is published up front.
SEND THIS PAGE TO PROCUREMENT
- Data Processing Agreement, ready to countersignAVAILABLE
- Sub-processor list, published and versionedPUBLISHED
- Security questionnaires (SIG, CAIQ) answered on requestON REQUEST
- No production data access, we work against fixtures and stagingBY DESIGN
Q·05
“Can you show us anything?”
Client work stays private. Studio reasoning is published.
Essays on privacy-respecting interface design and consent architecture, plus reference builds: hypothetical products, worked as if they were real.
Q·06 · THE LAST QUESTION
“What's the first step?”
If your product's hardest problem is making sensitive data safe to work with, start with a 30-minute call. No deck.
NEXT · RECORD 002 / APPROACH