Security
Plenior runs on your computer, with your own accounts. If you find a way to break that trust, tell us privately and we will fix it with you.
Last updated
Report a vulnerability
Email security@plenior.dev. Please do not open a public issue, pull request or discussion for a suspected vulnerability. You can write in English or Portuguese, and include as much of this as you can:
- A description of the issue and its impact.
- Steps to reproduce it, or a proof of concept.
- The affected version or page, and your operating system or browser.
What to expect
- An acknowledgment within three business days.
- Regular updates while the issue is investigated and fixed.
- Coordinated disclosure: the fix ships before the details are public, on a timeline agreed with you.
- Credit in the release notes, if you would like it.
Scope
This covers the Plenior app, its source code and plenior.dev. An issue in an agent that Plenior drives, such as Claude Code, belongs to that agent's vendor. If you are not sure, write to us anyway and we will route it.
How Plenior protects your work
- Your sign-ins stay with the agents you already use. Plenior never sees or stores your credentials.
- The agent asks before it edits files or runs commands, unless you pick a mode that allows it.
- The app's interface runs in a sandbox and reaches the rest of the app only through a small, typed channel.
- Plenior sends no telemetry, so there is no data about you on our side to leak.