Privacy Policy

Coohoo is an independent product operated by an individual developer based in Ukraine (“Coohoo”, “we”, “us”). It consists of the website at coohoo.app, the dashboard, and an embeddable visual-feedback widget. For any privacy question or request, contact hello@coohoo.app.

For your Coohoo account (your profile, project settings, billing and support requests) we are the data controller.

For feedback collected through the widget on your site, you — the site owner who installed it — are the data controller, and Coohoo acts as a processor handling that data on your behalf. You are responsible for having a lawful basis to collect it and for telling your reviewers that their feedback is collected and visible to you.

Feedback data (via the widget): the name a reviewer types on a comment, the comment or reply text, the URL of the page it was left on, and basic environment metadata (browser, operating system, and screen size). We also store the selected element’s selector, a short text snippet, pin position, comment status and, when the site provides it, a source-file path. No account or login is required to leave feedback. The widget is designed to stay hidden on production domains according to the project configuration. Site owners are responsible for setting the correct staging and production domains.

Account and collaboration data: your email address (for magic-link or Google sign-in), profile name and avatar, projects and settings, team memberships, and subscription identifiers and status. If an owner invites you by email, we process your email address to deliver the invitation. Team members can see other members’ names, emails, avatars and roles.

Contact messages: when you contact us through the website or app, we process your name, email, message and whether it came from the website or app to respond and provide support. Messages are delivered to our support inbox.

Agent access: we store token names, a token hash and prefix, creation, last-use and revocation timestamps. The raw token is shown once. Replies posted through MCP are marked as coming via an agent.

Technical data: we process IP addresses to rate-limit and prevent abuse of the public write endpoints. IP addresses are not stored alongside comments.

The dashboard uses essential authentication storage to keep you signed in. We use no advertising cookies and no cross-site tracking, and the widget sets no cookies at all.

Product analytics & error tracking: on the website and in the dashboard we use PostHog (EU region) to understand usage and catch errors. It is configured cookie-free — it stores an anonymous identifier in your browser’s local storage (not a cookie), and for signed-in users we associate events with your account email and profile name. It may also capture the URL and stack trace of an error to help us fix it. PostHog is not present in the embeddable widget.

The widget stores a small identifier in the host page’s local storage to remember a reviewer’s display name, edit permissions, read comments and widget preferences. Member review permissions may also be stored locally. It is not used to track people across sites.

Under the GDPR (where it applies), we rely on:

• Performance of a contract — to provide the dashboard and widget, manage team access and billing, send sign-in and invitation emails, and respond to requests related to your use of the service.
• Legitimate interests — to keep the service secure, prevent abuse of public endpoints, and understand product usage and diagnose errors (cookie-free analytics), and respond to general inquiries.

We never sell your data or use it for advertising.

We share data only with the providers needed to run Coohoo, each acting under its own terms. As of the effective date these are:

• Convex — backend and database hosting (comments, replies, projects, accounts).
• Cloudflare — dashboard hosting, widget CDN, and DNS.
• Resend — sending sign-in and invitation emails and delivering contact-form messages.
• PostHog (EU region) — product analytics and error tracking on the website and in the dashboard (not in the widget).
• Paddle (Paddle.com Market Ltd, UK): payment processing and billing for Pro subscriptions. We never see or store your card details.
• Google — optional OAuth sign-in, if you choose it.

Feedback is visible to reviewers with access to the widget or a shared review link, as well as the project owner and team members. Review links are intended to be shared; do not treat the widget as a place to store confidential information. Invitation links allow signed-in recipients to join a project. Keep member review links and agent tokens private because they grant additional permissions.

Copying feedback exports comment text, author names, replies, page and element details, environment metadata and available source-file paths. If you paste it into another service or connect an MCP client, that client and its provider can receive the feedback you make available. MCP access follows the token owner’s project memberships and supports reading, replying, resolving and reopening. Those external services process received data under their own terms and privacy policies. Revoking a token stops future access; it does not delete copies already received by another service.

We operate from Ukraine, and our infrastructure providers may process data in the European Union and the United States. Where personal data is transferred across borders, those providers rely on appropriate safeguards (such as the European Commission’s standard contractual clauses) within their own agreements.

Feedback is kept until the project owner deletes it. Deleting a comment removes its replies; deleting a project removes its comments, replies, and memberships. Archiving a project does not delete its feedback. Account data is kept while your account exists. Support correspondence is retained for as long as needed to handle the inquiry and related follow-up or legal obligations. Token records include revocation history; revocation disables access rather than deleting that history.

Data is transmitted over HTTPS. Dashboard and MCP access are checked against project membership; widget and shared-link access work as described above. No method of transmission or storage is completely secure, but we take reasonable measures to protect your data.

Depending on where you live (including under the GDPR, UK GDPR, and CCPA), you may have the right to access, correct, delete, restrict, export, or object to our processing of your personal data, and to withdraw consent. To exercise any of these, email hello@coohoo.app. For feedback left through the widget on someone else’s site, that site owner is the controller — contact them, and we will help them respond. If you are in the EU or UK, you also have the right to complain to your local data-protection supervisory authority.

Coohoo is not directed to children under 16 and is not intended for collecting feedback from them. Please don’t use it to do so.

We may update this policy; the “last updated” date above always reflects the current version, and we’ll flag material changes by reasonable means.

Questions or requests? Email hello@coohoo.app.