Three completely different ways to transform data — used interchangeably in conversation, and confusing them in practice is a genuine, common security mistake.
All three take some input and produce a different-looking output, so from a distance they look like variations on the same idea. They aren't. Encoding changes the format of data for compatibility — it's fully reversible by anyone, with no secret involved, and it was never designed to hide anything. Encryption changes data specifically to hide it, using an algorithm plus a secret key — reversible, but only by whoever holds the correct key. Hashing produces a fixed-size fingerprint of the data and is deliberately built to never be reversed at all — there is no key that turns a hash back into the original. Mixing these up isn't just a vocabulary slip. Treating a merely encoded value as if it were protected is a real category of security incident, and it happens because encoding looks — to the eye — exactly like the other two.