Privacy & Safety Research
Privacy and safety are design priorities. The architecture described here includes research goals and does not establish product-wide security, anonymity, HIPAA compliance, or clinical safety.
On-Device Intelligence
We are exploring local processing to reduce exposure of sensitive signals. Processing location depends on the feature and deployment; we do not make a product-wide claim that all information stays on the device. Data flows, external services, logs, and retention need verification before sensitive-data use.
Federated Learning
Federated learning is a research direction for model improvement. Its privacy protections need evaluation: model updates and derived scores must not be assumed anonymous merely because raw inputs remain local. This is not a claim that a production federated-learning service is operating.
Explainability & Auditability
We aim to make experimental outputs understandable and traceable. Whether those explanations are accurate, useful, and appropriate for clinical review remains to be evaluated. An explanation does not establish that a score is clinically meaningful.
Safety Governance
Formal clinical and ethics oversight is a requirement to address in planning future studies. Professional feedback is not clinical validation or evidence of an appointed advisory board. Study protocols need appropriate review, consent procedures, and safety responsibilities before enrollment.
Using this project website
Research access uses Google to verify your identity. Access requests store your Google account identifier, name, email, status, and review timestamps for administrator review. Signing up does not grant document access until approved. This is separate from clinical study enrollment and the email updates list.
Research-access records are stored using Upstash Redis, accessed by the website's Vercel server and the authorised administrator. They remain in the active access list until deleted. After signing in, use “Delete my access request and approval” to remove your record, end your session, and withdraw document access. This does not delete your Google account or recall documents you already downloaded. Provider logs or backups may have separate retention; this feature deletes the active access record.
The sign-in session cookie expires after two hours; a temporary sign-in nonce expires after ten minutes. Abuse-prevention counters use keyed digests of account identifiers or connection addresses and expire after ten minutes. These safeguards are not a claim that visiting the website is anonymous.
Partnership inquiries
The contact form collects your name, email, optional organization, selected interest, and message so the MANAS team can review and respond. Please do not submit health information. Submissions pass through Vercel and are stored in Upstash Redis, visible only through the administrator inbox to authorised administrators. Contact details are supplied by the sender and are not independently verified.
Inquiry records expire from the active inbox 90 days after submission, including records marked handled. Provider logs and backups may have separate retention. Sending an inquiry does not subscribe you to marketing or enroll you in a study. The form displays a receipt after saving; it does not send automatic emails. Website abuse-prevention counters expire after ten minutes.
The public demos illustrate proposed interactions with sample data. Use fictional details. They do not provide clinical assessments or emergency monitoring.
The updates form sends your email address to Brevo to request a confirmation email and manage your subscription. This is separate from study enrollment. You can unsubscribe through the link in each update. Website hosting and browser services can process technical request information; this site should not be treated as an anonymous or device-only environment.
This page describes the current approach and limitations. It is not a complete privacy policy for a health service. Before sensitive-data participation, the project needs verified disclosures covering the operator, data recipients, retention, deletion, and participant rights.