Not sure digging up your Slack, Google, Apple API keys is faster...and probably also more of a hassle for compliance than just using Slack and Email which are already there.
Although the future of Statused holds more than just forwarding emails to Slack. I intend to add support to other "channels", such as Teams, Discord and Telegram, as well as other types of integrations such as incoming webhooks, so a status update could directly trigger a custom action in your CI/CD pipeline, for example "detect the app has finished processing, then submit it for review".
On top of that, I don't think you get those emails for every Google Play changes that are made to your release, so not sure if that would work. Again, this might work, but I'm really not sure.
You have a point with those concerns about sharing API keys. But this has become pretty standard and devs share those keys with a bunch of services already, such as as with CI systems, app store user review services, sometimes ASO monitoring tools even.
The FAQ page highlights which permissions the API keys need: https://statused.com/faq#which-permissions-does-my-google-pl...
Thanks for raising these points! It's valuable feedback to understand how people perceive this product!
Ah, ok. That's the part I missed.
I would still be a bit worried about the security of it all if this were a big company though, but it's maybe doable for smaller ones?