POS Buying Guides

POS Data Security for Singapore Businesses: PDPA, Card Data and Access

Your POS holds card payments, customer details and staff records. This guide explains the rules that apply and the practical steps that make the biggest difference.

Padlock resting on a laptop keyboard

Key takeaways

  • Your POS holds card payments, customer contact details and staff records, so both PCI DSS and the PDPA are relevant.
  • Integrated card terminals keep card data away from your POS and staff, which reduces what you have to protect.
  • Most practical risk comes from shared logins, weak passwords, unmanaged devices and open Wi-Fi. Fix those first.
  • Have a written incident plan. If a personal data breach is notifiable, PDPC must be told within 3 calendar days of that assessment.

This is general information, not legal or security advice. It summarises published guidance from the PCI Security Standards Council, PDPC and the Cyber Security Agency of Singapore (CSA), checked in September 2026, and applies it to a typical restaurant, café or shop. Speak to your payment provider and a qualified adviser for your own setup.

What POS data needs protecting

A modern POS is more than a till. Depending on how you use it, it can hold:

  • Payment data: card transactions, refunds and settlement records.
  • Customer data: names, mobile numbers, emails, birthdays, order history, loyalty points and stored value.
  • Staff data: names, logins, shift records and sales by staff member.
  • Business data: menu and recipe costs, sales reports, supplier prices and cash records.

Each has a different owner, risk and rule. Card data is covered by the payment industry’s standard. Personal data is covered by the PDPA. Business data is yours to protect because losing it hurts the business.

PCI DSS basics for merchants

The PCI Security Standards Council says PCI DSS was developed “to encourage and enhance payment card account data security and facilitate the broad adoption of consistent data security measures globally”. It “provides a baseline of technical and operational requirements designed to protect payment account data”.

The Council says PCI DSS applies to entities that store, process or transmit cardholder data or sensitive authentication data, or could affect the security of the cardholder data environment, “including merchants, processors, acquirers, issuers, and service providers”. So if you accept cards, PCI DSS is relevant to your business.

The Council also notes that whether an entity must comply with or validate compliance “is at the discretion of organizations that manage compliance programs, such as a payment brand, acquirer, or other entity”. In practice, that means your acquiring bank or payment provider tells you what you need to do, which may include a self-assessment. Ask them directly, and keep their answer on file.

Why integrated terminals reduce card-data exposure

The less card data your business touches, the less you have to secure. With an integrated card terminal, the customer taps or inserts their card at the terminal, the terminal handles the card details with the payment provider, and the POS receives the approval result and amount. Your POS software and your staff generally do not see or store the full card number.

Compare that with keying card numbers into a computer, writing them on order slips for phone orders, or storing them in a spreadsheet to charge later. Each creates card data that you then have to protect. Good habits:

  • Never write down or photograph card numbers.
  • Take card payments on the terminal or a hosted payment page, not by keying numbers into your own systems.
  • Check terminals regularly for tampering, and know who is allowed to service them.
  • Keep receipts that show only masked card numbers.

ChaChaCha supports PayNow, PayLah!, NETS, Visa/Mastercard and GrabPay through DBS, UOB and 2C2P, and our self-order kiosk has a built-in card terminal. For more on terminal options, see our guide to payment terminals in Singapore and our POS payments page.

PDPA obligations for POS data

Customer and staff details in your POS are personal data. PDPC’s Advisory Guidelines on Key Concepts in the PDPA say organisations must make reasonable security arrangements to protect personal data in their possession or control. The same guidelines say a data intermediary, such as a software vendor processing data for you, must notify you of any data breach it detects.

Key points for a POS owner:

  • Appoint a DPO. PDPC’s DPO guide calls this the “mandatory first step”, and the DPO’s contact details must be publicly available.
  • Know the breach rules. PDPC’s data breach page says a breach is notifiable if it is likely to cause significant harm or affects 500 or more individuals. You must notify PDPC no later than 3 calendar days after determining that it is notifiable.
  • Know the penalties. PDPC’s DPO guide notes fines of up to S$1 million or 10% of annual Singapore turnover (for turnover exceeding S$10 million), whichever is higher.
  • Collect only what you need, and keep it only as long as you need it.

Our PDPA guide for F&B covers consent, marketing messages, NRIC limits and retention in detail.

Staff access and permissions

Shared logins are one of the most common weaknesses in small businesses. If everyone uses the same PIN, you cannot tell who issued a refund, deleted an item or exported a customer list.

  • One login per person. Give every staff member their own PIN or account.
  • Least privilege. Cashiers take orders and payments. Supervisors approve voids, discounts and refunds. Only owners or managers export customer data or change settings.
  • Remove leavers the same day. Disable accounts when someone leaves, and change any shared codes they knew.
  • Review regularly. Check the user list monthly and remove anyone who should not be there.

ChaChaCha includes staff permissions, so you can set what each role can do. Our guide to restaurant cash control and theft prevention explains how to set permissions for voids, discounts and refunds, and how to use POS reports to spot unusual patterns.

Passwords and two-factor authentication

Back-office accounts can see sales, customer lists and settings for every outlet, so protect them more strongly than a till PIN.

  • Use a long, unique password for the POS back office, and don’t reuse it for email or social media.
  • Use a password manager rather than a notebook by the register.
  • Turn on two-factor authentication (2FA) wherever your POS, email, payment provider and accounting software offer it. Ask each vendor, including us, to confirm what 2FA options are available for your account.
  • Protect the email account linked to your POS. Anyone who controls it can often reset your POS password.
  • Be wary of calls or messages asking for login codes. CSA’s website lists the 24/7 ScamShield Helpline at 1799 if you are unsure whether something is a scam.

Device security, Wi-Fi and backups

Devices

  • Keep POS tablets, terminals and back-office computers updated.
  • Use POS devices only for the POS. No personal browsing, games or unknown apps.
  • Set a screen lock on tablets and phones used for the POS or back office.
  • Keep an inventory of every device and who holds it, and know how to sign a lost device out.

Wi-Fi separation

Customer Wi-Fi and your business network should be separate. A guest on the same network as your POS and printers is an unnecessary risk. Most business routers can run a separate guest network. Our restaurant Wi-Fi and network set-up guide covers the layout in more detail. Change the router’s default admin password, and don’t print the business network password on the menu.

Backups and cloud

With a cloud or web-based POS, sales and settings are stored online rather than only on one machine in the shop, so a stolen or broken tablet does not mean lost records. ChaChaCha is a web/hybrid POS that keeps taking orders if the internet drops and syncs later. Our guide to cloud vs traditional POS explains the trade-offs.

Even with cloud storage, export key reports regularly, such as sales summaries and customer lists, and store them securely with restricted access. Ask each vendor, including us, where data is hosted, how it is backed up and how long it is kept.

CSA resources for SMEs

The Cyber Security Agency of Singapore’s Cyber Essentials page says “Small and Medium Enterprises (SMEs) are also prime targets for cyberattacks”. CSA’s Cyber Essentials certification is intended to help organisations “implement fundamental cybersecurity measures to protect against common threats”. CSA says the enhanced certification now covers Cloud Security, Operational Technology (OT) Security and AI Security, and describes it as designed for businesses of all sizes and a “practical and affordable” way to strengthen cybersecurity.

The same section of CSA’s site links to related programmes, including Cyber Trust and CISO as-a-Service for developing a cybersecurity health plan. Even if you don’t pursue certification, the Cyber Essentials measures are a useful checklist for a small business.

Incident response: what to do if something goes wrong

Write a one-page plan now, while things are calm. If you suspect a breach, such as a lost device, an unknown login or a leaked customer list:

  1. Contain it. Disable the affected accounts, change passwords, sign out lost devices and disconnect anything compromised.
  2. Tell your vendors. Contact your POS vendor and payment provider straight away. If card data may be involved, your acquirer will tell you what to do next.
  3. Assess it. Work out what data was affected and how many people. Record what you find and when.
  4. Decide whether it is notifiable. If it is likely to cause significant harm or affects 500 or more individuals, notify PDPC no later than 3 calendar days after that assessment, and notify affected individuals as PDPC’s guidance requires.
  5. Fix the cause. Update permissions, passwords, devices or processes so it doesn’t happen again.
  6. Review. Update your plan and brief staff.

Our restaurant emergency plan covers outages and other disruptions alongside security incidents.

POS data security checklist

Area Action How often
Card payments Take cards on the terminal only; never write down card numbers Always
PCI DSS Ask your acquirer what compliance steps apply to you Yearly, or when you change provider
Terminals Check for tampering and unknown devices Weekly
PDPA Appoint a DPO and publish contact details Once, then keep updated
Staff access One login per person; permissions by role Review monthly
Leavers Disable accounts and change shared codes Same day
Passwords and 2FA Unique back-office passwords; 2FA where offered Check quarterly
Devices Updates, screen locks, POS-only use, device list Monthly
Wi-Fi Separate guest network; change router admin password Once, then check yearly
Backups Export key reports and store securely Monthly
Vendors Data intermediary terms and breach notice in the contract At signing and renewal
Incident plan One-page plan with contacts and PDPC steps Review yearly

Choosing a new system? Read our guide to POS contract terms and our POS buying checklist, then talk to us about how ChaChaCha handles permissions and payments for your outlet.

Web Admin

Written by Web Admin

Frequently asked questions

Does a small restaurant need to comply with PCI DSS?

If you accept cards, PCI DSS is relevant. The PCI Security Standards Council says it applies to entities that store, process or transmit cardholder data, including merchants. It also says whether you must comply or validate compliance is set by organisations such as payment brands and acquirers. Ask your acquirer or payment provider exactly what steps apply to your business.

How do integrated card terminals improve POS security?

With an integrated terminal, the card is tapped or inserted at the terminal, which handles the card details with the payment provider. The POS receives the approval and amount, so your software and staff generally do not see or store full card numbers. That reduces the card data you have to protect compared with keying numbers in or writing them down.

What does the PDPA require for POS customer data?

PDPC guidance says organisations must make reasonable security arrangements to protect personal data, appoint a Data Protection Officer and publish their contact details. If a breach is likely to cause significant harm or affects 500 or more people, you must notify PDPC no later than 3 calendar days after assessing it as notifiable. Our PDPA guide for F&B covers consent and marketing.

How should I set staff permissions on a POS?

Give every staff member their own login, and set permissions by role. Cashiers take orders and payments, supervisors approve voids, discounts and refunds, and only owners or managers export customer data or change settings. Disable accounts the day someone leaves and review the user list monthly. ChaChaCha includes staff permissions so you can set what each role can do.

Should customer Wi-Fi be separate from the POS network?

Yes. Put guests on a separate guest network so they cannot reach your POS, printers or back-office computers. Most business routers support this. Also change the router's default admin password and avoid printing the business network password where customers can see it. Check the setup once a year or whenever you change routers or internet providers.

What is CSA Cyber Essentials and is it relevant to small businesses?

Cyber Essentials is a certification from the Cyber Security Agency of Singapore to help organisations implement fundamental cybersecurity measures against common threats. CSA says SMEs are also prime targets for cyberattacks and describes the certification as designed for businesses of all sizes. Even without certifying, its measures are a useful checklist for a restaurant or shop.

Can I store customers' NRIC numbers in my POS?

Usually not. PDPC's advisory guidelines say organisations should generally not collect, use or disclose NRIC numbers or copies of NRIC cards unless the law requires it or it is necessary to verify identity to a high degree of accuracy. Loyalty programmes, reservations, receipts and queue alerts do not need an NRIC. Use a mobile number or email, or a membership number you issue, and remove any NRIC numbers already sitting in old customer records.

How long should I keep customer data in my POS?

The PDPA does not set a fixed period. You should stop keeping personal data once it is no longer needed for the purpose it was collected for, or for a business or legal reason. Sales and tax records are different: IRAS expects business records to be kept for at least five years. A practical approach is to keep transaction records for the tax period but delete or anonymise inactive loyalty and marketing contacts on a set schedule.

Is it safe for staff to use their own phones for the POS?

It can be, with controls. Each person needs their own login, the phone needs a screen lock, and you need a way to sign the device out when the person leaves or loses the phone. Avoid letting staff export customer lists or reports to personal devices. For busy outlets, business-owned handhelds that stay at the outlet are easier to manage, update and keep separate from personal apps and messages.

Does CCTV footage at the counter fall under the PDPA?

Yes. CCTV footage that shows identifiable people is personal data, so the PDPA applies. Put up notices telling people that CCTV is in operation, position cameras so they cover the till and payment area without recording PIN entry on card terminals, limit who can view and copy recordings, and delete footage on a regular schedule unless you need it for an incident. Treat footage access like POS permissions.

See ChaChaCha running in your business

Book a 20-minute walkthrough. We'll set up your menu or catalogue and your payments so you can see how it would run on day one.