Privacy Policy

Wageclerk is run by [Your full name or business name], based in India ([Your postal address]). For privacy questions, contact [Name of the person responsible for data protection] at [Privacy email address].

Two groups of people have data in Wageclerk. You, the person who signs up, and your employees, whose details you enter. For your employees, you decide what to enter and why, and we handle it on your behalf under our Terms.

• Your account: your email address and password. The password is kept only as a one-way scrambled value by our sign-in provider, so we can’t read it. If you sign in with Google, we receive your name and email from Google.
• Your business: the business name, an optional UEN, and your CPF Submission Number.
• Your employees: full name, NRIC or FIN, date of birth, whether they are a citizen, permanent resident or foreigner (and the PR start date), the self-help group fund they contribute to (if any), and optionally an hourly rate, start date and last working day.
• Pay records: the monthly wages you enter, the CPF and levy amounts we work out, and a saved copy of each CPF file’s figures (names, ages, wages and contributions, without ID numbers).
• Technical data: your IP address and browser details in server logs, and short-lived counters used to limit abuse (see “Cookies and logs”).

We don’t collect card numbers, Singpass or CorpPass details, or your CPF account logins. We don’t submit anything to CPF for you. You upload the file yourself.

The self-help group fund an employee contributes to can hint at their community. We store it only to work out the right deduction, and you should enter it only for staff who actually contribute.

We ask for NRIC or FIN numbers only because CPF’s upload file requires them. They are encrypted before they are saved, using a key kept separately from the database. We keep a scrambled fingerprint to spot duplicates, and show only the last four characters in the app.

The full number is decrypted on our server only when you generate a CPF file. It is not written to logs, and it is not kept in the saved records or in payslips. Our systems can decrypt the numbers, and we don’t look at them unless you ask us to help fix a problem.

• To work out CPF and levy amounts, build your CPF upload file and payslips, and keep a history of what you generated.
• To run, secure and support your account, including sign-in emails and password resets.
• To fix faults, prevent abuse and meet legal duties.

We don’t sell personal data, show advertising, or use your employees’ details for marketing or profiling.

When you download a payslip, the PDF is built in your browser. We don’t keep a copy, so please keep the payslips you issue.

We use these providers to run Wageclerk:

• Supabase: our database and sign-in. The database is in Singapore.
• Cloudflare: hosting and delivery of the website over its global network, including request logs.
• Google: only if you choose to sign in with Google.
• Dodo Payments: if you buy a paid plan, it processes the payment as the seller of record. We learn that you paid, never your card details.
• Resend: our email service, which delivers sign-up, password and account emails.

We may share information if the law requires it. We don’t share it with anyone else.

The database is in Singapore. The website is delivered through Cloudflare’s network, and we run Wageclerk from India, so data may be handled in India when we maintain the service or help you. We use encryption, access controls and our providers’ contractual protections to keep the standard of protection high wherever data is handled.

• While your account is open, we keep what you enter so you can use Wageclerk.
• If you delete your account in Settings, your data is removed from our live database straight away. Copies may remain in our database provider’s backups or in server logs for a limited time until they are overwritten.
• Archiving an employee keeps their record. Deleting your account is the way to remove everything.

The law may require you, as an employer, to keep payroll records such as issued payslips. Deleting your account is permanent, so download the CPF files and payslips you need first.

• Connections to Wageclerk are encrypted (HTTPS).
• ID numbers are encrypted before they are stored.
• Each business can see only its own data, enforced in the database itself.
• We limit repeated sign-in and write attempts to slow down abuse.

No system is perfectly secure. If we have credible grounds to believe a breach has affected personal data we handle for you, we will tell you without undue delay, so you can decide what you need to do under the PDPA.

• You can view and edit your details in the app.
• You can delete your account and all its data in Settings.
• You can ask us for a copy of what we hold about you, or to correct it, by emailing us.
• Your employees can ask you for access to or correction of their details. We will help you respond.

You are responsible for having a proper reason to collect your employees’ details and for telling them why, for example that you use them for payroll and CPF contributions. See our Terms for how we handle that data for you.

We use only the cookies needed to keep you signed in and to run password reset, the welcome screen and account deletion. We don’t use advertising or analytics cookies.

Our hosting provider keeps request logs (such as IP address, the page requested, time and errors) for a short time to keep the service running and secure. We also keep short-lived counters, linked to a scrambled version of your IP address, email or account, to limit abuse.

If we make a material change, we will update the date above and tell you by email or in the app.

[Name of the person responsible for data protection], [Privacy email address]. General questions: [Contact email address].