Respecting the privacy of every member
Members trust their community with their contact details, and the community trusts us to look after them. We collect only what is needed to deliver a notice, we keep it for the community that collected it, and we never use it for anything else.
We do not monetize client data. Not now, and not as a future revenue line.
We do not sell, rent, licence or broker customer or member data to any third party.
We do not sell advertising, and we do not place third-party advertising or tracking technology inside community apps.
We do not build advertising or resale profiles of members, and we do not use member content to train third-party models.
The community remains the owner of its content and its member list. We are the processor, acting on documented instruction.
Why the subscription fee matters
A platform has to be paid for by someone. When the resident is not the customer, the resident's attention and data usually become the product. Communikit charges the organisation directly, so the incentive stays where it belongs.
One customer, one revenue line
The organisation pays a predictable monthly fee. There is no second business behind it that depends on member behaviour.
No engagement harvesting
Analytics exist so administrators can see whether a notice reached people. They are not sold onward, and they are not used to target members.
Written into the agreement
The commitment is a contractual term, not a marketing statement. It survives renewal and applies to every subprocessor we engage.
What the app holds, and what it does not
Communikit collects the minimum required to deliver a notice to the right people and to confirm it arrived. Everything below describes the mechanics of the app itself.
Controls that sit with the member
A member should be able to answer three questions inside the app: what am I receiving, who can see me, and how do I stop. Each of these is a setting, not a support request.
Resilience and continuity
Emergency communication is only useful if it works on the worst day of the year. Communikit has completed a comprehensive redundancy review covering the platform's infrastructure, data backup, and message delivery paths, and the resulting strategy is now in operation. Detailed architecture and recovery objectives are documented for customers under a confidentiality agreement.
Backed up and restorable
Customer data is backed up on a defined schedule, and restoration is tested rather than assumed.
Independent alert channels
SMS, voice call and push notification run through separate delivery paths, so one channel failing does not silence an alert.
Documented continuity plan
Recovery roles, escalation order and communication steps are written down and reviewed, not improvised during an incident.
Hosting and third parties
Communikit runs on established cloud infrastructure and uses a small number of specialist providers for message delivery. Every subprocessor is bound by the same non-monetization and confidentiality terms we hold ourselves to.
If something goes wrong
We maintain a documented incident response procedure covering detection, containment, assessment and notification. Customers are told what happened, what was affected, and what changed as a result.
The following can be requested
For procurement and IT reviewers, the following are held as current documents and released to customers and active prospects under a confidentiality agreement: the security overview, the data processing agreement, the subprocessor list, the business continuity and redundancy summary, and the incident response procedure.
Your Communikit account contact can arrange access to any of the above.
Request documentation