Quite possibly, I didn’t ask and couldn’t really see since it was still set up for Covid protection. It could have been a service like the one you mentioned, I have seen that some businesses use those and some that just have a cell phone or cellular tablet that they use. I have had similar instances with standard cell carriers though too
Correct, the “default” RCS protocol is client to server encryption. Problem is that’s hardly any more secure than SMS. The carrier/service whose RCS protocol you are using has the keys since it is client to server. Basically no different than it is now the only different is your neighbor can’t just intercept your texts. So just how it is now a simple request of phone records will still give info just as SMS.
Ultimately you are correct with it being more secure than SMS, but by a thin margin because I don’t see any news articles of someone intercepting SMS. Listen I do not have a problem with RCS at all, but if you can’t even match the security at least of the competition then it isn’t even a fight. Google just rolled out E2EE and waiting on group now and this is only using their protocol most messaging platforms has this now.
Google is basically doing the same thing as Apple, Google is pitching just RCS correct? But the features and abilities it pitches but leaves out is using only their protocol. So if iMessage can only be used between Apple devices, and similar abilities can only be used via Google’s protocol how are things any different?
Edit: I’m on mobile and don’t feel like editing out that top section I forgot to unquote. I also wanted to add to truly have a secure RCS standard protocol you would need client to server encryption and server encryption on top of it to secure that same data, problem is with server side encryption a hack can still get those keys and then we are back to where we were with client to server