Where your data sits and who can reach it.
5 answers
Every record is scoped to your company; staff see only what you grant.
Contacts, chats, templates and campaigns belong to your company account and are not shared between customers of the platform.
Inside your account, access is controlled feature by feature, so an inbox agent need never see billing or API keys.
Message delivery and the WABA are Meta's; your CRM records are ours.
WhatsApp messages travel through Meta's infrastructure under Meta's terms. VedLink stores the conversation record, your contacts and your business data so you can search and act on them.
Your WhatsApp Business Account stays yours. If you ever leave, the number and the WABA go with you.
Collect consent before you message, and honour a stop request immediately.
Only message people who gave you their number for this purpose. Give marketing templates an opt-out button, and act on it: Meta treats ignored stop requests as a policy problem, and customers treat them as a reason to block.
An opted-out contact can be tagged so campaigns skip them while service replies still work.
Delete a contact from its record; deleting removes related data with it.
Deleting a contact removes the associated conversation records too, so treat it as permanent from your side.
For a bulk removal request, contact us and we will confirm scope before anything is run.
Server-side only, one key per integration, revoke when a vendor leaves.
Never put a key in front-end code or a public repository. If one is exposed, revoke it in the app, that takes effect immediately, and issue a new one.
The activity log shows what a key has been doing, which is the fastest way to check whether an exposed key was used.
Tell us the number, the time and what you expected. That is usually enough for us to spot it.