NemvioLegal
SecurityPrivacyTermsSub-processors
ROnemvio.co
Nemviolegal.nemvio.co/en/securitate
Legal CenterSecurity

How we handle security and data

We are two people who build and maintain systems that carry your customers’ conversations and data. This page says plainly what we build on, what data our systems touch, who has access to it, and what we do not promise. We would rather you read a short true list than a long impressive one.

  • Updated on 9 November 2026
  • 6 min read
  • 7 sections

How we handle security and data

We are two people who build and maintain systems that carry your customers’ conversations and data. This page says plainly what we build on, what data our systems touch, who has access to it, and what we do not promise. We would rather you read a short true list than a long impressive one.

Updated on 9 November 2026 · 6 min read

On this page

01 / 07

  1. 01What we build on
  2. 02What data our systems touch
  3. 03Who has access
  4. 04What the bot never does
  5. 05GDPR, briefly
  6. 06Updates and incidents
  7. 07What we do not promise

01What we build on

We build exclusively on Meta’s official WhatsApp Business platform. We do not use unofficial libraries and we do not automate a personal WhatsApp number, because that breaks Meta’s terms and can get your number banned.

The artificial intelligence comes from OpenAI and Anthropic. OpenAI’s models read customers’ messages, carry the voice calls and read the documents in the automations. Anthropic, with its Claude models, is integrated too, so we never depend on a single provider. With both we work through their business service, where the data sent is not used to train models.

The websites and the panel are hosted on Vercel, the database on Supabase, and the voice service on an OVH server in France, all administered by us. All traffic between the browser and our servers goes encrypted over HTTPS. The full list of providers is on the sub-processors page.

02What data our systems touch

A WhatsApp bot and the panel behind it work with the minimum data a booking or an answer needs:

  • The phone number the customer writes from and the name they give
  • The conversation with the bot, so a person can take over when needed
  • The booking: the service, the time, and who it is with
  • Your business catalog: services, prices, hours, address

For calls taken by the voice agent we keep the text transcript, the number, the time and length of the call, not the audio recording. Automations work with the documents and emails they receive (invoices, requests, CVs, contracts) and the data taken from them; the invoice automation also reads the IBAN on supplier invoices, precisely to stop an invoice with a changed IBAN.

The access tokens received when you connect Google Calendar or the ANAF SPV are kept encrypted, apart from the rest of the data, and are deleted when you disconnect.

What we do not hold: card details, your customers’ passwords, medical records or other clinical data. For clinics, dental and veterinary practices, the panel keeps bookings and conversations, not medical history. Your medical software stays where it is.

03Who has access

Every client has their own account in the panel and sees only their own business data. The separation is enforced in the database itself, not just in the interface. There is no shared screen where several companies’ customers show up together.

For Nemvio team accounts, two-step authentication is mandatory. For your business’s accounts it is optional, but once switched on it is required at every sign-in, and without it nothing opens. You can make it mandatory for your whole team, and then the database itself shows nothing to an account that has not switched it on. Every change to a business’s data is written to an audit log: who, what and when.

The Nemvio team does not see your business content either. Conversations, calls, customers, bookings and the documents processed by automations are locked for our accounts in the database itself, not just hidden in the panel. We see numbers and states: how many conversations there were, how many documents were processed, which errors came up, without their content.

We see content in two situations only:

  • When you show it to us: you open a ticket in Support and attach a conversation, a call or a result. We see only that item, for 7 days, and you can take it back at any time.
  • In an emergency, when the system stops working and you cannot send us anything: the whole account, for one hour, with the reason written down. You get an email right away.

Every access shows up in the panel, under Support: what you attached, until when we can see it, and you can take it back at any time. Technical access to the servers is limited to the two of us, for building and maintenance. There are no account managers, subcontractors, or outsourced support team going through your data.

04What the bot never does

  • It never asks for card details, national ID numbers, passwords, or codes received by SMS
  • It does not process payments or hold money
  • It does not act inside your other systems unless we explicitly build that integration
  • It is built not to invent an answer when it does not know, but to hand the conversation to a person. Like any AI model it can still be wrong, which is why the conversations show in the panel
  • It does not answer medical questions, not even partially

05GDPR, briefly

For your customers’ data, you are the data controller and we are the processor: we process the data to run the system we built for you, not for purposes of our own. We do not sell or lend data to third parties.

The details of what we collect through our own site are in the privacy policy, and your obligations as a business messaging customers on WhatsApp are explained in our GDPR guide.

The data processing agreement (DPA) is part of the contract signed with every client. When we stop working together, your business data is deleted at your request or within 90 days of the account being closed at the latest, and exported for you first, if you want it. A specific retention period is agreed in writing, in the contract.

06Updates and incidents

We host and maintain the systems we build, so updates and fixes are our job, not yours. You have no server to manage and no updates to run.

If you notice something odd, you write directly to us, the people who built the system, from Support in the panel or at contact@nemvio.co, not to an outsourced department. You can see the state of the services at any time at status.nemvio.co. If a problem affects your data, we tell you what happened and what we did about it, without dancing around it.

07What we do not promise

We are two people, not a vendor with a dedicated security department. In practice, that means:

  • We hold no ISO 27001, SOC 2, or similar certification, and we do not claim to
  • We do not sell uptime guarantees we cannot back with measurements
  • If you have formal security requirements from a large client or an audit, tell us in the first conversation: either we can meet them, or we tell you honestly that we are not the right fit

Nemvio · contact@nemvio.co · Version of 9 November 2026. The latest version is always on legal.nemvio.co.

Other documents

PrivacyWhat data we collect when you write to us or use our systems, why, and how long we keep it.Updated on 2 November 2026
TermsWhat we build, how it is paid, the minimum term, and how a subscription is stopped.Updated on 9 November 2026
Sub-processorsThe providers data passes through so the system works, each with its role.Updated on 2 November 2026
NemvioLegal

The documents that describe how we protect the systems, what data we process, through which providers, and what the contract says.

Documents

  • Security
  • Privacy
  • Terms
  • Sub-processors

Nemvio

  • Services
  • Pricing
  • GDPR guide
  • Contact

Contact

  • contact@nemvio.co
  • 0733 370 725
  • WhatsApp
© 2026 Nemvio. All rights reserved.Documents revised on 2 November 2026Română