Duck Creek Data Retention — Jurisdiction-Aware Policy

Duck creek data retention is the carrier's policy and operating discipline for how long Duck Creek-originated data (policy records, claim records, billing records, reserve histories, treaty data, statutory filings) is retained, in what form, accessible to whom, and on what jurisdiction-specific schedule. Retention matters for several converging reasons: P&C carriers operate under statutory accounting retention requirements (typically 7+ years post-policy-expiration for primary records, longer for claim records on long-tail liability lines), state DOI examination requirements (varies by state, typically 10 years), tax retention requirements (typically 7 years federal, longer in some states for premium tax), reinsurance audit requirements (typically 10–15 years for treaty support), litigation retention requirements (the carrier's policy may require indefinite retention for claims with active or anticipated litigation), and privacy regulations (GDPR right-to-erasure, CCPA / CPRA right-to-delete) that can require deletion of in-scope personal data. A duck creek data retention policy reconciles all of these obligations into a coherent operating discipline.

Specific retention periods vary by jurisdiction, line of business and data type — and the duck creek data retention policy has to capture every combination. Common retention requirements (always confirm with carrier legal and compliance): policy records typically 7+ years post-expiration for primary records, 10+ years for E&S and surplus lines, indefinite for catastrophic-loss policies; claim records typically 7+ years post-closure for primary lines, 10–15 years for general liability and umbrella, indefinite for asbestos/environmental and other long-tail; billing records typically 7 years post-transaction for federal tax purposes; premium tax records typically 7+ years per state requirement; statutory filings (Annual Statement, Schedule F, etc.) typically permanent; reinsurance treaty data typically 15+ years post-treaty-expiration to support cession audit; reserves and actuarial documentation typically 10+ years to support reserve adequacy testing. The duck creek data retention policy captures these with explicit rules per data type per LOB per state.

Duck Creek system retention is how long data remains in the active Duck Creek system (OnDemand tenant or Platform deployment) where it is queryable by underwriters, billing analysts, claims adjusters and adjusters during their normal workflow. Archive retention is how long data remains accessible (typically read-only) in a separate archive — frequently a cloud object store with Parquet partitioning, sometimes a dedicated archive product. Carriers typically keep active records in Duck Creek for the working lifecycle (active policies, open claims, recent closed claims) and move closed and older records to archive on a defined schedule. Active retention in Duck Creek is therefore shorter than total retention — typically 2–3 years for closed policies and claims before archive transition. Archive retention then continues for the full statutory and regulatory period — typically 7–15+ years depending on data type. The duck creek data retention policy captures both windows explicitly.

Yes, for any personal data of EU data subjects in scope of GDPR — which includes EU residents on the carrier's books regardless of where the carrier is domiciled. UK GDPR has parallel requirements. CCPA (California) and CPRA include right-to-delete provisions. Other US state privacy laws (Virginia VCDPA, Colorado CPA, Connecticut CTDPA, Utah UCPA, and the growing list) include similar rights. Duck creek data retention has to accommodate erasure requests through a defined process: locate all personal data of the requesting subject across Duck Creek active and archive stores, apply erasure (deletion or pseudonymization depending on requirement and on statutory-accounting retention obligations that may override), produce evidence of erasure for the request response, log the erasure for audit. Note: statutory accounting retention obligations for premium and loss records can override individual erasure requests, but the carrier still has to handle the request properly and document the lawful basis for any partial fulfillment.

Through coordinated policy. Post-migration, financial records exist in both Duck Creek (the system-of-record for insurance operations) and Fusion (the system-of-record for finance). Statutory retention obligations apply to both — and the duck creek data retention policy coordinates with the Fusion retention policy to avoid premature deletion on either side. Common pattern: Duck Creek retains active and recently-closed records per the operational working-lifecycle window; Duck Creek archive (managed by Syntra ETL as a parallel Parquet-partitioned cloud-storage archive) retains the full statutory period; Fusion retains GL postings, AR/AP entries and reconciliation evidence per Oracle's own retention recommendations for the statutory period. Audit lineage links Fusion records back to Duck Creek source via the integration's preserved audit metadata. External audit and state DOI examination can pull lineage from Fusion through to Duck Creek source via the audit trail.

Three capabilities. (1) Archive build — Syntra ETL extracts Duck Creek data on a defined retention schedule (typically monthly or quarterly bulk archive runs) and writes to a Parquet-partitioned cloud archive (S3, GCS, Azure Blob) with KMS encryption and full audit metadata. The archive is queryable through standard SQL via Athena, BigQuery External, Synapse Serverless or similar. (2) Retention rule enforcement — Syntra ETL's retention engine reads retention rules from a governed policy table (per data type per LOB per jurisdiction) and applies automatic transition between active retention and archive, and automatic deletion at end of total retention. Every retention action is logged for audit. (3) Erasure orchestration — for GDPR, CCPA and similar right-to-delete requests, the erasure engine locates personal data across Duck Creek active stores, the Syntra archive and downstream destinations (Fusion, warehouse, BI), applies erasure or pseudonymization per request, and produces evidence of compliance.

State DOI financial-condition examinations occur every 3–5 years per state of domicile and may also occur out-of-cycle if the carrier is subject to NAIC IRIS ratio surveillance or other regulatory triggers. Examiners require access to historical financial records — policy issuance, premium-due, payment, claim payment, reserve adjustment, reinsurance cession — for the examination period (typically 3–5 years). Duck creek data retention has to support fast retrieval of historical records for examination support. The Syntra ETL archive's Parquet partitioning by fiscal period, LOB and state means examiners can query specific data slices efficiently — typical examination data pulls complete in minutes rather than hours. The audit metadata preserved with every archived record (extraction timestamp, source system version, integration version, transformation rule version) gives examiners the lineage they need to validate examination findings.

Vista ownership of Duck Creek introduces longer-horizon uncertainty about Duck Creek-as-a-vendor — pricing pressure, roadmap direction, potential M&A activity, eventual exit strategy. Carriers prudently plan for the scenario where they might displace Duck Creek (path 2 modernization) within a 3–7 year horizon, even if displacement is not the current plan. In that scenario, the archive of historical Duck Creek data becomes critical — it preserves the carrier's historical insurance-finance record independent of Duck Creek-as-a-vendor. Syntra ETL's archive is independent of Duck Creek — it lives in the carrier's own cloud account, is queryable through standard SQL, and remains accessible regardless of Duck Creek's future. Carriers that build a proper duck creek data retention strategy in 2026 inoculate themselves against Vista-related scenarios in 2028–2030 — the carrier's data is safe and queryable no matter what happens to Duck Creek as a corporate entity.