On 12 November 2026, the Personal Data Protection Commission and the Cyber Security Agency of Singapore issued a Joint Advisory on Data Protection Risks Arising from Insecure APIs. If you run a Singapore trade or service business that collects leads online, the advisory’s focus on insecure APIs applies directly to the hidden connections behind your website forms, Meta lead ads and WhatsApp inquiries.
Most owners never see these connections. A form on your site sends a customer’s name, mobile number and HDB unit address to a CRM. A Meta lead form pushes the same details through a connector tool. A booking app forwards the job sheet to your technician. Each of those hops is an API call or a webhook. Many of them were set up years ago by an agency or freelancer who has since moved on.
This post covers one job. You will list every connection that carries customer details, then close the ones nobody is watching.
What CSA and PDPC published on 12 November 2026
The facts are simple. The PDPC and CSA released a joint advisory on data protection risks from insecure APIs. CSA published it on its advisories page as advisory AD-2026-16, and the full advisory is available as a downloadable PDF. You can read it on the CSA advisory page for AD-2026-16 on insecure APIs.
We are not going to summarize the PDF line by line here. Download it and give it to whoever manages your website and CRM. What matters for this post is the signal. Singapore’s data protection regulator and its national cybersecurity agency have chosen to speak together, and their topic is the data that moves between systems.
That is exactly where small-business lead data lives.
Why the PDPC API advisory matters to a Singapore trade business
You might think API security is a problem for banks and big platforms. It isn’t only theirs. Under the PDPA, every organization that collects personal data has to make reasonable security arrangements to protect it. Size doesn’t change that. An aircon servicing company, a renovation contractor and a mover all collect the same kinds of details: who the customer is, how to reach them and where they live.
Look at what a single lead from your site holds. There is a full name and a mobile number. There is usually a block, street and unit number. Some forms include photos of the customer’s home. Notes may say when the house will be empty, or that an elderly parent lives alone. Put a few months of those records in one place and you have exactly what someone with bad intentions wants.
Your website might be locked down well. That protection does not cover the copy of the data sitting in a spreadsheet tool, the CRM’s own API, or a webhook URL that anyone holding the link can post to. PDPA lead form security has to cover the whole route, not just the form people see.
Where your lead data actually travels
Before you can close anything, you need a map. Here are the routes we see most often in Singapore trade businesses.
Website forms
Your contact or quote form usually does more than send an email. It may post to a CRM, add a row to Google Sheets, ping a Telegram or Slack group, and fire a conversion to Google Ads or Meta. Each of those is a separate connection with its own key or token.
Meta lead ads
Leads from Facebook and Instagram lead forms sit inside Meta until something pulls them out. That something is often a connector app or a custom script set up by a past agency. Each one holds permission to read your lead data.
Google Ads lead form assets
If you have run lead form assets on Google Ads, the leads can be sent out through a webhook URL with a key. If nobody changed that key when your old agency left, it still works.
WhatsApp inquiries
Many Singapore customers would rather WhatsApp you than fill in a form. If you use the WhatsApp Business Platform through a provider, or a shared-inbox tool, customer chats and phone numbers pass through that provider’s systems and often onward into your CRM.
Booking and job tools
Scheduling apps, quoting tools and job management software often receive the customer’s address and job details from your CRM. Then they send updates back the other way. That is two directions and two sets of credentials to manage.
In Singapore businesses, personal data sent through webhooks tends to spread quietly. Each tool was added to fix one problem, and nobody ever drew the full picture.
How to audit every connection in one afternoon
You don’t need a security firm to start. You need a spreadsheet and admin access to your tools. Here is the order we use.
Steps
- List every tool that touches a lead. Start with your website, your form plugin, your CRM, Meta Business Suite, Google Ads, your WhatsApp setup, your booking tool and any connector like Zapier or Make. Write each one in a row.
- Open the integrations or connected apps section of each tool. Most CRMs and form tools have a page that lists API keys, connected apps and webhooks. Screenshot it. Add every connection to your sheet, with where the data goes.
- Write down which fields each connection carries. Name, phone, email, address, photos, notes. Any connection that carries an address or free-text notes needs extra attention.
- Mark who set it up and who owns the login. If the answer is "the old agency" or "not sure," flag it red.
- Check Meta's business integrations. In your Meta business settings, review which apps and partners have access to your Page and lead forms. Remove anything you don't recognize or no longer use.
- Review users and partners in Google Ads. Remove people and accounts who no longer work with you. Then rotate the webhook key on any lead form asset.
- Look at your connector tool's run history. In Zapier or Make, open each active automation. If it sends leads to a sheet or inbox nobody reads, switch it off.
- Rotate every key you flagged red. Generate a new API key or webhook secret, update the one connection that should keep working, then delete the old key.
- Test one real lead end to end. Submit a test form, a test Meta lead and a test WhatsApp message. Confirm each one arrives only where it should.
While you are checking the website itself, run it through our free security headers checker. It won’t audit your APIs. It will show whether the site that hosts your forms has basic browser protections switched on, and your web person should fix any gaps it finds.
Closing the doors old agency setups left open
The audit will turn up problems. These are the ones we find most often in Singapore lead setups, and how to deal with each one.
Shared logins. An agency set up your CRM using its own email address, or everyone at the agency used one password. Move ownership to an email on your own domain. Give anyone outside your company a separate user that you can remove.
Webhook URLs with no secret. Some form tools send leads to a URL that accepts anything posted to it. If the receiving end doesn’t check a secret or signature, anyone who finds the URL could read or inject data. Turn on request verification where the tool offers it. Where it doesn’t, replace the connection.
Keys stored in the website code. Old setups sometimes paste a CRM API key straight into a page or a tracking script, where anyone viewing the source can see it. Ask your web person to search the site for anything that looks like a key or token. Move it to the server side, then rotate it.
Spreadsheet copies. A sheet set up “just as a backup” can end up holding every lead you’ve had since you launched. Most of the time nobody has checked who it is shared with. Lock the sharing down, delete rows you no longer need, or retire the sheet.
Over-collection. If your quote form asks for things you don’t use, stop asking. Every field you remove is one less thing to protect. Don’t collect NRIC numbers on a lead form.
Tracking scripts that grab form fields. Some older tag setups capture form values and send them to analytics or ad platforms. That is a data leak in its own right. If your tag manager has grown messy over the years, our Google Tag Manager setup and cleanup service exists for exactly this.
CRM integration data protection in Singapore isn’t about buying new software. It comes down to knowing what is connected, who controls it and why it is still switched on.
Keeping lead tracking accurate once the doors are closed
Owners often worry that shutting off old connections will break their reporting. It can, if you do it blind. Say you delete a connector on Friday. By Monday, Google Ads has stopped receiving conversions and starts optimizing on bad signals.
The fix is to rebuild deliberately. Decide which one system is your source of truth for leads, usually the CRM. Send ad conversion data from there, using only the fields the ad platform needs, instead of letting every tool talk to every other tool. You end up with fewer connections, cleaner attribution and less data in places it shouldn’t be.
This is the kind of work we do in our ads to CRM attribution setup. We map every route a lead takes, cut the ones that aren’t needed, and connect your ads to real booked jobs in a way you can explain to a regulator or a customer.
Frequently asked questions
Does the PDPC and CSA advisory apply to a small aircon or renovation business? The PDPA applies to organizations that collect personal data, and small trade businesses are included. An advisory is guidance rather than a new law, but it shows what the regulators are paying attention to. If your leads move through APIs and webhooks, it is relevant to you.
My old agency still has access to our Meta and Google accounts. Is that a problem? It can be. Anyone with access can see or export your lead data. Review the users and partners in both platforms, remove those who no longer work with you, and rotate any webhook keys they may have seen.
We get most inquiries by WhatsApp, not forms. Do we still need to audit anything? Yes. If you use a provider or shared-inbox tool for WhatsApp, customer numbers and chats pass through it and often into your CRM. List those connections the same way you would for a form.
Will turning off old Zapier or Make automations break our lead tracking? It might, if one of them was quietly sending conversions to your ad accounts. Check each automation’s history first. Rebuild the one route you actually need before you switch the others off.
Who in our company should own this? Whoever acts as your Data Protection Officer under the PDPA should own the list of connections. They don’t need to be technical. They need the map, the admin logins and a web person they can call.
How often should we repeat the connection audit? Repeat it whenever you add a tool, change agencies or launch a new lead source. Even if none of those happen, open the integrations pages a couple of times a year to catch anything that crept in.
Your next step
This week, open your CRM’s integrations page and your Meta business settings. Screenshot every connected app, key and webhook, and flag any you can’t name or that an old agency set up. That one list will tell you how much work is ahead.
If you’d like us to go through the list with you and close what shouldn’t be open, Chat with us on WhatsApp.