In general, we should consider all data we return to the user NTK and therefore, should look at all of the routes we return to the user to prevent return to the user. For a light example, when we query for a user's teams they belong to, we also return the createdAt and updatedAt. While these are likely not huge deals and are probably fine, we want to start a pattern of good practices in the code base and it should start with what we already have.
In general, we should consider all data we return to the user NTK and therefore, should look at all of the routes we return to the user to prevent return to the user. For a light example, when we query for a user's teams they belong to, we also return the
createdAtandupdatedAt. While these are likely not huge deals and are probably fine, we want to start a pattern of good practices in the code base and it should start with what we already have.