Comply DP

Cookie Policy

Last updated: July 13, 2026

This Cookie Policy explains how Nihonium Labs Private Limited (“ComplyDP”, “we”, “us”) uses cookies and similar technologies on https://www.complydp.com.


1) What are cookies?

Cookies are small text files stored on your device. We also use localStorage, pixels, and SDK identifiers. These support security, product features, analytics, and campaign measurement.

2) Why we use cookies

  • Strictly necessary: Clerk authentication and session security; LinkedIn Insight Tag; Google Ads conversion measurement; PostHog usage and error monitoring; Vercel Web Vitals (cookieless); Apollo.io website visitor identification.
  • Functional: Dashboard state, expert chat, Calendly in-page booking, and consent preferences in browser storage.
  • Analytics: None currently (see Strictly necessary).
  • Marketing: None currently (see Strictly necessary).

3) Your choices

Use the footer link Cookie Settings to accept, reject, or customise categories. Choices are saved in localStorage under cookie-preferences. Withdrawing consent is as easy as giving it under the DPDP Act.

4) Cookie & storage inventory

Technologies deployed on www.complydp.com as of July 13, 2026. Third-party cookies are set when their scripts load.

Strictly necessary cookies

Clerk authentication and session security; LinkedIn Insight Tag; Google Ads conversion measurement; PostHog usage and error monitoring; Vercel Web Vitals (cookieless); Apollo.io website visitor identification.

NameProviderPurposeDuration
__clientClerk (authentication)Identifies the browser/client for sign-in and session security.1 year
__client_uatClerk (authentication)Records client activity timestamp for session freshness.1 year
__sessionClerk (authentication)HttpOnly session token when you sign in to ComplyDP.Session or up to 7 days (remember me)
__clerk_db_jwtClerk (authentication)Short-lived JWT used for Clerk client synchronization.Session
li_sugrLinkedIn Insight TagBrowser identifier for LinkedIn campaign measurement.90 days
bcookieLinkedInBrowser ID for LinkedIn plugins and ad analytics.1 year
lidcLinkedInRouting and load-balancing for LinkedIn services.24 hours
UserMatchHistoryLinkedInSyncs LinkedIn Ads ID for retargeting measurement.30 days
AnalyticsSyncHistoryLinkedInStores sync timestamps for LinkedIn Ads ID matching.30 days
li_gcLinkedInStores LinkedIn guest consent state for the insight tag.6 months
_gcl_auGoogle AdsConversion linker: attributes ad clicks to on-site actions.90 days
_gcl_awGoogle AdsStores Google Ads click information for conversion reporting.90 days
test_cookieGoogle (doubleclick.net)Checks whether the browser accepts third-party cookies for ad measurement.Session
ph_phc_*_posthogPostHog (via /ingest proxy)Distinct visitor ID and session for product analytics and error capture.1 year
ph_*_posthogPostHog (via /ingest proxy)Session replay and feature-flag state when enabled.Session to 1 year
apollo visitor idApollo.ioAnonymous visitor ID so Apollo can attribute page views and match B2B visitors.Up to 12 months

Vercel Web Analytics (optional, cookieless): aggregate page views and Core Web Vitals. Country-level traffic splits only; not used for city-level marketing profiles.

Loads from va.vercel-scripts.com when its vendor tier allows. Does not set marketing cookies.

Loads tracker.iife.js from assets.apollo.io; sends visit events to api.apollo.io for company/contact identification.

Related browser storage

KeyProviderPurposeDurationScope
cookie-preferencesComplyDPStores your cookie consent category choices from the banner.Until cleared in browserAll visitors
ph_phc_*_posthogPostHogBackup persistence for analytics distinct ID when cookies are blocked.1 yearAll visitors (instrumentation-client.js)

Analytics (optional category)

None currently (see Strictly necessary).

Marketing (optional category)

None currently (see Strictly necessary).

Functional browser storage

Dashboard and product features, not ad profiling. Calendly loads only after Functional consent when you use Talk to DPDP Expert.

KeyProviderPurposeDurationScope
complydp_org_idComplyDPRemembers your active organisation in the dashboard.Until clearedSigned-in users
complydp_org_roleComplyDPCaches your role for the active organisation.Until clearedSigned-in users
dpdp_expert_chatComplyDPTemporary chat history for the on-site DPDP Expert assistant.24 hoursVisitors using the expert chat
complydp_cookie_jobComplyDPIn-progress cookie scan job state in the dashboard.Until scan completesSigned-in dashboard users
complydp_audit_jobComplyDPIn-progress DPDP audit job state in the dashboard.Until audit completesSigned-in dashboard users
consent_*ComplyDPPer-context consent banner choices on preview/demo flows.Until clearedConsent preview pages
  • Talk to DPDP Expert loads Calendly only with Functional consent. The in-page widget may also set data from Calendly subprocessors: Stripe (m.stripe.com, m.stripe.network) and Google reCAPTCHA (recaptcha.net). ComplyDP does not load these until you open the scheduler.

Third-party services

  • Clerk (clerk.com): Authentication
  • PostHog (posthog.com): PostHog usage and error monitoring (necessary)
  • Google Ads (google.com): Google Ads conversion measurement (necessary)
  • LinkedIn (linkedin.com): LinkedIn Insight Tag (necessary)
  • Vercel (vercel.com): Vercel Web Vitals (cookieless) (necessary)
  • Apollo (apollo.io): Apollo.io website visitor identification (necessary)
  • Calendly (calendly.com): In-page meeting scheduler (Functional consent)
  • Stripe (via Calendly) (stripe.com): Fraud and payment checks inside Calendly
  • Google reCAPTCHA (via Calendly) (recaptcha.net): Bot protection on Calendly forms

5) Contact

Cookie or privacy queries: privacy@complydp.com