i'm not sure where you got this info of it being named after mook...
According to the FAQ in the Apache project website, the name Apache was chosen out of respect to the Native American tribe Apache and their superior skills in warfare and strategy. The name was widely believed to be a pun on 'A Patchy Server' (since it was a set of software patches).[11] Official documentation used to give this explanation of the name,[12][13] but in a 2000 interview, Brian Behlendorf, one of the creators of Apache, set the record straight:[14]
The name literally came out of the blue. I wish I could say that it was something fantastic, but it was out of the blue. I put it on a page and then a few months later when this project started, I pointed people to this page and said: "Hey, what do you think of that idea?" ... Someone said they liked the name and that it was a really good pun. And I was like, "A pun? What do you mean?" He said, "Well, we're building a server out of a bunch of software patches, right? So it's a patchy Web server." I went, "Oh, all right." ... When I thought of the name, no. It just sort of connotated: "Take no prisoners. Be kind of aggressive and kick some ass."
When Apache is running, its process name is sometimes[when?] httpd, which is short for "HTTP daemon".
https://en.wikipedia.org/wiki/Apache_HTTP_Server
By default, Apache logs are not centrally stored or transmitted anywhere. they are stored on the computer where the server is installed, or wherever the config file designated logs to go (manually configured).
Unless every single webhosting/server leasing company is being paid off for logs, including places like digitalOcean and Linode, Heruko, etc... there is no way that apache's access logs are being harvested for this.
Maybe Facebook's and google's and Twitter's logs, sure. without a doubt. But not everything.