A good question to ask yourself: "Presume that my daemon is compromised by an attacker ...
* ... what processes can it trace, debug, read/write the memory spaces and environments of, or send signals to?"
* ... what files, devices, and directories can it read and write?"
* ... what files, devices, and directories does it own, and can thus grant access to?"
Then ask: "How does the answer change if instead of all of my daemons running as the same (even if unprivileged) user they each run as different users, some (where appropriate) having no write access to anything and owning no files nor directories at all?"
Generally it's fairly easy to make a system user for an application if no special accesses are required - just make a custom system user for the application, and ensure it can access the various things it needs to touch (eg: logging).