Σύνεσις
Synesis. Permission, on the record
Consent as a versioned record with a lawful basis attached.
A person replies, not an autoresponder.
Consent as a record, not a claim
Notices, issued receipts, withdrawal, and a customer-facing Privacy Centre with DSR self-service, scoped per entity or across the group, so one consent event can lawfully cover the subsidiaries the customer actually deals with.
The situation today
Consent was collected as a checkbox in a form, in a system that no longer exists, under a notice nobody kept a copy of. Mapping which permission covers which processing becomes an argument, and subject rights requests are worked by hand under a statutory clock.
What Synesis does about it
Synesis holds consent as a versioned record with a lawful basis and the notice version attached, issues receipts, treats withdrawal as a first-class event, and gives the customer a Privacy Centre where rights requests are raised and answered rather than emailed.
Runs alone as
A consent-management and DSR platform sized for a banking group: remediation of legacy consent, receipts, withdrawal and self-service rights handling under UK GDPR.
Permission, on the record, in four parts.
Versioned, with a lawful basis
Each consent record names its purpose, its basis and the notice version the customer actually saw. Which consent covers which processing stops being an argument.
Receipts and withdrawal
The customer holds proof of what they agreed to, and withdrawal is a first-class event that propagates rather than a support ticket.
Privacy Centre with DSR self-service
Access, rectification and erasure requests are raised, tracked and answered in a customer-facing surface instead of by hand.
Entity or group scope
Consent can be scoped to one subsidiary or across the group, which is the mechanism that makes intra-group reuse lawful later.
Reference set shown: UK. EU and EEA equivalents on request.
What changes once it is running.
The mapping question, answered
Each record names its purpose, its basis and the notice the customer actually saw.
Withdrawal that propagates
Taking consent back is an event the platform acts on, not a ticket somebody has to chase.
Rights handled by the customer
Access, rectification and erasure are raised and tracked in a surface built for it.
Group scope, lawfully
One consent event can cover the subsidiaries the customer actually deals with, the mechanism reuse depends on later.
Phase one, one number
Consent coverage · DSR handling time
Including remediation of the legacy consent nobody can currently map to a processing purpose.
Written to the evidence rail
worked example
- CONSENT_GRANTEDscope group, lawful basis attached, receipt issued
Stronger with Kanon. Kanon enforces at delivery time what Synesis captured at consent time.
Four weeks. One number for Synesis.
We map Synesis against two entities in your group and quantify phase one, consent coverage and DSR handling time, with no integration required to produce the number.
A person replies, not an autoresponder.
Proven in production at a systemic European bank: transmission to regulated subsidiaries with full consent management and audit trail.
- Enquiries
- info@trustnexus.eu
- Partnerships
- Become a provider