If you use a stateless client (like just rawdogging cli llama.cpp) there’s nothing to discover. Setting a program with an option to have logs to not do that could conceivably get you in trouble but using a widely used program that never had logs seems like it has to be fine. Maybe they could nail you for googling “which local llm approach generates logs?” also, don’t get nailed by your bash history!
Why do you think this would be less discoverable than hosting your own email server?
If you use a stateless client (like just rawdogging cli llama.cpp) there’s nothing to discover. Setting a program with an option to have logs to not do that could conceivably get you in trouble but using a widely used program that never had logs seems like it has to be fine. Maybe they could nail you for googling “which local llm approach generates logs?” also, don’t get nailed by your bash history!
Because you don't keep logs.
Because nobody would know about it unless you told them for some reason
That might fall under the “unethical” part of my question. Could “probably” get away with it if done carefully, but I’d rather be fully in compliance.
You’d need to hand that mac mini over if subpoenaed
Can’t hand over something that doesn’t exist if it’s running in a VM container and gets destroyed every 12 hours