Connect
Integrations inbox
Let the tools your organisation authorises send you what they find, and let a person on your team decide what enters your records.
What it is for
The tools your organisation authorises — for example, those of whoever manages your cybersecurity — send Alethexis three types of entry: incident notices, AI tools they have found in use and documentary evidence.
Alethexis does not detect incidents or AI tools in your systems on its own: it receives and organises what those tools send. Everything arrives pending review, and a person in your organisation decides whether to confirm or discard it. Nothing enters your records by itself.
The Owner creates and revokes the inbound sources. The inbox is available in M2 and M3.
How it works
Three types of entry
An incident, which once confirmed becomes an event in the incident register (GOB-6); a detected AI tool, which becomes an AI use request or is linked to a system in your inventory; and evidence, which is added to your evidence.
Pending until someone decides
Each entry arrives pending review. It is reviewed by whoever can record in its destination, who decides: confirm or discard. While it is pending, it does not appear in your records, does not move the progress of any section and is not sent out through the API or the webhooks. Once confirmed, it is incorporated by the same path as if you had recorded it by hand.
A person sets the severity
When confirming an incident, the reviewer chooses its severity (N1, N2 or N3). It is mandatory and has no default value: a person in your organisation decides it, never the tool that sends the notice.
One credential per source
Each inbound source has its own credential, which is shown only once and can be revoked at any time. It only allows sending the types of entry you authorised for that source and gives no read access to anything in your organisation.
Personal data breaches
If a serious incident (N3) involves a personal data breach, GOB-6 records the date on which your organisation became aware of it and calculates from that date the reference deadline under Article 33 GDPR. Receiving a notice does not set that date by itself: your organisation determines it.
FAQ
- Does Alethexis detect incidents or AI tools on its own?
- No. It receives and organises what the tools your organisation authorises send. It does not analyse your systems or classify the entries: each one is reviewed and decided by a person in your organisation.
- Is the tool that sends the entries a sub-processor of Alethexis?
- No. Alethexis does not engage it or entrust it with any part of its service: it is a third party that your organisation designates and authorises. Its status vis-à-vis your organisation depends on the relationship between you. This is set out in the Data Processing Agreement.
- What data should each tool send?
- Only what is needed for the purpose of the integration, with no data about persons. The channel only accepts the expected technical fields and rejects the rest, but free text or a document may contain personal data, and that depends on what each tool sends. Configuring it is up to your organisation.
- Does Alethexis notify breaches to the supervisory authority?
- No. Alethexis does not notify the competent supervisory authority, does not decide whether an incident is a personal data breach and does not ensure that the deadline is met. It records the date of awareness that your organisation determines and calculates the reference deadline from it; investigating the facts and making the communications the law requires is up to your organisation.
- What happens to an entry that is discarded?
- Its content is erased when it is discarded. Only a minimal trace remains — the type, a pseudonymised external reference, the dates of receipt and discarding, who discarded it and why, and a technical identifier — which is erased within the period set by the Data Processing Agreement. If a notice corresponds to a personal data breach, do not discard it: confirm it, so that it is documented in the incident register (GOB-6).