Why we built an anonymous feedback tool, and what "anonymous to us" actually means.
Most in-app feedback tools ask you to identify the person answering before you've even asked your question. For B2B products that means a DPA, a consent banner, and a legal review before the first survey ever ships. Insightdive exists to skip that step entirely: no user identifiers ever leave the device, so there's nothing to review and nothing to protect.
The product started as the feedback layer for Devolutions' own B2B tools (RDM, DVLS, Hub) — over 1M end-users across the product line — before becoming a standalone SDK for other product teams who hate building feedback tooling from scratch.
The SDK never sends a user ID, email address, IP address, device fingerprint, advertising identifier, or cookie. Only a project slug, your app's version string, locale, theme, an opaque session id, and the survey answers themselves ever leave the device. Operators can optionally stamp non-identifying context (plan tier, feature flags) or pass an opaque hash for their own cross-referencing — but Insightdive never stores enough to identify a respondent. See the privacy policy for the full technical breakdown.
Data lives in encrypted PostgreSQL in Montréal, Canada, behind Cloudflare. The anonymous-by-default design means SDK survey data falls outside GDPR's scope of personal data and Quebec's Law 25 — no DPA required, no consent banner needed for the survey itself. Full details are in the legal & privacy page.
Questions about the product, pricing, or how the anonymous design works: info@insightdive.com