Thank you for contributing to the discussion. I appreciate your perspective, and I am inclined to agree with you.

The social media component lends itself to screenshots. At the very least, disabling screen access to the most sensitive areas (nsec, payment-related features, DMs, etc.) by default would be a viable solution.

This could be paired with a toggle or slider in settings, where users could set one of three options:

- least private (allows access to all screens)

- default privacy (denies access to screens with sensitive data)

- maximum privacy (denies access to all screens)

...allowing users to screenshot freely while maintaining privacy for sensitive data, keeping everyone happy.

Either way, it’s clear that we need something. The average end user is not going to dig into Google/Apple settings an harden AI access to apps individually.

This is why I opened the discussion.

The current default of allowing unrestricted AI access to all app screens has become an unnecessary liability—and one that could be easily rectified in the same way Amethyst increased user privacy and security by baking-in Tor, giving users control over the auto-loading of media etc.

That said, I've said my peace. I hope Vitor considers this feedback and decides to incorporate it in a future Amethyst release.