Private previewWorkspaces are by invitation

HeedPost

01Collect

Feedback boardsBoards that ask for exactly what your team needs to act.Votes, comments & mentionsOne vote per person, threads with mentions, and notes only your team sees.In-app widgetFeedback from inside your product, from customers who are already signed in.

02Understand

Merge & duplicatesTen posts asking for the same thing become one, with every vote kept.User segments & revenueProSee which requests your biggest customers want, in dollars.InsightsWho reads, what's rising, and whether you answered.HeedPost AIPlus and ProTags, duplicate judging, drafts, summaries, themes and Ask, each with its own switch.

03Ship and tell

Roadmap & statusesMove a post and everyone who asked hears, in your own status words.ChangelogRelease notes linked to the requests behind them, mailed to everyone who asked.Notifications & digestThe right email to the right person, and a switch for every one.

04Run it

Activity logEvery change, who made it and when, a day at a time.Team, roles & sign-inUnlimited teammates, clear roles, and sign-in your way.Branding, domain & languagesYour logo and colour, your own domain, and 21 languages.ImportMove in from Canny, Featurebase or UserJot, with nobody emailed.

05Connect

Slack & issue trackersPlus and ProSlack threads, and issues in Linear, Jira, GitHub or ClickUp that move posts back.MCP serverPlus and ProYour AI agent can read, file, vote and ship, as you.REST APIPlus and Pro27 operations and one key: build anything on top of your feedback.WebhooksPlus and Pro110 events, signed and retried, the moment they happen.
AIDocsHelpPricingBlog

Collect

Understand

Ship and tell

Run it

Connect

Request an inviteSign in

Privacy Policy

What HeedPost collects, who processes it, and how to have it deleted.

Last updated 18 October 2026Zanaf Labs LLC, which makes HeedPost

This covers the website, the product, and every board somebody runs with it. HeedPost sells no data, rents none, and shares none for anybody's marketing.

01Who is responsible

Zanaf Labs LLC, which makes HeedPost, decides how the data described here is handled, except for the feedback content inside a workspace: there the workspace customer decides what to collect, which boards are public, and who may read or publish, and we act on their instructions. Address: 117 S Lexington Street, Ste 100, Harrisonville, MO 64701, United States. Contact: [email protected].

02What HeedPost collects

Your account, the settings of any workspace you run, the feedback people post into it, and the ordinary technical details every web request carries. Nothing is bought from a data broker and nothing is used to follow you around other websites.

AccountName, email address, role in each workspace, and how you signed in.
Feedback contentPosts, comments, votes, reactions and any files attached to them.
UsageDevice and browser, request logs, and an approximate location from the IP address.

03Cookies and analytics

Two cookies, and neither is for advertising: one keeps you signed in, one protects forms against cross-site requests. Analytics is privacy-preserving, sets no cookie of its own and builds no per-visitor profile, so there is no consent banner because there is nothing to consent to. Some pages carry a bot check on the forms where anybody may post or ask for a sign-in link, and the network that delivers the site may set its own bot-management cookie as part of that. There is no advertising tag and no cross-site tracking anywhere in this product. The checkout page also runs Paddle's own scripts, which may set cookies of their own there; they are described under Purchases.

04Workspace content and end users

A workspace customer runs their own feedback programme. What appears on a public board, who is invited, and how posts are moderated are theirs to decide, and we hold that content for them. One thing is ours and is worth stating: vote counts are public and voters are never listed publicly: who voted is shown only to the workspace's own team.

If you posted on somebody's board and want something changed or removed, ask that workspace first. Write to us if they do not answer and we will help.

05Purchases

Paddle.com Market Ltd acts as merchant of record and processes all payments. Paddle collects and handles your payment details directly. Card and bank details are never sent to, seen by, or stored by HeedPost, and we have no ability to charge your card ourselves. Paddle also calculates and remits sales tax and VAT and issues your invoice, under its own privacy notice.

From Paddle we receive and store the order record: the name and email address used at checkout, your country and the tax treatment applied, the plan bought, the amount, the currency and the transaction reference. It is used to run your subscription, answer questions about it, process refunds, and keep the accounting records the law requires.

The checkout page loads Paddle's own scripts to take the payment, including Paddle Retain, which Paddle uses to help with failed payments and cancellations. They run on that page only, not on any board or workspace page, and may keep their own identifiers in your browser there, under Paddle's privacy notice.

06Why this is lawful

Where data-protection law of the kind found in the UK and EU applies, we rely on: performance of a contract for accounts, subscriptions and support; legal obligation for tax and accounting records; and legitimate interests for answering correspondence and for keeping the service secure. No processing here relies on consent. One step is automatic: where a workspace turns it on, a language model reads a new post or comment before it appears, and one it calls spam waits for a person on that workspace's team, who publishes or removes it. The model never removes anything and never decides alone, and the author sees their post while it waits. None of this is profiling.

07Who else sees your data

We do not sell your data, do not rent it, and do not share it for anyone's marketing. It is disclosed only to the companies that make the service work (Paddle for payment and tax, the provider that carries our email, our hosting and content network, the object storage that holds uploaded files, and the provider that runs our language models, for spam checks, summaries, drafted replies and the other AI features a workspace turns on, on the feedback that workspace collects) and to any authority where disclosure is legally required. What a model writes is kept apart and reaches nobody until a person on the team applies it, with one exception: on a workspace with translation for readers on, a post, a comment or a changelog entry is shown to a reader translated into their language, marked as translated, with the original one press away. A workspace's admins can turn translation off. Write to [email protected] for the current list.

08International transfers

HeedPost and its suppliers operate internationally, so data covered by this policy may be processed outside your own country, including outside the UK and the European Economic Area. Where the law requires a safeguard for such a transfer, we rely on the mechanisms offered by the supplier concerned, such as the standard contractual clauses in its data processing terms.

09How long things are kept

Workspace content is kept while the workspace exists, and deleting the workspace deletes it. Deleting an account is scheduled thirty days ahead and can be cancelled by signing in during that window; after it runs, the account is anonymised and its memberships are removed. Order and invoice records are kept for seven years, to satisfy tax and accounting requirements. Support and sales email is kept for up to three years from the last message.

Access is scoped per workspace in the database itself rather than only in the application, and connections are encrypted in transit. No service can promise to be perfectly secure, and this one does not.

10Your rights

Most of this you can do yourself and immediately: change your name and email in your account, take any board away as CSV, switch off a category of email from a workspace, unsubscribe from all of it in one click from the foot of any message, or schedule the deletion of your account.

Beyond that, and subject to the law that applies to you, you can ask for a copy of the data held about you, ask for it to be corrected or deleted, ask for processing to be restricted, object to processing based on legitimate interests, or ask for your data in a portable format.

11How to request deletion

Email [email protected] with Data request in the subject line, saying what you want done. Include the email address we hold for you, and the Paddle order reference if your request concerns a payment. This is how the request is matched to a record, and a request that cannot be matched cannot be actioned.

Requests are acknowledged within 7 days and completed within 30. If one is complex you will be told before that deadline and given a date. There is no charge.

One limit worth stating plainly: invoice and transaction records cannot be deleted on request while the law still requires them to be kept. Everything not caught by that requirement is deleted. Deleting payment data held by Paddle is a request you make to Paddle, and we will point you to the right place if you ask.

12Children and changes

Nothing here is directed at children, and we do not knowingly collect data from anyone under 16. If you believe a child has sent us personal data, email and it will be deleted.

If this policy changes, the date at the top of the page changes with it, and a change that materially affects how your data is handled will be announced by email to customers on record.