The data-flow diagram has no vendor box in the path

You draw a browser, a TLS connection, and a server you rent. That's the drawing. The proxy that terminates TLS runs on that server, not on a Hoody tier in between. There is no central data plane to add, because there isn't one.

Hoody's API gets a small box off to the side, labeled with what it actually records: container created, snapshot taken, billing, API call metadata. It doesn't see terminal commands, files, database queries, or the HTTP your services answer. Hoody administers the machine; it doesn't route your traffic.

On most platforms question 14 takes a week and a lawyer. Here it takes a whiteboard.

The arrow from the user goes to your rack and stops there.