NotiSynk legal information
WhatsApp Messaging and Consent Policy
How reminders reach a Client on WhatsApp
- Version:
- 1.0
- Effective date:
- 2026-08-16
NotiSynk can send reminders to a Client on WhatsApp using the Meta Platforms (WhatsApp Business Platform). This policy describes how that works, what consent is required, and what the delivery information in the Service does and does not prove.
1. What is sent
WhatsApp is used for operational reminders about a Client Subscription or a session: that a Client Subscription is approaching its end date, or that a session is due. It is not used for advertising.
Messages are sent as templates that have been submitted to and approved by the provider before use. A Professional supplies the values that fill the template, not free-form message text. Template approval is controlled by the provider, so a template can be rejected or withdrawn for reasons outside NotiSynk's control.
Messages are sent from a single NotiSynk sender shared by every Workspace. That is why the rules below are enforced strictly: misuse by one Workspace affects the delivery of every other Workspace.
2. Consent
A Client must have active consent before NotiSynk will send them a WhatsApp message. A Client with no consent record, or whose consent has been withdrawn, is never sent one.
Consent is recorded in one way: the Professional confirms in the Service that the Client agreed to receive WhatsApp reminders. NotiSynk does not currently have a flow through which a Client gives consent to NotiSynk directly. That places the responsibility squarely on the Professional.
- Ask the Client, in a way they understand, before enabling WhatsApp reminders for them.
- Only confirm consent in NotiSynk where it has actually been given. Confirming it without asking is a breach of the Acceptable Use Policy.
- Keep your own record of when and how consent was given, in case you are ever asked to show it.
- Stop sending as soon as a Client asks you to, whether they tell you through WhatsApp, in person, or any other way.
3. Withdrawing consent
A Client can withdraw consent at any time. When consent is withdrawn in the Service, WhatsApp messages to that Client stop.
Changing a Client's phone number withdraws their consent automatically. This is deliberate: consent was given for the old number, and NotiSynk will not carry it over to a number the Client may not have agreed to be contacted on. To resume WhatsApp reminders after a number change, ask the Client again and record the new consent.
A Client can also block the sender in WhatsApp itself, which stops delivery regardless of what is recorded in NotiSynk.
4. What the delivery information means
The Service shows the state of each reminder. For WhatsApp, the later states come from status callbacks sent by the provider, and NotiSynk records only what the provider reports.
| State | What it means |
|---|---|
| Queued | Created and waiting for its sending attempt |
| Sent | Handed to the provider and accepted by it. Not confirmation that it arrived |
| Delivered | The provider reported that it reached the Client's device |
| Read | The provider reported that it was opened. This is the provider's report, not proof that the Client read or understood it |
| Failed | The attempt did not succeed. A safe reason is shown where one is available |
A message that stays at Delivered and never becomes Read is normal. It means the Client has not opened it, which is not a failure. NotiSynk never infers Delivered from Sent, and never infers Read from Delivered.
Email works differently. Email is handed to the mail provider over SMTP, which returns no delivery or read callbacks, so an email reminder can only ever reach Sent. NotiSynk does not track whether an email was delivered or opened, and no part of the Service should be read as saying otherwise.
5. What is not guaranteed
- NotiSynk does not guarantee that a message will be delivered, read or acted on.
- The provider controls delivery, template approval, sending limits and the reputation of the sender, and can restrict or suspend any of them.
- A message can fail for reasons NotiSynk cannot see or fix: an invalid or reassigned number, a device that is offline, a Client who has blocked the sender, or a provider restriction.
- A reminder is a convenience. It is not a substitute for your own record of what you agreed with your Client.
6. What the provider receives
To send a message, Meta Platforms (WhatsApp Business Platform) receives the Client's phone number, the identifier of the approved template and the values that fill it. It returns a message identifier and, afterwards, status callbacks. It keeps its own records under its own retention rules, which NotiSynk does not control.
The Subprocessors notice lists this provider and the Privacy Policy explains how the information is handled on NotiSynk's side.
7. Misuse
Sending advertising through WhatsApp reminders, confirming consent that was never given, or messaging people who are not your Clients puts the shared sender at risk and can be unlawful. Lebanese law prohibits sending advertising to someone who has not agreed to receive it, unless the address was lawfully obtained through a previous dealing with them.
NotiSynk may block a message, disable WhatsApp for a Workspace, or suspend the account where this policy or the Acceptable Use Policy is breached. To report misuse, write to info@notisynk.com.
Change log
- v1.02026-08-16First published version. Describes the implemented WhatsApp behaviour: the central sender, approved templates, active Client consent, consent withdrawal on a phone-number change, and the provider delivery states reported by Meta.