https://novita.ai/blog/minimax-requests-privacy-notice/
> A routing configuration issue caused an API forwarding path intended for specific customers to apply more broadly.
> If you used MiniMax models through Novita between 2026-05-28 and 2026-11-11, your request contents may have been accessed or retained by a third party. This includes requests made directly through Novita and those routed to Novita through OpenRouter.
“routing configuration issue”?!? Imagine if AWS got caught storing your S3 on some other provider’s disks and they said it was a “routing configuration error”! They shouldn’t have software that can do this at all! The API is supposed to be for their own GPUs!
Together’s is weird:
> As part of routine software testing, we collected prompt samples authorized for that use and stored them in a private Hugging Face repository. The samples came from requests to the MiniMax M3, GLM-5.2, and Kimi K2.6 models, primarily on June 24, July 4, July 8, and July 14, 2026.
Did Dragos really “authorize” Together to store their canary “prompt samples”? Somebody screwed up here.
> During development of our public GitHub repository, xorl, an AI coding agent committed a credential that provided access to the private Hugging Face repository. Our automated scanning detected the exposed credential, and we reverted the commit.
They didn't rotate the credential they knew was exposed!?! I guess "an AI coding agent" didn't think of doing that. Also FYI kids, reverting a commit does not delete the data from the repository.
In before they claim an AI agent wrote this disclosure that included certain "errors".
https://www.together.ai/blog/security-event-prompt-leakage-f...
Amusingly, the first time I typed “neocloud” it got autocorrected to “bro cloud”. I almost decided to leave it alone.
Yet, the basic idea of these myriads of canaries is good. I see several use cases, including in research.
The only thing you can trust is possibly(and not always) your own hardware, your own staff and companies you can directly inspect.