Does airfocus require visitor consent to run?

No. airfocus portal scripts embed feedback submission forms and public roadmap widgets that visitors actively choose to engage with. No behavioral tracking or advertising profiling occurs, making consent unnecessary under GDPR and ePrivacy.

What data does the airfocus portal collect from visitors?

The portal collects only data visitors voluntarily submit — feature request text, optional name and email, and upvotes. Session cookies prevent duplicate votes within a session. No passive behavioral tracking or cross-site data collection takes place.

How does ConsentStack handle airfocus?

ConsentStack classifies airfocus as functional and does not block it by default. Because the portal operates on user-initiated interactions without passive tracking, it loads freely regardless of visitor consent choices.

What tracker domains does airfocus use?

ConsentStack has catalogued tracker domains for airfocus including airfocus.com. These are the network destinations airfocus's scripts contact, which a consent platform blocks until a visitor agrees.

airfocus (app.airfocus.com) - Product Feedback Portal Consent

Back to Vendor Library

Overview

airfocus is a modular product management and roadmapping platform used by product teams to prioritize features, manage backlogs, gather stakeholder feedback, and communicate product direction. The platform's core functionality operates as a SaaS application accessed by authenticated product team members. However, airfocus also offers a public-facing portal feature — the "airfocus Portal" — that allows teams to embed interactive widgets on their product websites to collect feature requests from users and display public roadmaps.

airfocus is headquartered in Hamburg, Germany (GDPR jurisdiction), and serves product teams at companies ranging from startups to enterprises.

What This Script Does

When the public portal feature is deployed, airfocus scripts embed interactive widgets on the product's website or help center:

Feature request submission: The portal widget provides a form through which website visitors can submit feature requests or ideas. The form typically collects the request text and may optionally collect the submitter's name and email address. Submitted ideas are sent to the airfocus workspace where product managers review and triage them.

Public roadmap display: The script renders a read-only or interactive view of the product's public roadmap — showing planned, in-progress, and released features across configurable status columns. Visitors can browse what is being worked on without submitting data themselves.

Voting on feature requests: If voting is enabled, the portal allows authenticated or anonymous visitors to upvote existing feature requests. Anonymous voting may use session cookies or local storage to prevent duplicate votes within a session. Authenticated voting requires an email address and may set a longer-lived identifier.

Portal session management: Session cookies or local storage entries maintain the state of the portal interaction — preserving the visitor's submitted requests, vote state, and any authenticated session if the portal requires login. These are functional identifiers scoped to the portal interaction.

Data transmission to airfocus: Feature request text, votes, and any provided contact information (name, email) are transmitted to airfocus's servers (app.airfocus.com or api.airfocus.com) for storage in the product team's workspace.

No behavioral analytics or advertising: airfocus portal scripts do not perform behavioral tracking beyond what is necessary to render and operate the portal widget. They do not deploy advertising pixels, retargeting tags, or cross-site tracking.

Consent & Compliance

airfocus portal scripts operate in a functional context with clear data handling:

GDPR / ePrivacy: The portal's core functionality — displaying a roadmap and collecting user-submitted feature requests — involves users actively providing information rather than passive behavioral tracking. Under GDPR, the lawful basis for processing submitted feature requests is legitimate interests (Article 6(1)(f)) or consent (Article 6(1)(a)) depending on the contact data collected. Session identifiers used for vote deduplication fall within the functional/strictly necessary category under ePrivacy. airfocus is an EU-based company (Hamburg), so GDPR compliance is built into the platform's design.
Contact data: If the portal collects email addresses from submitters, this constitutes personal data under GDPR. Implementers should disclose airfocus as a data processor in their privacy policy and ensure a DPA is in place with airfocus.
CCPA: If the portal is deployed on sites with California users, email addresses collected constitute personal information under CCPA and should be disclosed in the privacy policy.
No ePrivacy consent required for functional widgets: Interactive widgets that operate at the explicit request of users (submitting feedback, browsing a roadmap) do not trigger ePrivacy consent obligations provided they do not set persistent cross-site tracking cookies.

Should You Block This Without Consent?

No. airfocus portal widgets provide functional feedback collection and public roadmap display — features that users actively choose to engage with by submitting requests or browsing planned features. The data collected is intentionally provided by users, not passively observed. No behavioral tracking or advertising profiling is involved.

Is airfocus GDPR compliant?

airfocus typically loads functional trackers, which are not strictly necessary for your site to work. Under the GDPR and the ePrivacy Directive, non-essential cookies and trackers must stay blocked until a visitor gives clear opt-in consent. So airfocus can be fully GDPR compliant, but only if your site holds its scripts until consent is granted and lets visitors decline just as easily. Compliance depends on how your site loads airfocus, not on airfocus itself.

Visit website