Legal

Acceptable use

Draft pending review. Cairnflow is built to find conversations worth joining, not to broadcast into them. These rules exist so it stays that way.

What the product will not do

These are architectural, not policy choices you could ask us to relax: Cairnflow has no code path that submits content to any platform, so it cannot post, comment, message, or schedule outreach. Every reply draft passes deterministic safety checks before you can copy it.

How we read public content. Through official APIs, open protocols, published feeds, and public web pages the site’s own robots.txt permits. We identify ourselves on every request, obey the rate limits and crawl delays sites publish, and never access anything behind a login, a paywall or a private group. If a site asks automated clients to stay out — inrobots.txt or by refusing them — we stay out. We do not disguise our client, rotate addresses or accounts, or use scraping vendors to get around a refusal.

What you must not do with it

• Post the same or near-identical reply across many conversations.
• Hide that you are affiliated with the product you are recommending. Disclosure is required, and drafts include it.
• Reply where the community’s rules prohibit promotion, or evade a moderator’s decision.
• Use exported lead data to build a cold-outreach list, or feed it into an automated sending tool.
• Target people rather than topics — Cairnflow finds questions to answer, not individuals to pursue.
• Share one account between people, or use the free tools to work around plan quotas.

Prohibited content and industries

Do not use Cairnflow to promote anything illegal, to impersonate a person or organisation, or to target people based on sensitive characteristics such as health conditions, financial distress, immigration status or sexual orientation.

How we enforce this

We monitor for patterns that suggest misuse — near-duplicate drafts, unusual export volumes, quota circumvention — and record them for review by a human. Where a rule has clearly been broken we may restrict features or suspend a workspace. We will tell you what we found and give you a way to respond, unless we are legally prevented from doing so.

If you see something

If you believe a Cairnflow user has broken these rules, or that content was surfaced that should not have been, email support@cairnflow.io and we will look into it.