Security boundaries designed around a private CV

Dashboard reads and writes are scoped to the authenticated owner.

Uploads are identified by content, scanned, and stored under server-generated keys.

Public rendering imports no authoring, parser, AI, or private-storage path.

Any page can be given its own share password, checked server-side, without exposing which pages exist to someone who doesn't have it.

An unpublished portfolio and a typo return the identical response, so probing addresses can't tell the two apart.

A security concern reaches the team directly through the contact page — no need to describe it publicly first.