Privacy
Harku is anonymous-first. Voting and suggesting need no account and collect no personal data.
For people who vote and suggest
You don't sign in to use a Harku widget, and we don't ask for your name, email, or any personal detail. To stop the same browser from voting twice, the widget generates a random id and keeps it in your browser's local storage. That id isn't linked to your identity — it only deduplicates votes.
When you post a suggestion, we store the text you write — a title and an optional description — and your vote records. That's all.
Our application code does not log or store IP addresses or any other personal identifiers for end users.
What the widget keeps in your browser
The widget stores a few small values in local storage, each scoped to the site you're on:
harku_voter_id— the random, anonymous id used to deduplicate votes.harku_voted_*— which suggestions you've upvoted, so the button shows the right state.harku:cl-seen:*— the last changelog entry you've seen, for the unread badge.harku_config_*— a cached copy of the widget's appearance, so it loads without a flash.
Clearing your browser storage removes all of these.
For site owners
If you run a Harku project, you sign in with an email and password (handled by our authentication provider). We store your email, your projects, the suggestions and roadmap items in them, and your changelog entries. Your dashboard data is protected by row-level security — only you can see and manage your own projects.
How data flows
The widget never reads from or writes to our database directly. Everything goes through a public API that validates your project's public key and only allows safe operations. The one direct connection the widget makes is a read-only, notifications-only channel that keeps the open panel live — it carries no personal data.
Questions
This page describes Harku v1. A full, formal privacy policy ships alongside the public launch. Until then, if you have a question about data, get in touch.