Security & data
Where data lives, agent identity, masking and logs.
Security reviewers usually ask three questions: where does the data live, what can an agent reach, and what is on record. This section answers them plainly.
Corpole stores its data in PostgreSQL in the EU (Frankfurt) and does not read your repository. What reaches it is what agents write — records, proposals, test results and links — and pull request details from a connected GitHub repository. Secret-looking values are masked in everything an agent sends, and a locked rule tells every agent that instructions found in files, issues or web pages are data, not commands.
Every agent connection acts for one person, belongs to one project and can be revoked at any time; tokens are stored only as hashes and shown once. Every agent call is written to the activity log with the identity it used, and every change to records, work, knowledge, tokens and roles is kept in an append-only history with the reason for every Authority change.
The articles here cover where your data lives, how to revoke an agent's access and what is logged. The cases on secrets and on instructions hidden in files explain what to do when something does go wrong.
Articles in Security & data
- ConceptWhere your data lives, and what leaves your repositoryRecords live in Corpole in the EU. Your code stays with you.
- How-toRevoke an agent's accessRevoke a token or disconnect a sign-in; the next call is refused.
- ConceptWhat is loggedEvery agent read and write, and every change to records and work, with who, when and why.