Who benefits from RECIN?
RECIN is built to be industry-neutral, but not arbitrary. It helps most where knowledge has to be brought together across many parties, and where you must be able to show at any time who may see what and what a statement rests on. Three kinds of organisation stand for that.
Associations and chambers
An association brings together knowledge about members who compete with each other in the market. Committees, positions, statements and regulations belong together – but the connection lives in people's heads, in mailboxes and in meeting minutes. And not everything the head office knows may be seen by every committee, let alone by every member.
That gradation belongs in the structure, not in the discipline of individuals. In RECIN every piece of information carries its confidentiality as a property – not as a folder name someone has to get right. Prices, volumes and market shares of individual members stay where they belong: outside the shared network.
Knowledge organisations
Institutes, learned societies, foundations, research bodies: organisations whose actual output is knowledge. Their holdings grow over decades while their staffing is often temporary – project posts, doctoral researchers, voluntary committees. What is lost on departure is rarely the document. It is the context: why something was decided, what it rested on, who objected.
RECIN holds exactly those connections, not just the files. When someone leaves the organisation, the network remains – and their successor sees immediately what belongs to a topic and what it is based on.
Consulting firms
Consulting sells knowledge that arises in a project – and usually disappears there again. Two requirements collide: you want to learn across engagements, but you must keep client data strictly separate. Attempt both in the same filing system and you end up solving neither.
RECIN keeps them apart cleanly: for engagements that must not see each other, a separate workspace can be set up per engagement. What the firm itself carries – methods, expertise, contacts, project histories – keeps growing untouched in its own network.
Here, data protection is the architecture, not an accessory
All three groups share one problem: they work with knowledge that does not belong to everyone. Laying data protection over a data platform afterwards rarely works. In RECIN it is part of the data architecture – and therefore still effective on the days when nobody is thinking about it.
Separate tenants, not separate folders
Every customer works in a strictly separated tenant. The separation is not a setting someone can forget, but the way the data sits. This foundation is already in productive use.
Retention periods run by themselves
Personal data is automatically marked for deletion once the statutory period expires, and the person the information belongs to is notified. The periods are centrally configurable per information type, for instance where a legitimate interest carries further. That addresses storage limitation exactly where it is otherwise left undone: in everyday work.
Your data does not leave the EU
The language model is Mistral, a European provider; hosting is in the EU. There is no detour via a US service – and therefore no third-country transfer you would have to justify to a regulator, your members or your clients.
Every answer shows its source
The AI chat answers exclusively from your own data and names the evidence for every statement. What cannot be evidenced is not asserted. For accountability and logging duties, that is the difference between an answer and a guess.
Checked, not guessed
The AI proposes entities and relationships but decides nothing. Every proposal is confirmed, changed or rejected by someone who knows the subject. The result is a verified body of knowledge rather than automation whose errors only surface in the finished answer.
A dedicated workspace where separation is not enough
Where protection requirements are higher, RECIN runs in its own dedicated workspace instead of shared operation – same functions, separate environment.
Coming next
Visibility already takes effect in the database itself: every piece of information carries its visibility level, permissions are connections in the network and inherit along defined paths – confidential items stop the inheritance. Not yet finished is the review of every side path: hints, suggestions and document lists are being attached to the same rule step by step.