TRANSPARENCY · VERSION 1.1

Security & safeguards

Effective and last updated: 21 November 2026 · Current chat foundation

This page describes the security controls currently implemented in the deployed chat foundation. It is updated alongside security-related releases. It is not a penetration-test certificate or a claim that all risks have been eliminated.

1. Current safeguards

2. Current limits and risks

A committed npm lockfile is not present yet. CI audits the resolved production dependency tree, but reproducible dependency installation remains a follow-up hardening task.

3. Data and privacy boundary

Chat messages are sent to Google's Gemini API to produce replies. The application does not intentionally write prompts or replies to its own logs or persistent database. See the Privacy notice for provider processing, retention boundaries and user choices.

4. Security reporting

If you notice suspicious activity, unexpected access or a security weakness, stop using the service and contact the administrator through the channel used to provide access. Do not publish exploit details or send secrets in a report. A dedicated security contact must be published before public launch.

5. Release and update discipline

Security changes are developed on an isolated branch, reviewed against the existing implementation, tested in CI, merged only when required checks pass, and then verified on the live deployment. Material changes to data handling must update this page and the Privacy notice in the same release. Known limitations must remain visible rather than being described as completed controls.

6. Change history

Version 1.1 · 21 November 2026 · Privacy notice · Return to Meghana