TRANSPARENCY · VERSION 1.0
Privacy notice
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.
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
- Access credential: the access password you submit to sign in. The server compares it with a secret held in the hosting environment; it does not create an individual password account or store a password record in an application database.
- Session data: a signed session cookie used to keep you signed in. It is HttpOnly, Secure, SameSite=Strict and expires after 12 hours. The application does not maintain a server-side session database.
- Chat content: the messages you choose to send and the recent conversation context included with a request. The browser keeps this conversation in page memory while the page remains open; reloading the page or signing out clears that in-memory conversation.
- Operational data: the model identifier and token-usage counts are logged for service diagnostics. Provider failures may generate short, sanitised status/error metadata. The application is designed not to log message prompts or generated replies.
- Network data: the server uses the network peer address visible to Node.js for abuse controls. The application deliberately does not trust an unverified X-Forwarded-For header. On a proxied deployment, this address may identify the hosting proxy rather than your device. Rate-limit counters are held in bounded process memory, not a user profile database.
3. Why information is used
- To authenticate access and maintain a short-lived session.
- To send the message and necessary recent context to the configured Gemini model so it can generate a reply.
- To apply basic request limits, prevent abuse, troubleshoot failures and monitor token usage.
- To protect the service and maintain its operation.
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
- Google Gemini API: chat messages and recent context are transmitted to Google through the Gemini API. Google's handling, retention, security and data-use terms depend on the API product, account tier and terms applicable to the configured project. Meghana cannot independently promise Google's retention or training treatment. Review Gemini API terms and Gemini API billing information before sending sensitive content.
- Domain India / Colosoft hosting: the application is hosted and deployed through this service. The provider may process infrastructure and security metadata under its own terms. The exact hosting region, provider log fields and retention period have not been independently confirmed in this release.
- GitHub: source code and deployment automation are hosted there. The live chat messages are not intentionally sent to GitHub by the application.
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
- Application chat storage: the current app has no persistent chat-history database. Chat history exists in browser memory for the open page only and is cleared by reload or sign-out.
- Session: the browser session cookie expires after 12 hours. Signing out clears the cookie in that browser. Rotating the server session secret invalidates all existing sessions.
- Rate-limit counters: held in bounded application memory, expire according to their rate-limit window (up to 24 hours), and are lost when the process restarts.
- Application logs: token counts, model identifiers and limited error metadata may be retained in hosting logs according to provider configuration. The exact provider retention period is not currently verified.
- Google and hosting-provider records: any retention by those providers is governed by their own applicable terms and settings, not by the browser-memory behaviour described above.
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