Consent and Analytics

How MarkDocket handles cookie consent across the landing site and app subdomains, what analytics data is collected, and how to manage your preferences.

MarkDocket uses a first-party cookie to remember your consent choices and share them across its two web properties — the marketing and landing site (www.markdocket.com) and the app (app.markdocket.com) — so you are never prompted twice for the same decision.

When you visit either property, the consent system checks for an existing preference cookie scoped to .markdocket.com. Because the cookie domain covers all subdomains, a choice made on www.markdocket.com is visible to app.markdocket.com immediately — no separate banner appears when you sign in.

The current active policy version is cookies-2026-07-17. If the policy version changes in the future, you will be re-prompted on your next visit regardless of any previous choice.

Region detection

MarkDocket detects whether your region requires opt-in consent (for example, under GDPR). If you are in an opt-in region, analytics and non-essential tracking are fully disabled until you explicitly accept. If you are not in an opt-in region, analytics run by default but you can still opt out at any time.

Scope: .markdocket.com — shared across www. and app. subdomains.
Contents: Your preference (accepted or declined) and the policy version at the time you chose.
Duration: Persisted across sessions; re-evaluated when the policy version is updated.
Type: First-party only. No third-party consent cookies are set by MarkDocket.

On the landing site, the consent banner height is tracked in real time using a ResizeObserver. Floating UI controls automatically shift upward to stay above the banner as it appears or resizes (for example, on small screens where text wraps). The banner disappears as soon as you make a choice.

The StartWise partner iframe (/embed/startwise) operates in an isolated context. Global services — including the consent banner, analytics, and the billing-block dialog — are intentionally not mounted inside the embed. Consent management for embedded contexts is handled by the embedding application.

What analytics data is collected

MarkDocket uses PostHog for product analytics. The same PostHog project receives events from both the landing site and the app, giving a unified view of the user journey without stitching together separate systems.

Client-side events (browser)

When analytics are active, PostHog's browser library (posthog-js) captures:

Page views and navigation events.
Feature interactions (for example, opening a search, running an agent turn, viewing a draft).
UI-level error boundaries when an unexpected error is displayed.

Server-side events (API)

The API server (markdocket-api) also sends events to PostHog using the server-side library (posthog-node). Server-side capture provides:

Events for actions that complete asynchronously or in the background (for example, automation run completion, background draft research).
Error and exception tracking for server-side failures.

Server-side analytics are only active when the service is configured with a valid PostHog project key. If no key is present, all server-side capture is silently skipped — there is no fallback or alternative destination.

What is NOT collected

Payment card details or billing amounts — these flow through Stripe and are never sent to PostHog.
The content of agent messages, trademark search queries, or patent draft text.
IP addresses or precise geolocation beyond the region detection used for consent gating.
Any data from the StartWise embed context (analytics are fully suppressed there).

Managing your preferences

Accepting or declining on first visit

A consent banner appears on your first visit to www.markdocket.com or app.markdocket.com if you are in an opt-in region or if no existing preference cookie is found. Select Accept or Decline. Your choice is saved immediately and applied to both subdomains.

Changing your preference later

You can update your analytics preference at any time:

In the app, open Settings → Privacy.
Toggle analytics on or off.
Your updated preference is written back to the .markdocket.com consent cookie and takes effect immediately for both the app and the landing site.

On the landing site, use the privacy link in the site footer to re-open the consent panel.

Clearing your preference manually

If you clear your browser cookies for markdocket.com, your consent preference is removed. The next time you visit either subdomain, the banner will appear again.

Clearing cookies re-prompts on both subdomains

Because the preference is stored in a single shared cookie, clearing it means you will see the consent banner on whichever subdomain you visit next — even if you had previously accepted on the other.

Analytics and the partner embed

If you access MarkDocket through an embedded integration (such as the StartWise iframe), analytics, the consent banner, and related global services are completely excluded from that context at render time — they are never initialized, not merely hidden. Any analytics for your activity in that context are the responsibility of the embedding application.

Frequently asked questions

Does MarkDocket use third-party advertising cookies? No. MarkDocket does not place advertising or retargeting cookies. The only analytics tool in use is PostHog, operated as a product analytics service.

Does consent apply to the CLI or MCP integrations? The CLI and MCP server do not run in a browser and do not set cookies. Server-side analytics events from CLI-initiated actions may still be captured via posthog-node on the API server, subject to the same server-key availability requirement described above.

What happens if I decline analytics? MarkDocket's core features — trademark and patent search, agent chat, draft workflows, portfolio management, billing — function identically whether you accept or decline analytics. No feature is gated on analytics consent.

Will I be re-prompted if MarkDocket updates its cookie policy? Yes. When the policy version changes, the consent system detects that your stored preference was recorded under an older version and presents the banner again on your next visit.

On this page