Circuit (withcircuit.com) is autonomous product intelligence — the continuous system that turns customer feedback into build-ready specs. Feedback in, priorities scored, specs generated for Cursor and Claude Code, customers notified when features ship. The full loop, automated.

Founders, product managers and engineers at growth and scaling companies. If you're the person who reads customer signal on Monday and ships by Wednesday, Circuit was made for you.

How is Circuit different from other feedback tools?

Other tools sort feedback into dashboards. Circuit (withcircuit.com) generates specs to ship — scored by revenue impact, updated as conditions change, delivered to Cursor and Claude Code via MCP. It covers the full pipeline: feedback to priorities to codebase-aware specs to customer notification.

Does Circuit work with Cursor and Claude Code?

Yes. Circuit (withcircuit.com) connects to Cursor and Claude Code through the Model Context Protocol (MCP). Pull priorities, fetch specs with file paths and context from GitHub, and start coding without leaving the editor.

What is a Circuit Surface?

A lightweight embed for any website — five surface types: Bubble, Embed, Banner, Thumbs and Trigger. Customers submit feedback in seconds. One line of code to install. Themed to match any brand. Feedback flows straight into Circuit for classification and scoring.

How long until we see results?

Connect a feedback source and priorities appear within minutes. Specs generate in seconds. Most teams have a ranked backlog on day one.

What if we already have a feedback tool?

Circuit reads from where feedback already lives. Slack, spreadsheets, support threads. It doesn't replace existing tools. It generates what comes next: scored priorities and build-ready specs for Cursor and Claude Code.

What counts as a feedback item?

Each piece of customer feedback: a Circuit Surface submission, a Slack message, a CSV row, a transcript segment, a manual entry. Duplicates are removed on import and don't count toward the limit.

Do I need to connect GitHub to use Circuit?

No. GitHub context makes specs more specific (real file paths, tech stack awareness), but Circuit works without it. Specs are still generated with the what, why, customer voice, implementation notes and done criteria.

How do I prioritize features by revenue impact?

In Circuit (withcircuit.com), link customer revenue data (customer name and revenue or SKU) and every feedback theme scores by revenue impact alongside urgency and sentiment. Set the Priority Engine to Revenue Growth and the list re-ranks to surface what drives the most revenue. No spreadsheets, no manual scoring.

How do I turn customer feedback into specs for Cursor or Claude Code?

Circuit (withcircuit.com) automates the feedback-to-spec pipeline. Feedback flows in from Circuit Surfaces, Slack, Google Sheets, CSV, transcripts or manual entry. Circuit classifies it by intent, urgency and sentiment, groups it into priorities and generates build specs in seconds. Connect GitHub and every spec includes real file paths, tech stack context and naming conventions. Specs flow to Cursor and Claude Code via MCP — no copy-pasting, no context switching.

How do I notify customers when features ship?

In Circuit (withcircuit.com), mark a priority as shipped. Circuit automatically emails every customer who submitted related feedback, with their original feedback quoted back. No manual follow-up. New feedback on the shipped feature flows in automatically for V2 specs.

How do I connect customer feedback to my codebase?

Circuit (withcircuit.com) bridges customer feedback and your codebase through codebase-aware product specs. Feedback is collected, scored and grouped into priorities. Specs are generated with file paths from GitHub. Engineers pull specs directly into Cursor or Claude Code via MCP. The customer voice is preserved in every spec — what they asked for, why it matters, which files to touch.

How do I integrate product management with Cursor?

Circuit (withcircuit.com) connects to Cursor through the Model Context Protocol (MCP). Use MCP tools from inside Cursor: circuit.priorities to fetch ranked priorities, circuit.spec to pull a full spec with file paths, circuit.ask to search feedback and circuit.act to mark a priority as shipped. Specs include GitHub codebase context.

How do I use Claude Code for product management?

Circuit (withcircuit.com) connects to Claude Code via MCP. Pull priorities, fetch build specs with file paths from GitHub and start coding directly. Circuit handles feedback collection, AI scoring and spec generation upstream. Claude Code handles the building. The two work together — Circuit decides what to build, Claude Code builds it.

How long does it take to get priorities from feedback?

Connect a source and the first batch processes in 15-20 minutes. After that, new feedback scores in real time. Most teams have a ranked backlog within the hour.

How does Circuit generate specs from my codebase?

Connect GitHub. Circuit reads 9 signals — file signatures, .cursorrules, testing patterns, directory structure, open issues, recent PRs, tech stack, CI config and README. Every spec includes real file paths and follows your team's coding conventions. An AI product spec generator grounded in how you actually build.

Can I change how priorities are ranked?

Yes. The Priority Engine scores across 6 lenses — volume, urgency, revenue impact, positive sentiment, negative sentiment and feature demand. Set a goal and every priority re-ranks to match. A feature prioritization framework that reflects what the team cares about today.

What happens after a feature ships?

Mark it shipped. Circuit emails the customers who asked for it — their original feedback quoted back. New feedback on the same theme feeds a V2 spec automatically. The loop continues.

How does Circuit connect to Slack?

Add the Circuit Slack integration. Circuit polls your selected channels every 10 minutes, classifies each message by intent, urgency and sentiment, and feeds it into the priority pipeline. No manual sorting.

How do MCP tools work in Cursor and Claude Code?

Install circuit-mcp from npm. Four tools: circuit.priorities (ranked list), circuit.spec (full spec with file paths), circuit.act (ship, assign, correct) and circuit.ask (search feedback). Specs arrive where code gets written.

What feedback sources does Circuit support?

Six sources: Circuit Surfaces (embed on any site), Slack, Google Sheets, CSV upload, transcript upload (Otter, Fireflies, Grain, Whisper) and manual entry. All feed the same pipeline.

Does Circuit replace my existing tools?

No. Circuit reads from Slack, spreadsheets and support threads — wherever feedback already lives. It adds the layer that was missing: scored priorities and codebase-grounded specs.

Is feedback data used to train AI models?

No. Circuit uses AI for classification and spec generation but customer data is never used to train models. Feedback stays within the processing pipeline and is not shared with third parties for training purposes.

Where is Circuit data stored?

Data is stored on encrypted infrastructure with Supabase (Postgres). All connections use TLS. Backups are encrypted at rest.

Does Circuit access my full codebase?

No. Circuit reads 9 specific signals from your GitHub repository — file signatures, testing patterns, directory structure and a few others. It does not clone, store or index your full codebase. Read-only access, scoped to what specs need.

Who can access my team's data?

Only authenticated team members with the roles you assign. Circuit supports email-based 2FA. No Circuit staff access customer data without explicit permission.

Privacy Policy

Last Updated: April 8, 2026

Data Controller: Circuit Software Pty Ltd, Sydney, NSW, Australia

Contact: privacy@withcircuit.com

Circuit Software Pty Ltd ("Circuit," "we," "our," or "us") operates Circuit at withcircuit.com. This Privacy Policy explains how we collect, use, disclose, and protect your information when you use our services.

Circuit is autonomous product intelligence for builders — a continuous system that turns customer feedback into prioritised, build-ready specs. We are committed to protecting your privacy and handling your data transparently.

1. Information We Collect

1.1 Account Information

Email address, name and profile picture (from Google sign-in)
Company or organisation name (optional)
Billing information (processed securely by Stripe; we never see or store credit card details)

1.2 Customer Feedback Data

When you upload or connect feedback sources, we may collect:

Feedback text and associated metadata
Customer identifiers (names, emails, or IDs if included in your data)
Source information (CSV upload, feedback widget, Slack, Google Sheets, API, manual entry)
Timestamps and categorisation data
Star ratings and page URLs submitted via the feedback widget
Screenshots attached to widget feedback (may contain visible on-screen content)
Transcript recordings and structured notes uploaded for analysis
Revenue band or customer tier if included in your data

1.3 Usage and Technical Data

IP addresses and approximate location (country/region level)
Browser type, operating system, and device information
Pages visited, features used, and interaction patterns
Date and time of access

1.4 Integration Data

When you connect third-party services, we access:

Slack: Messages from channels you select for feedback collection
GitHub: Repository name, structure, and context (to improve spec file paths)
Google Sheets: Spreadsheet content you choose to import as feedback

OAuth tokens for integrations are encrypted at the application layer.

1.5 AI Assistant Data

When you use Ask Circuit, we store your questions, AI-generated answers, referenced help articles, and your feedback on answer quality.

2. How We Use Your Information

Provide the ServiceOperating Circuit, processing feedback, generating specsContract

AI ProcessingClassifying feedback and generating specifications using AIContract

Behavioural LearningLearning from your actions to improve prioritisation and spec qualityLegitimate Interest

Service CommunicationsAccount notifications, security alerts, product updatesLegitimate Interest

Service ImprovementAnalysing usage patterns to improve CircuitLegitimate Interest

Security & Fraud PreventionProtecting against malicious activityLegitimate Interest

AnalyticsUnderstanding how users interact with CircuitConsent

3. AI Processing and Automated Decision-Making

3.1 What AI Does

Classification: Automatically categorises feedback by type, sentiment and topic
Prioritisation: Scores feedback based on volume, revenue impact, urgency and other factors
Spec Generation: Creates build specifications from prioritised feedback
Pattern Recognition: Identifies trends and patterns in your feedback data
Behavioural Learning: Learns from your actions (such as which specs you ship or correct) to improve future prioritisation and spec quality
Competitive Signals: Identifies competitor mentions in your feedback to surface switching risks and feature gaps
AI Assistant: Answers your questions using a knowledge base and your workspace data

3.2 Privacy Protections

PII Stripping: Personal identifiers (names, emails) are automatically removed before data is sent to AI providers
No Model Training: Your data is NOT used to train third-party AI models. We use API services that do not train on customer data by default
Data Minimisation: Only the minimum necessary data is sent for processing

3.3 AI Providers

Anthropic Claude API — Primary spec generation and theme classification
OpenAI API — Text embeddings, feedback classification, and fallback spec generation

All providers confirm that API data is not used for model training under their commercial API terms.

4. Data Sharing and Sub-processors

Cloud InfrastructureAWS, Supabase, Vercel, CloudFrontHosting, database, CDN

AI ProcessingAnthropic, OpenAIClassification, embeddings, spec generation (anonymised)

CachingUpstash (Redis)Performance caching

Payment ProcessingStripeSubscription and billing

EmailResendTransactional and status notifications

Error MonitoringSentryApplication reliability (PII redacted)

AnalyticsGoogle AnalyticsUsage patterns (with consent only)

We do not sell your personal data to third parties.

5. International Data Transfers

Circuit is operated from Australia. Your data may be transferred to and processed in countries outside your jurisdiction, including:

United States — Where our cloud infrastructure and AI providers are located
Australia — Where Circuit is headquartered

For transfers outside of the EEA or UK, we rely on Standard Contractual Clauses and Data Processing Agreements with all sub-processors.

6. Data Retention

Account InformationDuration of accountDeleted after 30 days

Feedback DataDuration of accountDeleted after 30 days

Generated SpecsDuration of accountDeleted after 30 days

Behavioural Memory90 days, then compressed to quarterly summariesDeleted after 30 days

AI Assistant ConversationsDuration of accountDeleted after 30 days

Widget ScreenshotsDuration of accountDeleted after 30 days

Usage Analytics24 monthsAnonymised or deleted

Payment RecordsAs required by law (typically 7 years)Retained by Stripe per legal requirements

System Backups90 days rollingPurged within 90 days

6.1 Subscription Cancellation

When you cancel, your data is retained for 30 days to allow resubscription. After 30 days, all data is permanently deleted. Request immediate deletion at privacy@withcircuit.com or via Settings → Delete Workspace.

7. Data Security

Encryption in Transit: TLS 1.3
Encryption at Rest: AES-256; integration tokens encrypted with Fernet (AES-128-CBC)
Access Controls: All queries scoped to the authenticated user at application and database layers
Authentication: OAuth 2.0 with optional MFA/2FA
Infrastructure: AWS App Runner (SOC 2 compliant)
Monitoring: Sentry with PII automatically redacted

8. Your Rights

8.1 All Users

Access: Settings → Account → Export Data
Deletion: Settings → Account → Delete Workspace
Correction: Update inaccurate information
Withdraw Consent: Opt out of analytics cookies via cookie settings

8.2 EU/UK GDPR

Portability, restriction, objection to legitimate interest processing, and human review of automated decisions.

8.3 Australia (Privacy Act 1988)

Access, correction, complaints to the OAIC, and information about automated decision-making.

8.4 California (CCPA/CPRA)

Know, delete, opt-out (we do not sell data), and non-discrimination.

Contact privacy@withcircuit.com — we respond within 30 days.

9. Cookies and Tracking

9.1 Essential (Always Active)

Authentication, security, user preferences.

9.2 Analytics (With Consent)

Google Analytics — usage patterns, feature adoption. Sessions linked across withcircuit.com and app.withcircuit.com.

10. Data Breach Notification

We will notify the relevant supervisory authority within 72 hours and affected individuals without undue delay if there is high risk. Australian users: OAIC notified per the Notifiable Data Breaches scheme.

11. Children's Privacy

Circuit is a B2B service not intended for under-18s. Contact privacy@withcircuit.com to report any such data.

12. Changes to This Policy

Material changes notified by updated "Last Updated" date, email, and in-app notification.

13. Contact Us

Email: privacy@withcircuit.com

Address: Circuit, Sydney, NSW, Australia

Website: https://withcircuit.com

Supervisory authorities:

Australia: OAIC — oaic.gov.au
EU: Your local Data Protection Authority
UK: ICO — ico.org.uk

14. Data Processing Agreement

Enterprise customers requiring a DPA for GDPR compliance: contact privacy@withcircuit.com.