Between: the Client named in the order form or quotation (the "Client"), and Techneek Global Ltd (UK company no. 13879281), Kemp House, 160 City Road, London EC1V 2NX, trading as Crewkora ("Crewkora"). Effective date: the date the Client first uses the Service, or the date of the order form, whichever is earlier.
1. Purpose and meaning
1.1 This agreement sets out how Crewkora handles personal data for the Client when the Client uses Crewkora (the "Service"). It forms part of the Crewkora Terms of Service.
1.2 It is meant to meet the Personal Data Protection Act 2012 of Singapore (the "PDPA"), including its rules on data intermediaries.
1.3 In this agreement:
- Client Personal Data means personal data that Crewkora processes for the Client through the Service, mainly about the Client's workers (see Annex A);
- Worker means a person whose data the Client manages through the Service;
- Subprocessor means a third party that Crewkora uses to process Client Personal Data; and
- Personal Data Breach means a security incident that results in unauthorised access to, collection, use, disclosure, copying, modification or disposal of, or loss of, Client Personal Data.
2. Roles
2.1 The Client is the organisation under the PDPA for Client Personal Data. It decides why and how the data is used.
2.2 Crewkora is the Client's data intermediary. It processes Client Personal Data on the Client's behalf and under its instructions.
2.3 Crewkora is the organisation for its own data (such as business contacts and website visitors), which is covered by the Privacy Policy, not this agreement.
3. Instructions
3.1 Crewkora will process Client Personal Data only to provide the Service and in line with the Client's documented instructions. The Terms, the order form, this agreement and the Client's use of the Service's settings are the Client's instructions.
3.2 Crewkora will not use Client Personal Data for its own purposes and will not sell it. Crewkora may use aggregated usage statistics that contain no personal data and identify no person or client.
3.3 If Crewkora thinks an instruction breaks the law, it will tell the Client, and may pause that instruction until the issue is resolved.
3.4 The Client is responsible for having the right to give those instructions, including giving Workers the required notices and getting any consent needed (see section 12).
4. Confidentiality
4.1 Crewkora will keep Client Personal Data confidential and treat it as the Client's confidential information.
4.2 Crewkora will allow access to Client Personal Data only to staff and contractors who need it to provide the Service and who are bound by confidentiality obligations.
5. Security measures
5.1 Crewkora will protect Client Personal Data with reasonable security arrangements, as the PDPA requires of a data intermediary. The measures currently in place are in Annex B.
5.2 Crewkora may update its measures, but will not materially reduce the level of protection.
6. Subprocessors
6.1 The Client agrees that Crewkora may use the Subprocessors in Annex C.
6.2 Crewkora will have a written contract or terms with each Subprocessor that require protection of the data comparable to this agreement, and remains responsible to the Client for its Subprocessors' handling of Client Personal Data.
6.3 Change notice. Crewkora will give the Client at least 30 days' notice by email before adding or replacing a Subprocessor. The Client may object on reasonable data protection grounds within 14 days of the notice. If the objection cannot be resolved, the Client may terminate and Crewkora will refund the fees the Client has prepaid for the period after termination.
6.4 Some Subprocessors are optional and only used if the Client enables the feature (for example AWS face comparison, WhatsApp using the Client's own number, AI helpers or SMS).
7. Transfers outside Singapore
7.1 Production hosting for the Service will be in Singapore.
7.2 Client Personal Data may be accessed or processed outside Singapore in the circumstances in Annex C and by Crewkora's staff accessing systems remotely from the United Kingdom, Singapore and Malaysia.
7.3 Where Client Personal Data is transferred outside Singapore, Crewkora will make sure that the recipient is bound by legally enforceable contractual obligations to give the data a standard of protection comparable to the PDPA, as the PDPA's Transfer Limitation Obligation requires.
8. Personal Data Breach
8.1 Crewkora will tell the Client without undue delay and in any case within 48 hours after Crewkora discovers a Personal Data Breach affecting Client Personal Data. Notice goes to the breach contact the Client gives at onboarding.
8.2 The notice will, as far as Crewkora then knows, say what happened, what kinds of data and roughly how many Workers are affected, what Crewkora has done to contain it, and a contact for follow-up. Crewkora will send updates as it learns more.
8.3 Crewkora will help the Client investigate, contain and fix the breach and give the information the Client reasonably needs to assess it.
8.4 The Client, as the organisation, decides whether a breach is notifiable and is responsible for notifying the Personal Data Protection Commission (within 3 calendar days after it assesses that the breach is notifiable) and affected individuals where the PDPA requires. Crewkora will not notify regulators or Workers about Client Personal Data unless the law requires it or the Client asks it to, and will tell the Client first where it is allowed to.
9. Help with access, correction and other requests
9.1 If a Worker asks Crewkora for access to or correction of their data, or withdraws consent, Crewkora will pass the request to the Client within 3 working days and will not respond to the Worker itself unless the Client instructs.
9.2 Crewkora will give the Client reasonable help to respond to access, correction and withdrawal requests. The Client can also use the Service's own export and edit features.
9.3 Ordinary help is free. Large data exports and legal or regulatory work are chargeable at rates agreed in advance.
10. Retention, return and deletion
10.1 Crewkora keeps Client Personal Data only as long as needed to provide the Service and as the Client instructs. For face photos, the reference photo is kept while the Worker works for the Client and is deleted when the Worker leaves or withdraws consent. Clock-in photos are kept for the period the Client sets (default 90 days, range 7 days to 10 years).
10.2 When the agreement ends, the Client chooses within 30 days of termination whether Crewkora returns or deletes Client Personal Data. If the Client does not choose within that time, Crewkora will delete it. On request, Crewkora will confirm in writing that this has been done.
10.3 Encrypted database backups are kept as 14 daily, 8 weekly and 12 monthly copies, so the oldest backup is about 12 months old. Client Personal Data in a backup is deleted when that backup expires. Crewkora will not use backups for any purpose other than restoring the Service after a failure, and will not restore deleted data after termination.
10.4 Crewkora may keep data where the law requires it, and will tell the Client what and why, unless the law prevents that.
11. Audits and information
11.1 Crewkora will give the Client the information reasonably needed to show it is meeting this agreement, for example answers to security and data protection questionnaires.
11.2 The Client may audit Crewkora's compliance with this agreement, no more than once a year (unless there has been a Personal Data Breach or a regulator requires it), on at least 30 days' written notice, during business hours, subject to confidentiality, and in a way that does not unreasonably disrupt Crewkora or put other clients' data at risk. The Client may use an independent auditor who has signed a confidentiality agreement.
11.3 The Client pays the reasonable costs of the audit, unless the audit finds a material breach by Crewkora.
11.4 Crewkora does not yet hold a security certification or have an independent audit report to offer.
12. Client responsibilities
12.1 The Client will make sure it has a lawful basis for the Client Personal Data and its instructions to Crewkora, and that Workers have been given the notices required by the PDPA and have consented where necessary.
12.2 In particular, the Client will, before enabling face check:
- tell Workers what face data is collected, why, who receives it (including AWS if cloud comparison is on), and how long it is kept;
- get each Worker's consent; and
- offer a reasonable alternative (confirmation of the clock-in by the site lead) to any Worker who declines or withdraws.
12.3 The Client will choose the Service's settings (such as retention, face check mode and user roles) with care and will keep its user accounts secure.
12.4 The Client will tell Crewkora promptly if it is told of a breach or complaint about Client Personal Data that affects Crewkora.
13. Liability
Liability under this agreement is subject to the limits and exclusions in the Terms of Service, section 13. The same cap applies to data protection claims.
14. Term, law and order of precedence
14.1 This agreement lasts as long as Crewkora processes Client Personal Data for the Client, including the period for return or deletion in section 10.
14.2 If this agreement conflicts with the Terms on personal data, this agreement prevails.
14.3 This agreement is governed by Singapore law, and the dispute resolution provisions of the Terms apply.
Annex A. Details of the processing
Subject and duration: providing the Service to the Client for the length of the agreement.
Nature and purpose: hosting and operating the app for shift scheduling, clock-in with GPS geofence check, optional face check, device binding, timesheets, leave management, payroll exports, and notifications by WhatsApp and email.
Categories of individuals: the Client's Workers, supervisors and administrators, and people who receive deliveries and sign for them.
Types of personal data:
- identity and contact (name, staff ID, phone number, email);
- role, shift, attendance, timesheet and leave records;
- GPS location captured at the moment of clock-in and clock-out, and the geofence result (not tracked in the background);
- device identifier and device-binding data;
- face-check data, if enabled: an on-device face detection result, the clock-in photo, the reference photo, and the match result;
- payroll export data chosen by the Client;
- trip and delivery records: stop times, the location where proof-of-delivery photos are taken, proof-of-delivery photos, and the recipient's name and signature;
- notification content and delivery status;
- addresses of sites or Workers entered by the Client (sent to OneMap as address only); and
- if the Client enables them, text sent to optional AI helpers.
Sensitive treatment: face data is biometric and is handled with additional care. By default a face-check result flags a clock-in for supervisor review and never reduces pay automatically.
Annex B. Security measures
Crewkora currently uses:
- Singapore hosting. Production hosting in a Singapore data centre.
- Encrypted backups. Backups are encrypted before they are written. Database backups are kept as 14 daily, 8 weekly and 12 monthly copies (see clause 10.3), with an encrypted off-site copy on Cloudflare R2.
- Encrypted face photos. Face photos are encrypted before they are stored, with a separate key for each client company, and are served only through the Service's access-controlled interface.
- On-device face detection. Face detection runs on the Worker's device (MediaPipe). Photos are sent for cloud comparison only if the Client has enabled it.
- Limited face data retention. Face photos are kept only for verification, for the periods in clause 10.1.
- Device binding. Worker accounts can be bound to a registered phone.
- Role-based access. Access within the Service is limited by user roles set by the Client.
- Minimised sharing. Only the data needed is sent to Subprocessors (for example, address only to OneMap).
- Bot protection. Cloudflare Turnstile and rate limits protect sign-in and sign-up from abuse.
Annex C. Subprocessors
- Hosting provider. Hosts the Service and its database. Location: Singapore. Data: all Client Personal Data.
- Amazon Web Services (AWS Rekognition). Optional cloud face comparison, only if the Client enables it. Data: clock-in photo and reference photo. Location: Singapore (ap-southeast-1). AWS does not use the content to train its services.
- Meta Platforms (WhatsApp Business). Delivery of WhatsApp messages from the Client's own WhatsApp Business number. Data: recipient phone number, name where included, message content. Location: Meta operates globally.
- A2 Hosting (SMTP email). Delivery of email notifications. Data: recipient email address and message content. Location: Singapore.
- OneMap (Singapore Land Authority). Address geocoding. Data: address only. Location: Singapore.
- Cloudflare (R2 storage). Encrypted off-site backups. Data: encrypted copies of database backups. Location:.
- Cloudflare (Turnstile). Bot protection on sign-in and website forms. Data: IP address and browser signals.
- Anthropic (optional AI helpers). Only if the Client switches on AI features. Data: limited text from the Client's workflows, with personal data redacted where the feature allows.