Last updated: July 17, 2026

Privacy Policy

This Privacy Policy explains how Analog Research & Design LLC ("Analog," "we," "us," or "our") collects, uses, discloses, stores, and protects information when you use clickclick, including the clickclick for macOS application, the companion app for iMessage, the accounts and support websites, downloads, updates, command routing, and related services (collectively, the "Service").

We do not sell personal information. We also do not use your private local files, messages, notes, screenshots, or CloudKit command content for advertising.

1. Information We Collect

Account, Billing, and Website Data

When you create an account, sign in, buy credits, subscribe, contact support, or use our websites, we may collect:

  • Name, email address, authentication identifiers, profile data, and support messages.
  • Subscription status, credit balances, checkout sessions, billing events, payment-provider customer IDs, transaction history, and tax or refund information.
  • Website and app portal usage data such as pages visited, timestamps, session identifiers, device/browser information, error data, and cookie or analytics preferences.

Payments are processed by providers such as Stripe or Apple. We do not intentionally store full payment card numbers.

Local App Data on Your Device

The macOS app stores and processes data locally, including:

  • Chat history, conversation titles, project links, model names, compaction summaries, model payload snapshots, attachments, and generated files.
  • Workspace paths, file metadata, file contents you ask the Service to read or edit, Git/worktree metadata, terminal commands, command outputs, logs, and PTY snapshots.
  • Screenshots, images, browser content, clipboard content, and GUI state when you attach them or authorize computer-use features.
  • Local retrieval indexes and embeddings for selected project files. These embeddings are generated on-device using Apple NaturalLanguage.
  • Memory records. Session memory may be in-memory or persisted if enabled; global memory is stored in local SQLite; user memory is encrypted at rest with AES-GCM under Application Support, with keys protected through local secure storage.
  • Settings, feature flags, selected models, custom instructions, project roots, provider base URLs, prompt-cache settings, subagent configuration, and iMessage/Notes routing preferences.

Local logs can contain prompts, outputs, command text, file paths, terminal output, errors, and tool results. You should treat local logs as potentially sensitive.

Apple Contacts, Messages, iMessage, Notes, and Automation Data

If you grant permission or configure these features, the Service may access:

  • Contacts data to populate iMessage recipient options.
  • Messages and iMessage data, including chat identifiers, participants, handles, aliases, message text, attachments, timestamps, sender identity settings, and delivery state.
  • Apple Notes folders, note metadata, note bodies, and note structure for configured Notes workflows.
  • Apple Events, Accessibility, Full Disk Access, and related macOS permissions to control apps, send messages, open notes, run Terminal setup flows, or perform requested automation.

These permissions are optional, but the related features may not work without them.

iCloud and CloudKit Data for the iMessage Companion

The iMessage companion writes records to your private CloudKit database in the iCloud.com.clickclick.code.20260516 container. It does not write these records to a public CloudKit database.

CloudKit records can include command text, command arguments, result text, result image assets, route hashes, client or device identifiers, companion status, model and subagent settings, message filter settings, record status, trace identifiers, source bundle identifiers, and timestamps.

AI Provider and Third-Party Tool Data

Depending on your settings, the Service may send prompts, conversation context, files, screenshots, images, tool results, usage metadata, and related request data to:

  • OpenAI or an OpenAI-compatible API endpoint you configure.
  • Anthropic services through Claude Code or other Anthropic tools you authenticate.
  • OpenAI services through Codex or other OpenAI tools you authenticate.
  • Google services through Gemini or other Google tools you authenticate.
  • Other third-party tools, APIs, browsers, websites, command-line programs, MCP servers, or integrations you use through the Service.

Those providers process data under their own terms, privacy policies, data controls, retention rules, and account settings. We do not control their processing when you authenticate directly with them or configure their endpoints.

Usage and Telemetry Data

If enabled or required for account, billing, reliability, or safety features, we may collect usage and telemetry such as:

  • User ID, date, model, operation type, token counts, request counts, estimated cost, conversation or message identifiers, client timestamps, and sync status.
  • Event type, app version, platform, session identifier, error data, performance data, and sanitized event payloads.

Telemetry is intended to avoid raw prompt, file, message, note, or screenshot content. Some diagnostic data may still include file paths, command names, error strings, model names, feature names, or other metadata.

2. How We Use Information

We use information to:

  • Provide, operate, authenticate, secure, meter, bill, support, and improve the Service.
  • Route prompts, commands, results, files, screenshots, and messages according to your settings.
  • Store local history, memories, attachments, project indexes, and settings.
  • Sync iMessage companion commands and results through your private CloudKit database.
  • Process subscriptions, credits, refunds, invoices, and payment events.
  • Diagnose crashes, bugs, performance issues, permission issues, abuse, fraud, and security events.
  • Enforce our Terms of Service, Usage Policy, provider requirements, and legal obligations.

3. How We Disclose Information

We may disclose information to:

  • Service providers that help with hosting, authentication, storage, analytics, payments, support, email, security, and infrastructure.
  • AI providers and third-party tools you configure or authenticate, including OpenAI, Anthropic, Google, Apple, and provider-compatible endpoints.
  • Apple services such as iCloud, CloudKit, iMessage, Messages, Contacts, Notes, and App Store systems when those features are used.
  • Payment providers such as Stripe or Apple for checkout, subscriptions, billing portals, invoices, taxes, refunds, and fraud prevention.
  • Legal, regulatory, or safety authorities when required by law or when we believe disclosure is necessary to protect rights, safety, security, or the integrity of the Service.
  • Successors in a merger, acquisition, financing, reorganization, bankruptcy, or sale of assets.

4. Provider Privacy Alignment

This policy is designed to align with provider materials reviewed on July 17, 2026, including:

Provider terms can change. You should review the provider terms and privacy settings for accounts or API keys you connect to clickclick.

5. Local Storage, Security, and Secrets

The Service stores much of its operational data on your device. Secrets such as command PINs, unlock passwords, and memory encryption material are stored through the macOS Keychain or local secure storage where available. A local unsafe credential-cache mode exists only for explicit testing and may store secrets as plaintext under Application Support.

We use reasonable administrative, technical, and organizational safeguards. No method of storage, transmission, AI processing, endpoint configuration, local automation, or third-party integration is completely secure.

6. Retention

Retention depends on the data type:

  • Local chat history, attachments, logs, project indexes, memory, settings, and generated files remain on your device until you delete them through the app, filesystem, operating-system tools, or uninstall/cleanup processes.
  • Local project files and repositories remain under your control.
  • Telemetry events are designed for a 30-day retention window where the production cleanup job is enabled.
  • Usage, billing, subscription, credit, account, support, audit, tax, fraud-prevention, and legal records may be retained as long as needed for the purposes described above and as required by law.
  • CloudKit conversation-scoped records can remain in your private CloudKit database after an iMessage conversation is unbound. The normal Switch flow clears local binding and revokes the current conversation binding when present, but it does not currently delete every conversation-scoped CloudKit command/result record.
  • AI providers and third-party tools retain data according to their own terms, privacy policies, and account settings.

7. Your Choices and Controls

You can:

  • Decline or revoke macOS permissions such as Contacts, Apple Events, Accessibility, Full Disk Access, and related app access in System Settings.
  • Disable or avoid iMessage, Notes, memory persistence, prompt-cache retention, telemetry, custom provider endpoints, or third-party CLI integrations where the app exposes those controls.
  • Delete local conversations, projects, memory entries, attachments, logs, app preferences, and Application Support data.
  • Delete or manage CloudKit/iCloud data through Apple tools where available.
  • Configure provider accounts and data controls directly with OpenAI, Anthropic, Google, Apple, and other providers.
  • Request access, correction, deletion, or export of account data we control by contacting us.

Some deletion requests may be limited by law, security, fraud-prevention, billing, tax, backup, provider, or technical obligations.

8. Cookies and Analytics

Our websites may use cookies or similar technologies for authentication, preferences, traffic measurement, reliability, and abuse prevention. You can manage cookies through your browser or site controls where available. Blocking cookies may affect account or billing features.

9. Children

The Service is not directed to children or teenagers under 18. Do not use the Service if you are under 18. We do not knowingly collect personal information from children under 13. If you believe a child provided personal information to us, contact us and we will take appropriate steps.

10. International Transfers

We are based in the United States. If you use the Service from outside the United States, information may be processed in the United States and other countries where we, our providers, or the providers you configure operate.

11. U.S. State Privacy Disclosures

Depending on where you live, you may have rights to access, correct, delete, export, or restrict certain personal information, and to appeal a privacy request decision. We do not sell personal information or share it for cross-context behavioral advertising as those terms are commonly used in U.S. state privacy laws.

To exercise rights over data we control, contact us at support@clickclick.ly. For data processed by Apple, OpenAI, Anthropic, Google, Stripe, Supabase, or another provider under your account, use that provider's privacy tools.

12. Changes

We may update this Privacy Policy from time to time. The updated version will be posted with a new "Last updated" date.

13. Contact

Analog Research & Design LLC

Los Angeles, California, USA

support@clickclick.ly