Privacy notice

1. Who we are

NeMeets builds a connected meeting speaker and an AI meeting suite. In this notice, “NeMeets”, “we”, “us” and “our” refer to the NeMeets business and the people who operate this website and the pilot programme. “You” means the person contacting us, or the person whose meeting is captured.

For any question about this notice, or to exercise a right described below, write to hello@nemeets.com.

2. What this website collects

The site itself is deliberately thin. Today it collects only what you choose to type into the pilot form:

• Your name, work email and company — required, so we can reply and know which organisation we are talking to.
• Role, team size, main meeting language — optional, used to understand whether the pilot fits your situation.
• Your description of your meetings — optional free text.

The form does not post to a server from this page. It composes a message in your own email application so the request travels by your own mail provider, and you can see exactly what is being sent before it leaves. Nothing is stored in your browser after you close the tab.

We do not run advertising or behavioural analytics on this site, we do not set marketing cookies, and we do not embed third-party tracking pixels. The only external resource is the web-font stylesheet, which is requested from Google Fonts when a page loads.

Server logs

When the site is served from a web host, that host records standard request information — IP address, timestamp, requested URL, user agent and response status — for security and reliability. These logs are held by the host under its own terms and are not used by us to build profiles of visitors.

3. Why we use it

• To answer you. If you ask for a pilot conversation, we use your details to reply, to arrange a call and to keep a record of that exchange.
• To decide pilot fit. The optional role, team-size and language answers help us avoid wasting your time if what we have does not suit how you meet.
• To keep the site working and secure. Host-level logs are used to detect abuse and fix failures.

We do not sell your details, we do not add you to a newsletter because you submitted a pilot request, and we do not share your message with advertisers.

4. Recording and meeting data

Meeting content is a different category of information from a website enquiry, and it is handled by different rules. The product is designed so that:

• Consent comes first. Participants are informed and consent is recorded before recording begins, and a visible indicator shows that capture is active. Capture is user-initiated, never covert.
• The original audio is preserved unchanged. Processing happens on copies, so a recording can always be checked against what was actually said.
• Capture is controlled by a person. There is no always-on recording. On mobile, capture depends on the operating system's microphone permissions and cannot run in the background on platforms that prohibit it.
• Access is scoped. Recordings, transcripts and outputs sit inside a workspace with role-based access rather than being open to anyone with a link.

Where a customer deploys NeMeets, that customer decides the purpose of processing and the people who may access a meeting record. NeMeets acts on their instructions and does not use customer meeting content for its own purposes.

5. Where processing happens

NeMeets is designed local-first. Where the chosen device or host has the capacity, audio preparation, speech-to-text, speaker-turn detection and analysis run on that machine rather than being sent to a third-party AI service by default.

Local processing is an engineering objective, not a claim that every model runs on the speaker itself. Where a local device cannot handle a task adequately, a workspace may choose a cloud-processing option. That choice is explicit, disclosed in the interface, and shows which mode is active for a given meeting. Offline capability is limited to the functions that actually run locally; app sync, cloud services and third-party meeting platforms still require a network.

6. AI outputs and human review

• Evidence before assertion. Decisions, tasks, deadlines and requirements are linked to the transcript passages that support them.
• Uncertainty is marked, not filled in. Where an owner, amount or date is ambiguous, the item is flagged for review rather than guessed.
• A person approves. Follow-up messages and downstream actions are drafted for review; nothing is sent from an unreviewed output.
• No voice identity matching. Speaker turns are labelled anonymously (“Speaker 1”, “Speaker 2”) and named by a person during review. The first version does not build voiceprints or identify people by their voice.

7. Sharing

We do not sell personal information. Information is shared only in these situations:

• Service providers that host the website, deliver email or, where a workspace has opted into cloud processing, run that processing — each bound to process data only for the agreed purpose.
• Legal requirements, where we are obliged to disclose information by a valid legal order.
• With your direction, for example when you approve a follow-up message to a named recipient.

A current list of the sub-processors used for a deployment is provided with that deployment's data-processing terms. Product pages on this site do not name suppliers, because the hardware and software stack for the final product is still being validated.

8. Retention

• Enquiries are kept while we are in conversation with you and for a reasonable period afterwards, so a later question has context.
• Meeting records follow the retention setting of the workspace that owns them. Retention and secure deletion are workspace controls, not a fixed global policy.
• Deletion removes the recording, transcript and derived outputs together. A deletion request made to us is confirmed once it has been carried out.

9. Security

The design calls for encryption in transit and at rest, workspace isolation, role-based access, retention controls, secure deletion and audit logs of processing and corrections. These are implementation requirements that must be built and tested before they are described as guarantees. We will not claim a security property on this site that has not been verified for the deployment in question.

10. Your rights

Subject to applicable law, you can ask us to:

• confirm what personal information we hold about you and give you a summary of it;
• correct information that is inaccurate or incomplete;
• erase information that is no longer needed for the purpose it was collected for;
• withdraw a consent you previously gave, without affecting processing that already happened;
• nominate a person to exercise these rights on your behalf in the event of death or incapacity.

Write to hello@nemeets.com with enough detail for us to identify you and the information concerned. We respond within the period required by applicable law. If you are not satisfied with the response, you may escalate to the Data Protection Board of India once the applicable rules are in force.

11. Data processing summary

A short version of the sections above, for procurement and security review conversations:

12. Children

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. If you believe a child's information has reached us, write to us and we will delete it.

13. Changes

This notice will change as the product moves from pilot to general release — for example when the pilot form is connected to a form service, or when cloud processing becomes selectable in a workspace. The “last updated” date at the top of the page reflects the current version, and material changes will be described here rather than made quietly.

14. Contact

Privacy questions, deletion requests and security reports: hello@nemeets.com. For a product conversation instead, use the pilot request form.

Back to the NeMeets site