The agreement defines the service
Fields, permitted uses, volume, refresh, service levels, internal use, retention, redistribution and embedding are contract-specific. They are reviewed together so technical delivery and legal rights match the intended workflow.
From requirements to delivery
Define the dataset
Select the population, identifiers, firm context, geography, registration categories and business-contact fields needed for the approved workflow. Fields remain subject to availability and permission.
Choose delivery
Use controlled full or delta files where contracted, or scope an API for approved query and integration patterns. Delivery design follows the agreed use case and operational requirements.
Set operational expectations
Document volume, refresh, service levels, support, data dictionary and change handling in the order form or customer agreement rather than assuming a standard feed.
Establish usage rights
Separate internal operational use from redistribution, customer-facing display, embedding, model use or AI training. Any broader rights require explicit written agreement.
Worked example: an internal account-matching feed
A financial-services vendor needs to normalize Canadian firm accounts inside its own operations system. The parties define input identifiers, matching output, selected firm and location fields, delivery volume, refresh, retention and internal users. Customer-facing display is excluded unless separately reviewed and granted in writing.
Data feed and API FAQs
Is API access included in low-priced plans?
No. API access is not included in low-priced plans and requires a separately scoped data agreement.
Can we receive change-only files?
Delta delivery may be available where contracted and operationally supported.
May we redistribute records to customers?
Not under an internal-use license. Redistribution or embedding requires separate written rights.
Is there a standard refresh cadence?
No public cadence is stated until operationally confirmed. The agreed refresh for a licensed delivery is contract-specific.
Can retention differ by field?
Yes. Retention and deletion obligations can depend on the field, source, permitted use and agreement.