This notice explains how Kirklees Council collects and uses your personal information when you use Our Council App. It is written for council staff using the app and applies to both staff.kirklees.link and any service-specific page (for example service.kirklees.link/van-scan).
It is intended to satisfy our transparency obligations under Article 13 of the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018.
1. Who is responsible for your information
The data controller is Kirklees Council, Civic Centre 3, Market Street, Huddersfield, HD1 2EY.
Day-to-day responsibility for the app sits with:
- Senior Communications Officer: Max Youell — max.youell@kirklees.gov.uk
- Communications Lead for Digital, Insight & Improvement: Susie Richmond
- Head of Communications: Marcus Bowell
The council's Data Protection Officer can be contacted at dataprotection@kirklees.gov.uk for any data-protection question.
2. What information we collect
Information you give us when you start using the app
| Field | Required? | What it's for |
|---|---|---|
| Your name | Yes | So administrators can see who is using the app, and so colleagues can see who has posted shoutouts or feedback if you choose not to be anonymous. |
| Mobile number or email address (one of the two) | Yes | So we know how to contact you about the app, verify you are a member of council staff, and reach you if there is a problem with your account. |
| Your service or team | Yes | So you only see news and notifications relevant to your work. |
If you don't have a council-issued mobile number, an email address is enough.
When you come back to the app on the same device, we recognise that device and bring back the name, contact details and service you gave us before, so you don't have to enter them again. You can change them at any time from the app's settings.
Information collected automatically
| What | Type | What it's for |
|---|---|---|
| Anonymous device identifier | Random string stored in a first-party cookie scoped to kirklees.link | So we can recognise the same device on later visits, deduplicate views and acknowledgements, and avoid sending the same push notification twice. It is not linked to your real identity by itself. |
| Push notification subscription | An endpoint URL and two cryptographic keys generated by your browser | To deliver push notifications to your device. Created only if you choose to enable notifications, and deleted automatically after 30 days of inactivity. |
| Engagement events | Article views, reactions ("Helpful" / "Not helpful"), acknowledgements of must-read posts, poll votes | To measure reach, confirm important messages have landed, and improve content. Linked to your device identifier and (where you posted while signed in) your name. |
| Service-page visits | A record that your device visited a particular service space (for example, van-scan), and the time of last visit | To show the live "active members" count on each service page and trigger the right team-scoped news. |
| Audit log entries (admin actions only) | Time, admin username, action description | So we can investigate any security incident or content dispute. |
Content you submit
- Feedback ("Our Conversation"): the message you write, your name and team if you provided them, or "anonymous" if you ticked the anonymous box.
- Shoutouts: the giver's name, the recipient's name, the team, and the council value tagged.
- Poll votes: the option you chose, linked to your device identifier so the same device can't vote twice. Names are not linked to poll votes.
- News reactions and acknowledgements: linked to your device identifier and to your name if you provided one.
Information about administrators
If you have a content-management role (Communications team or service admin), we additionally store: your username (chosen by you), a securely hashed password, your access level, the team you administer (if applicable), the date your account was created, and the date you last logged in.
What we do not collect: council email addresses (unless you give one in place of a mobile number), employee numbers, location data, special category data (such as health information), payment information, or browsing history outside this app.
3. Why we collect it and our legal basis
Most of the processing in the app is carried out for the performance of a public task — the council communicating with its workforce — under Article 6(1)(e) of the UK GDPR. Specifically:
- Operating an internal staff communications channel
- Reaching frontline staff who are not regularly at a desk or council email
- Confirming that important messages (must-reads) have been seen
- Understanding how the app is used so we can improve it
- Investigating security incidents or content disputes
Push notifications are sent only with your consent (Article 6(1)(a) UK GDPR), captured by the operating system permission prompt the first time you enable them. You can withdraw consent at any time in your device or app settings.
4. Who has access to your information
Inside the council, your information is accessible to:
- The Communications team (org-wide admins) — for everything in the app.
- Service admins (e.g. heads of service who help curate their service page) — only for information relating to staff in their service.
- The council's IT and Information Governance teams, where required for support, audit, or security.
Outside the council, your information is processed by:
- Cloudflare, Inc. — our hosting provider. They store the database, files, and configuration for the app on our behalf, under a written processor agreement. Cloudflare is ISO 27001, SOC 2 Type II, and PCI DSS Level 1 certified, and is GDPR compliant. Some processing may take place outside the UK on Cloudflare's global network; international transfers are covered by the UK International Data Transfer Addendum.
- Browser push services (Apple Push Notification service, Google Firebase Cloud Messaging, Mozilla Push Service) — these are the standard mechanisms your phone or browser uses to deliver push notifications. The notification content is encrypted before leaving our servers.
We do not sell your personal information. We do not share it with marketing partners. We do not use third-party analytics, advertising, or tracking pixels in this app.
5. How long we keep your information
| Type of information | How long we keep it |
|---|---|
| Identity (name, mobile / email, team) | For as long as you are a member of council staff using the app, plus a defined period after your account becomes inactive in line with the council's records-retention schedule. |
| Anonymous device identifier (cookie) | Up to 1 year from your last visit, then re-issued on the next visit. |
| Push notification subscriptions | Automatically deleted after 30 days of inactivity. Deleted immediately if you turn notifications off. |
| Engagement events (views, reactions, acks, poll votes) | Retained while the linked content (article, poll, etc.) is live, plus a defined period for reporting and audit. |
| Feedback and shoutouts | Retained for the lifetime of the app unless you ask us to remove them. |
| Audit log of admin actions | Retained for at least 12 months for security investigation purposes. |
| Admin account records | Retained while you have an admin role, then archived in line with HR records retention. |
6. Cookies and similar technologies
The app uses cookies and browser local storage that are essential for it to work. We do not use third-party analytics or advertising cookies.
| Name | Type | Purpose | Lifetime |
|---|---|---|---|
kc_device | First-party cookie (Domain=.kirklees.link) | Anonymous device ID for deduplication and audience counts. Not linked to your identity by itself. | 1 year |
kc_auth | First-party cookie (HttpOnly) | Admin login session. Only set if you have a content-management account and are signed in. | 7 days |
csrf_token / csrf_token_js | First-party cookies | Security tokens to prevent cross-site request forgery on admin actions. | 7 days |
kc_access, kc_service_slug, kc_service_team | First-party cookies | Used by the admin interface to remember your role and which service you administer. Set only on admin accounts. | 7 days |
kc_team, kc_name, kc-onboarded-v1, kc-visit-count | Browser local storage | Remembers your service, name, and that you've completed onboarding so we don't repeat it on every visit. | Until you clear your browser data |
7. Your rights
Under UK data protection law you have the following rights in relation to your personal information. We will respond within one calendar month of receiving a request.
- Right of access: ask for a copy of the information we hold about you.
- Right of rectification: ask us to correct anything that is wrong.
- Right of erasure: ask us to delete information about you, where we no longer have a lawful reason to keep it.
- Right to restrict processing: ask us to pause the use of your information while we look into a question you have raised.
- Right to object: object to processing carried out under public task on grounds relating to your particular situation.
- Right to withdraw consent: for processing based on consent (in this app, push notifications), you can withdraw consent at any time in your device settings or in the app's notification settings panel.
To exercise any of these rights, email dataprotection@kirklees.gov.uk.
8. Complaints
If you are unhappy with how we have handled your personal information you can complain to the Information Commissioner's Office:
Information Commissioner's Office, Wycliffe House, Water Lane, Wilmslow, Cheshire, SK9 5AF.
Helpline 0303 123 1113 · ico.org.uk
We would appreciate the chance to deal with your concerns first, so please consider contacting us before raising a complaint.
9. Children
The app is intended for use by adult council employees and contractors. It is not directed at children, and we do not knowingly collect information from anyone under 16. If you believe a child has used the app, please contact dataprotection@kirklees.gov.uk.
10. Automated decision-making
We do not use the information collected by the app to make automated decisions about you, and the app does not profile you for any purpose.
11. Changes to this notice
We will update this notice when the app changes in a way that affects how we use your information. The version number and "last updated" date at the top of this page will be revised, and significant changes will be communicated in the app itself.
12. How to contact us
Day-to-day questions: max.youell@kirklees.gov.uk
Data-protection questions, subject access requests, or complaints: dataprotection@kirklees.gov.uk