liveBook · Manning

Privacy

As explained in LLMs in Production

The protection of data from unauthorized access, disclosure, misuse, or loss while respecting requirements governing personal information.

Suppose an LLM assistant needs access to sensitive maintenance manuals. Uploading those manuals to another company may be unacceptable, even if the service is convenient. Fine-tuning and running a model locally is an alternative when the information must remain private. section 1.2.2

The same constraint can keep a police analytics team from using a hosted assistant for its most valuable work: the data and conversations are too sensitive to expose. Privacy is therefore a build-versus-buy question, not just a feature to consider after choosing a model. Local deployment still calls for a safe, secure setup; building your own model does not settle that work by itself. section 1.2.2

How LLMs in Production covers it

How deep it goes
Explains the deployment trade-off through scenarios but does not specify privacy controls or a secure deployment procedure.
Examples
Uses sensitive military maintenance manuals and police analytics conversations to illustrate why a hosted assistant may be unsuitable.
What you can do after
Evaluate/understand when sensitive data makes local LLM development preferable to uploading information to another company.
How it connects
Connects privacy to LLM fine-tuning, local deployment, hosted services, and prompt engineering.

Also explained in

Compare how 21 books explain privacy →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of LLMs in Production. The section links point to the parts of the book it draws on.