Privacy
Privacy should be a design requirement, not an afterthought.
TRC is being built around private evidence. The public website should therefore say plainly what is collected now, what is not collected, and what must be true before any future diary, photo or voice feature goes live.
The First Checkpoint
Your checkpoint answers and optional 24-hour move stay in the current browser session. TRC does not send them to a server, store them in a database, place them in cookies or browser storage, or attach them to an account. Refreshing or leaving the page clears them.
The 300-Day ME Project Workbook
The application-level download counter stores only the total number of successful workbook file requests and the time that aggregate was last updated. It does not create a user profile or an individual download history.
Email updates
No public email form is live yet. Before email updates open, this page will identify the service provider, the purpose of collection, how to unsubscribe and the contact path for privacy questions.
Future app evidence
No private diary, photo or voice feature is live. Before any private storage launches, export and delete controls are core requirements. No AI is intended to read private diary, photo or voice evidence.
Hosting and necessary technical data
Like most hosted websites, infrastructure providers may process technical request data needed to deliver and secure the service. TRC will not describe infrastructure logs as a personal-growth profile or use private checkpoint answers for advertising.
Safety boundary
TRC is not therapy, medical advice, clinical screening or crisis support. The First Checkpoint is a private reflection tool, not a professional assessment.
Contact
A privacy contact address will be added before the production site collects email addresses or stores private user evidence.