HoneyBook

Overview

HoneyBook is a client management and business operations platform used by independent service providers and creative businesses — photographers, event planners, graphic designers, consultants, and similar freelancers. The platform consolidates project proposals, service agreements, payment collection, invoicing, and appointment scheduling into a single client workflow system. Businesses embed HoneyBook-powered forms and booking interfaces directly on their websites to capture new client inquiries and guide them through the intake process without leaving the host site.

HoneyBook is distinct from general-purpose form tools in that it manages the full client lifecycle: from first inquiry through signed contract to final payment, with automated follow-up emails and workflow triggers built into the platform. Clients interact with HoneyBook through an iframe-embedded interface that renders the merchant's branded proposal and contract documents.

What This Script Does

Script loading and iframe embedding: HoneyBook injects a JavaScript snippet (typically loaded from www.honeybook.com/widget/honeybook_widget.js or via a Squarespace/WordPress plugin) that renders an iframe pointing to a HoneyBook-hosted URL. The iframe contains the full client-facing interface — contact forms, service selection, contract terms, and e-signature capture — all hosted on HoneyBook's domain.

Data collected through the widget:

• Client contact information: full name, email address, phone number
• Project details: event date, service type, location, budget range, custom form questions
• E-signature data: typed name or drawn signature, timestamp, IP address (for legal enforceability)
• Payment information: credit card or ACH details entered within the payment iframe (processed through Stripe; HoneyBook does not store raw card data)

Cookies and storage:

• Session cookies on honeybook.com domain — Set within the iframe context, session duration, maintain form progress state and multi-step flow position during contract review and signing
• No persistent tracking cookies on the host domain — HoneyBook does not set first-party cookies or localStorage entries on the embedding site's domain
• No advertising pixels, remarketing tags, or behavioral tracking are included in the widget

Network requests: Form submissions and signature events are sent to api.honeybook.com. Payment processing flows through Stripe's secure payment infrastructure. No data is shared with advertising networks.

HoneyBook mobile app: Separate from the website widget, HoneyBook operates a mobile app for business owners to manage their pipeline. This is unrelated to the website consent context.

Consent & Compliance

HoneyBook is categorized as functional.

• GDPR/ePrivacy: HoneyBook's iframe widget delivers a user-initiated service — a booking or inquiry form that the visitor has deliberately chosen to fill out. The session cookies within the iframe are strictly necessary to maintain form state during the interaction. No consent is required for these functional cookies under the strictly necessary exemption. The personal data submitted through the form (name, email, contract details) is processed on behalf of the business owner; the business owner bears primary GDPR responsibility as data controller.
• CCPA/CPRA: Data collected through the HoneyBook form is voluntarily provided by the consumer to complete a requested transaction. HoneyBook operates as a service provider to the business owner. The business owner's privacy policy should disclose HoneyBook as a service provider.
• Data transfers: HoneyBook is a US-based company. EU-based businesses using HoneyBook should ensure appropriate data transfer mechanisms are in place, including reviewing HoneyBook's DPA availability.
• E-signature compliance: HoneyBook's e-signature functionality is designed to comply with the US ESIGN Act and UETA. European contract enforceability depends on the applicable national law.

Should You Block This Without Consent?

No. HoneyBook scripts and iframe widgets deliver a functional client intake service directly tied to actions the visitor has chosen to take. No behavioral tracking, advertising, or cross-site data collection is performed. Blocking HoneyBook would prevent visitors from submitting inquiries, signing contracts, or making payments through the embedded interface.