They're claiming "end to end" encryption, which usually implies the service is unable to spy on individual users that are communicating to one-another over an individualized channel.
However in this case there are no other users, and their server is one of the "ends" doing the communicating, which is... perhaps not a literal contradiction in terms, but certainly breaking the spirit of the phrase.
I can't blame most people for calling TLS "E2EE", even some folks in industry, but it's not great for a company to advertise that you offer X if the meaning of X has shifted so drastically in the last decade.
Papers in academia and the greater industry[2] also referred to it in this way at the time.
Stack Overflow has plenty of examples of folks calling it "end to end encryption" and you can start to see the time period after the Signal protocol and WhatsApp implemented it that the term started to take on a much wider meaning[4]
This also came up a lot in the context of games that rolled out client side encryption for packets on the way to the server. Folks would run MITM applications on their computer to intercept game packets coming out of the client and back from the server. Clever mechanisms were setup for key management and key exchange[3].
[0] as SSL became more common lots of tooling broke at the network level around packet inspection, routing, caching, etc. As well as engineers "having fun" on Friday nights looking at what folks were looking at.
[1] Stack Overflow's security section has references from that era
[2] "Encrypting the internet" (2010) - https://dl.acm.org/doi/10.1145/1851275.1851200
[3] Habbo Hotel's prime and generator being hidden in one of the dynamic images fetched from the server as well as their DH mechanism comes to mind.
[4] Jabber/XMPP however used E2EE in the more modern sense around that time as they were exploring going beyond TLS and having true E2EE.
Granted, it's a marketing piece trying to sell a product, but still.
You can easily find these references in the literature, often comparing link encryption with end-to-end encryption. Some of the earliest papers outlining the plans for SSL in the 90s (Analysis of the SSL 3.0 Protocol) are based on this exact foundation from the 80s (End-To-End Arguments in System Design).
Hell, you can even go back to 1978 and see MITRE discussing this exact thing in "Limitations of end-to-end encryption in secure computer networks".
While you are technically correct in a network topology sense (where the "ends" are the TCP connection points), that definition has been obsolete in consumer privacy contexts for a decade now due to "true" E2EE encryption.
If we use your definition, then Gmail, Facebook, and Amazon are all "End-to-End Encrypted" because the traffic is encrypted between my client and their server. But we don't call them E2EE because the service provider holds the keys and can see the data.
In 2025, when a company claims a camera product is "E2EE", a consumer interprets that to mean "Zero Knowledge". I.e. the provider cannot see the video feeds. If Kohler holds the keys to analyze the data, that is Encryption in Transit, not E2EE. Even though in an older sense (which is what my original comment was saying), it was "End to End Encrypted" because the two ends were defined as Client and Server and not Client to Client (e.g. FB Messenger User1 and FB Messenger User2).
That may or may not be the case. TLS is always terminated at a load balancer that uses TLS but it's still common to use HTTP within datacenters. So it may not be E2EE and it's a meaningful security feature.
Am I understanding correctly that the other end of this is a rear end?
Of course, only authorized users could see the data, but that was a different compliance line item.
Bank data is never E2EE because the bank needs to see it. If banks call it E2EE they are misusing the term. E2EE for financial transactions would look like e.g. ZCash.
That being said, the person you're replying to seems to be saying that "the server" is always an "intended" end, which is wrong.
Are we talking about 2 different things here?
This is what it takes to make a financial transaction E2EE. I'm not saying that banks could or should do this. I'm just saying that their systems do not qualify as E2EE unless they do. It's not ambiguous.
My understanding is that banks, at least in the US, need to have fairly extensive knowledge relating to all transfers of money, both for fraud handling and for non-fraud (money laundering, etc). A transaction they can't know anything about other than "transfer X money to some recipient you can't know anything about" just doesn't seem realistic with the regulations involved.
Plus, even "transfer X money to some recipient you can't know anything about" is a message that you're sending _to_ the bank, that they have to be able to decode and read. And, presumably, you'd encrypt that message and expect the bank to decrypt it.
Honestly, I don't understand what argument is that you're not sending a message TO the bank, and they need to be able to read it in order to act on it, and they need to decrypt it to read it. The bank is the target of the message, they are one of the "ends" in E2EE.
I feel like I need an "Explain this like I'm 5", because clearly you believe differently than me... and I don't understand _how_ it can be otherwise.
It doesn't "imply", it outright states that. Their server isn't the end, it's the middle. They're not "breaking the spirit" or something, what they are doing is called lying.
But in all seriousness, of course they can access the data. Otherwise who else would process it to give any health results back? I don't think encryption in transit is relevant to privacy concerns because the concerns are about such data being tied to you at all, in any way. At the same time, yes, this could product valuable health information.
Their better bet would be to allow full anonymity, so even if there is a leak (yeah, the puns write themselves), there is never a connection between this data and your person.
Doing on device compute is probably expensive and would prohibit such a product based on the economics but ITS A GENITAL CAM
Well it could be processed on-device.
It's "of course" for very knowledgeable people, normal people just assume that it means guaranteed privacy
When companies first wanted to sell things over the Web, a concern I heard a lot was that consumers would be afraid of getting ripped off somehow. So companies started emphasizing prominently how the customer was protected with n bits of encryption. As if this solved the problem. It did not, but people were confused by confident buzzwords.
(I was reminded of this, because I actually saw a modern Web site touting that prominently just last week, like maybe they were working from a 30 year-old Dotcom Marketing for Dummies book, and it was still not very applicable to the concern.)
Some marketers lie, or don't care what the truth is. They want success, and bonuses, and promotions. And, really, a toilet company possibly getting class-action sued for a feces camera that behaves in an unexpected way, that attorneys would have to convince a judge was misrepresented, and then quantify the unclear harm, and finally settle, several years later, for lawyers' fees and a $10 off coupon for the latest model Voyeur Toilet 3000... isn't on the radar of the marketers.
But the linked privacy policy talks about making anonymous (aka de-identified) bulk data sets and using them for "lawful business purposes" (aka anything they want that's not illegal).
Anyway a chemical or biological sensor in the bowl might be more useful.
Optical could be useful if it's doing spectrographic analysis: the color of poo and urine is sometimes informative.
Then you can incorporate this into a "health care product" and charge insurance companies insane rates on personal toilet cameras.
- Deviation in consistency/texture/color/etc.
- Obvious signs related to the above (eg: diarrhea, dehydration, blood in stool).
Ultimately though, you can get the same results by just looking down yourself and being curious if things look off...
tldr: this feels like literal internet-of-shit IoT stuff.
That’s not end-to-end encryption. By that logic HN, and any other website over HTTPS is E2E encrypted.
This sounds like the marketing department came up with this "market opportunity" and then some poor team at Kohler was asked to make it real.
No doubt there is health data to be had in waste products (it was used extensively during covid to figure out community-wide infection rates) but that used physical samples that were then analyzed. Trying to figure out if someone has a UTI, or pathogenic poop from a webcam image ... it is hopeless.
And people who are being treated for gut issues can pay for their $600 medical toilet with HSA or insurance
Honestly, that this camera toilet exists is not a WTF for me. If my doctor needs to track changes to my stool, I certainly don’t want to have to hover over the bowl with my phone out. Please, just have the toilet take the picture.
And yes, if my doctor wanted me to collect that info, I’d vastly rather buy a smart toilet and let it do the dirty work. That is, assuming it was actually secure.
An ADA toilet at Home Depot is $300 so even the price isn’t that outrageous, honestly. It’s a unique niche product so it’s gonna be a little bit pricey.
I don’t know, it just feels a bit gauche to make jokes about a medical device. Nobody’s buying this unless they need it, and if they need it then best of luck to them.
If you continue to have GI issues anyways, perhaps due to genetic causes, then what is constant surveillance of the situation -- at $7,200/year -- going to improve?
You wouldn't want that cheap tat miring up the clean lines of your throne.
For normal people E2EE means privacy, and that's why some company tries to sneak the term in products where it makes no sense.
It's misunderstood.
In the begining it's used to describe chat apps, your chat message are delivered in a secure way.
But later some marketers try to use it as a "transport channel" for client-server interactions.
Not in my experience, except by very few
> But later some marketers try to use it as a "transport channel" for client-server interactions.
Some, still few enough to not make the term confusing, for what I can tell
Smart Pipe | Infomercials | Adult Swim
Everything in our lives is connected to the internet, so why not our toilets? Take a tour of Smart Pipe, the hot new tech startup that turns your waste into valuable information and fun social connectivity.
[Smart Pipe Inc. is a registered sex offender.]
>https://www.nytimes.com/2025/12/02/world/asia/south-korea-ca...
Oh...
I remember a sign in our dorm bathroom that read, “toilet cam is for research purposes only”. It was a joke, but always got a nice reaction from new people in the building.
But they actually sell this?! And want to charge me for it!?
Holy crap!
E2EE now means something wildly different in the context of messaging applications and the like (since like 2014) so this is more of an outdated way of saying "no one is getting your poop pictures between your toilet and us".
It also feels like it would never make sense for this to be "E2EE encrypted" in the modern sense of the term as the "end user recipient" of the message is the service provider (Kohler) itself. "Encrypted in Transit" and "Encrypted at Rest" is about as good as you're going to get here IMO as the service provider is going to have to have access to the keys, so E2EE in a product like this is kind of impossible if you're not doing the processing on the device.
I wonder if they encrypt it and then send it over TLS or if they're just relying on TLS as the client->server encryption. Restated, I wonder how deep in their stack the encrypted blob goes before it's decrypted.
No, before that it was simply not a term, except in some obscure radio protocol (and even there someone competent in cryptography would probably not have chosen that term)
> E2EE now means something wildly different in the context of messaging applications and the like (since like 2014) so this is more of an outdated way of saying "no one is getting your poop pictures between your toilet and us".
The outdated way was saying "Military-grade 128-bit encryption", no one really used the E2EE term before it got the current meaning
> I wonder if they encrypt it and then send it over TLS or if they're just relying on TLS as the client->server encryption. Restated, I wonder how deep in their stack the encrypted blob goes before it's decrypted.
Some homemade encryption added on top of TLS is very unlikely to increase the security of the system
> no one really used the E2EE term before it got the current meaning
It most certainly was a term and no it wasn't simply limited to "some obscure radio protocol".
1994: https://ieeexplore.ieee.org/abstract/document/363791
1984: https://dl.acm.org/doi/pdf/10.1145/357401.357402
1978: https://apps.dtic.mil/sti/tr/pdf/ADA059221.pdf
> Some homemade encryption added on top of TLS is very unlikely to increase the security of the system
"Some homemade encryption" is not what I was suggesting at all. E.g. encrypted-at-the-source (client side) AWS files are still sent over TLS as an encrypted blob within an encrypted blob but remain encrypted past the TLS boundary.
Oh wait, maybe this is what Cory Doctorow is referring to as enshittified?
I mean, these jokes make themselves, including whoever buys the hardware, AND buys the marketing pitch.
BTW, someone please tell me that there is/was a social media site dedicated to poop, and the founder got rich from it. I need that today.
cough bullshit.