Overview
Aha! is a product management platform for strategy, roadmapping, idea management, and feature prioritization. Beyond its internal planning suite, Aha! offers embeddable public-facing portals that allow companies to publish product roadmaps, run idea voting boards, and collect feature requests directly on their websites. These public portals are the browser-side presence relevant to consent management — they load Aha! scripts on the host website to render interactive product feedback interfaces for external visitors.
What This Script Does
When Aha! portal scripts are embedded on a website, they load from Aha!'s CDN (typically secure.aha.io or a custom subdomain configured by the organization) and render interactive product feedback interfaces:
Public roadmap portals:
- Fetches and renders a visual roadmap timeline showing planned, in-progress, and completed features in configurable time formats (now/next/later, quarterly, Gantt-style)
- Dynamically loads feature cards with status indicators, estimated timelines, and optional descriptions
- Sets a session cookie for portal navigation state (current view, active filters) that expires at session end
Idea boards and voting:
- Renders a searchable list of submitted ideas/feature requests with upvote counts and status labels
- Loads the idea submission form when a visitor clicks "Submit Idea" — form fields collect idea title, description, and optionally the submitter's name and email address
- Manages vote state: when a visitor votes on an idea, Aha! stores their vote using a cookie or
localStorageentry keyed to the portal, preventing duplicate votes - The vote-tracking identifier (typically
_aha_portal_[portal_id], first-party, 30-day expiry) is the primary persistent identifier set by Aha! portals
Network requests and data flow:
- Portal content is fetched via authenticated API calls from the browser to
secure.aha.io - Form submissions (ideas, votes) POST data directly to Aha!'s servers
- No behavioral tracking, analytics collection, or advertising-related processing occurs
What Aha! portals do not do:
- Do not set cross-site tracking cookies
- Do not load advertising pixels or analytics trackers
- Do not collect passive behavioral data (scroll depth, click tracking outside portal interactions)
- Do not share data with third-party advertising platforms
Consent & Compliance
- Category: Functional
- GDPR: Aha! portal scripts serve a clearly functional purpose — delivering a product feedback and roadmap experience that visitors actively choose to use. The vote-tracking cookie prevents duplicate votes and is necessary for the service to function correctly. Form submissions collect personal data (name, email) based on explicit, voluntary user action — this requires a lawful basis (legitimate interest or contract performance) and appropriate privacy notice disclosure. Aha! acts as a data processor for portal content and submissions.
- ePrivacy: The
_aha_portal_[portal_id]cookie is used solely to maintain voting state for the service the visitor requested. This falls within the exemption for cookies strictly necessary for a service explicitly requested by the user. No advertising or cross-site tracking cookies are involved. - CCPA: Email addresses and names submitted through idea forms are personal information. Disclose Aha!'s use in your privacy policy. Aha! is a US company — EU transfers use Standard Contractual Clauses.
- Data minimization: Aha! portals collect only data explicitly submitted by visitors. No passive collection occurs beyond session state management.
Should You Block This Without Consent?
No. Aha!'s embedded portal scripts deliver functional product feedback features. Data collection is limited to explicit user submissions and necessary session state. They do not perform behavioral tracking, advertising profiling, or cross-site data sharing. Aha! portals can operate under a functional basis without requiring prior visitor consent.
Consent Categories
Also Known As
Industries
Tracked Domains (1)
aha.ioFunctionalFrequently Asked Questions
Does embedding an Aha! portal on my site require visitor consent?
Generally no. Aha! portals deliver functional product feedback features — roadmap timelines and idea voting — that visitors actively choose to use. The vote-tracking cookie prevents duplicate votes and is necessary for the service, qualifying as strictly necessary under ePrivacy rules.
What data does an embedded Aha! portal collect?
Aha! portals set a session cookie for navigation state and a persistent vote-tracking cookie (30-day expiry) to prevent duplicate votes. If a visitor submits an idea, the form collects their name and email address voluntarily. No behavioral tracking or advertising data is collected.
How does ConsentStack categorize Aha! portals?
ConsentStack classifies Aha! as a functional vendor. Embedded portal scripts deliver a service visitors explicitly request and do not perform behavioral tracking or advertising. ConsentStack does not require you to gate Aha! behind a consent prompt for standard portal implementations.
Related Vendors
Manage consent for Aha!
ConsentStack automatically detects and manages Aha! trackers so your site stays compliant with global privacy regulations.