Skip to main content
Security & Trust

How CiCwtch approaches privacy, security, and resilience

This page summarises the intended controls, operating principles, and governance direction for the public-facing CiCwtch service.

Privacy-first direction Multi-tenant SaaS Preview content

Security principles

  • Least-privilege access and role separation where practical.
  • Secure-by-default application patterns for authentication, session handling, and tenant isolation.
  • Change control through versioned source, CI checks, and documented architecture decisions.
  • Defence in depth across application, infrastructure, and data layers.

Data protection posture

CiCwtch is being built with a privacy-first approach intended to support UK GDPR and related data protection expectations. The service direction includes data inventories, retention controls, documented processing, and structured privacy assessment work.

Important:

This trust page is an overview, not a substitute for a formal DPA, privacy notice, or legal advice. Those documents should be published separately and kept aligned with the live service.

Infrastructure direction

The current technical direction uses Cloudflare-hosted components for web delivery and API hosting, with managed storage layers for relational data and object storage. Public assets and application components are intended to be separated so the root marketing site and tenant application flows do not bleed into each other.

  • Public marketing pages only on root domain hosts.
  • Tenant subdomains route directly into the application experience.
  • Static web assets served separately from business data processing APIs.

Operational safeguards

  • Repository guardrails for architecture-sensitive and privacy-sensitive changes.
  • Documented migration practices for database evolution.
  • Configuration-based deployment with environment-separated secrets.
  • Planned monitoring, status visibility, and incident response maturity over time.

Customer responsibilities

Customers remain responsible for lawful collection and use of their client, pet, and staff data; internal access management; device security; and the accuracy of information entered into the system. A secure platform does not replace sensible operational controls in the real world.

Roadmap intent

The trust model is expected to expand over time with clearer public documentation for privacy, retention, data processing, security commitments, and service status. This page is meant to give visitors a sensible top-level view without pretending the whole legal stack lives in one paragraph and a prayer.