Overview
ClickUp is a project management and productivity platform primarily used as a standalone SaaS application. Its presence on external websites is limited to specific embedded components — task intake forms, project status portals, and document sharing widgets — that organizations deploy for customer-facing workflows. These embeds are less common than ClickUp's core application usage and typically appear on support portals, client project dashboards, and internal knowledge bases.
What This Script Does
When embedded on external websites, ClickUp loads scripts from app.clickup.com and associated CDN domains. The embedded components render within iframes or JavaScript widgets, displaying task submission forms, project board views, or shared document content. Cookies set by the integration include session identifiers for maintaining widget state and authentication tokens if the embed requires visitor sign-in. The clickup_session and related cookies typically persist for the browsing session. The scripts communicate with ClickUp's API to submit form data, retrieve project status information, or load shared documents. Minimal analytics data is collected on the host page — primarily widget load events and basic interaction metrics such as form submission counts.
Consent & Compliance
ClickUp embedded widgets are classified as functional. The embedded forms and project portals serve a direct operational purpose — enabling customers or team members to submit tasks, view project status, or access shared documentation. Under GDPR, the cookies required to operate these functional widgets may qualify under the strictly necessary exemption when the widget is integral to the service being provided (e.g., a customer support intake form). The ePrivacy Directive similarly exempts cookies that are essential for a service explicitly requested by the user. Under CCPA/CPRA, data submitted through ClickUp's embedded forms is collected for a disclosed business purpose and generally falls under standard business operation exemptions.
Should You Block This Without Consent?
No. ClickUp's embedded widgets serve operational purposes — task submission, project visibility, and document sharing — that are functionally necessary for the workflows they support. The cookies set are limited to session management and widget state. Blocking these widgets would prevent visitors from accessing the functionality the site owner has intentionally provided. If ClickUp introduces marketing or analytics tracking in its embeds, that assessment should be revisited.
Consent Categories
Also Known As
Industries
Tracked Domains (1)
clickup.comFunctionalFrequently Asked Questions
Do ClickUp embedded widgets require visitor consent?
No. ClickUp's embedded components — task intake forms, project status portals, and document sharing widgets — serve operational purposes explicitly chosen by the site owner and engaged with by visitors. Session cookies used for widget state are strictly necessary for functionality, qualifying for the consent exemption under GDPR and ePrivacy.
What does the ClickUp script do when embedded on a website?
ClickUp loads from app.clickup.com and renders task submission forms, project board views, or shared document widgets within iframes. It sets clickup_session and authentication tokens scoped to the browsing session. Scripts communicate with ClickUp's API to submit tasks, retrieve project status, and load shared documents on demand.
How does ConsentStack handle ClickUp on a website?
ConsentStack classifies ClickUp as functional and allows embedded widgets to load without consent. Session-scoped cookies are treated as strictly necessary for the operational workflows supported. ConsentStack does not block ClickUp, so task intake forms and project portals remain accessible to visitors without a consent barrier.
Related Vendors
Manage consent for ClickUp
ConsentStack automatically detects and manages ClickUp trackers so your site stays compliant with global privacy regulations.