Skip to content
Back to site Sign in

Privacy

How we handle church records.

DigiKirk keeps membership and ministry records for local PCEA congregations. This page says plainly what is stored, who can see it, and what you can ask us to do about it. It is written to the Kenyan Data Protection Act 2019.

Last updated 15 August 2026

Who is responsible for your records

Your local church is the data controller. It decides what is recorded about its members and who in the church may see it. DigiKirk is the church's data processor: we hold and protect the records and act on the church's instructions, and we do not decide what goes in them.

DigiKirk is the controller only for staff sign-in accounts and for this website. If your enquiry is about your own membership record, your church is the right place to start, and we will help them answer it.

What is recorded

Member records, entered by your church: name and title, phone numbers, email, gender, date of birth, residence and postal address, occupation, family relationships, district, membership and communicant status, baptism and confirmation dates, the dates somebody joined or left and why, and pastoral notes.

Staff accounts: name, email, phone, the roles held and the churches they cover, and a record of sign-ins and record changes for accountability.

This website: two cookies and nothing else. One keeps you signed in, the other stops another site submitting forms in your name. There is no analytics, no advertising and no third-party tracking.

Why we hold it

To run the church: keeping an accurate roll, organising districts, groups and ministries, preparing services and communion, and sending church notices. Records of who changed what are kept so that access to sensitive information stays accountable.

Messages

Church SMS is sent through Africa's Talking, a Kenyan messaging provider, which receives the recipient's phone number and the message in order to deliver it. We send only to members whose consent is recorded, and a member who asks to stop receiving messages stops immediately — consent is held against each member and can be withdrawn at any time by telling the church.

Who else sees it

Only the people in your church whose role requires it, and only for the church they serve. One congregation cannot see another's records. Beyond that, records are held by our hosting and database providers and in encrypted backups, all under contract and only to keep the service running.

We do not sell personal data, share it for advertising, or use it to profile anyone.

How long it is kept

Membership records are part of a church's history and are kept for as long as the church keeps them: a member who transfers away or dies stays on the roll, marked as such, rather than being erased. Accountability records of changes are kept unaltered. If you ask for deletion we will act on it with your church, except where the church must keep a record to meet its own obligations.

Your rights

Under the Data Protection Act 2019 you may ask to see the personal data held about you, to correct it, to have it deleted, to object to or restrict how it is used, and to receive a copy. You may also complain to the Office of the Data Protection Commissioner.

Ask your church first, since the record belongs to them. If that does not resolve it, write to us at hello@digikirk.co.ke and we will respond within the period the Act allows.

Changes

If what we do with records changes, this page changes with it and the date above is updated. If a change materially affects members, your church will be told rather than left to notice.

Questions about this policy: hello@digikirk.co.ke

DigiKirk, Mutaratara Mtandaoni DigiKirk, Mutaratara Mtandaoni

Mutaratara Mtandaoni

Home Privacy Sign in

© 2026 DigiKirk

Cookies on this site

DigiKirk stores two cookies, both needed for it to work: one keeps you signed in, the other stops another site submitting forms in your name. There is no advertising, no analytics and no third-party tracking, so there is nothing here to turn off. Your light or dark theme choice is saved by your browser, not in a cookie. Read the privacy policy.