SSL/TLS

TLS encrypts traffic between two endpoints. A third party listening on the network cannot read the content, and the server’s identity is verified by certificate, making interception attacks harder.

What it does not protect is data at rest on either end. TLS does not encrypt data stored on the server; database content, log records, and backups all sit outside this layer.

That distinction is often blurred in marketing copy. The word "encrypted" frequently describes transport encryption alone, and what it means should be stated explicitly.

TLS today is a baseline expectation rather than a differentiator; a product using TLS is not something to boast about. The real questions go deeper.

Is data stored encrypted on the server, are backups encrypted, do logs hold sensitive content, and how is certificate management handled? These questions reveal a product’s actual security posture.

The second group concerns access: who can reach which data, and is that access logged? Encryption prevents eavesdropping, not unauthorised access — these are different risks.

Security claims should be verifiable. Phrases like "end-to-end encryption" carry a specific technical meaning and should not be used without a matching implementation; this claim is deliberately avoided in KobiGPT documentation.

The right approach is stating concretely what happens at each layer: is there transport encryption, where is data stored, how is access limited, is there an audit log?

That concreteness is what to look for in a vendor assessment. A vendor answering layer by layer, rather than with general security language, has made its claim verifiable.