Privacy Policy
Effective date: 1 June 2026 · Last updated: 12 October 2026 (who is responsible for your data, and transfers outside Malaysia)
TACNow is committed to protecting your privacy and complying with the Personal Data Protection Act 2010 (PDPA) of Malaysia.
TACNow is operated by WebbyX Sdn Bhd (202301001788). This policy covers two kinds of personal data: information about you as a TACNow customer, and the phone numbers and codes you send through our API to your own users. For the first kind, WebbyX Sdn Bhd is the data controller. For the second kind, you decide what is sent and to whom, so you are the data controller, and we process it on your behalf to deliver the message.
1. Information We Collect
Account data: When your account is set up, or you are invited to one, we collect your email address and your organisation's name. Passwords are stored only in hashed form.
Billing details: To invoice your top-ups, we collect your organisation's company name, SSM registration number, tax identification number (TIN), SST registration number (if you have one), billing address and billing email. When a top-up is credited, these details are copied onto it so that WebbyX Sdn Bhd, the company that operates TACNow, can issue the tax invoice. We also record the email address of the person who requested each top-up.
Payment data: If you pay by bank transfer, we store the payment reference you give us. If you pay online by card, FPX or GrabPay where they are offered, you pay on a page hosted by Stripe: your card details and online banking credentials go to Stripe and are never received by TACNow. We pass Stripe the requesting member's email address and references for the top-up and your organisation, and we store what Stripe reports back: its reference numbers for the payment, the payment method type (for example, card or FPX), the amount paid, Stripe's fee, and any refund, dispute or payout linked to the payment.
API usage data: For each message you send, we record the project and API key used, the channel, the status and when it changed, any error, the amount charged and, for WhatsApp, the delivery status Meta reports (such as delivered or read). Our servers also log incoming requests, including the time, the address requested, the response code and the IP address.
Phone numbers, codes and message text (your end users): When you send an OTP, we receive the recipient's phone number and, for WhatsApp, the code. For SMS, we receive the message text you supply. Section 2 explains how we handle them.
Contact form: If you write to us through the contact form on our website, we keep your name, email address and message, and any company name or phone number you give us, so that we can reply.
Cookies: The console uses cookies to keep you signed in. We do not use advertising or analytics cookies.
2. Phone Numbers, Codes and Message Text
- Full phone numbers are kept only while a message is being sent. The number is stored encrypted (AES-256-GCM), and the encrypted copy is deleted as soon as the send succeeds or fails. After that we keep only:
- A one-way SHA-256 hash of the phone number
- The last 4 digits in masked form (e.g.
****6789) for your delivery logs
- WhatsApp codes are handled the same way: stored encrypted while the message is being sent, read once to send it, then deleted.
- SMS message text, including any code in it, is stored as you sent it. It is not separately encrypted in the way phone numbers and WhatsApp codes are, and it is deleted with the rest of the message record after 90 days (section 3).
A hashed phone number can still be matched against a known number, so we treat the hash and the masked digits as personal data too, and delete them on the same schedule.
3. Data Retention
Message records, including the phone number data kept with them, are automatically deleted 90 days after creation. A job runs every night to do this, and it needs no action from you or your users.
This covers everything kept about a message: the phone number hash, the masked digits, SMS message text, status and delivery details.
Backups: Our database is backed up every night and backups are kept for up to 30 days, so a deleted record can remain in a backup for up to 30 days after it is deleted.
Financial records (wallet transactions, top-ups with the billing details copied onto them, and payment records) are not deleted with message records. We keep them, including after an account is closed, for as long as tax and accounting law requires.
Account data (email addresses and organisation details) is retained while your account is open. When a member is removed from an organisation, their sign-in account is deleted, although their email address remains on any top-up they requested. To close your organisation's account, contact us.
Contact form enquiries are kept so that we can follow them up. We have not yet set a fixed period after which they are deleted.
4. How We Use Your Data
We use the data we collect to:
- Provide and operate the Service, including delivering your messages by WhatsApp or SMS
- Process top-ups and payments, and give WebbyX Sdn Bhd what it needs to issue your tax invoices
- Send service emails: account and sign-in emails, top-up updates and low-balance alerts
- Reply to enquiries and support requests
- Investigate abuse and enforce our Terms of Service
- Comply with legal obligations
We do not sell your data or use it for advertising.
5. PDPA Compliance
TACNow is built for PDPA compliance:
| PDPA Principle | How TACNow complies |
|---|---|
| Purpose limitation | Data used only to provide the Service, bill for it and meet legal obligations |
| Data minimisation | Full phone numbers and WhatsApp codes held, encrypted, only while a message is being sent |
| Retention limit | Message records deleted after 90 days |
| Access rights | Contact us to request your data |
| Security | Data encrypted in transit (TLS); phone numbers and WhatsApp codes also encrypted while stored |
Data residency: Our database and its backups are hosted in Malaysia. To deliver messages, send email and take payments, we pass the data each service needs to the providers in section 7, some of which process it outside Malaysia: SMS is sent through Alibaba Cloud's Singapore region, and Meta, Stripe and Resend operate internationally. We make these transfers under section 129 of the PDPA: each is needed to provide the Service you have contracted us for, and each provider is bound by data protection terms that require it to keep the data secure and use it only to provide its service to us.
6. Your Rights
Under the PDPA, you have the right to:
- Access personal data we hold about you
- Correct inaccurate personal data
- Delete your account and associated data, except the financial records we must keep (section 3)
- Withdraw consent to processing
To exercise these rights, email privacy@tacnow.co.
7. Third-Party Services
We use the following third-party services to operate TACNow:
| Service | Purpose | Data it receives |
|---|---|---|
| Alibaba Cloud (Malaysia) | Hosting for our API servers, database and backups | The data described in this policy |
| Meta (WhatsApp Cloud API) | WhatsApp message delivery | Recipient phone number and code |
| Alibaba Cloud SMS (Singapore region) | SMS delivery | Recipient phone number and message text |
| Stripe | Online payments by card, FPX or GrabPay | Payment details you enter on Stripe's page; the requesting member's email address and top-up references |
| Resend | Sending our emails | Recipient email address and the email's content |
| Cloudflare | DNS for tacnow.co, and routing of email sent to our tacnow.co addresses | Emails you send us |
Messages sent in test mode are never passed to Meta or Alibaba Cloud SMS. While we move our websites onto the same Alibaba Cloud servers, they are served by a separate web host, which sees connection data such as IP addresses but is not used to store your account or message data.
These providers are bound by their own privacy and security policies. We do not share personal data with any third party beyond what is necessary to deliver the Service.
8. Security
We protect your data using:
- TLS encryption in transit
- AES-256-GCM encryption for phone numbers and WhatsApp codes while they are stored
- Hashing for API keys and passwords, which are never stored in plaintext
- IP allowlists and rate limiting
- Logs that redact phone numbers, codes, API keys and authorisation headers
- Stripe's hosted payment page, so card and online banking details never reach our servers
If you discover a security vulnerability, please disclose it responsibly at security@tacnow.co.
9. Changes to This Policy
We will notify registered users by email before making material changes to this Privacy Policy. Continued use of the Service constitutes acceptance.
Contact
Data controller: WebbyX Sdn Bhd (202301001788), which operates TACNow.
Privacy enquiries: privacy@tacnow.co