Data & Security Overview

Effective date: 15 October 2026

A clear view of how Ciru handles community information

Ciru helps organisations facilitate introductions within their existing networks. This overview describes the current operating model and identifies information available for customer review. Contractual commitments are set out in the agreed order and applicable data-processing agreement.

Workspace boundaries

Customers configure their own communities and decide whom to invite. Organisational workspaces are separated. Ciru does not move participant profiles between customer workspaces or its own peer communities for matching.

Customer administrators can view participant information in their workspace. Participants receive only the information shared through the relevant match and introduction workflow, rather than general access to other full profiles.

Authorised product and customer-support personnel may access information as required for their responsibilities.

Participant choice

Participants receive a brief about a proposed counterpart and can accept or decline. Introductions occur only after both people agree. Reporting and blocking are available, and members can opt out of future participation.

An invitation or profile upload is not itself consent to every introduction. Contact details and other fields shared at each stage must match the Privacy Notice and actual product behaviour.

Information and service providers

Ciru processes professional identity/contact details, participant needs and expertise, supplied LinkedIn links, introduction decisions and feedback, and customer billing information. Profiles can be supplied by participants or uploaded by administrators. Ciru does not externally enrich profiles. Customers determine their workspace's purposes; Ciru does not reuse identifiable participant data for unrelated marketing or unrelated product development.

Provider	Role reported by Ciru
Vercel	Hosting
Supabase	Database/application infrastructure
Resend	Email delivery
Stripe	Payment processing
OpenAI	AI matching and website assistant

These are cloud services. This architecture should not be described as on-premises or locally hosted unless an actual customer-local deployment exists.

AI and communications

Introductions are delivered by email. AI supports matching and the website assistant. Ciru does not intentionally store website-chat transcripts as conversation records. This does not establish that providers retain no inputs, outputs, application state or operational logs.

Ciru does not access private conversations participants conduct after introductions. It collects feedback separately.

Peer-community emails are limited to matching, introductions and related follow-up, rather than product marketing.

Data lifecycle and customer requests

Customers are responsible for lawful participant uploads, workspace configuration, administrator authorisation, necessary privacy notices and recruitment of their network. Ciru and the customer should document processing instructions and assistance obligations in a DPA where applicable.

Contact

Send data-handling questions, access/deletion requests and security reports to ciru@ciru.io. Product personnel handle these enquiries. Customer support is email-only. Please describe the issue without including passwords, full payment details or unnecessary personal information. No fixed support hours, response time or incident-response SLA is stated unless separately agreed.