In the first case, I think technically you could fit that data into the
PersonInImageWDetails structure, but parts of that are meant to be used with a Controlled Vocabulary and structures aren't necessarily easy to keep all the data in the proper places if you're using flattened tags.
I can't think of anything specific for logos.
For me, these would be places I would use
HierarchicalSubject. For example, a hierarchy of something like "Websites|Person name|http:\\facebook\blahblahblah" and "Logos|Company Logo".
But then I should have mentioned previously that it helps to have a Digital asset management (DAM) program that works well with
HierarchicalSubject. Lightroom, for example, does well. And while there are things about iMatch 5 that I don't care for (still using iMatch 3 for a lot of stuff), it does have great options with regards to metadata and
HierarchicalSubject in particular.
Here's an example. I've been adding Timezone IDs (e.g. America/Los_Angeles, Europe/Paris) and names (Pacific Standard Time, Central European Summer Time) to images just because I've found an easy way to add them. There's no tag that's made for it and if I created a tag specifically for it, it wouldn't show up in any DAM software anyway. But dropping it into
HierarchicalSubject, I end up with this (from iMatch 5)

.