Integrations inbox
Alethexis feature that receives the information sent by the tools or third parties an organisation authorises and leaves it pending review. It accepts three types of entry: incident notices, AI tools detected in use and documentary evidence. The Alethexis Terms of Service and Data Processing Agreement (DPA) call it the “automated intake channel”, and those who send through it, “senders”. In the product, the same feature is the “Integrations inbox”, and each authorised sender, with its own credential, is an “inbound source”.
It is the door through which other tools provide information to an organisation, and nothing that comes in through it counts until a person reviews it.
Which obligations it carries
It is a product feature, not a legal figure: no rule requires having it or using it. It touches a legal obligation when a notice corresponds to a personal data breach: the controller must notify it to the supervisory authority without undue delay and, where feasible, not later than 72 hours after having become aware of it, unless the breach is unlikely to result in a risk to the rights and freedoms of natural persons (Article 33(1) of Regulation (EU) 2016/679), an obligation applicable from 25 May 2018. Receiving the notice does not by itself fix that moment: the organisation determines it, and the inbox neither notifies the supervisory authority nor decides whether there was a breach.
What it is not
It is not a detection system: it does not look for incidents or AI tools on its own and does not classify what it receives. Nor does it incorporate anything into the organisation's records by itself: each entry remains pending until an authorised person confirms or discards it, and the severity of an incident is always set by a person. And an inbound source's credential gives no read access: it only allows the authorised types of entry to be sent, and the organisation can revoke it.
The nuance almost nobody captures
A sender does not thereby become a sub-processor of Alethexis: it is a third party that the organisation designates and authorises, and its status vis-à-vis the organisation — processor, independent controller or otherwise — depends on the relationship between them. That is why it is for the organisation to authorise each sender, to limit the types of entry it may send and to revoke its credential when it is no longer needed.