curators@duecare-ai.com
Pack content, tool behaviour, eval results, citation accuracy, anything that affects what the model says.
Median first response: 3 working days.
DueCare has no support tickets, no chat widget, no community account. Feedback is by email. The address is published; the inbox is gated through the same privacy filter as the newsletter, and routed to the curator on rotation.
Pick the one that matches what you have to say. Misrouted mail still gets read; curators rebalance daily.
Pack content, tool behaviour, eval results, citation accuracy, anything that affects what the model says.
Median first response: 3 working days.
Policy questions, key rotation, audit replay, partner agreements, anything about how the hub is governed.
Median first response: 5 working days.
Suspected boundary violations, security disclosures, vulnerability reports. PGP key in technical docs.
Median first response: 24h on weekdays.
If a reply contains the categories below, the gate drops them and replies with a structured-form link instead.
| Don’t send | What happens if you do | Where to put it instead |
|---|---|---|
| Worker case content (names, narratives) | Auto-rejected at gate; submitter receives a notice and a link to a structured form. | Local frontline tool, not the hub. |
| Document images / scans | Attachments are stripped at the gateway. | Local case file. Never uploaded to the hub. |
| Confidential partner data | Held in the email provider only; never written to hub storage. | Partner agreement & private channel. |
| Press inquiries | Forwarded to a designated press curator on rotation. | press@duecare-ai.com |
Every accepted email receives a structured receipt: ticket id, classified type, expected review window, and a link to the hub queue if the reply has produced one.
tk-2026-04-22-0091npl-qat-construction@1.3.0/api/hub/feedback/tk-2026-04-22-0091