Skip to content
EN
+373 78 155 277Book a Consultation

GDPR

Leads, CRM and newsletters under Law 195/2024: what to change in your website form

Replying to an enquiry, sending newsletters and measuring the form are different purposes. What a good form looks like, which documents come first and what the law says about promotional email.

Published 7 min read

Someone requests a quote on your website and a week later receives a promotional email they never signed up for. To them it is spam. Under Law No. 195/2024 it is processing without a suitable legal basis. To avoid it, the form, the CRM and the newsletter need to be separated by purpose, and each purpose needs a trace in your documents.

This is the third article in our series on Law 195/2024. The first covers what to check on your website, the second covers Google Ads and Meta after cookie rejection. Here we follow an enquiry after someone clicks “Send”.

In brief

  • Replying to an enquiry, sending promotional emails and measuring the form are three different purposes. Not all of them need consent, but people must be told about each.
  • A single mandatory “I agree to everything” box does not work. Newsletter consent is given separately and voluntarily.
  • Every service an enquiry passes through (email, CRM, messenger, hosting) is a processor. You need a contract with each, and transfers outside Moldova belong in your privacy policy.
  • You must answer a person’s request about their data within one month, and report a data breach to the CNPDCP within 72 hours where feasible.
  • For promotional emails, Moldova’s e-commerce law No. 284/2004 requires the recipient’s prior consent.

Article 6 of the law lists the grounds for processing data. For a typical service business form, three situations matter.

Scroll the table horizontally →

Purposes for form data
PurposeUsual legal basisWhat to do on the website
Replying to the enquiry, preparing a quoteSteps taken at the person’s request before a contractA short notice next to the button and a link to the policy
Sending news and offersConsentA separate, unticked checkbox and an easy unsubscribe link in every email
Measuring where the enquiry came fromConsent to analytics and advertising cookiesA banner and Consent Mode, as described in the second article

Choosing the basis for a particular business is a job for your data protection contact or a lawyer. The table shows a typical case, not a legal opinion.

What a good form looks like

Article 7 requires the consent request to be clearly separated from other terms. That gives a simple rule: people can send an enquiry without subscribing to anything.

Avoid: “☑ I agree to the processing of personal data, to receiving promotional materials and accept the terms”, with the box mandatory and pre-ticked.

Better: under the button, “By sending this request you give us your name and phone number so we can prepare a quote. Details in our privacy policy.” Below it, an optional, unticked box: “Send me news and offers by email”.

Demo example. A furniture company, illustrative scenario. Its form had one mandatory box covering everything, and every contact went into the mailing list. After the split, roughly one visitor in five ticks the newsletter box. The list is smaller, but everyone on it asked for the emails, and the business can show that consent during an inspection.

Where an enquiry goes after it is sent

An enquiry rarely stays in one place. A typical path is website → manager’s inbox → CRM → messenger, if the client prefers it → archive. At each step someone stores the data: the hosting provider, the email service, the CRM vendor.

For each of these services, check three things:

  • whether a contract or data processing terms state that it acts on your instructions;
  • where the data is physically stored, and whether a transfer outside Moldova appears in your policy;
  • who in the company has access, and how access is removed when someone leaves.

The law does not set one retention period for enquiries. The business decides it based on the purpose and records it in the register and the policy. Keeping enquiries indefinitely “just in case” is a bad idea.

The documents an inspector asks for first

Scroll the table horizontally →

Core document set
DocumentPurposeBasis in the law
Privacy policyTells people what is collected, why, for how long and what rights they haveArticle 12 onwards
Record of processing activitiesDescribes purposes, data categories, recipients, retention and security measuresArticle 30
Processor contractsConfirm that hosting, CRM and email act on your instructionsRequirements for processors
Consent logShows who agreed to what, and whenArticle 7
Breach procedureHelps you meet the 72-hour deadlineArticles 33–34

One caveat on the record. Article 30 exempts organisations with fewer than 250 employees, but only when processing is occasional, poses no risk and involves no special categories of data. Website enquiries arrive all the time, so most businesses that collect leads still need the record.

Newsletters, SMS and messengers

Article 22 of Law No. 284/2004 on electronic commerce bans promotional emails without the recipient’s prior consent. The sender must be clearly identifiable, and recipients have the right to refuse such messages. For SMS, Viber and WhatsApp it is sensible to apply the same rule: promotions only to people who agreed.

Replying to an enquiry in the channel the client chose is not advertising. If a sales manager writes to the same client a month later about a promotion, that is a promotional message and needs consent.

Check two things: unsubscribing takes one click, and the CRM records it so the person does not return to the list on the next import.

Data subject requests and breaches

People may ask what data you hold about them and ask you to correct or delete it. Under Article 12 you must respond within one month. For complex requests the period can be extended by two more months, but you have to tell the person within the first month. Decide who handles these requests and put the contact in your policy.

After a data breach, Article 33 requires notifying the CNPDCP without undue delay and, where feasible, within 72 hours. No notification is needed if the breach is unlikely to put people at risk. If the risk is high, Article 34 also requires informing the people affected. The 72 hours include weekends, so write the procedure down in advance.

Do you need a data protection officer?

Article 37 requires a DPO in three cases: a public authority does the processing; the core activity involves regular and systematic monitoring of people on a large scale; or the core activity involves large-scale processing of special categories of data. An ordinary service website usually does not need one. Someone in the company still has to own requests and incidents, and that decision is worth recording.

How Search Boost helps

We handle the technical side: a form with separate purposes, the banner and consent log, sending enquiries to the CRM with the unsubscribe flag, and connecting the CRM to advertising. We also prepare the technical details for your policy: which services receive data and where it is stored.

Policies, legal bases and retention periods are agreed with your data protection contact and a lawyer where needed. Technical setup does not replace a legal assessment or certify compliance.

Want to know what to change in your form and CRM? See how we check websites and configure consent. We will send a plan: which fields and consents your form needs and how to connect it to your CRM and advertising.

Search Boost editorial team. Sources checked on 29 October 2026: Law No. 195/2024, Law No. 284/2004 on electronic commerce. The demo example is illustrative. General information; legal assessment depends on the specific processing activities.

Let's find where enquiries are lost

Tell us what you advertise and how the path from click to enquiry works. We will reply with a verification plan — no guarantees.

If the form did not send, call or email us: +373 78 155 277 · [email protected]

The form requires JavaScript. Call or email us:

+373 78 155 277 · [email protected]