NemvioLegal
SecurityPrivacyTermsSub-processors
ROnemvio.co
Nemviolegal.nemvio.co/en/confidentialitate
Legal CenterPrivacy

Privacy Policy

This policy explains what happens to your data when you visit nemvio.co, book a call with us, buy an automation, accept a quote or sign a contract, and when we write to you by email. It doesn't cover how each client handles their own customers' data, that's governed by that client's own privacy policy, but below you'll find a summary of how we, as a provider, process that data on their behalf.

  • Updated on 2 November 2026
  • 10 min read
  • 14 sections

Privacy Policy

This policy explains what happens to your data when you visit nemvio.co, book a call with us, buy an automation, accept a quote or sign a contract, and when we write to you by email. It doesn't cover how each client handles their own customers' data, that's governed by that client's own privacy policy, but below you'll find a summary of how we, as a provider, process that data on their behalf.

Updated on 2 November 2026 · 10 min read

On this page

01 / 14

  1. 01Who we are
  2. 02What we collect
  3. 03Why we collect it
  4. 04When we write to you
  5. 05Where it is stored
  6. 06Data processed for clients
  7. 07Phone calls and voice
  8. 08Data from your Google account
  9. 09Transfers outside the European Union
  10. 10Marketing messages and unsubscribing
  11. 11How we protect the data
  12. 12How long we keep the data
  13. 13Your rights
  14. 14Changes to this policy

01Who we are

Nemvio is operated by State Alexandru and Lupu Alexandru. For any question about this policy or your data, write to us at contact@nemvio.co.

02What we collect

We only collect what you fill in, depending on what you do on the site:

  • When you book a call: your name, email address, phone number, your company or its CUI, the note you leave, if you leave one, and the time you pick. The call takes place on Google Meet, so your name and email address go into the Google Calendar invitation
  • When you buy an automation: the company name, its CUI, your name and email address. Card payment goes through Stripe; you enter your card details at Stripe and they never reach us
  • When you accept a quote or sign a contract: the name, role and email address you fill in, the note left on the quote, if you leave one, the date and time, and the IP address and browser type the acceptance or signature was made from, as proof of it

We don't use cookies and don't install third-party tracking scripts on this site. We use Vercel Web Analytics, which counts visits without cookies and without identifying anyone individually, only aggregate traffic numbers. On the booking page we use Cloudflare Turnstile, which only checks that the form is filled in by a person and not a robot.

As with any website, the servers that deliver the pages see your IP address and browser type when you open a page. This technical data is used only to get the page to you and to protect the site from attacks, not to identify you.

03Why we collect it

To hold the call you booked, to prepare your quote and, if you become a client, to sign the contract, prepare and deliver the project and issue the invoices. We don't sell it or give it to others for their marketing.

Legal basis: the steps you take before a contract and the contract itself, for booking, quotes, purchases and signing (Art. 6(1)(b) GDPR); legal accounting and tax obligations, for invoices and contracts (point c); our legitimate interest, for the emails introducing us to businesses and for the proof of acceptance or signature (point f).

04When we write to you

We also introduce ourselves to businesses by email. We find them on Google Maps, and the address we write to is the one the business published on its own website. We keep only the business's public details (name, address, phone, website, the published email address and its Instagram or Facebook pages) and the history of the emails exchanged.

Every email has an unsubscribe link. If you use it or reply that you do not want to hear from us, we stop writing: we keep only the address on an exclusion list, precisely so we do not write again. You can object to these emails at any time and ask for the data to be deleted at contact@nemvio.co.

05Where it is stored

The data above is stored in our database, hosted by Supabase, Inc., which acts as an infrastructure provider. Supabase doesn't use your data for its own purposes, it only stores it on our behalf. The emails we send you (confirmations, quotes, contracts) go out through Resend, Inc., booked calls are in Google Calendar and Google Meet, and card payments go through Stripe.

The nemvio.co website is hosted by Vercel Inc. and served through the network of Cloudflare, Inc., which delivers the pages and protects them from attacks. Both see visitors' IP address and browser only in order to do that. The forms on the site do not pass through the Cloudflare network: they are sent straight to our database. WhatsApp conversations, calls and the client panel do not pass through Cloudflare either.

06Data processed for clients

In addition to the data above, collected directly on this site, we build and maintain systems (WhatsApp bots, panels, AI and email automations) that process the data of the end customers of the businesses we serve: the names, phone numbers, messages, and bookings of the people who write to them on WhatsApp or email. If a business connects its ANAF Virtual Private Space (SPV) to the invoice automation, we read from it the invoices the business received through e-Factura; we keep, encrypted, only the access token, for as long as the SPV stays connected.

In this case, the client business is the data controller, and Nemvio acts as a data processor, handling the data solely according to the client's instructions. The exact terms of this processing are set out in a data processing agreement (DPA), part of the signed contract with each client, not by this page, which only covers use of the nemvio.co website.

To deliver these systems, we work with the following sub-processors:

  • Meta Platforms, Inc.: the official WhatsApp Business platform, for sending and receiving messages and for incoming calls
  • OpenAI Ireland Limited: the artificial intelligence model that reads the end customer's message and composes the reply, for clients with an active voice agent the real-time voice conversation of WhatsApp calls, and, for clients with automations, the documents and emails those automations read (invoices, requests, CVs, contracts). The data sent is not used to train models, and OpenAI may keep abuse-monitoring logs for up to 30 days
  • Anthropic, PBC: the Claude models, integrated for the written assistant. It receives the end customer's messages only if we switch the assistant to its models, and the data sent is not used to train models
  • Supabase, Inc.: the database and infrastructure
  • Resend, Inc.: sending the automated emails, meaning confirmations, reschedules, cancellations, reminders
  • Vercel Inc.: hosting the website and the admin panel
  • Cloudflare, Inc.: receiving the emails sent to an automation's own address (for example the invoices a business forwards), which it hands straight to our system, for clients with automations
  • OVH SAS: the server in France running the voice service, for clients with an active voice agent
  • Google LLC: only for clients who enable Google Calendar sync

07Phone calls and voice

Clients with an active voice agent receive WhatsApp calls answered by an automated system, not a person. When someone calls, their speech is streamed in real time, through our voice server in France, to the OpenAI model, which understands what the caller says, composes the reply, and speaks it.

We do not keep an audio recording of the call. What remains stored is the text transcript of the conversation, the caller's number, the time and length of the call, and the resulting booking, if one was made. The code contains an audio-saving feature used strictly for debugging, and it is switched off in production.

The bot says at the start of the conversation that it is an automated assistant. The caller can ask to speak to a person at any time.

08Data from your Google account

Our clients and their team members can optionally connect Google Calendar to the Nemvio panel. When you do, you give us access to two things: the email address of the Google account, so you can see which account is connected, and permission to create, change, and delete events in your calendar.

We use this access only to put the bookings made through the business's assistant into your calendar and to update them when they are moved or cancelled. The sync runs one way: we do not read, copy, or keep the other events in your calendar. We keep, encrypted, only the access token Google gives us, for as long as the calendar stays connected.

We do not sell data from your Google account, use it for advertising, share it with others, or use it to train artificial intelligence models. Our use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

You can disconnect the calendar at any time from the panel, in Account settings, under Integrations, or from your Google account at myaccount.google.com/permissions. On disconnecting we delete the access token; the bookings already in your calendar stay there, since they are yours.

09Transfers outside the European Union

Some of the providers above are companies in the United States, and processing may take place on their servers. Where that happens, the transfer relies on the standard contractual clauses approved by the European Commission, or another mechanism provided for by the GDPR, through the contracts held with each provider.

10Marketing messages and unsubscribing

Some clients use the platform to send their own campaigns on WhatsApp or by email to their own customers. Those messages come from that business, not from Nemvio, and the business decides who receives them. Every campaign email carries an unsubscribe link, and a WhatsApp message can be answered with STOP: in both cases the choice is recorded immediately and that number or address stops receiving campaigns from that business.

11How we protect the data

Each business's data is isolated from every other business's at the database level, not merely in the interface. Two-step authentication is mandatory for Nemvio team accounts and optional for business accounts, and once switched on it is required at every sign-in; changes to the data are written to an audit log, and privileged keys exist only on the server, never in code running in a browser. The full detail is at legal.nemvio.co/securitate.

12How long we keep the data

Booking data and the details of businesses we wrote to are kept for up to 24 months from our last contact, unless we're actively working together or you ask us to delete them sooner. Unsubscribed addresses remain only on the exclusion list, so we don't write to them again. Quotes, contracts and invoices, together with the proof of acceptance or signature, are kept for the duration of the relationship and then for as long as legal accounting and tax obligations require.

For data processed on behalf of a client, the client sets the retention period, because the client is the controller. As a platform rule, conversations, bookings, and call transcripts are kept for as long as the account is active, the log of sent emails is kept for 12 months, documents received by automations (the files and the text of the emails) are kept for 12 months and then deleted automatically, while the data extracted from them stays for as long as the account is active, and when the relationship ends the data is deleted at the client's request or within 90 days of the account being closed at the latest.

13Your rights

Under GDPR, you can ask us to:

  • Show you what data we hold about you
  • Correct it if it's wrong
  • Delete it
  • Restrict how we use it, or object to a specific use
  • Send you a copy in a portable format

Write to us at contact@nemvio.co and we'll handle it directly. You can also file a complaint with the Romanian data protection authority, ANSPDCP (dataprotection.ro), if you think we've mishandled your data.

14Changes to this policy

If this policy changes substantially, we'll update the date at the top of this page.

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

Other documents

SecurityHow your data and your customers' data are protected, who can access them, and what we do not promise.Updated on 9 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ă