App development / WORKING NOTE

Privacy starts at the architecture sketch

A privacy statement is easier to make precise when the system has a clear boundary. Start by drawing the data flow, before writing the promise.

3 min read · Open to revision

Name the data

“User data” is too broad to be a useful design unit. A camera frame, a document, a derived measurement, and a diagnostic log each have different purposes. List them separately. Then ask which ones the feature needs to retain, transmit, or discard.

Choose the smallest useful boundary

For a feature that can work on the device, keeping processing there can remove a whole category of data transfers. That choice also has costs: model downloads, device capability, energy use, and update delivery still need attention. Local processing is a design decision with tradeoffs, not a substitute for examining the rest of the system.

Let the product explain the boundary

DistanceDefender processes camera information on the Mac. RAG Playground runs its document and retrieval workflows in the browser. These are concrete boundaries a visitor can understand. They are more useful than a broad claim that a product is simply “secure.”

Review the edges

Look at logs, analytics, support requests, and error reporting as well as the core feature. A local workflow can still send information through a peripheral service. The final description should match the whole product, including those less visible paths.

Find a thread

Search across projects, notes, and ideas.