Kaldwick legal

Cookie Notice

This notice explains how Kaldwick uses cookies and similar technologies across the app, public quote forms, and launch workflows.

Last updated: September 19, 2026

Kaldwick does not require advertising pixels to operate. If a workspace later adds third-party ad pixels or external analytics to its funnel, the workspace should update notices and consent behavior before sending paid traffic.

1. Technologies we use

Kaldwick may use cookies, local storage, session storage, server logs, and similar technologies to operate the service, authenticate users, protect sessions, understand quote-form performance, and troubleshoot errors.

2. Categories

  • Strictly necessary technologies: used for login, session continuity, routing, security, and webhook-safe operations.
  • Functional technologies: used to remember preferences, workspace context, onboarding state, and form progress where applicable.
  • Analytics technologies: used to measure form views, steps, abandonment, submission rates, and launch readiness.
  • Marketing technologies: not required by default, but may be added later by a customer or deployment configuration.

Kaldwick sets a first-party cookie named kw_ft, stored for up to 90 days, that records the first page, referrer, and any tagged campaign source and medium of your first visit. Kaldwick uses it only to understand which page led to a new account, a published quote link, a Founding application, or a tracker download. It is not shared with third parties.

On commercial pages, Kaldwick may also set a first-party, HttpOnly cookie named kw_aid for up to 30 days. It contains only a random identifier used to connect an acquisition page view to a later signup. It does not contain contact details, homeowner information, or a device fingerprint, and it is not shared with third parties.

3. Public quote forms

Public Kaldwick quote forms capture attribution context such as UTM parameters, referrer, landing page, step progress, and abandonment events. This helps contractors understand which campaigns produce usable job requests and where a form creates friction.

4. Choices

Browser settings may allow users to block or delete cookies. Blocking necessary technologies may prevent login, dashboard use, or reliable form submission. Customers running paid traffic should review their own tracking stack and privacy obligations before launch.

Request follow-up

Keep the owner, last action, and next action visible.

Start building