Privacy policy
Last updated: 2 August 2026
Pay Docly is built so that we never receive your payroll data in the first place. Payslips are generated entirely inside your browser — there is no account, no database and no upload step.
The short version: we do not collect, transmit, sell or store your company details, employee names, salaries or logos. Everything you type stays on your own device until you choose to export or print it.
1. Who we are
Pay Docly ("we", "the site") provides free browser-based tools for creating and downloading payslips, invoices, quotations, receipts, expense claims, timesheets, HR letters and CPF estimates at https://www.paydocly.com. For any privacy question, contact [email protected].
2. What we do not collect
We do not collect or receive any of the following:
- Company names, addresses, email addresses, phone numbers or logos
- Employee names, employee IDs, departments or designations
- Client names, addresses, invoice numbers or amounts billed
- Salary amounts, earnings, deductions, net pay or bank details
- The payslip, invoice and receipt PDFs you generate
- Account credentials — there are no accounts
Every document is assembled by JavaScript running in your browser. No form field is ever sent over the network to us or to any third party.
3. Data stored on your device
To make the tool usable across visits, the site saves a small amount of data in your browser's local storage. This is storage on your own computer or phone — it is not transmitted to us and we cannot read it.
What is stored locally
payDocly.records— the employee records you explicitly savepayDocly.draft— the payslip you are currently editing, so a refresh doesn't lose your workpayDocly.logo— the company logo you upload, encoded as an imagepayDocly.logoMeta— the file name and size of that logo, shown next to the previewpayDocly.build— which version of the page you last used, so outdated sample data can be clearedpayDocly.invoice.records— the invoices you explicitly savepayDocly.invoice.draft— the invoice you are currently editingpayDocly.invoice.build— the invoice tool's equivalent version markerpayDocly.receipt.records— the payment receipts you explicitly savepayDocly.receipt.draft— the receipt you are currently editingpayDocly.receipt.build— the receipt tool's version markerpayDocly.letter.records/.draft/.build— saved HR letters and the one being editedpayDocly.cpf.rates— your edits to the CPF contribution rate tablepayDocly.cpf.draft/.build— the figures last entered in the CPF calculatorpayDocly.quote.records/.draft/.build— saved quotationspayDocly.rent.records/.draft/.build— saved rent receiptspayDocly.expense.records/.draft/.build— saved expense claimspayDocly.timesheet.records/.draft/.build— saved timesheetspayDocly.businessProfile— your own company name, address and tax ID, shared across tools so you don't retype them
The logo keys are deliberately shared between the payslip and invoice tools, so uploading your logo once applies it to both. Each tool keeps its records under its own key and they never overwrite each other.
How to delete it
Use Clear All in the generator to remove saved employee records, or clear your browser's site data for this domain to remove everything, including the draft and logo. Uploading nothing and using private/incognito mode means the data disappears when you close the window.
Because this data lives only on your device, it is also lost if you clear your browsing data, use a different browser, or use a different computer. Use Export Backup to keep a copy under your own control.
4. Files you upload and download
Logo images, CSV imports and JSON backups are read by your browser using the standard File API and processed in memory on your device. They are not uploaded anywhere. Files you download — PDFs, CSV templates, JSON backups — are written directly by your browser to your own storage.
5. Cookies and tracking
This site sets no cookies and runs no advertising or analytics trackers. There is no cross-site tracking, no fingerprinting, no advertising identifiers and nothing sold or shared with data brokers. Local storage is used only for the purposes listed in section 3.
6. Server logs
The pages themselves are served by a web host. Like almost all web servers, the host may record standard technical request information — IP address, date and time, requested URL, referring page and browser user agent — in access logs for security and reliability purposes. These logs contain no payslip content, because payslip content is never sent to the server. Retention and handling of those logs are governed by our hosting provider's policies.
7. Third parties
The site loads no third-party scripts, fonts, or embedded content. Nothing on the page calls out to an external service while you work, and the donation button is a plain link rather than an embedded widget, so no request is made to it unless you click.
The support page offers one optional way to tip: a link to PayPal. PayPal is an independent service with its own privacy policy and terms, and no request is made to it unless you click the link. Any payment details are entered on PayPal's site and handled entirely by them — we never see, receive or store your card or account information, and no payment is required to use anything on this site.
8. Children
This is a business tool and is not directed at children. We do not knowingly collect information from anyone — including children — because we do not collect personal information at all.
9. Your rights
Data protection laws such as the GDPR and India's DPDP Act give you rights of access, correction, deletion and portability over personal data held by a service. Because we hold no personal data about you, there is nothing for us to disclose, correct or delete on your behalf — you already hold and fully control all of it on your own device, and can export or delete it at any time using the buttons in the generator.
You remain the data controller for the employee information you enter. If you are creating payslips for other people's salaries, you are responsible for handling that information lawfully, including keeping exported backups and generated PDFs secure.
10. Security
Keeping all processing on-device removes the risk of a server-side breach of payroll data — there is no server-side copy to breach. Data on your device is only as secure as the device and browser profile it sits in, so use a locked, up-to-date device and be careful where you store exported backups and PDFs, which are unencrypted files.
11. Changes to this policy
If this policy changes — for example if analytics or advertising were ever added to the site — the "last updated" date above will change and the new terms will be described here. Material changes will be noted on the home page.
12. Contact
Questions about this policy: [email protected].