Privacy
A plain-language summary of how the current JointJournal prototype handles information.
Information you provide
An account can contain your email address, display name, baseline, symptom entries, body locations, notes, imported history, prediction follow-ups, and product requests. Do not enter information you do not want stored in the prototype.
Authentication and storage
Passwords are salted and hashed; the application does not store readable passwords. Account email and credentials are kept in a separate identity container. Health and journal records do not store the email address: they are partitioned in Azure Cosmos DB by a random, opaque internal user identifier, using Cosmos DB hash partitioning. The authenticated server resolves that identifier and supplies the account email to the Profile screen without copying it into the journal partition. Sessions use secure, HTTP-only cookies in production.
Synthetic demo
The no-login demo uses isolated synthetic information. Demo changes remain in the browser session, are not added to an account, and are discarded when the demo ends.
Operations and deletion
Operational monitoring is designed to exclude names, emails, symptom values, notes, transcripts, and record contents. Signed-in users can delete journal data or delete their account from Profile. This prototype does not claim HIPAA or other regulatory certification.
Before real-world use
Privacy, retention, consent, incident-response, and regulatory requirements need formal review before inviting real patients or using JointJournal in clinical care.