Krowd

Legal

Krowd Privacy Policy

This Privacy Policy describes how Krowd Group Limited collects, uses, stores, and shares personal data when you use our websites, products, and related services.

Last updated: 15 October 2026

Scope

This Policy applies to personal data processed through Krowd websites, including krowd.org.uk, and our products such as House Krowd, Signals, Krowd Source, and Insights.

It should be read alongside our Terms of Service, which explain service usage, commercial terms, and product-specific obligations.

Who we are and our role

Krowd Group Limited is the controller for personal data where we determine why and how that data is processed, including website, account, security, service-operation, product-governance, audit and customer-relationship activities.

Our role can differ by workflow and category of personal data. Where a customer uses our platform to process resident, tenant, participant, workforce or other personal data under that customer's instructions, Krowd will generally act as processor for that processing and the customer will remain controller.

In some workflows Krowd and a customer or service provider may each act as independent controllers for the processing they separately determine. If a workflow requires a joint-controller arrangement, that arrangement will be documented separately rather than assumed merely because the parties use the same platform or exchange data.

Data we collect

  • Identity and contact details (name, email, job title, organisation).
  • Account and authentication details (login identifiers, access logs).
  • Product usage data (events, interactions, configuration settings).
  • Workflow and provenance data, including source references, campaign or cohort configuration, selection criteria, declarations, consent or authority, provider choice, transmission, delivery and disclosure events.
  • Operational content uploaded by customers and users.
  • Technical data (IP address, browser type, device metadata).
  • Support and communication records (tickets, emails, meeting notes).

Provenance and audit records

Some Krowd products, including Signals, are designed to preserve a machine-readable record of how data, opportunities and transactions move through a workflow. These records may include source, timing, configuration, selection, declarations, consent or other authority, provider choice, transmission, delivery and disclosure events.

We use provenance and audit records to operate and secure the Services, evidence how a workflow arose, investigate incidents, resolve disputes, support customer and regulatory audits, prevent misuse and meet legal or regulatory obligations. Where we act as a processor, we process those records in accordance with the customer's documented instructions except where law requires otherwise or where limited processing is necessary for our own security, integrity or legal obligations.

How we use personal data

  • To provide, operate, and improve our products and services.
  • To manage accounts, billing, and customer support.
  • To maintain platform security, resilience, and abuse prevention.
  • To communicate product updates, service notices, and legal changes.
  • To develop analytics, reporting, and aggregated service insights.
  • To maintain provenance, consent, authority, delivery and disclosure records for configured workflows.
  • To operate customer-configured integrations, listeners, exports, campaigns and other workflow controls.
  • To comply with applicable legal and regulatory requirements.

Lawful bases (UK GDPR)

Depending on context, we rely on contract, legitimate interests, legal obligation, and where required, consent. Our legitimate interests can include operating and improving the Services, maintaining security and integrity, preserving audit and provenance records, preventing misuse, supporting compliance and resolving disputes, provided those interests are not overridden by the rights and freedoms of the individual.

Where a customer is controller, that customer is responsible for identifying the lawful basis and any additional consent, notice, authority or other condition required for the purpose it configures. The availability of a Krowd feature, filter, export or integration does not itself create a lawful basis for processing or disclosure.

Controller vs processor

Data-protection roles depend on the relevant processing activity. Krowd may act as controller for processing we determine ourselves and as processor where we handle personal data on a customer's documented instructions. The applicable role may be further described in an order form, Data Processing Addendum, product-specific privacy information or other written arrangement.

Sharing and subprocessors

We share personal data only where there is an appropriate basis to do so. This can include infrastructure providers, analytics services, support tooling, professional advisers and recipients that a customer or user has validly configured or selected as part of a workflow.

Where a customer determines the recipient, purpose or scope of an export or disclosure, the customer is responsible for ensuring that disclosure is lawful and consistent with applicable notices, permissions, consent, authority and provider-choice requirements. Krowd may apply technical or governance controls before allowing a destination, field set or workflow to operate.

A failed or rejected technical delivery does not, by itself, create authority to disclose personal data to a different recipient. Any retry or rerouting must remain within the permissions and other conditions applicable to that workflow.

We require service providers acting on our behalf to implement appropriate technical and organisational safeguards, confidentiality commitments, and data protection obligations.

International transfers

If personal data is transferred outside the UK, we use appropriate safeguards such as adequacy regulations or approved contractual transfer mechanisms.

Data retention

We retain personal data only for as long as necessary for the purposes set out in this Policy, and to satisfy legal, accounting, reporting, contractual, security and audit obligations. Provenance and disclosure records may need to be retained for longer than active workflow data where they are required to evidence consent, authority, platform operation, a transaction history, a dispute or regulatory compliance.

Security

We maintain proportionate security measures designed to protect personal data against unauthorised access, loss, misuse, or alteration, including access controls, monitoring, and secure development practices.

Your data protection rights

Subject to applicable law, you may have rights to access, correct, erase, restrict, or object to processing of personal data, and to request portability.

If we process data solely on behalf of a customer, please contact that customer first so they can handle your request as controller. If Krowd is controller for the relevant processing, you may contact us directly using the details below.

Cookies and analytics

We use cookies and similar technologies for essential functionality, performance measurement, and product improvement. You can manage browser-level cookie preferences at any time.

Children's privacy

Our services are designed for organisations and professional users and are not directed to children under 13.

Changes to this Policy

We may update this Privacy Policy from time to time. When we make material changes, we will update the date above and provide notice where appropriate.

Contact

If you have privacy questions or want to exercise your rights, contact us via the contact page.