Cookie Policy

Overview

Chaindoc relies on cookies and similar technologies to keep signing sessions secure, remember workspace preferences, and understand how customers adopt our blockchain-based signing tools. Every cookie we set exists to support a compliant enterprise experience — we do not broker or sell behavioural data.

Essential cookies

• Maintain encrypted sign-in sessions for the Chaindoc Console, signer links, and API playground.
• Enforce workspace security preferences such as mandatory MFA, device trust, and step-up verification.
• Route traffic through our edge network so large signature envelopes stay responsive worldwide.

Functional cookies

• Remember selected language, signature style, and document preview settings for each workspace.
• Surface your most recent templates, playbooks, and blockchain audit exports.
• Synchronise support chat, guided tours, and onboarding progress across visits.

Analytics cookies

• Highlight which notarisation, compliance, and API capabilities are most valuable to teams.
• Measure reliability of webhook callbacks and document hashing so we can optimise throughput.
• Provide anonymised adoption metrics that inform our roadmap without exposing document contents.

Third-party providers

Chaindoc may enable trusted third parties (for example Google Analytics or Intercom) when a workspace activates optional services. These partners receive usage metadata only — signature hashes, documents, and identity attributes remain encrypted and are never shared.

Managing preferences

You can adjust cookie behaviour through the Chaindoc Cookie Manager or directly in your browser. Disabling essential cookies will block access to secure signing flows, while opting out of analytics has no impact on core product functionality.

Questions

If your organisation requires a detailed cookie inventory or DPA addendum, contact privacy@chaindoc.com. Our compliance team will share the full breakdown we use for SOC 2, ISO 27001, and GDPR audits.