HRStuff

Sign up

You will be this company's first administrator, and will be able to set up accounts for the other users.

How would you like to pay?
Choose from 3 to 1,000 people.
The email you will log in with.
At least 10 characters. Cannot contain part of your name or part of your email.

Company settings

Choose how HRStuff should display information for this company.

Where the company is based.
Suggested from the country. Check that this is the currency the company pays people in.
Suggested from this device. Change it if the company normally works in another time zone.
Used everywhere on the site.
Used for amounts and other numbers throughout the site.

Important Disclaimer: HRStuff is software, not a compliance service

HRStuff is self-service software for HR records, leave, claims, payroll calculations, and payslips. It applies the information and rules your organization enters. HRStuff is not a managed payroll bureau, employer of record, professional employer organization, law firm, accounting firm, tax adviser, compliance adviser, or representative before any government authority.

HRStuff does not provide legal, tax, accounting, payroll, employment, labour, benefits, immigration, data-protection, or other regulatory advice. We do not determine which laws, agreements, rates, rules, filings, or deadlines apply to you; monitor legal changes; or approve your payroll setup.

We do not pay employees, move or remit money, register employers or workers, or prepare, sign, submit, or file official returns, reports, declarations, or payments. This includes payroll and employment taxes; social security, national insurance, Medicare or public-health contributions; unemployment and workers’ compensation; pensions, provident funds and superannuation; levies; and similar statutory obligations.

Your organization, acting through its authorized HR, payroll, finance, compliance, or other representative, is responsible in every country and local jurisdiction where a worker is hired, employed, resident, or working. This includes:

  • determining worker status and all applicable pay, leave, benefits, withholding, deduction, contribution, reporting, record-keeping, notice, and payslip requirements;
  • entering and maintaining complete and accurate employee data and rules, lawfully handling employee information, and monitoring changes in laws or circumstances;
  • independently checking calculations, payslips, rules, and automated actions before relying on or publishing them; and
  • paying workers, making all filings and remittances, meeting deadlines, correcting errors, responding to authorities and employees, and handling resulting taxes, underpayments, overpayments, interest, penalties, or claims.

Outputs depend on the information and rules you provide. Examples, templates, preconfigured settings, test results, explanations, and support are general technical information only. They may be incomplete, outdated, or unsuitable for your circumstances and are not official guidance. Availability in a particular country, currency, or language does not mean HRStuff is approved, legally compliant, or suitable there.

Verify your requirements and results with the relevant authorities and appropriately qualified local advisers before your first payroll run, before enabling automation, and whenever laws or circumstances change. Support can explain how the software works, but it does not provide or certify compliance.

Nothing in this notice transfers obligations that applicable law places directly on HRStuff or excludes rights or liability that cannot lawfully be excluded.

Terms of Service

These Terms govern access to and use of the HRStuff website and application. “HRStuff”, “we”, “us” and “our” mean Clearworks Pte. Ltd., the Singapore company operating the HRStuff service, contactable at info@hrstuff.io. “Customer”, “you” and “your” mean the organization named during sign-up and the person accepting these Terms for it.

1. Business use and authority

HRStuff is offered for business and professional use. By creating an account, accepting an order, or using the service, you agree to these Terms for the Customer. You confirm that you are at least 18 years old and authorized to bind the Customer. If you do not have that authority, do not create the account or use the service.

2. The service

HRStuff is self-service software for employee records, leave, claims, payroll calculations, payslips, reports and related administration. Available features depend on the Customer’s plan and settings. The service applies data, policies and calculation rules entered or approved by the Customer. The compliance Disclaimer shown at sign-up forms part of these Terms.

We may maintain, repair, secure and improve the service. We may change a feature where reasonably necessary for security, law, reliability or product improvement. Where a planned change materially reduces paid functionality, we will give reasonable notice when practicable.

3. The Customer’s responsibilities

The Customer is responsible for:

  • deciding whether HRStuff is suitable for its organization and each place where its workers are hired, employed, resident or working;
  • providing lawful, complete and accurate data, policies, rules, opening balances and instructions, and keeping them current;
  • reviewing calculations, reports, payslips and scheduled actions before relying on or publishing them;
  • meeting its employment, payroll, tax, leave, benefits, privacy, record-keeping, filing, payment and other legal obligations;
  • giving workers and other individuals any required notices and obtaining any required permissions or other lawful basis for their data; and
  • assigning appropriate access roles and ensuring that its users follow these Terms.

4. Accounts and security

Account information must be accurate. Each user must keep their password and device secure, must not share a login, and must tell the Customer and HRStuff promptly about suspected unauthorized access. The Customer is responsible for activity carried out through its accounts unless it resulted from HRStuff’s breach of these Terms or failure to use reasonable care.

5. Customer Data

“Customer Data” means information, files and instructions submitted to the service by or for the Customer. As between the parties, the Customer retains its rights in Customer Data. The Customer gives HRStuff a limited right to host, copy, transmit, back up and otherwise process Customer Data only as needed to provide, secure, support and maintain the service, follow lawful Customer instructions, and comply with law.

The Customer confirms that it has the authority and lawful basis needed to provide and use Customer Data, including sensitive employee information. The Data Processing Agreement in section 18 forms part of these Terms and governs HRStuff’s processing of personal data on the Customer’s behalf. Required international-transfer arrangements are addressed in that DPA.

6. Acceptable use

You must not use HRStuff to break the law or another person’s rights; upload malicious, unlawful or infringing material; access another customer’s data; bypass permissions or security controls; probe or disrupt the service; overwhelm it with automated requests; share, resell or provide the service to an unauthorized third party; or reverse engineer it except where applicable law expressly permits that activity.

7. Plans, renewal, cancellation, fees, refunds and taxes

The plan, price, billing period and minimum quantity shown at sign-up or in a written order form part of the agreement. Fees are charged in advance through Stripe. The subscription renews automatically for the same billing period until the Customer cancels it before the next charge date. The Customer authorizes Stripe to charge the saved payment method for each renewal. The next charge date is shown on the Billing page.

If the Customer starts with a free trial, no card is required during the trial. Unless HRStuff has made the trial ongoing, ordinary access pauses at the recorded trial end. Where a Stripe subscription is linked, Stripe issues the invoice for continued monthly service. Full access resumes only after Stripe confirms that invoice is paid. Otherwise, the Customer must contact HRStuff to arrange continued access.

The first payment uses the quantity confirmed at sign-up. After that, the billable quantity is at least three and otherwise counts active employee records, whether or not the employee has logged in. Before additional employees are activated, HRStuff shows the administrator the new paid headcount and the amount Stripe will charge for the rest of the current billing period. The extra employees remain pending unless that payment succeeds.

When active employee records are made inactive, the lower quantity applies at the next renewal without a mid-period refund or credit. Changes between the Monthly and Yearly Plans also take effect at the next renewal without mid-period proration or credit.

An authorized Customer administrator may cancel through the Billing page and Stripe's secure customer portal. Cancellation takes effect at the end of the current paid billing period. The Customer may continue using the service until then, and no further renewal will be charged. Cancellation does not remove amounts already due.

Paid fees are non-refundable except where applicable law requires a refund or HRStuff confirms a billing error. HRStuff does not give a refund or credit for an unused part of a billing period, a mid-period cancellation, a reduction in billable employees, or a plan change. A suspected billing error should be reported promptly through the Contact page or to info@hrstuff.io.

If a monthly or yearly renewal payment fails, Stripe may retry it and HRStuff may ask the Customer to update the payment method. If Stripe then cancels the subscription for that unresolved payment failure, employee, manager and Assistant Administrator access pauses. A full HR Administrator may still sign in to Billing, support and essential account pages to recover the subscription.

Recovery keeps the previous plan and uses the current billable headcount, subject to the minimum quantity. Because the service period began on the first unpaid date, Stripe may charge from that date rather than begin a new billing period on the recovery date. Full access resumes only after Stripe confirms that the replacement subscription is active and its first invoice is paid. Voluntary cancellation, company deletion and an unresolved cancellation reason are reviewed separately and do not automatically use this payment-lapse restriction.

The Customer must pay applicable taxes. We will give reasonable advance notice of a price change that affects a future renewal period.

8. Ownership and feedback

HRStuff and its licensors own the service, software, design, documentation, trade marks and related intellectual property. These Terms give the Customer a limited, non-exclusive, non-transferable right to use the service during its subscription. If you provide suggestions, we may use them without restriction or payment, but we will not identify you publicly without permission.

9. Service providers and third-party services

We may use reputable service providers for hosting, databases, communications and other infrastructure. A third-party service that the Customer chooses to connect to HRStuff is governed by that provider’s terms. We are not responsible for a third party’s service, but we remain responsible for our own obligations when we appoint a provider to process data for us.

When the Customer enables an integration, it instructs HRStuff to send the selected event or calendar information to that destination. The Customer is responsible for choosing appropriate destinations and recipients, protecting private calendar links and webhook addresses, and disconnecting access that is no longer needed.

10. Availability, support and security

We will use reasonable care and skill to operate the service and reasonable technical and organizational measures to protect it. Internet and software services can still be interrupted or contain faults. Unless a separate written service-level agreement says otherwise, HRStuff does not promise uninterrupted availability or a particular response or recovery time. Support explains how the software works; it does not provide legal, tax, payroll, accounting or compliance advice.

11. Suspension and termination

We may suspend access where reasonably necessary to address a security risk, unlawful use, material breach, non-payment, or harm to the service or another person. Where practicable, we will explain the reason and allow a reasonable opportunity to correct it. The Customer may cancel its subscription as described in section 7. We may end the service for a material breach that is not corrected within a reasonable time, or where continuing the service would be unlawful. Before access ends, the Customer should export records it must retain.

After termination, return and deletion of personal data are governed by the Customer’s choice under the DPA and applicable law. Provisions that by their nature should continue, including ownership, confidentiality, accrued payment obligations, liability and dispute provisions, survive termination.

12. Confidentiality

Each party must protect the other’s non-public information with reasonable care and use it only for the agreement. This does not cover information that is already public without breach, was lawfully known without restriction, was independently developed, or was lawfully received from another source. A party may disclose information where law requires it, after giving notice when legally permitted.

13. Warranties and responsibility for results

HRStuff will provide the service with reasonable care and skill. Except for that promise and rights that cannot lawfully be excluded, the service is provided without additional warranties. We do not warrant that Customer-entered rules are legally correct, that an output satisfies a particular authority, or that the service is suitable for every country or circumstance.

HRStuff is not responsible for an incorrect result caused by inaccurate or incomplete Customer Data, Customer-configured rules, unauthorized use, failure to review an output, or instructions contrary to our documentation, except to the extent that HRStuff caused or contributed to the loss.

14. Liability

Nothing in these Terms excludes or limits liability for fraud, fraudulent misrepresentation, wilful misconduct, death or personal injury caused by negligence, or any other liability that law does not allow to be excluded or limited.

Subject to that sentence and to any different limit in a signed agreement, neither party is liable for indirect or consequential loss, or for loss of profit, revenue, goodwill or anticipated savings that was not reasonably foreseeable when the agreement was made. HRStuff’s total aggregate liability arising from or relating to the service is limited to the fees the Customer paid for its most recent paid month of service before the event giving rise to the claim. If the Customer is billed yearly, this limit is one-twelfth of the yearly fees paid for the subscription year in which the event occurred. This limit does not reduce any mandatory statutory remedy.

15. Changes to these Terms

We may update these Terms for legal, security or service changes. We will identify the effective date and give reasonable notice of a material change. If a material change is unacceptable, the Customer may stop using the service before it takes effect, subject to any existing order and mandatory law.

16. General

If a provision cannot be enforced, the remaining provisions continue. A delay in enforcing a right is not a waiver. The Customer may not transfer the agreement without our consent, except as part of a genuine sale or reorganization of its business. We may transfer it as part of a sale or reorganization of HRStuff if the transfer does not materially reduce the Customer’s rights.

The governing law and courts are those stated in a written order or separate agreement. If none is stated, applicable conflict-of-laws rules determine the governing law and forum. Mandatory rights and the jurisdiction of a competent regulator are not affected.

17. Contact

Questions about these Terms may be sent through the Contact page or to info@hrstuff.io.

18. Data Processing Agreement (DPA)

This DPA forms part of the Terms between Clearworks Pte. Ltd., the Singapore company operating HRStuff, and the Customer identified in the account or applicable order. Accepting the Terms includes accepting this DPA; a separate signature is not required for that electronic acceptance. An existing Customer must accept this version or otherwise validly agree to its incorporation under the parties’ agreement. Earlier acceptance records are not treated as acceptance of wording that did not then exist.

18.1 Scope and roles. “Customer Personal Data” means personal data within Customer Data that HRStuff processes on the Customer’s behalf. The Customer is the controller or equivalent responsible organization; HRStuff is its processor or data intermediary. If the Customer is itself a processor, it confirms that its controller has authorized these instructions and HRStuff’s appointment. “Data Protection Law” means the Singapore Personal Data Protection Act, the EU General Data Protection Regulation (GDPR), the UK GDPR and other personal-data protection laws to the extent they apply to the relevant processing. HRStuff’s separate controller activities, including its own billing administration and public enquiries, are described in the Privacy Notice. This distinction does not authorize HRStuff to repurpose Customer workforce records for its own advertising.

18.2 Processing description and duration. The subject matter is providing the HRStuff services selected by the Customer: workforce administration, leave, claims, payroll calculations, payslips, reports, support and enabled integrations. Processing includes receiving, recording, organizing, storing, retrieving, calculating, displaying, exporting, transmitting, backing up, correcting and deleting information. It continues while those processing services are provided and for the limited period needed to carry out the Customer’s return or deletion instructions under section 18.10.

Data subjects may include current and former workers, applicants entered by the Customer, account users, dependants, emergency contacts, claimants, approvers and people mentioned in Customer documents or communications. Data may include identity and contact details, government identifiers, employment and demographic information, salary and bank details, payroll calculations, leave and claim records, uploaded files, communications, access permissions and activity records. Depending on the Customer’s configuration and submissions, it may include health or disability information, race, religion and other special-category or sensitive data. The Customer determines which fields and records are necessary and establishes the required legal basis and any special-category condition. Accepting this DPA does not itself provide an employee’s consent or another legal basis.

18.3 Instructions and permitted use. HRStuff will process Customer Personal Data only on the Customer’s documented instructions, including the Terms, this DPA, the applicable order, authorized account settings and requests from authorized Customer representatives. This includes instructions about disclosures and international transfers, subject to section 18.8. HRStuff will not sell Customer Personal Data, use it for third-party advertising or disclose it for purposes unrelated to those instructions. The Customer remains responsible for the lawfulness, accuracy, necessity and content of its instructions and for notices to individuals.

If HRStuff considers an instruction to infringe Data Protection Law, it will immediately inform the Customer and may pause the affected processing while the issue is resolved. Processing required by law will be handled only as permitted by Data Protection Law, including the limits in GDPR Article 28(3)(a) where applicable. HRStuff will inform the Customer before legally required processing unless that law prohibits notice on important grounds of public interest. A third-country demand does not by itself replace any safeguard required for a restricted international transfer.

18.4 Confidentiality and access. HRStuff will ensure that people authorized to process Customer Personal Data are bound by confidentiality commitments or an appropriate statutory confidentiality obligation. Access will be limited to what is needed for their duties. Customer users receive access according to the Customer’s roles and permissions. HRStuff’s in-application customer support access is read-only, reason-based, time-limited and recorded; necessary infrastructure access remains subject to access restrictions and confidentiality.

18.5 Technical and organizational security measures. HRStuff will maintain measures appropriate to the risks and required by Data Protection Law, including GDPR Article 32 where applicable. The assessment takes account of the nature, scope, context and purposes of processing, the state of the art, implementation costs and risks to individuals. Measures include:

  • role-based permissions, separation between customer organizations, protected login sessions, salted password hashing and restricted administrative access;
  • production HTTPS and protected provider connections, private file storage, application-level encryption of identity and bank-account numbers, and separately encrypted company backup archives;
  • protection of credentials and encryption keys, request-forgery protection, validation of uploaded files and bounded processing of files and requests;
  • activity records, controlled support access, incident handling and secure deletion processes;
  • measures to preserve confidentiality, integrity, availability and resilience, restore access after incidents and regularly assess and test the effectiveness of relevant security and recovery controls.

HRStuff may improve or replace individual controls while maintaining an appropriate overall level of protection. The Customer manages its users, permissions, devices, exports, selected recipients and integration destinations. These allocations do not remove either party’s own legal duties. No certification or audit standard is implied unless it is expressly identified in a separate written agreement.

18.6 Subprocessors. The Customer gives general written authorization for HRStuff to use the subprocessors identified below to provide their stated functions. HRStuff will bind each appointed subprocessor to data-protection obligations equivalent to those required of HRStuff for the work it performs, including appropriate security and confidentiality. HRStuff remains responsible to the Customer for the performance of its subprocessors’ data-protection obligations.

  • Render: application and PostgreSQL hosting in Singapore, including related infrastructure and recovery services.
  • Cloudflare: private R2 storage of receipts, documents and encrypted company backups. Storage locations depend on the bucket configuration; a location hint is not a guarantee of Singapore-only storage.
  • Resend: transactional email delivery, including employee and administrator messages where enabled; processing is primarily in the United States.

Before adding or replacing a subprocessor for Customer Personal Data, HRStuff will give at least 30 days’ advance notice to the Customer’s administrator email address on record, identifying the proposed provider, function and relevant processing location. The Customer may object during that period on reasonable data-protection grounds by contacting info@hrstuff.io. The parties will seek a suitable alternative or resolution. HRStuff will not begin the affected processing with the proposed subprocessor while such an objection remains unresolved; affected processing may instead be suspended or ended under the Terms and applicable law.

Providers appointed directly by the Customer, such as a selected Slack, Teams, Telegram, Zapier, Make or calendar destination, are governed by the Customer’s arrangements with those providers to the extent they act independently of HRStuff’s appointment. This does not exclude any provider HRStuff itself appoints from this section. Stripe’s handling of subscription and payment information for HRStuff’s own billing purposes is described separately in the Privacy Notice.

18.7 Assistance with individual rights. Taking account of the nature of processing, HRStuff will assist the Customer through appropriate technical and organizational measures, insofar as possible, with applicable requests to access, correct, restrict, erase, object to or receive portable Customer Personal Data. If HRStuff receives a request about Customer-controlled records directly, it will inform the Customer without undue delay unless legally prohibited and will not decide the request on the Customer’s behalf without authorization or a legal requirement. The parties will verify identity and authority and protect other individuals’ information.

18.8 International transfers. The processing locations described above and in the Privacy Notice do not remove transfer restrictions imposed by Data Protection Law. HRStuff will maintain the applicable safeguards for transfers it carries out, including comparable protection where required by Singapore law. For a restricted EU/EEA or UK transfer, section 19 incorporates the applicable EU Standard Contractual Clauses and UK Addendum where those instruments can lawfully be used. The parties must complete the required particulars, annexes and assessments and implement necessary supplementary safeguards before the affected processing begins, or establish another legally valid transfer mechanism.

The incorporated instruments do not represent that Singapore has an EU or UK adequacy decision. An advertising-cookie choice, a Customer instruction or acceptance of the Terms does not replace a required transfer assessment or missing safeguards. Until the required arrangements are in place, the Customer must not submit the affected data and HRStuff will not carry out the affected restricted processing. Each party will assist the other with the information needed to establish and assess lawful transfers.

18.9 Breaches and regulatory assistance. HRStuff will notify the Customer without undue delay after becoming aware of a personal-data breach affecting Customer Personal Data. It will provide available information about the nature of the breach, affected data and individuals, likely consequences, contact point, containment and remedial measures, and further information as it becomes available. Initial notice will not be delayed solely because the investigation is incomplete.

Taking account of the nature of processing and information available to it, HRStuff will assist the Customer with security obligations, breach assessment and notifications, data protection impact assessments and prior consultation with regulators, including GDPR Articles 32 to 36 where applicable. The Customer determines and makes its required notifications unless the parties agree otherwise in writing; HRStuff remains responsible for any notification or cooperation duty imposed directly on it by law.

18.10 Return, deletion and remaining copies. At the Customer’s choice, HRStuff will return or delete Customer Personal Data after the end of the relevant processing services and delete its existing copies, except where retention is required by law as permitted by Data Protection Law. The Customer may request a secure export through an authorized administrator or info@hrstuff.io and should arrange the return before confirming permanent deletion. HRStuff will reasonably assist with return requests and will not treat a request for return as permission to destroy the only available copy.

Cancelling billing is separate from instructing permanent account deletion. Any storage while return or closure is being arranged remains subject to documented instructions, purpose limitation and the applicable retention requirements. Once company deletion is confirmed, live records are removed and app-managed backup archives are blocked from download or restore and queued for removal, normally within a 24-hour completion target. Removal failures are retried and reported to platform administrators; the target is not an unconditional guarantee.

Where immediate removal from hosting-provider infrastructure snapshots is not technically possible, remaining copies must be kept beyond ordinary use and expire under a documented, justified retention schedule. HRStuff will provide available retention details on request and ensure that recovery procedures reapply deletions before restored data is made available. Backups are not a basis for indefinite retention. Any legally required retention must be limited to the data, purpose and period required, with protection maintained and other use prohibited. On request, HRStuff will provide reasonable confirmation of completed return or deletion.

18.11 Compliance information and audits. HRStuff will make available information needed to demonstrate compliance with this DPA and applicable processor obligations, and will allow and contribute to audits, including inspections, by the Customer or an auditor it appoints. The parties will first use relevant existing documentation where that can meet the need. Reasonable notice, confidentiality, security arrangements and protection of other customers’ data may be agreed, but must not prevent an audit required by law or a competent regulator. Urgent incidents or reasonable evidence of non-compliance may require expedited arrangements.

18.12 Priority, contact and continuing duties. If this DPA conflicts with another part of the Terms about processing Customer Personal Data, this DPA prevails. A binding international-transfer instrument prevails to the extent required by that instrument. Commercial terms otherwise continue to apply, subject to mandatory law; nothing limits individuals’ statutory rights, regulatory powers or obligations that cannot lawfully be excluded. Confidentiality, protection, assistance and deletion obligations continue for as long as HRStuff retains Customer Personal Data. Send DPA instructions, objections and privacy enquiries to info@hrstuff.io.

19. International Transfer Addendum

This addendum forms part of the DPA in section 18. It addresses transfers of Customer Personal Data from the Customer to Clearworks Pte. Ltd. operating HRStuff. It does not cover HRStuff's separate controller activities or replace the safeguards required for onward transfers to subprocessors. Section 19.7 applies before the parties rely on these arrangements for a restricted transfer.

19.1 EU/EEA transfer clauses. Where a transfer requires safeguards under GDPR Article 46, falls within the permitted scope of the clauses below and is not covered by another valid transfer mechanism agreed by the parties, the Standard Contractual Clauses in the Annex to Commission Implementing Decision (EU) 2021/914 of 4 June 2021 (the “EU SCCs”) are incorporated by reference in full into this agreement, with the applicable module, options and appendix information specified here. Their approved wording is not otherwise amended.

Module Two (controller to processor) applies when the Customer is a controller. Module Three (processor to processor) applies when the Customer is a processor engaging HRStuff as its subprocessor with the relevant controller's authorization. Only the module appropriate to the actual transfer applies. These EU SCCs are not represented as a valid mechanism for a transfer outside their legal scope, including where the relevant processing by the importer is already directly subject to the GDPR and these clauses cannot lawfully be used for that transfer.

19.2 Selected EU SCC options. For the applicable module:

  • the optional docking clause in Clause 7 is not included;
  • Clause 9(a), Option 2 (general written authorization), applies with at least 30 days' advance notice of an intended addition or replacement, as described in section 18.6;
  • the optional independent dispute-resolution provision in Clause 11(a) is not included; the remaining redress provisions apply;
  • Clause 17, Option 1, selects the law of Ireland; and
  • Clause 18(b) selects the courts of Ireland, without restricting an individual's rights to bring proceedings in another court permitted by the EU SCCs.

19.3 Annex I.A — parties and acceptance. The data exporter is the Customer identified by its full legal name and relevant contact particulars in the applicable account, billing record, order or other agreed written particulars. Its contact is the authorized Customer administrator or its separately designated privacy contact. Its role is controller under Module Two or processor under Module Three. Its relevant activity is using HRStuff for the workforce processing described in section 18.2.

The data importer is Clearworks Pte. Ltd., trading as HRStuff, in Singapore. Its privacy contact is info@hrstuff.io. It acts as processor under Module Two or subprocessor under Module Three to provide those services. The parties agree that their legally binding electronic acceptance of this agreement also executes the incorporated EU SCCs, including Annex I.A. The applicable date is the date of that acceptance or a separately recorded written agreement. This does not treat an earlier acceptance as agreement to a later version. Required party particulars not already recorded must be completed under section 19.7.

19.4 Annex I.B — description of transfers. The data subjects, categories of personal data, processing operations, purposes and subject matter are those described in section 18.2 for the services and settings the Customer actually selects. Transfers occur on an ongoing basis as the Customer and its users use those services, including scheduled processing, authorized support and backups. The destination is HRStuff's processing in Singapore, with onward processing by the subprocessors described in section 18.6 subject to the applicable onward-transfer requirements. Processing duration and retention follow sections 18.2 and 18.10.

Where sensitive or special-category data is submitted, the safeguards include Customer-controlled permissions, separation between customer organizations, private file storage, encryption of identity and bank-account numbers, encrypted company backup archives and controlled support access, as described in sections 18.4 and 18.5. The Customer must limit submissions and access to what is necessary and lawful. Any additional restrictions or safeguards required for the particular sensitive-data transfer must be documented and implemented before that transfer.

19.5 Annex I.C, Annex II and subprocessors. The competent supervisory authority for Annex I.C is determined under Clause 13: the authority responsible for the Customer's relevant establishment, its applicable Article 27 representative, or, where the Clause 13 conditions permit, an authority in a Member State where affected individuals are located. The parties must identify the applicable authority in their transfer particulars before relying on the EU SCCs.

For Annex II, the technical and organizational measures are those described in sections 18.4 and 18.5, including access controls, tenant separation, protected sessions, password hashing, production HTTPS, protected provider connections, private storage, field and backup encryption, key protection, validation, activity records, controlled support access, recovery and security testing. Sections 18.7, 18.9, 18.10 and 18.11 describe the measures and procedures for assisting with rights requests, incidents, assessments, return, deletion and audits. These descriptions must be supplemented with the specific measures needed for the actual transfer under section 19.7; no unverified certification, storage location or end-to-end encryption guarantee is implied.

The authorized subprocessor list and functions are in section 18.6. Annex III is not required for the selected general-authorization option; the subprocessor information, notice, objection and onward-transfer obligations still apply. A provider's agreement with HRStuff does not itself replace the safeguards for the Customer's transfer to HRStuff.

19.6 UK transfers. For a restricted transfer subject to UK GDPR, where these arrangements are a legally available safeguard and no other valid mechanism agreed by the parties covers it, the ICO International Data Transfer Addendum to the EU Commission Standard Contractual Clauses, version B1.0, in force 21 March 2022 (the “UK Addendum”), including its Part 2 Mandatory Clauses as revised under its Section 18, is incorporated by reference. The EU SCCs specified above form the Addendum EU SCCs with the following Part 1 entries:

  • Table 1: the parties, roles, key contacts and acceptance are as described in section 19.3, supplemented with the required party particulars. The start date is the date the parties validly agree to the UK Addendum.
  • Table 2: the EU SCCs identified in section 19.1 apply with Module Two or Three according to the actual roles and the options in section 19.2.
  • Table 3: the appendix information is in sections 19.3 to 19.5 and any required agreed transfer particulars and supplementary measures.
  • Table 4: both the importer and exporter may end the UK Addendum under its Section 19 when the conditions in that section are met.

The Mandatory Clauses make the required UK adaptations, including the ICO as the competent authority and the laws and courts of England and Wales, subject to the rights preserved by the UK Addendum. They govern any conflict as specified in their hierarchy provisions. The parties must complete the applicable UK transfer risk assessment and any necessary additional protections before relying on this safeguard.

19.7 Preconditions, assessment and continuing protection. Inclusion of the standard instruments does not certify that all required party particulars, transfer-specific appendix information, provider arrangements or assessments are already complete. Before the affected restricted processing begins, the parties must complete and agree the required particulars, document the applicable transfer assessment, and implement any necessary supplementary safeguards. Existing account, billing and order information may be used where accurate and sufficient. Missing information can be completed through the existing privacy contact; a new sign-up form or a separate paper signature is not required merely by this addendum.

The assessment must address the particular transfer, relevant destination-country laws and practices, access by public authorities and the effectiveness of the actual protections. The parties will provide necessary information, keep the assessment under review and respond to changes affecting protection. Until the required arrangements are in place, the Customer must not submit the affected data and HRStuff will not carry out the affected restricted processing. If the required protection cannot be maintained, the affected transfers must be suspended or ended as required by the applicable instrument. Acceptance of these Terms alone does not complete that assessment or establish that a country has adequate protection.

19.8 Priority and enforceable rights. The applicable EU SCCs and UK Addendum prevail as required by their own hierarchy provisions, including over conflicting governing-law, forum, audit and liability provisions elsewhere in the Terms or DPA. No commercial limitation excludes or restricts rights or liabilities that cannot be limited under those instruments. Nothing here removes data subjects' third-party beneficiary rights or the powers of a competent regulator.

Privacy Notice

This notice explains how personal data is handled on the HRStuff website and in the HRStuff application. “HRStuff”, “we”, “us” and “our” mean Clearworks Pte. Ltd., the Singapore company operating the HRStuff service. HRStuff’s data-protection contact is info@hrstuff.io.

1. Who is responsible for personal data

For employee, payroll, leave, claim and other workforce records entered by a customer organization, that organization normally decides why and how the data is used and is the data controller or equivalent responsible organization. HRStuff processes that data to provide the service and normally acts as its processor or service provider.

HRStuff is responsible as controller, or in an equivalent role, when we decide how to use sign-up and account administration details, public Contact enquiries, service security information, our support inbox and records needed to operate or defend the service. If you are an employee or other worker asking about information entered by your organization, contact that organization first. We will assist it where required.

2. Information we may handle

Depending on how the service is used, this may include:

  • Organization and account details: company name, country, currency, time zone, plan, workforce size, administrator and user names, work email addresses, roles, password hashes and sign-up acceptance records;
  • Identity and contact details: employee number, name, work and personal email, telephone number, address, date of birth, national identity or work permit number, nationality, country, emergency contacts and login details;
  • Employment and demographic details: job, department, manager, employment type and dates, gender, race, religion, marital status, residency status and numbers of dependants and children, and disability eligibility;
  • Pay and financial details: salary, allowances, deductions, contributions, payroll rules, bank name, account and routing details, payslips and payroll reports;
  • Payment and subscription details: payer and Customer name, email, plan, billed headcount, amounts, currency, payment and subscription status, renewal and cancellation dates, and the card brand, last four digits and expiry date. Stripe collects full card and payment-method details directly; HRStuff does not store the full card number or security code;
  • Leave, claims and documents: leave types, dates, reasons and decisions; expense descriptions, amounts, categories and receipts; employment documents; and related comments. These records may reveal health, religion or other sensitive information;
  • Support and communications: Contact enquiries, support requests, reply addresses, attachments, the page concerned and responses; and
  • Connected services and delivery records: enabled provider, workspace, channel, chat, account or destination identifiers and display names; protected connection credentials or webhook addresses; command text received from a connected provider; selected event types and safe event data; and delivery times, outcomes and errors; and
  • Security and usage records: IP address, browser or device user-agent, approximate country code supplied by the website proxy, public-site page loads and sign-up clicks, a random per-tab visit code, visible-tab time, session times, failed logins, activity-log entries, support-access reasons and email delivery records.

Passwords are not stored in plain text. HRStuff stores a salted password hash used to check a later login.

3. Where information comes from

We receive information from people who sign up or contact us, from customer administrators and other authorized users, from workers using their own accounts, from files uploaded or imported by the Customer, from connected-service providers when a user sends a command to HRStuff through them, and automatically from use of the website and application. A Customer may therefore provide information about a worker without that worker entering it personally.

4. Why information is used

We use personal data as needed to:

  • create and administer organizations, users, permissions and subscriptions;
  • provide employee records, leave, claims, payroll calculations, payslips, reports, notifications, connected-service commands, imports, downloads and other requested features;
  • authenticate users, maintain sessions, prevent abuse, investigate faults, secure the service and preserve an activity trail;
  • answer enquiries and support requests and, where enabled, deliver those messages by email;
  • maintain, troubleshoot and improve the reliability and usability of the service;
  • administer subscriptions, payments, renewals, failed payments, cancellations and billing support; and
  • comply with law, enforce agreements, and establish, exercise or defend legal claims.

5. Legal grounds

Where laws such as the GDPR require a legal basis, HRStuff relies as appropriate on performing a contract or taking requested pre-contract steps, complying with legal obligations, and legitimate interests in providing, securing, supporting and improving a business service. We rely on consent only where we specifically ask for it and the law makes it appropriate. The Customer is responsible for identifying its own legal basis for workforce data, including any sensitive or special-category data.

6. Payroll rules and scheduled actions

HRStuff can apply rules configured by the Customer and can run scheduled actions, such as creating or publishing payslips. These processes use the data and instructions the Customer supplies. HRStuff does not decide who should be hired, dismissed, promoted or disciplined. The Customer decides whether to use automation and is responsible for appropriate human review. Workers should ask their organization for information about the rules and consequences that apply to them.

7. Who may receive information

Personal data is available to Customer users only according to their assigned role and permissions. HRStuff personnel or contractors may receive limited access where needed for security, operations or requested support. Customer support access inside an organization is read-only, reason-based, time-limited and recorded in that organization’s activity log.

We use service providers to operate HRStuff. Render provides application and database hosting in Singapore and keeps infrastructure backups. Cloudflare provides private R2 object storage for uploaded files and separately encrypted company backups, and may supply the approximate country code used in public-site statistics. Resend delivers transactional service email, including login-creation, password-reset and notification messages, and forwards enquiries submitted through the public Contact page. Stripe provides the embedded sign-up checkout, subscription billing, invoices, saved payment methods, payment collection, fraud prevention and the customer billing portal. Each provider receives only the information needed to perform its service under its own security and contractual obligations.

When a payer uses Stripe, Stripe may receive contact, billing, transaction, payment-method, device, browser and fraud-prevention information. HRStuff receives the payment status, Stripe reference numbers, amounts, currency, renewal information and masked card details, but not the full card number or security code. Stripe explains its handling of personal data in its Privacy Policy.

If the Customer enables event delivery through Slack, Microsoft Teams, Telegram, Zapier or Make, HRStuff sends the selected event type, status, employee or requester and approver names where needed, and a link back to HRStuff to the chosen destination. Claim amounts, leave reasons, attachments and payslip contents are not included in those event deliveries. Zapier and Make receive one selected event at a time; shared messaging destinations may receive grouped summaries.

If the Customer enables personal Slack notifications, Slack supplies HRStuff with workspace member profiles, including Slack user identifiers, names and work email addresses. HRStuff matches work email addresses exactly to active employee records and stores the resulting employee-to-Slack-account link so personal notifications can be delivered.

A user who links a private Telegram chat can also send the /leavebalance and /claims commands to the HRStuff bot. Telegram sends the command text and Telegram user and chat identifiers to HRStuff. After matching that private chat to an active HRStuff login, HRStuff replies through Telegram. A leave balance reply includes leave types and balance figures. A claims reply includes counts and currency totals for pending and approved but unpaid claims.

If a user connects a private calendar feed to Google Calendar, Microsoft Outlook, Apple Calendar or another calendar reader, that reader can retrieve the names, job titles, leave types, dates and approval status visible to that user, together with public holidays. The private feed address acts as a credential. HRStuff stores only its one-way fingerprint and rechecks the owner’s current access whenever the feed is requested.

If a Customer connects direct Google Calendar sync, Google supplies HRStuff with an authorization token and the names and identifiers of calendars that the connecting administrator may update. HRStuff encrypts the lasting authorization token, stores the selected calendar identifier, and creates, updates or removes HRStuff-managed approved leave events in that calendar. Those events contain the employee name, leave type and leave dates, but not the leave reason. HRStuff does not read or change unrelated calendar events.

We may also disclose information to professional advisers, auditors, insurers, regulators, courts, law-enforcement bodies, or a buyer or successor to the service where reasonably necessary and lawful. We do not sell personal data or use Customer workforce data for third-party advertising.

8. Countries and international transfers

HRStuff is designed for organizations in different countries. Its main hosting and storage arrangements are:

  • Render - application and database hosting: Customer account, workforce and service data are processed by the application and primary PostgreSQL database in Render’s Singapore region. Render may also keep infrastructure backups. Safeguards include restricted administrative access, encrypted network connections and Render’s contractual data-protection obligations.
  • Resend - transactional and contact email: sender and recipient addresses, subject lines, message text and delivery details are processed primarily in the United States. Resend states that email and log data on its standard plans are normally kept for 30 days. Safeguards include encrypted connections and the protections described in Resend’s Data Processing Addendum and security information.
  • Cloudflare R2 - private files and encrypted backups: uploaded receipts and documents, and separately encrypted company backup archives, are stored in private R2 buckets. The location depends on the setting used for each bucket and is not represented as Singapore-only. Under Automatic placement, Cloudflare selects a location; a location hint is best effort and is not a data-residency guarantee. Safeguards include restricted bucket credentials, encryption in transit and at rest, and the protections in Cloudflare’s Data Processing Addendum. Cloudflare explains its placement options in its R2 data-location documentation.

Connected services such as Slack, Microsoft Teams, Telegram, Zapier and Make, payment provider Stripe, and authorized users may process information in other countries according to the destination selected by the Customer and the provider’s terms.

Where personal data is transferred outside Singapore, HRStuff uses applicable provider terms, data-processing agreements and technical controls intended to require protection comparable to the Singapore Personal Data Protection Act. HRStuff reviews material provider and subprocessor changes and updates this notice where appropriate. The Customer remains responsible for safeguards required for destinations it selects or controls.

9. How long information is kept

Customer workforce data is generally kept while the Customer account is active and until the Customer deletes the relevant record or a platform administrator deletes the company account, subject to verified backup archives, deletion queues and legal requirements. When a live company account is deleted, its live HR data, logins, uploaded files, company activity log and original sign-up record are deleted. That sign-up record includes the company name and the administrator name and email address supplied during sign-up. Messages sent to HRStuff’s support inbox and related email-delivery records may be kept after account deletion so an unanswered request, security issue or dispute is not erased.

For disaster recovery, HRStuff normally keeps a rolling set of up to seven verified, encrypted company backup archives in storage separate from ordinary uploaded files. Older verified archives are removed as newer ones complete. When the company account is deleted, its app-managed backup archives become unavailable for download or restore and are queued for automatic removal, with a normal completion target of 24 hours. Failed removals are retried and reported to platform administrators. Infrastructure snapshots kept by the hosting provider follow that provider’s separate retention schedule; an infrastructure recovery must reapply completed company deletions before restored data is made available. Copies previously downloaded by the Customer remain under the Customer’s control.

Ordinary login sessions expire after the configured inactivity period. A customer user may instead choose a private-device session that expires no later than 30 days after login. Expired sessions are removed. Other retention periods are chosen according to the purpose of the record, contractual and legal duties, security needs, limitation periods and whether a dispute is reasonably expected. We will not knowingly keep personal data longer than needed for those purposes.

10. Security

HRStuff uses measures including role-based access, separation between customer organizations, password hashing, protected session cookies, request-forgery protection, upload checks, activity records and production HTTPS settings. No internet service can guarantee absolute security. Customers must manage user permissions, devices, exports and passwords appropriately and report suspected incidents promptly.

If HRStuff reasonably believes that Customer Data has been involved in a personal-data breach, we will notify the affected Customer without undue delay where the law requires it and provide available information needed for the Customer’s assessment. Where HRStuff controls the affected data, we will make required notifications to individuals and regulators.

11. Cookies, analytics and advertising measurement

HRStuff uses necessary cookies to sign users in securely, protect form submissions and carry short-lived status messages between pages. These do not depend on an advertising choice.

Optional public-site analytics and advertising measurement stay off until you choose “Accept all cookies”. “Necessary only” and “Reject cookies” both keep them off and remove this tab’s analytics identifiers. The website remembers your choice in a preference cookie for up to 180 days and in the browser's local storage. The preference cookie contains only your choice, not a visitor identifier. Earlier advertising-only acceptance does not enable analytics; we ask for the combined choice again.

When allowed, public-site analytics use a random code stored only in the browser tab's session storage. It ends with that tab's browsing session and is stored by HRStuff only as a one-way code. It is used to calculate active visible-tab time without identifying the person using the tab.

When analytics are allowed, HRStuff also briefly uses the IP address and browser user-agent sent with a public-page request to create a one-way identifier for that combination. The identifier changes each calendar day in HRStuff's reporting timezone and is used to estimate daily visitors and sign-up interest. HRStuff does not write the raw IP address or user-agent to its public-site analytics tables. The resulting daily identifiers and related public-site statistics are kept for up to 367 days.

On public marketing pages, the same choice also allows Google Ads measurement. Google’s advertising tag is not loaded unless that choice is allowed. If allowed, the tag may store or read advertising cookies and receive the public page, advertising interaction and one confirmed company-level outcome: a trial start or the company’s first successful subscription payment. The first-payment event includes the actual payment amount excluding tax, currency and a Stripe transaction reference so retries are not counted twice.

Google Ads tags are not placed on employee-facing application pages. HRStuff does not send employee details, payroll, leave, claims, sign-up contact details or enhanced- conversion personal data to Google. Advertising personalization stays off. The choice itself is stored in the browser's local storage.

Stripe's embedded payment form and Stripe-hosted billing pages may use cookies and device or browser information to complete payments, remember payment choices, secure its services and prevent fraud. Stripe describes those uses in its own Privacy Policy.

12. Your rights

Depending on the law that applies, an individual may have rights to be informed, access personal data, correct it, request deletion or restriction, object to certain uses, receive portable data, withdraw consent, and complain to a data-protection authority. These rights are not absolute and differ by jurisdiction and legal basis.

For workforce records controlled by a Customer, send the request to that Customer. For HRStuff-controlled account, Contact or security records, use the Contact page or email info@hrstuff.io. We may need to verify identity and authority before acting. You may also complain to the data-protection regulator in your country where the law gives you that right.

13. Changes to this notice

We may update this notice when the service, providers or law changes. We will change the effective date and give appropriate notice of material changes. An older notice continues to describe processing that occurred while it was in effect.