Continued from E1, the memory · the conditions it is held under
Safe to keep.
A memory like this is only worth having if it is safe to hold. Three commitments, each built into how the system works.
GDPR-native, configurable
Retention periods and consent cadence set at organisation level. A named data protection contact on every record. What an individual has shared, they can revoke at any time; your own notes stay yours alone.
The candour compact
Your team’s honest notes are never a performance dashboard. Convenor cannot rank people by their activity; that is built into the system, not promised in a policy. When people are careful in front of the record, the record stops telling the truth.
Sovereign deployment
European cloud, on-premise, or air-gapped for institutions that require it. Made in Europe, by deliberate choice.
What your team writes
“Prefers panels to keynotes. Her board is lukewarm on the code; do not push before June.”
What a performance dashboard would make of it
When people are careful in front of the record, the record stops telling the truth. So the ranking is impossible, in the system itself.
The register · What your data protection officer will ask
- Hosting & jurisdiction
- European cloud, on-premise, or air-gapped; chosen per deployment.
- Lawful basis
- Consent records and legitimate-interest records both live on the map, each carrying its basis, with objection handling.
- Retention
- Set at organisation level and enforced by the system, not by remembering.
- Revocation
- Information shared by the individual can be revoked by them at any time. Your organisation's own notes remain your organisation's, never visible to the individual.
- Export & erasure
- Complete export and erasure paths in every deployment; the detail travels with the proposal.
- Subprocessors
- Disclosed per deployment, before signature.
Bring the rest of the checklist · we answer before signature →