Legal — privacy
NeMeets is built around a simple rule: a meeting belongs to the people in it. This notice explains what happens to information when you contact us, and how the product is designed to handle meeting recordings and AI outputs.
This notice describes how the product is designed to behave and what the website does today. It is a draft and must be reviewed by a qualified lawyer, including against the Digital Personal Data Protection Act, 2023 and applicable rules, before it is relied on commercially.
NeMeets builds a connected meeting speaker and an AI meeting suite. “NeMeets”, “we”, “us” and “our” refer to the NeMeets business. “You” means the person contacting us or the person whose meeting is captured.
Entity details: [add registered entity name, address and grievance officer].
Contact: hello@nemeets.com.
Only what you type into the pilot form: your name, work email and company (required), plus optional role, team size, main meeting language and a description of your meetings.
The form does not post to a server from this page. It composes a message in your own email application, so you can see exactly what is being sent. We do not run advertising or behavioural analytics, set marketing cookies, or embed tracking pixels. The only external request is the web-font stylesheet from Google Fonts.
We do not sell your details, and submitting the form does not subscribe you to a newsletter.
Where a customer deploys NeMeets, the customer decides the purpose of processing and who may access a meeting record. NeMeets acts on their instructions.
NeMeets is designed local-first: audio preparation, speech recognition and analysis run on a compatible device or server where capacity allows. Local processing is an engineering objective, not a claim that every model runs on the speaker itself. Where a workspace chooses cloud processing, that choice is disclosed and visible for the meeting concerned.
We do not sell personal information. Information is shared with service providers that host the site or deliver email, where required by a valid legal order, or with your direction — for example when you approve a follow-up to a named recipient. A sub-processor list is provided with each deployment’s data-processing terms.
The design calls for encryption in transit and at rest, workspace isolation, role-based access, retention controls, secure deletion and audit logs. These are implementation requirements that must be built and tested before they are described as guarantees.
Subject to applicable law, you can ask us to confirm what we hold, correct it, erase it, withdraw consent, or nominate someone to act for you. Write to hello@nemeets.com with enough detail to identify you. If you are not satisfied with our response, you may escalate to the Data Protection Board of India once the applicable rules are in force.
A short version for procurement and security review conversations.
| Data | Purpose | Where it goes | Retention |
|---|---|---|---|
| Pilot form: name, work email, company | Reply to your request | Your own email application sends it to our inbox | While in conversation, plus a reasonable period |
| Pilot form: role, team size, language, notes | Decide pilot fit | Same as above | Same as above |
| Host request logs | Security and reliability | Web host | Per host policy |
| Meeting audio | Produce a reviewable record | Local device or server first; cloud only if chosen | Workspace retention setting |
| Transcript and outputs | Summary, decisions, tasks, approved follow-ups | Workspace storage; exports go where you send them | Deleted with the record |
NeMeets is a product for businesses and their meetings. It is not directed at children, and we do not knowingly collect information from anyone under 18 through this website.
This notice will change as the product moves from pilot to release. The date below reflects the current version, and material changes will be described rather than made quietly.
Privacy questions, deletion requests and security reports: hello@nemeets.com.
Last updated 2 November 2026.
