I might have a thing or two to say about that.
However, that doesn't erase the fact that the restaurant now has more data on their customers that they wouldn't have had before.
Depending on the state's library confidentiality laws, this information is protected from disclosure. But again, the library now has created a paper trail of a patron's use of the library.
And that's just the beginning.
What happens if this data is entered into a spreadsheet on a local work computer? A database that lives in a 3rd party cloud service?
What starts out with a paper log fast becomes a privacy nightmare.
When tech companies start collecting data from contact tracing apps, the library has very little recourse in protecting the patron's right to privacy (in this case just visiting the library).
The other big can of privacy worms is patron health data.
Some people might not be aware that libraries are now collecting patron health data as part of the reopening process.
Again, once you collect the data, there's the risk of harm through a data breach or leak.
I've addressed some of these concerns at chooseprivacyeveryday.org/when-libraries…
One thing that folks keep saying is that any type of health data is protected by HIPAA.
Unless you're working in a medical library that fits HIPAA's definitions of a covered entity or business associate, that health data isn't protected under HIPAA.
</IANAL>
If you're considering collecting patron health data, you need to take a long, hard look at your library's data protections.
How about public records request regulations? I know of at least one time where patron medical data was released through a public records request.