It's always been a possibility that when you sent an email to someone their provider could be building an ad profile on you. Any third party tool someone else uses to manage their personal files and communications could always have some arbitrary privacy policy that let them do what they see fit.
For the most part, you never know what random SAAS someone on the other end of a relationship is really using.
Yes, and that's exactly why E2EE messaging became a thing. Signal put it on the map through the WhatsApp integration.
To me there is a difference if the server spies on me (that's without E2EE) or if the person I am writing to leaks everything on the Internet.
If the person you're writing to leaks everything on the Internet, you should consider you are talking to them in public. I'm sure you don't say all the same things when you are in the metro or when you are in private, or do you?
Pretty much never for email. Maybe some people go out of their way to perform PGP but that's usually only for the most sensitive of information and sometimes not even for that.
The only thing I've used PGP for in many years is encrypting my home address when buying darknet drugs
Imagine someone puts all the Signal messages someone else sent them through an AI. I dunno. I think problem is most AI doesn't work like Confer.to, also by Signal's founder.
The entire concept of conversations being "secure" is only as good as your ability to trust the other party isn't doing something insecure with them (and that yours and their devices are, themselves, as secure as you think they are. Which they generally aren't.)
All of which is to say, it's security theater and always has been when applied to real life situations.
but it's an MCP, so that also means it'll be more token-verbose than an API, which means your local agent hardware is going to chug a bit.
i have reached the point of just using LLMs to build my own API servers and tooling like search, and teach the LLM how to use those APIs, rather than MCPs.
* Unless you want to go into a conspiracy theory that all the Meta employees can see the source code and nobody has ever felt like whistleblowing about the backdoor Meta put into WhatsApp, that is.
Its still preferable to use Signal since now it actually supports numberless registration. Hopefully they will actually fee payable not via credit card at some point.
Feeding someone else's personal data in to an AI company is unethical even if there is no way as an individual to prevent someone doing that.
When that happens it immediately cuts your access and makes you request a reconsideration that can take 24+ hours. Some accounts get booted without this option. So if you use Whatsapp for anything important that can be a really big problem. I was reinstated, and only discovered this from going through a couple of cycles trying to add these back.
So doing what you are doing with this seems almost like a guarantee that you will be perma banned.
If a bot needs to text me it sends an API request or it can read whatever I allow with full visibility as I have the logs and limit the access.
The amount of effort was minimal. About 4 prompts to get it all working and zero SaaS, 3rd party, or purchases after the software was built.
Do you know if running Whatsapp in Cloud risks your account to be banned?
I'm working on a similar tool, connecting all that data to build your context graph that knows all the people and conversations and expose it via MCP. https://lobu.ai/for/personal/
My approach is requiring you to have a home device where you keep your accounts open in a browser and observing the data from there. The same applies to Linkedin, Instagram, X etc. even reading my timeline to summarize what I need to know without me doomscrolling.
> […] default CPU limit on Workers is too small for it. wrangler.jsonc raises it, and raising it needs the paid plan, which is a few dollars a month. I haven't tried the free plan.
https://github.com/finereli/whatsapp-mcp/tree/64f1b3017931e4...