Yes and No.
Encryption isn't a "have it" or "don't have it" sort of proposition. The concept of encryption only makes sense in context.
As an example that should more obviously demonstrate the failure: Imagine you have a document that needs to be kept safe. You upload it to your Dropbox account. Now, is it encrypted?
Yes, it was encrypted in transit. Dropbox uses HTTPS, so it was encrypted using TLS during upload (and any download). It's then decrypted on the other side after it's been transferred.
Yes, it's is encrypted in storage (as far as we know). Dropbox says they encrypt all data on their servers using keys specific to your account. It's then transparently decrypted for you on demand.
But No, the document is not encrypted in a way that matters to you. Dropbox syncs the files to all your computers, and stores a plain text copy on your machine. So if anyone looks at your computer, they can read the document without having to circumvent any encryption at all.
When encrypting data, you have to figure out what you're trying to protect and whom you're trying to protect it from. You need to understand what you're trying to prevent with your encryption. Once you understand what you're trying to accomplish, it should be immediately obvious whether the encryption you have is doing you any good or not.