Privacy Policy

This Privacy Policy explains how Colorblend Consulting LLC ("Colorblend", "we", "us") collects, uses, and protects information in connection with Feedstick (the "Service") — a hosted product-feedback platform with a public feedback board, a developer feedback-ingest API, and an MCP server that lets coding agents you authorize read and triage your board.

Controller and processor roles

For information about the people who create Feedstick accounts (our customers), Colorblend acts as the data controller. For end-user feedback that a customer collects through their own application and sends to Feedstick, the customer is the controller and Colorblend acts as a processor, handling that feedback on the customer's behalf and on their instructions. Customers who need processor terms can review our Data Processing Agreement.

Information we collect

• Account data. When you sign in, we collect your email address and issue session tokens. Feedstick uses passwordless, one-time-code (OTP) sign-in, so we do not store account passwords.
• Feedback submitted through the API. Customer applications send feedback to our ingest endpoint (POST /feedback). A submission may include the feedback content, optional structured context (arbitrary JSON the customer chooses to attach), an app_name label, a feedback type, and an optional submitter_email. Feedback content is controlled by the customer and their end users and may contain personal data.
• Ingest keys. Each app is issued a public, write-only ingest key used to authenticate submissions. Keys are rotatable and revocable.
• Coding-agent connections (MCP). If you connect a coding agent (such as Claude Code, Cursor, or Codex) to your board, we store the records needed to run that connection: the registration details the client software submits, the authorization request and your approval of it, the scopes you granted (read, comment, triage), the access and refresh tokens issued to that client, and the time the connection was last used. You can revoke a connection at any time from your dashboard, which invalidates its tokens.
• Billing data. Pass purchases are handled by Polar, our payment provider and merchant of record. Polar collects your payment details directly under its own privacy policy; we receive which Pass you bought, when its access window ends, and customer identifiers — not your full payment card details.
• Support submissions. If you contact us through the in-app support widget, we collect your message and any screenshot you choose to attach.
• Operational data. With each feedback submission we record the submitting client's IP address and browser user agent, along with timestamps and a hash of the request body used to detect duplicates. We use this data to rate-limit, prevent abuse, secure, and operate the Service, together with standard server logs. When a submitter email is provided, we also derive a pseudonymous display handle from it for the feedback board.
• Product analytics and session replay. With your consent, we use PostHog to collect usage analytics (such as page views, feature interactions, device and browser type, and — when signed in — your account identifier) and to record replays of your own sessions on our site and app so we can understand usage and fix bugs. Session replays mask all text and form inputs, so the content you type (including feedback and email addresses) is not captured. This is optional and off until you accept — see Analytics and session replay below.

How we use information

• Provide and operate the hosted feedback board and ingest API.
• Authenticate sign-in and send transactional email (such as one-time codes).
• Organize, group ("stack"), and classify feedback so teams can triage it.
• Serve your board to coding agents you have authorized, within the scopes you approved.
• Rate-limit, secure, debug, and improve the Service.
• Communicate with account holders about the Service.

We do not sell or share personal information (as "sell" and "share" are defined by the California Consumer Privacy Act), and we do not use feedback content for advertising.

AI processing

AI is a core part of how Feedstick works. The text content of a feedback submission is sent to our AI provider to generate an embedding and to classify and group ("stack") related feedback, so teams see organized signal instead of a raw queue. Only feedback content is processed for this purpose; it is used to provide the Service, not to train third-party models.

Coding agents and MCP

Feedstick runs an MCP server, so you can connect a coding agent — Claude Code, Cursor, Codex, or any other MCP client — to your board. Connecting one is entirely your choice, and no agent can reach your data until you complete an OAuth approval and grant it scopes.

Understand what that approval does: it sends your feedback data to software we do not operate. When your agent reads the board, the feedback you selected — which may contain personal data your end users wrote — is delivered to that client and, in most cases, to the AI provider behind it. That provider is chosen by you, not by us; it is not one of our service providers, we have no contract with it on your behalf, and its handling of the data is governed by its own terms and privacy policy. If you are a controller for that data, authorizing a connection is a disclosure you are making, and you are responsible for having a lawful basis for it.

Two protections are built into the connection and cannot be switched off:

• Submitter email addresses are never sent to an agent. Feedback is attributed by the same pseudonymous handle the board shows, and responses are stripped of email addresses on the way out — including addresses that appear inside the feedback text itself.
• An agent cannot email your customers. The mention machinery that sends mail to a submitter is not reachable from an MCP connection.

Feedback is written by members of the public, so text an agent reads may be phrased to manipulate it. We label user-submitted content before handing it to a model, but no server-side measure can fully separate an instruction from a feature request. Be deliberate about what other tools you give an agent that is connected to your board — see our coding agents documentation.

Service providers

We rely on a small set of infrastructure providers that process data on our behalf under their own security and privacy commitments:

• Convex — application database, backend runtime, file storage, and vector search.
• Cloudflare — hosting, content delivery, and network security.
• Resend — delivery of transactional email (such as sign-in codes).
• OpenAI — embeddings, classification, and feedback grouping.
• Polar — Pass purchases and payment processing, as merchant of record.
• PostHog — product analytics and session replay, used only with your consent (see below).

Apart from these providers, feedback and account data leave our infrastructure in only one other way: through a coding-agent connection you have authorized, as described above. We do not otherwise disclose your data to third parties, and we use it only as needed to operate the Service.

Analytics and session replay

To understand how the Service is used and to find and fix problems, we use PostHog for product analytics and session replay on our marketing site and app. This processing is optional and consent-based: when you first visit, we ask whether to enable it, and nothing is loaded or recorded until you accept. If you decline, no PostHog analytics or replay run and no related cookies are set.

Session replays are configured to mask all text and form inputs, so the words you type — including feedback content, email addresses, and other entries — are not captured in recordings. You can change your choice at any time using the “Cookie preferences” link in the site footer or the cookie control in the app. Your choice is remembered in a cookie shared across feedstick.app and its subdomains.

Cookies

The Service uses essential cookies required to keep you signed in, secure your session, and remember your cookie choice. With your consent (see above), we also set analytics cookies for PostHog product analytics and session replay. We do not use third-party advertising or cross-site tracking cookies on this site.

Data retention

We retain account and feedback data for as long as the related account is active or as needed to provide the Service. Customers can delete feedback items and may request deletion of their account data; we will delete or de-identify data within a reasonable period, subject to legal and operational requirements.

Security

We use industry-standard measures to protect data, including encryption in transit and write-only, rotatable ingest keys that limit what an exposed key can do. No method of transmission or storage is completely secure, but we work to protect your information and to respond promptly to issues.

Your rights

Depending on your location, you may have rights to access, correct, export, or delete personal data we hold about you, and to object to or restrict certain processing. End users who submitted feedback through a customer's application should contact that customer (the controller) first; we will support our customers in honoring such requests. To exercise rights with us directly, contact us using the details below. Account holders can request a copy of their data or deletion of their account by emailing support, and we will respond within a reasonable period.

International transfers

Our providers may process data in the United States and other countries. Where required, we rely on appropriate safeguards for cross-border transfers, such as the European Commission's Standard Contractual Clauses or equivalent mechanisms.

Children

The Service is not directed to children under 16, and we do not knowingly collect personal information from them.

Changes to this policy

We may update this Privacy Policy from time to time. When we do, we will revise the "Last updated" date above and, where appropriate, provide additional notice.

Contact

Questions about this policy or your data? Contact Colorblend Consulting LLC at support@clrblnd.co.