Consumer case records
Reports, incident details, evidence, case messages, status history, outcomes and referrals belong to the authenticated case-management system.
Delivery Accountability Canada is designed around separation: case information, security/audit records, public contact enquiries, voluntary project-support records and optional website analytics serve different purposes and should not be treated as one data pool.
Reports, incident details, evidence, case messages, status history, outcomes and referrals belong to the authenticated case-management system.
Authentication events, administrator actions, evidence access, anti-abuse assessments and operational security events support platform integrity and accountability.
General contact messages receive separate DAC-CON references. Case evidence should remain in the secure case workspace rather than the public contact form.
Interac e-Transfer and PayPal support records exist for financial reconciliation and transparency and are kept separate from consumer case priority and decisions.
The pre-launch form stores the submitted name, email address, consent record and operational delivery status only for confirming the request and sending essential launch information. Confirmation and unsubscribe links are provided.
Website analytics is a separate measurement layer. Analytics should not receive case numbers, narratives, evidence filenames, order numbers, contact messages or financial account information.
Where enabled, AI inputs should be minimized and redacted. AI assistance does not replace human responsibility for consequential case decisions.
Never send account or banking passwords.
Mask payment-card information before uploading screenshots.
Do not submit identification unless specifically required through an approved process.
Remove information about other people that is not necessary for the consumer issue.
Account holders can manage notification and consent-related settings in the secure portal. Formal access, correction, deletion or privacy requests may require identity verification before records can be disclosed or changed.
Signed-in consumers can manage notification preferences and review account information.
Launch messages require email confirmation. Every launch message includes a one-click unsubscribe link; unsubscribed addresses are suppressed from future launch sends. DAC retains the minimum suppression record needed to honour that choice and avoid resending.
Optional analytics can be accepted or declined independently from necessary security and case functions.
Use the Contact & Support Centre and select Privacy / data handling for general privacy questions.
Contact Privacy Support →Aggregate public reporting is separated from individual consumer records and should not expose individual cases.
View Public Transparency →The DAC AI Assistant is designed as an internal-knowledge assistant rather than an unrestricted web chatbot. Public mode has no client/account data access. Signed-in mode can receive only server-authorized information belonging to the current account when it is actually relevant to the question.
Answers use indexed public DAC pages, verified DAC policy records and approved navigation. No case, evidence, contact, Network-member or account record is available.
For relevant questions, DAC may provide minimal summaries from the signed-in user's own permitted records. The general assistant does not receive evidence-file contents or secure case-message bodies.
DAC stores assistant conversation records for continuity, security and operational review under the configured retention period. Do not enter passwords, banking credentials or unnecessary sensitive information into chat.
If you request a human, DAC creates a Contact & Support request only after you confirm and submit the handoff form. Including the recent AI transcript is optional and off by default.
AI boundary: an AI answer is informational assistance, not a case decision, legal finding or promise of an outcome. When approved DAC information is insufficient, the assistant should say so and can route you to a human.
When a visitor selects a supported non-English language, DAC may send eligible interface text to Google Cloud Translation so the page controls, instructions and public information can be displayed in that language. Translation requests are proxied through the DAC server; the Google API key is not exposed to the browser.
DAC does not automatically send case narratives, uploaded evidence, case messages, names, email addresses, account identifiers or professional credentials to Google for interface translation. Private-content translation is disabled by default and would require a separate controlled workflow.
Original-record rule: machine-translated text is an accessibility aid. The original submitted record remains authoritative. Translation does not change consent, evidence, case status, audit history or legal meaning.