The hard part of privacy is not the policy: it is the design. Much of what follows is not a promise, it is the absence of a path in the code. The corresponding technical document is SEGURANCA.md, handed to the client's IT team during evaluation.
The organisation's panel suppresses any slice with fewer than five sessions. Suppression happens in storage, not on screen — slicing filters successively does not get around it.
No other user reads a manager's session, not even by direct link. The response for another author's session is identical to that of a session that does not exist.
Support access only exists with a record visible to the session's owner. The record is append-only: there is no delete operation.
The aggregate has no drill-down to the individual session. It is an absent route, not an unchecked permission — there is no key to join on.