Separate Encrypted Persistent File vs Embedded Persistent Data in Ren'Py Saves

Ren'Py keeps persistent data alongside save data by default, and the engine exposes config.encrypted_persistent as an optional flag. The documented description does not make clear whether enabling that flag encrypts persistent values wherever they are written, or whether it only takes effect when persistent data is written to a dedicated persistent file.

That distinction matters for a project shipping a single distributed build that wants save files to stay portable while keeping unlock flags, gallery progress, or preference data out of plain text. A separate persistent file can be encrypted and managed independently, but adds a second artifact to back up, migrate, and clear. Embedding persistent data in each save keeps distribution simple, yet those values may remain readable inside the save container.

Version assumption: Ren'Py 8.x defaults; older releases and custom persistence overrides may behave differently.

Which behavior does config.encrypted_persistent actually govern? Does a separate persistent file get created automatically, or must it be configured explicitly? For a small project, which trade-off is preferable?