# Contact Page title: Contact and Reporting Problems > How to report a wrong or outdated claim, how to report a security problem, and how to send the maintainer a general message. Canonical page: Three kinds of message, three routes: a claim on a page that is wrong, a security problem with the site, or anything else. This is a one-person project, so there is no promised reply time. Last updated: 2026-10-12 ## A page says something wrong Corrections are the most useful mail this site gets, and a correction with a source is the most useful kind. - **Open a content-error issue** on GitHub with the [content-error form](https://github.com/sandgraal/letstalkcdc/issues/new?template=content-error.yml). It asks for the page, the claim, and what you think is right. Issues are public, so do not put anything private in one. - **Check the [errata page](https://sandgraal.github.io/letstalkcdc/errata/)** first: it lists the corrections already made. How a correction is handled is described under ["When we're wrong"](https://sandgraal.github.io/letstalkcdc/methodology/#corrections) in the methodology. - **Or fix it yourself:** every page footer has an "Edit this page on GitHub" link that opens the page source in the editor. ## A security problem The site is static pages with a little browser JavaScript, and the only server-side piece is an optional database table that receives assistant votes and the Change Feed Playground's rows. Please report anything you find in that scope: a script injection, a leaked key or secret, a database permission that is too wide, or a vulnerable dependency. - **Email** [cennisc@gmail.com](mailto:cennisc@gmail.com). This is the maintainer's designated public address for security reports. Say which page or file, the steps to reproduce, and the impact. - **Or use GitHub's private reporting** from the repository's Security tab, as described in the [security policy](https://github.com/sandgraal/letstalkcdc/blob/main/SECURITY.md). - **For tools:** the standard [security.txt](https://sandgraal.github.io/letstalkcdc/.well-known/security.txt) file carries the same contact. Under this project address it can be served only below the site's own path, not at the host root. Please do not open a public issue for a vulnerability, and do not put real data, secrets or connection strings in a report. Reports are read by one person and a reply is not guaranteed within any particular time. ## Anything else For a question, a suggestion or a general message, write to [cennisc@gmail.com](mailto:cennisc@gmail.com) or message Christopher Ennis on [LinkedIn](https://www.linkedin.com/in/cennis/). To ask what the assistant or the playground stored about you, or to ask for an entry to be deleted, read the [privacy page](https://sandgraal.github.io/letstalkcdc/privacy/#delete) first. An email address is not a private channel from the web's point of view: this one is published on this page, so it can attract spam. ## About how the content is written Much of the text on this site is drafted with AI assistance. A page is described as reviewed by the maintainer only after he has confirmed that review. This is why correction reports matter: they are one way a wrong claim gets found. --- CDC: The Missing Manual by Christopher Ennis (Let's Talk CDC), licensed under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Attribution is required.