This page explains DocketPulse practices for access control, public-record data, enrichment evidence, lineage, responsible use, and customer security questions. It is not a certification, legal opinion, or promise that every record is complete.
Workspace access is enforced server-side using account roles and assigned territory scope. Administrative tools are separated from client workflows.
DocketPulse organizes booking records, provider-returned evidence, and customer-supplied business details for workflow purposes. Public-record data may be incomplete, delayed, corrected, or unavailable.
Customer-authorized enrichment, analytics, messaging, and mail providers may process the fields needed for the configured workflow. PostGrid credentials and sender settings are handled server-side for the connected workspace and are not displayed as public content.
Google Analytics 4 may receive page, source, workspace-type, state or county context, and selected marketing events such as availability actions or social-link clicks. Analytics is not used to publish lead records on the public site.
Identity, address, phone, email, relative, and validation observations are treated as evidence for review. Provider observations, enrichment runs, selected person records, contact candidates, and validation results remain connected where supported so teams can understand what was observed and when.
Contact the DocketPulse team about workspace roles, territory scope, data handling, retention questions, integrations, or organization-specific requirements.