Ciaren

Privacy Policy

Last updated: July 12, 2026

This policy explains what data is collected when you visit this website and when you use the Ciaren software. The short version: the software collects nothing, and the website collects only standard hosting logs plus optional aggregate analytics.

The Ciaren software

Ciaren is local-first. The open-source core:

  • runs entirely on your machine — there is no Ciaren-hosted backend the core needs to talk to;
  • sends no telemetry, usage statistics, or crash reports to us or anyone else;
  • requires no account, registration, or license key to use;
  • stores your flows, datasets, and settings only where you configure it to (your local database and file system).

Some official, opt-in plugins (for example, a future hosted AI feature) may send specific data you choose to a Ciaren-operated service to do their job. That will always be disclosed at install or enable time and covered by its own terms — it is never silent and never on by default.

Your pipelines may of course connect to databases or services you configure; that traffic goes directly from your machine to those services under their own terms, and never through us.

This website

Hosting

This site is a static site. The hosting provider may log standard request data (such as IP addresses) to operate the service. We do not have access to those raw logs.

Analytics (opt-in only)

This site may use privacy-friendly analytics or Google Analytics to understand aggregate traffic (pages visited, referrers, approximate geography) — but only if you say yes. On your first visit a small banner asks for permission:

  • Until you accept, no analytics script is loaded and no analytics cookies are set. Declining (or dismissing the banner) keeps analytics off.
  • Your choice is remembered in your browser's localStorage under the key ciaren-analytics-consent. That value stays on your machine and is not a tracking cookie.
  • To change your mind later, clear this site's data in your browser (or delete that key from localStorage) and the banner will ask again.

If you accept, the enabled analytics provider(s) may set cookies and process your IP address and browser information under their own privacy policy — for Google Analytics, the Google Privacy Policy applies. We use this data only in aggregate to improve the site and documentation; we do not use it to identify individuals, and we do not sell or share it. The site works fully with analytics declined or blocked.

Contact and early-access forms

Some pages (for example, Enterprise early access and marketplace launch notifications) include optional forms. If you choose to submit one, we receive only what you type — such as your name, company, work email, team size, use case, and notes — and we use it solely to respond to that request (for example, to contact you about Ciaren Enterprise or to send one launch notification email).

  • Submitting a form is always optional; the site works fully without it.
  • Depending on configuration, submissions are delivered either as an email you send yourself from your own mail client, or through a form-delivery service acting as our processor; if a processor is used, it will be named here.
  • We do not use form data for advertising, sell it, or add you to a newsletter. To have your submission deleted, contact us via the channels under "Data requests" below.

What we do not do

  • No accounts and no newsletters — forms above are used only to answer the specific request you made.
  • No advertising or ad-tech trackers.
  • No selling of personal data.

This site links to external services (GitHub, PyPI, Google, and others). Once you leave this site, their privacy policies apply, not this one.

Data requests

We hold essentially no personal data about visitors ourselves. For data collected by analytics providers or the hosting provider, requests are best directed to those providers; if you believe we can help with a privacy question or request, contact us via GitHub Discussions or the maintainer's website.

Changes to this policy

We may update this policy as the project evolves (for example, if analytics tooling changes). The "Last updated" date above reflects the latest revision.