Process only what is needed
CommsPliant processes the customer data required to produce the communication requested by the client.
A clear view of how data moves through CommsPliant.
CommsPliant separates template governance from customer-data processing so clients can see where data enters, what happens to it, what is returned, and what governance evidence is retained.
Data Flow Overview
Template Governance
Implemented
-
Create / Edit Template
-
Review
-
Approval
-
Approved Version
Template governance controls who can create, review and approve communication content before it is used for generation.
Customer Data Flow
Implemented
-
Client System / Upload
-
Customer Data
-
CommsPliant Generation using the approved template
-
Completed Communication
Then either:
-
Returned to Client System
-
Optional Delivery by CommsPliant
Customer personal data is processed for the communication task and is not retained by default.
If a client requires completed communications or related customer data to be stored by CommsPliant, this is enabled only through a separate agreed retention arrangement.
Governance & Evidence
Implemented
-
Version
-
Approval
-
Generation Event
-
Governance & Evidence Record
-
CommsPliant Vault
Governance and evidence records remain connected to the communication workflow so organisations can later show which version was approved and how the communication process was controlled.
Full customer documents are retained only where separately agreed.
Data Handling Principles
No default PII retention
Personally identifiable information used for communication generation is not retained by default after the processing task is complete.
Restricted access
Access to customer data is restricted to authorised personnel and only where necessary for controlled operational or support purposes.
Client-controlled retention
Longer-term storage of completed communications or related customer data is used only where separately agreed with the client.
Data Flow FAQ
No. Templates are reviewed and approved before customer data is used for generation. Customer personal data enters the process only when CommsPliant generates the communication using the approved template.
CommsPliant processes only the customer data needed to produce the requested communication. The completed communication is then returned to the client system or, where selected, delivered by CommsPliant.
Not by default. Personally identifiable information used for generation is not retained after the processing task is complete. Longer-term storage is used only where separately agreed with the client.
CommsPliant keeps governance and evidence records connected to the communication workflow so organisations can show which version was approved and how the communication process was controlled. Full customer documents are retained only where separately agreed.
Not by default. CommsPliant processes customer personal data only for the communication-generation task and does not retain it after that task is complete. If a client requires longer-term storage of completed communications or related customer data, this can be enabled under a separate agreed retention arrangement with appropriate contractual terms.
Still have questions?
If you need more detail about data flow, retention or governance evidence, contact us and we'll help.
Request more informationSupporting Records
| Resource | Availability | Action |
|---|---|---|
| Data Map |
On request
|
Request access |
| Processor ROPA |
Controlled · On request
|
Request access |
| Data Processing Agreement |
Client onboarding
|
Request access |
| Retention and Deletion Schedule |
Controlled · On request
|
Request access |
| Governance Audit Trail Evidence |
Controlled · On request
|
Request access |
| Client Offboarding, Export and Deletion Procedure |
Controlled · On request
|
Request access |
A request does not automatically mean the full internal document will be shared. Where more appropriate, CommsPliant may provide a client-facing version, extract, summary or controlled evidence instead.
Request data-flow information