TRANSPARENCY · VERSION 1.0

Privacy notice

Effective and last updated: 21 November 2026 · Applies to the current Meghana chat foundation

This notice explains what the current version of Meghana handles, why it handles it, and which service providers are involved. It describes the implementation as it exists today; it is not a promise about features that have not been built.

Important: Do not send passwords, API keys, financial credentials, medical records, highly sensitive personal information, or confidential third-party information to the chat. Your message is sent to Google's Gemini API to generate a response.

1. Who operates Meghana?

Meghana is a private, founder-controlled application currently operated as a limited chat foundation. The legal name and postal address of the operating entity, and a dedicated privacy contact email, have not yet been supplied for publication. Until those details are published, privacy questions or requests can be sent to the administrator through the same channel used to provide access to Meghana. This notice should be completed with the operator's legal identity and designated privacy/grievance contact before public launch.

2. Information handled

3. Why information is used

The current application does not use chat content for advertising, behavioural profiling, or analytics. It does not intentionally access your contacts, SMS, call logs, photos, files, microphone, camera or location.

4. Service providers and data sharing

Meghana does not sell personal information or share chat content with advertisers. No advertising or third-party analytics SDK is included in the current interface.

5. Storage and retention

6. Your choices and requests

You can stop using the service and sign out at any time. You can avoid sending personal or sensitive information. You may ask the administrator to rotate the access password or session secret; doing so can revoke access for all authorised users, not just one person. Because the current app does not retain chat history in an application database, it cannot retrieve or selectively delete a conversation after it has left browser memory. Requests concerning provider-held records must also be addressed under the relevant provider's process.

For access, correction, deletion, grievance or other privacy requests, contact the administrator through the channel used to provide your Meghana access. A dedicated named contact and email address must be added before public launch.

7. Security

The current foundation uses password-gated access, signed short-lived sessions, secure cookie attributes, same-origin checks for state-changing requests, request-size limits, security headers, bounded in-memory rate limiting and server-side API credentials. These controls reduce risk but do not guarantee that the service is immune to attack. See the Security & safeguards page for the current controls, known limitations and update history.

8. Children

Meghana is a private prototype and is not designed for use by children. Do not provide information about a child or another person unless you have appropriate authority and a clear need to do so.

9. Changes to this notice

This notice is versioned and will be updated when the application changes how it collects, uses, stores, shares or protects information. The version and last-updated date at the top will change with material revisions. Material changes should be reviewed before release; the latest published version is available from the Meghana interface.

10. Legal status and launch readiness

This is an operational transparency notice, not a legal opinion or a certification of compliance. Indian data-protection requirements have phased commencement dates. The operator must obtain a qualified legal review, confirm the applicable obligations and complete the missing operator/contact, retention, hosting-region and processor details before making Meghana publicly available.

Version 1.0 · 21 November 2026 · Current chat foundation only · Security page · Return to Meghana