Status and live surfaces
Health routes show that a Worker is responding; they do not prove sign-in, storage, Queue processing, Gmail installation, or analytics correctness. Confirmed customer-impacting incidents and recovery updates will be posted on this page.
Support
Report a product problem to support@sendarq.com. Include the affected public path, approximate UTC time, browser/client, and safe visible error text. Do not send credentials, cookies, OAuth data, private message content, recipient information, or uploaded originals.
Security reporting
For a suspected vulnerability, use the dedicated Security reporting route.
Backup, rollback, and recovery
Production deployments are versioned and retain an explicit rollback anchor. D1 migrations are additive. Published signature versions and media paths are immutable, so a code rollback must not delete newer data or historical assets. Queue/DLQ recovery, database restore practice, and deploy rollback are independently exercised by the operational-readiness gate before release.
Operational privacy
Worker invocation logging is disabled where full tracked-link URLs could expose tokens. Custom telemetry is minimized and must not contain session or OAuth tokens, raw IP addresses, full user agents, destinations, recipient identity, email subject/body, request headers, or uploaded bytes. See the public privacy summary.