Refactor models for better readability

**Feature request**
It would be great to have encryption for lib.

**Use case**
Many users need this functionality for production deployments.

**Implementation idea**
Add a new config option `enable_encryption` with default `false`.

The issue names no files, tests, or entry points. First trace how library configuration is loaded and where production-facing library behavior is defined; clarify what data encryption covers, then verify that enable_encryption defaults to false and the requested behavior is covered by tests.

Written by the indexing model from the issue text.