Privacy policy

Who this covers

Two kinds of people use Murmur:

• Teams who create a workspace to collect feedback about their product. For their customers' data, the team decides what is collected and why, and Murmur processes it on the team's behalf.
• Customers of those teams who post, vote or comment on a feedback portal or widget, or whose feedback a team captures from email, chat, reviews or surveys.

What we collect

• Account details: your name, email address and a hashed password (or the identity a team's app passes to the widget).
• Feedback content: ideas, votes, comments and the text of emails, messages, reviews and survey answers that a team sends to Murmur, with the source link and the customer's name, email and company where the team provides them.
• Workspace settings and connections: boards, roadmap, changelog, and the keys or tokens a team adds to connect sources such as Slack, Discord, PostHog, G2 or App Store Connect. Those keys are encrypted before they are stored.
• Usage records: the actions taken in a workspace (an audit log) and counts used for plan limits, such as AI captures per month.
• Billing: handled by our payment provider. We keep your plan and subscription status, never your card number.

We do not sell personal data and we do not use it for advertising. The Murmur website and app do not run third-party advertising or tracking scripts.

The Murmur Chrome extension

The extension lets a team member send text they highlight on a web page to their own Murmur workspace.

• It reads the page only when you use it: when you right-click selected text and choose Send to Murmur, or open the extension. It then reads the selected text, the page address and the page title.
• That information, plus any customer name, email or company you type in, is sent to your Murmur workspace only when you press Send. Nothing is sent in the background.
• Your connection code (which includes an API key for your workspace) is kept in Chrome's local extension storage on your device. Disconnecting removes it.
• The extension does not collect browsing history, does not track you across sites, and does not send data to anyone other than your Murmur workspace.

How we use it

• To run the service: show boards and roadmaps, rank ideas, send the emails a team turns on (for example, telling voters an idea shipped), and enforce plan limits.
• To run Autopilot: feedback text is sent to an AI model to find the requests in it and suggest matching ideas. If a team turns on Fix with Claude or AI visibility, the relevant text is sent to the AI providers listed below.
• To keep accounts secure, prevent abuse and answer support requests.

Who processes it for us

• Cloudflare: hosting, database and inbound email routing.
• Resend: sending email.
• Anthropic: AI processing for Autopilot, summaries, replies and Fix with Claude.
• OpenAI: only for workspaces that turn on AI visibility, to ask ChatGPT about the product.
• Polar: payments and subscriptions.

Services a team chooses to connect (Slack, Discord, GitHub, PostHog, G2, App Store Connect, Product Hunt and others) receive or send data under that team's own account with them.

How long we keep it

We keep workspace data while the workspace exists. When a team asks us to delete its workspace, its ideas, comments, votes, captured feedback and connections are deleted with it. Deleting your account removes your profile and the comments and votes tied to it. To delete a workspace or account, email us from the address on the account.

Your choices

• Ask for a copy of your data, a correction or deletion by emailing hello@murmurfeedback.com. If your data is in a team's workspace, we may pass your request to that team, since they control it.
• Unsubscribe from any Murmur email with the link in its footer.
• Disconnect the Chrome extension or any connected source at any time.

Changes

If we change this policy in a way that matters, we will update the date above and tell workspace owners by email.