Front

Front

Front is a collaborative inbox platform that manages shared email, chat, and messaging channels for customer-facing teams. Scripts may embed chat or messaging widgets on websites that route inquiries into shared Front inboxes. Conversations are assigned, commented on, and tracked within the Front workspace.

Overview

Front is a collaborative inbox platform that centralises customer communications from multiple channels — email, SMS, live chat, social media direct messages, and WhatsApp — into a shared team workspace. Rather than individual inboxes, Front routes incoming messages into shared queues where agents can assign, comment on, collaborate over, and respond to customer conversations. It is used by customer support, success, and sales teams as a primary customer communication hub. When deployed with a live chat widget on a website, Front's script loads a messaging component that allows website visitors to initiate conversations routed directly into the team's Front workspace.

Front is headquartered in San Francisco and holds EU-US Data Privacy Framework certification and SOC 2 Type II compliance.

What This Script Does

Front's website presence manifests as a live chat or messaging widget embedded on company websites to enable visitor-to-team communication.

Scripts loaded: Front's chat widget loads from cdn2.frontapp.com or chat.frontapp.com, injecting the chat launcher button and conversation interface into the host page.

Cookies set:

  • front_chat_session — First-party session cookie on the host domain (or third-party on frontapp.com depending on embed configuration). Maintains the active conversation session so the chat does not reset if the visitor navigates between pages during the same session. Expiry: session.
  • front_visitor_id — First-party persistent cookie. Stores a pseudonymous visitor identifier used to reconnect returning visitors to their previous conversation thread, providing conversation continuity across visits. Expiry: 1 year.
  • localStorage tokens: Front's widget may also use browser localStorage to persist conversation state client-side, reducing reliance on cookies for session continuity.

Data collected:

  • Visitor messages and agent responses (stored in Front's platform as the conversation record)
  • Current page URL at the time the chat is initiated (provided as context to the responding agent)
  • Browser type and operating system (displayed as metadata in the Front conversation view)
  • IP address (for geolocation context shown to agents)
  • If the visitor provides their name or email during the chat, this is stored in the conversation record within Front

No advertising or analytics tracking: Front does not deploy retargeting pixels, analytics beacons, or audience profiling scripts on the host website. Data collection is limited to what is necessary for the chat conversation service.

Consent & Compliance

Consent category: Functional

Front's live chat widget delivers a direct communication service — enabling visitors to contact the company's support or sales team. The cookies it sets serve conversation session management and continuity purposes.

Under GDPR and ePrivacy, a live chat widget initiated by the visitor is a functional service. Session cookies required for the chat to work across page navigations are likely to qualify as strictly necessary under the ePrivacy Directive. However, the persistent front_visitor_id cookie (1-year expiry) that tracks returning visitors across sessions goes beyond strict session necessity. Depending on jurisdiction and DPA guidance, this persistent identification cookie may require consent or disclosure as a functional cookie.

Under CCPA/CPRA, Front processes conversation data (messages, contact details voluntarily provided) as a service provider on behalf of the site operator. Front's DPA covers this processing relationship.

Front holds EU-US Data Privacy Framework certification and SOC 2 Type II compliance. A Data Processing Agreement is available for GDPR compliance.

Should You Block This Without Consent?

No. Front provides functional customer communication capabilities through a live chat widget. Session cookies are strictly necessary for the messaging service. The persistent visitor identifier cookie enables conversation continuity across return visits — a functional feature that may warrant disclosure in a cookie notice but does not require blocking. Blocking Front removes visitors' ability to contact your team through the chat interface.

Visit website

Consent Categories

Functional

Also Known As

Front appFront inboxshared inbox toolcustomer messaging platformFront chat widget

Industries

Computers Electronics and TechnologyProgramming and Developer SoftwareBusiness and Consumer ServicesHeavy Industry and Engineering

Tracked Domains (1)

chat-assets.frontapp.comFunctional

Frequently Asked Questions

Does Front's chat widget require visitor consent?

Front's live chat widget is a functional communication service. Session cookies are strictly necessary for chat continuity across page navigation. The persistent front_visitor_id cookie enabling cross-visit conversation continuity may warrant disclosure depending on applicable DPA guidance.

What data does Front's chat widget collect?

The chat widget collects visitor messages, the page URL at conversation start, browser and OS metadata, and IP address for agent context. If the visitor provides name or email, these are stored in the conversation record within the Front workspace.

How does ConsentStack categorize Front?

ConsentStack categorizes Front as functional, allowing the chat widget to load without a consent gate. The persistent visitor ID cookie is disclosed in the cookie notice, and ConsentStack can suppress it for visitors in stricter jurisdictions if required.

Related Vendors

Google Maps
Google Maps
Google Maps is the dominant web mapping service used for embedded maps and location features on websites. Scripts load interactive map tiles, geocoding, and Places API functionality through the Maps JavaScript API. May set cookies to remember map preferences and manage API quota.
Google Search
Google Search
Google Search appears on websites through the Programmable Search Engine, enabling custom site-specific search functionality. Scripts load the search widget from Google's servers to render search bars and display results within the host website. Sends search queries to Google's index and may set cookies for search personalization and query history.
Google
Google
Google is the dominant provider of web analytics, advertising, and infrastructure tools. Scripts like Google Analytics, Tag Manager, Ads, and reCAPTCHA collect behavioral data, manage tag firing, serve targeted ads, and detect bots. Sets persistent cookies to track users and correlate activity across sites.
Microsoft Teams
Microsoft Teams
Microsoft Teams is a workplace communication and collaboration platform that can be embedded on websites for chat, meetings, and document sharing. Embedded widgets load from Microsoft's servers to enable real-time messaging, video calls, and file collaboration. Sets authentication and session cookies to verify participant identity and maintain connection state.
Apple Maps JS
Apple Maps JS
Apple Maps JS is Apple's JavaScript mapping framework for embedding interactive maps on websites. Scripts load map tiles, location pins, and routing data from Apple's MapKit servers to render navigable maps within web pages. Requires a MapKit JS token for authentication but does not set tracking cookies or collect behavioral analytics data.
Apple Business Chat
Apple Business Chat
Apple Business Chat enables direct customer messaging between websites and Apple's Messages app. Scripts load chat buttons and conversation interfaces that connect visitors to business support agents through iMessage. Sets minimal session cookies to maintain conversation context but does not track browsing behavior or collect analytics data.

Manage consent for Front

ConsentStack automatically detects and manages Front trackers so your site stays compliant with global privacy regulations.