Plain language
Cairn privacy policy
This page explains what the mini app sends, stores, and shares. Last updated 24 September 2026.
What stays on your device
Your saved plans, daily check-ins, build journal, validation experiments, release drafts, and private Track data are stored in your browser's local storage. Cairn does not require an email account, password, or contact list. A protected team workspace is optional and uses a short lived signed Nimiq wallet session.
What is sent for generation
When you generate or refine a plan, the text you submit is sent to Cairn's Cloudflare Worker. The Worker sends the request to Google Gemini to produce the response. Cairn does not put an API key in the app.
Wallet information
Cairn receives the connected Nimiq wallet address to verify your identity and protect team access. Your wallet signs a short lived login challenge. Cairn does not receive or store your private key. A teammate reward goes directly from the owner's wallet to the named member. The Worker asks the configured Nimiq RPC service for public transaction data. Cairn never holds teammate reward funds.
Refinement and network limits
A normal planner follow up sends the PRD, flow, and text only builder pack to Cairn's Worker and Google Gemini for that one response. Choosing Replan from progress also sends a compact check-in summary, task status and due dates, and milestone blocker state. Private notes, priorities, dependencies, wallet assignments, rewards, the full journal, experiments, and release drafts stay on your device. Cairn uses a short lived, sanitized network address during wallet sign in and abuse checks. It is not used for analytics or advertising.
Sharing
Nothing is shared until you tap Share. A public shared plan is uploaded to the Worker so another person can open its read only link. The snapshot includes progress, milestone dates, task due dates, labels, and recorded reward proofs. It excludes notes, priorities, and dependency details. The creator can revoke the link. Do not share confidential material.
Protected team workspaces
The owner can create an optional protected workspace for Track and add named Nimiq wallet addresses as Viewers or Editors. Members must sign in with the wallet that the owner added. The Worker checks the wallet session and role on every request. The team snapshot includes milestone and task text, progress, labels, dates, the owner's milestone blocker flag, and recorded reward proofs. It excludes the PRD, user flow, Build summary, private notes, priorities, and dependency details. The owner can delete the workspace. Team records otherwise remain available for up to one year.
Tracking and analytics
Cairn has no analytics cookies, Google Analytics, advertising pixels, device fingerprinting, or third party tracking script. It keeps first-party aggregate evidence from successful wallet-authenticated actions. A private key inside one Durable Object converts the signed wallet address to a stable digest; the usage record does not store the raw address, plan text, task content, IP address, balance, or transaction hash. The public usage report returns counts only. Optional ref labels stay in the browser tab until wallet verification, and source groups with fewer than three wallets remain hidden.
To find a slow or failing service, the Worker also keeps a ten-percent operational sample containing only the API category, request method, response status, and duration. It does not log prompts, URLs, share or team identifiers, wallet addresses, request bodies, or network addresses.
Security and retention
Cloudflare manages encryption at rest for server records in KV and SQLite-backed Durable Objects. Wallet sessions expire after twelve hours and login challenges expire after five minutes. Public shared plans and protected team records remain available for up to one year, unless the storage provider removes them sooner. Anonymous usage records remain as competition evidence until the ledger is retired. Do not put confidential material in a shared plan or team tracker.
Questions
For a privacy question or a correction request, open an issue in the public Cairn repository. Do not include private wallet keys or confidential product documents.