CBT Cards / Contact

Start with the right kind of message.

Use the route that matches your question. CBT Cards does not ask for private journal entries, health information, or other sensitive reflection content.

The CBT Cards mascot and two abstract paper figures align blank cards around an open notebook.
Clear context helps the project respond without collecting personal reflection data.

What would you like to discuss?

App support

For crashes, reminders, backups, exports, or store versions, use the troubleshooting checklist first.

Open support →

Privacy or accessibility

Report a privacy question, inaccessible interaction, readability problem, keyboard issue, or content-format barrier.

Read the privacy boundary →

Editorial correction

Point to the exact URL and passage, explain the concern, and include a primary source when one is relevant.

See the review policy →

Partnership or translation

Share the audience, use case, language, distribution plan, and whether the work is commercial or non-commercial.

See partnership paths →

AI or data integration

Describe the agent/runtime, required public resource, versioning needs, and how safety exclusions will remain visible.

Start with the AI guide →

Security report

Use the dedicated security instructions and avoid publishing exploit details in a general issue.

Open security.txt →

Current contact options

Message MetalHatsCats on LinkedIn Open a public GitHub issue

Do not include sensitive information. Do not send diary entries, check-in text, diagnoses, medical details, passwords, backup files, access tokens, or other private content. GitHub issues are public. Use LinkedIn for a non-public first contact, while still keeping sensitive reflection content out of the message.

CBT Cards does not publish a response-time guarantee. If a message concerns immediate danger or severe distress, this contact page is not emergency support; use appropriate local emergency or qualified professional help.