{"id":202,"date":"2026-07-20T12:36:58","date_gmt":"2026-07-20T12:36:58","guid":{"rendered":"https:\/\/oasiswebasia.com\/blog\/pdpa-data-inventory-how-to-singapore-sme\/"},"modified":"2026-07-20T12:36:58","modified_gmt":"2026-07-20T12:36:58","slug":"pdpa-data-inventory-how-to-singapore-sme","status":"publish","type":"post","link":"https:\/\/www.oasiswebasia.com\/blog\/pdpa-data-inventory-how-to-singapore-sme\/","title":{"rendered":"The PDPA Data Inventory: How to Find Out What Customer Data You&rsquo;re Actually Holding (Before Someone Else Does)"},"content":{"rendered":"<p>Quick test. Right now, without looking anything up: could you list every place your business holds customers&rsquo; personal data? Every form, every spreadsheet, every inbox, every old system, every vendor?<\/p>\n<p>If you hesitated, you&rsquo;re in good company &mdash; and in trouble worth fixing. When we wrote about Singapore&rsquo;s biggest data breach, the lesson wasn&rsquo;t sophisticated hacking; it was a company that lost track of what it owned. One forgotten file, 5.9 million records. And the PDPC&rsquo;s verdict &mdash; <em>it could have been prevented<\/em> &mdash; starts with a discipline almost no SME actually practises: the <strong>data inventory<\/strong>.<\/p>\n<p>Here&rsquo;s the thing: under the PDPA you&rsquo;re accountable for the personal data in your possession <em>or under your control<\/em> &mdash; whether or not you remember having it. You can&rsquo;t protect what you don&rsquo;t know you have, you can&rsquo;t answer a customer&rsquo;s access request about it, and when the breach clock starts ticking you can&rsquo;t assess what leaked. The inventory is the foundation everything else stands on. The good news: for a typical SME it&rsquo;s a spreadsheet and an afternoon or two. Here&rsquo;s exactly how to do it.<\/p>\n<h2>Step 1: Hunt the data &mdash; including where it hides<\/h2>\n<p>Grab a spreadsheet and start listing every <em>place<\/em> personal data lives. Don&rsquo;t overthink &ldquo;personal data&rdquo; &mdash; if it can identify a person (name, phone, email, NRIC, photo, address, purchase history), it counts.<\/p>\n<p>The obvious places first: your website&rsquo;s contact and checkout forms, your CRM, your accounting system, your e-commerce platform, your email marketing list, your booking system.<\/p>\n<p>Now the places that actually cause breaches &mdash; the hiding spots:<\/p>\n<ul>\n<li><strong>The website&rsquo;s back end.<\/strong> Form submissions often sit in the CMS database forever, long after they&rsquo;ve been emailed to you. If your site was built years ago, there&rsquo;s a plugin quietly storing every enquiry since launch.<\/li>\n<li><strong>Inboxes.<\/strong> Every quotation, CV, and customer email attachment. Email is most SMEs&rsquo; largest, least-protected database.<\/li>\n<li><strong>Spreadsheets and exports.<\/strong> The customer list someone downloaded &ldquo;temporarily&rdquo; in 2023, still sitting in a Downloads folder or shared drive.<\/li>\n<li><strong>Chat apps.<\/strong> WhatsApp threads with customer details, photos of NRICs, delivery addresses &mdash; on staff members&rsquo; personal phones.<\/li>\n<li><strong>Old systems.<\/strong> The previous CRM you migrated off but never emptied. The defunct app. The old website still live on a subdomain. (This is precisely the RedDoorz failure mode: &ldquo;defunct&rdquo; is not a security status.)<\/li>\n<li><strong>Your vendors.<\/strong> The payroll provider, the marketing agency, the developer with database access, the cloud storage. Under the PDPA, data your vendors process for you is still your responsibility.<\/li>\n<li><strong>Paper.<\/strong> Sign-in books, printed invoices, forms in a filing cabinet.<\/li>\n<\/ul>\n<p>A practical trick for completeness: instead of asking &ldquo;where is data stored?&rdquo;, walk through your customer&rsquo;s journey &mdash; enquiry, quote, purchase, delivery, support, marketing &mdash; and note every point where information about them gets captured or copied. Data follows process; trace the process and you find the data.<\/p>\n<h2>Step 2: Record six things about each entry<\/h2>\n<p>For every location you found, fill in six columns. This is the whole inventory &mdash; resist the urge to make it fancier:<\/p>\n<ol>\n<li><strong>What<\/strong> personal data is there (names, contacts, payment details, NRIC, etc.)<\/li>\n<li><strong>Whose<\/strong> &mdash; customers, staff, job applicants, suppliers<\/li>\n<li><strong>Why<\/strong> you have it &mdash; the purpose it was collected for<\/li>\n<li><strong>Who can access it<\/strong> &mdash; which staff, which vendors<\/li>\n<li><strong>How long<\/strong> you keep it &mdash; and whether anything is ever actually deleted<\/li>\n<li><strong>How it&rsquo;s protected<\/strong> &mdash; password? MFA? Encryption? Or &ldquo;it&rsquo;s just&hellip; there&rdquo;?<\/li>\n<\/ol>\n<p>Two of these columns will hurt, and that&rsquo;s the point. &ldquo;Why&rdquo; exposes data you collected with no real purpose &mdash; and under the PDPA&rsquo;s purpose limitation, that&rsquo;s data you shouldn&rsquo;t be holding. &ldquo;How long&rdquo; exposes the honest answer at most SMEs: <em>forever, by default<\/em> &mdash; which collides with the retention limitation obligation to stop keeping data once its purpose is served.<\/p>\n<h2>Step 3: Act on the three ugly findings<\/h2>\n<p>Every first inventory produces the same three discoveries. Deal with them in this order:<\/p>\n<p><strong>Delete what you don&rsquo;t need.<\/strong> Old enquiries, ex-customers from years back, CVs from closed roles, that 2023 export. This is the highest-value security action there is, and it&rsquo;s free: <strong>data you don&rsquo;t hold can&rsquo;t be breached, and you can&rsquo;t be fined for mishandling data you&rsquo;ve deleted.<\/strong> Minimisation beats every firewall.<\/p>\n<p><strong>Lock down what you keep.<\/strong> Anything sensitive sitting without MFA, shared logins that five people (and one ex-employee) know, vendor access nobody remembers granting &mdash; fix by risk, worst first. Your inventory&rsquo;s column six is now a prioritised to-do list.<\/p>\n<p><strong>Close the orphans.<\/strong> The old systems, dead subdomains, and forgotten apps get properly emptied and retired &mdash; not &ldquo;we don&rsquo;t use it anymore,&rdquo; but actually shut down with the data removed. RedDoorz is the S$74,000 case study in the difference.<\/p>\n<h2>Step 4: Keep it alive (this is where everyone fails)<\/h2>\n<p>An inventory done once is a photograph; the business keeps moving. Three habits keep it true:<\/p>\n<ul>\n<li><strong>Name an owner.<\/strong> If you have a Data Protection Officer &mdash; which the PDPA requires every organisation to designate &mdash; the inventory is naturally theirs. In a small SME that&rsquo;s often the owner or office manager wearing the DPO hat, and that&rsquo;s fine; what matters is that it&rsquo;s <em>someone&rsquo;s job<\/em>.<\/li>\n<li><strong>Update on trigger events<\/strong>, not a schedule you&rsquo;ll ignore: new tool adopted, new vendor engaged, staff member leaves (revoke access the same week), new form added to the website.<\/li>\n<li><strong>Re-run the hunt annually.<\/strong> One afternoon a year to catch what crept in. Put it next to your tax filing so it actually happens.<\/li>\n<\/ul>\n<h2>What this buys you<\/h2>\n<p>For a few hours of unglamorous work, the inventory quietly solves half your PDPA obligations at once. It&rsquo;s the backbone of the accountability obligation (you can actually demonstrate what you hold and why). It makes a customer&rsquo;s access or correction request answerable in minutes instead of a panicked week. It&rsquo;s what lets you meet the breach-notification clock &mdash; you can only assess &ldquo;what leaked and how many people&rdquo; within three days if you knew what was where <em>before<\/em> the incident. And it converts your security spending from guesswork into targeting: protect the crown jewels you&rsquo;ve now located, not everything vaguely.<\/p>\n<p>There&rsquo;s a softer payoff too. Customers increasingly ask suppliers &mdash; especially B2B &mdash; how their data is handled. &ldquo;Here&rsquo;s our data inventory and retention policy&rdquo; is a trust signal most of your competitors cannot produce.<\/p>\n<p>(Usual honesty: this is practical guidance, not legal advice. For edge cases &mdash; NRIC handling rules, cross-border transfers, sector-specific requirements &mdash; check the PDPC&rsquo;s guides or ask a professional.)<\/p>\n<h2>Where Oasis Web Asia comes in<\/h2>\n<blockquote>\n<p>A surprising amount of any SME&rsquo;s hidden data lives in its website and digital systems &mdash; the form plugin hoarding every submission since 2019, the staging site nobody remembers, the developer access never revoked. When we build or take over a site, mapping and minimising that data footprint is part of the job: forms that don&rsquo;t hoard, retention that actually deletes, access that gets revoked when people move on, and a clear record of what lives where. It&rsquo;s the same evidence-first approach behind the web development Singapore SMEs trust us with &mdash; and if you&rsquo;d like a second pair of eyes on the digital half of your inventory, we can tell you quickly where your forgotten files are.<\/p>\n<p>If step one of this guide already surfaced something that made you wince, that&rsquo;s exactly the conversation we like to have.<\/p>\n<p><strong><a href=\"https:\/\/www.oasiswebasia.com\/contact\">Start a conversation &rarr;<\/a><\/strong> &mdash; get a free consultation with our Singapore-based team.<\/p>\n<\/blockquote>\n","protected":false},"excerpt":{"rendered":"<p>Under the PDPA you&rsquo;re accountable for data you&rsquo;ve forgotten you hold. A practical, afternoon-sized guide to building your data inventory &mdash; and the hiding spots that cause breaches.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[20],"tags":[],"class_list":["post-202","post","type-post","status-publish","format-standard","hentry","category-data-privacy-pdpa"],"_links":{"self":[{"href":"https:\/\/www.oasiswebasia.com\/blog\/wp-json\/wp\/v2\/posts\/202","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.oasiswebasia.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.oasiswebasia.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.oasiswebasia.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.oasiswebasia.com\/blog\/wp-json\/wp\/v2\/comments?post=202"}],"version-history":[{"count":0,"href":"https:\/\/www.oasiswebasia.com\/blog\/wp-json\/wp\/v2\/posts\/202\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.oasiswebasia.com\/blog\/wp-json\/wp\/v2\/media?parent=202"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.oasiswebasia.com\/blog\/wp-json\/wp\/v2\/categories?post=202"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.oasiswebasia.com\/blog\/wp-json\/wp\/v2\/tags?post=202"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}