For a proposed monitoring system, the strongest starting configuration is limited work-related reporting, with private content and off-duty collection excluded, intrusive inference disabled, and consequential decisions reserved for a documented process. The employer must establish the applicable legal basis, worker information and participation before activating even that restricted version. The vendor must show that its settings and data flows can maintain the agreed limits.
This guide compares 17 countries across North America, Europe, Asia, the Middle East, Africa, Latin America and Oceania. It distinguishes United Arab Emirates (UAE) federal, Dubai International Financial Centre (DIFC) and Abu Dhabi Global Market (ADGM) rules, the common EU layer and decisive state or provincial differences. It concerns existing workers and ongoing workplace monitoring. Licentium's separate recruitment analysis addresses candidate assessment and a supplier's French launch.
Choose the monitoring route before choosing the software
The employer should approve a purpose and a configuration together. A security feature should not quietly become a performance measure; a coaching score should not acquire a dismissal threshold through a later manager setting. The legal analysis must follow those changes.
- Routine productivity or capacity reporting. Configuration to assess: Necessary work-app events, completed work and appropriate aggregated reports; minimum useful detail. Conditions before activation: Lawful purpose and basis, necessity assessment, applicable impact assessment, representative process, worker notice, retention and vendor controls. When the proposed route is unavailable: The same purpose can reasonably be achieved with less intrusive data, private activity cannot be excluded, or the metric does not measure the asserted work.
- Targeted security or misconduct investigation. Configuration to assess: Defined event, people or devices, data categories and period; restricted evidence file. Conditions before activation: Legally sufficient grounds, surveillance and communications authority, any covert authorisation, lawful notice restriction, evidence-preservation plan and fair response process. When the proposed route is unavailable: General curiosity or low productivity is used to justify indiscriminate capture; required authorisation is absent; private areas or communications are unlawfully intercepted.
- Scores affecting pay, allocation, promotion, discipline or termination. Configuration to assess: Relevant validated inputs, intelligible reasons, effective review, correction and challenge. Conditions before activation: Automated-decision classification, any required exception, discrimination and accommodation assessment, worker rights and lawful employment procedure. When the proposed route is unavailable: A prohibited inference drives the result, the reviewer cannot evaluate or reverse it, or the applicable law bars the automated consequence.
These are recommended designs. The country rules below identify where a particular control is mandatory and where the law offers a different route. There is no single international employee-monitoring licence.
Permission to collect is different from notice and consultation
A notice explains processing. Lawfulness also requires the applicable legal basis and necessity conditions. A consent checkbox matters only where consent is the applicable legal route and satisfies that jurisdiction's conditions. An employment contract cannot waive a statutory prohibition or replace an independent works-council, union or employee-representative process.
Under the EU GDPR, an employer needs an Article 6 basis and must meet the Article 5 principles. Special-category data can require an additional Article 9 condition. Systematic monitoring may require a data protection impact assessment (DPIA), with supervisory consultation where high residual risk cannot be mitigated. The imbalance in an employment relationship can make freely given consent difficult to establish. The employer should identify the real basis for each use instead of asking workers to consent to every available feature. GDPR, Articles 5–7, 9 and 35–36.
Other systems offer different employment routes. Singapore permits specified reasonable employment processing without consent while preserving employment-purpose notification. Saudi Arabia has a conditional legitimate-interest route that excludes sensitive data. UAE federal law does not contain an equivalent general legitimate-interest ground. Ontario's requirement to maintain an electronic-monitoring policy is a transparency rule and does not itself make every listed practice lawful. Those differences directly affect which configuration an employer can approve. Singapore PDPA, First Schedule, Part 3, paragraph 10, and section 20; Saudi Implementing Regulation, Article 16; UAE PDPL, Article 4; Ontario ESA, section 41.1.1.
Review each feature and each later use
The employer needs the product's actual data dictionary. A keyboard activity count is different from a record of every character typed. An application category differs from a complete web address containing search terms or a case identifier. Classify a photograph and a template used to identify a person according to the applicable biometric definition. A model may infer health or protected characteristics even if its visible fields do not use those labels.
- Application and activity metadata. Practical starting position: Limit to specified work applications, working sessions and useful granularity. Questions that can change the result: Does the measure distinguish work from inactivity accurately? Can aggregated or output-based information meet the purpose?
- Screenshots. Practical starting position: Keep disabled unless a defined purpose justifies necessary capture and masking. Questions that can change the result: Can private messages, credentials, health information, customer material and household content be excluded? Is continuous capture disproportionate?
- Keystroke content and clipboard. Practical starting position: Exclude from routine productivity reporting. Questions that can change the result: Does a narrowly defined investigation have lawful authority to collect content? Activity counters do not authorise keylogging.
- Location. Practical starting position: Limit purpose, precision, duration and access; provide required off-duty controls. Questions that can change the result: Is location necessary for dispatch, safety or a particular job? Does the system keep tracking a personal device after work?
- Audio, calls and private messages. Practical starting position: Require a separate communications-law assessment. Questions that can change the result: Which participants and locations are involved? Is interception occurring? Does a business exception actually cover this architecture?
- Biometric identification. Practical starting position: Use only after the applicable sensitive-data, biometric and necessity analysis. Questions that can change the result: Is ordinary access authentication available? Are notice, consent, registration, notification or impact requirements triggered?
- Emotion, personality and health inference. Practical starting position: Keep disabled until the exact inference and legal route are established. Questions that can change the result: Does an express prohibition apply? Is the vendor making an unsupported claim about productivity, honesty or fatigue?
- Consequential scores. Practical starting position: Separate the score from employment action and test meaningful review. Questions that can change the result: Does the system make, determine or materially influence the decision? Which explanation, refusal, appeal and labour rights apply?
- Model training and product improvement. Practical starting position: Prohibit unapproved secondary use in the deployment terms. Questions that can change the result: Is the vendor now pursuing its own purpose? What basis, notice, data rights and transfer route support it?
The following comparisons apply those questions to the selected systems. Country-specific surveillance, interception and employment conditions remain additional to the privacy route.
North America: build a state and provincial map
United States: monitoring notice, privacy and AI rules overlap
US employers should identify where each worker works, where communications occur and which entities receive the data. Federal interception and stored-communications rules operate alongside state recording and monitoring laws. Employer ownership of a device does not decide every interception or access question. Anti-discrimination, disability accommodation and collective-bargaining obligations also remain relevant when software changes how work is evaluated. 18 USC sections 2511 and 2701; stored communications; Title VII; ADA; NLRB employer obligations.
Employee monitoring laws by state have different triggers. New York Civil Rights Law section 52-c covers specified telephone, electronic-mail and internet monitoring by private employers with a place of business in the state: give the covered hiring notice, obtain written/electronic acknowledgement and post a conspicuous notice. Delaware section 705 covers an employer with a place of business in Delaware monitoring covered activity of employees in the state; it permits either the prescribed electronic notice on each access day or one prior written/electronic notice acknowledged by the employee. Each statute’s system-management exception has defined conditions. Private-content capture still requires the separate communications and privacy analysis. New York section 52-c; Delaware section 705.
Connecticut changed section 31-48d with Public Act 26-73, effective 1 October 2026. For monitoring within its on-premises definition, notices and postings must identify specific monitored locations, subject to limited exceptions. Employees hired on or after that date must receive, before starting employment, a plain-language written statement identifying prohibited activities that may be monitored under the misconduct exception without prior notice. The airport and reasonable-ground security/safety exception concerns disclosure of specific locations; it does not remove every notice requirement. A remote home should not simply be assumed to be the employer's premises. Public Act 26-73, section 1.
California adds workforce privacy duties for a covered California Consumer Privacy Act (CCPA) business, alongside employment discrimination rules. Its privacy regulations took effect on 1 January 2026. New covered high-risk processing requires a prior risk assessment; relevant processing already underway before that date has a 31 December 2027 assessment deadline. Systematic worker observation used for automated profiling can trigger assessment even where the eventual decision falls outside the automated decision-making technology (ADMT) definition. The ADMT significant-decision provisions require compliance from 1 January 2027. A human removes a decision from the “substantially replaces” limb only by understanding the output, analysing it and other relevant information, and having authority to change the decision. The opt-out exceptions include a qualifying human appeal and systems used solely for allocation or compensation that work for their purpose and do not unlawfully discriminate. California’s automated-employment discrimination regulations have applied since 1 October 2025. CCPA; CPPA regulations, sections 7001(e), 7150, 7155, 7200 and 7221; Civil Rights Department explanation.
A separate California law, SB 947, Chapter 859 of 2026, becomes operative on 1 July 2027. Its automated decision system (ADS) definition reaches covered systems that assist or replace human discretion and materially affect people. It bars sole reliance on ADS for discipline or termination; when the employer primarily relies on the output, a human must corroborate it, and an uncorroborated, inaccurate, incomplete or misleading output cannot support that decision. It adds employee-data-description and post-use notice requirements. Its specified collective-agreement and federal-operation exceptions are conditional, and it preserves applicable California Privacy Protection Agency (CPPA) obligations. These are enacted future duties as at 21 November 2026. SB 947, Labor Code sections 1520–1526.7.
Colorado’s SB 26-189 replaces the earlier AI regime. Its principal duties apply by statute to decisions on or after 1 January 2027. Covered ADMT must materially influence a consequential decision, including a covered employment decision. Following an adverse outcome, the consumer can request review by a trained human with authority to change the result, to the extent commercially reasonable. The separate correction right excludes opinions, predictions and scores. Developers and deployers have different documentation and retention duties. The Attorney General adopted rules on 19 November 2026. Enacted sections 6-1-1701–1705 and commencement; AG rulemaking status.
Illinois’s employment-AI discrimination and employee-notice amendment has applied since 1 January 2026. Detailed proposed notice rules were withdrawn in June 2026; implement the enacted notice duty rather than relying on the withdrawn thirty-day or annual timetable. Illinois amendment; withdrawal.
Biometric products need another state-specific analysis, including the Illinois Biometric Information Privacy Act (BIPA). New York City's automated employment decision law is focused on hiring and promotion, so it is not a general licence or comprehensive code for every existing-worker performance measure. A vendor that supplies employment consumer reports can also engage the Fair Credit Reporting Act (FCRA) under its actual activities. An employer should therefore record the legal role and function of each score rather than label the entire product simply “employee monitoring.” Illinois BIPA; NYC Local Law 144; FCRA employment reports.
Canada: determine the employment privacy regime first
The Personal Information Protection and Electronic Documents Act (PIPEDA) does not govern every private-sector employment relationship in Canada in the same way. Federal employment coverage, substantially similar provincial laws and the actual processing connection matter. British Columbia and Alberta have employment-information routes subject to their statutory reasonableness and notice conditions. Quebec imposes its own private-sector requirements. The employer should classify the business, province, worker relationship and data flow before selecting a basis. PIPEDA; federal privacy regulator workplace guidance; BC PIPA; Alberta guidance; Quebec Act.
In Ontario, an employer with 25 or more employees on 1 January must have the required written electronic-monitoring policy before 1 March. The policy states whether monitoring occurs and, if so, describes how and in what circumstances it occurs and the purposes for which the employer may use the information. Delivery obligations and the relevant 30-day periods must also be met. The rule does not itself create a general right not to be monitored or a power to monitor without considering other law. ESA, section 41.1.1.
Quebec's section 12.1 addresses a decision based exclusively on automated processing. It requires disclosure of that fact and, on request, specified information about the personal information used and the reasons and principal factors or parameters behind the decision, with an opportunity to make observations to a person able to review it. Biometric identity measures have additional rules. These duties should be designed into the vendor interface and employer response process. Quebec private-sector Act, section 12.1; CAI biometric guidance.
Ontario’s defined digital-platform regime has applied since 1 July 2025 to covered ride-share, delivery and courier work, with taxicab and limousine services excluded by Regulation 344/24. Within 24 hours after initial access, the operator must provide the required pay, assignment, rating and performance-evaluation information, including relevant internal or external evaluation methods and consequences. Removal requires a written explanation. The ordinary two-week notice period applies to removal lasting 24 hours or more; exceptions cover non-trivial uncondoned wilful misconduct, public-safety concerns and specified legal requirements or inability to work lawfully. Those exceptions leave the written-explanation duty in place. Classify the service and build the information, removal and retained-record workflows before activating automated restrictions. Digital Platform Workers’ Rights Act, sections 7, 11 and 14; Regulation 344/24, sections 1–2, 5–6, 9–10.
Europe: privacy permission and collective participation remain separate
The EU layer: existing duties survive the AI timetable change
The GDPR applies to identifiable monitoring inputs and to personal inferences and scores. Article 22 restricts decisions based solely on automated processing that produce legal or similarly significant effects, subject to its defined exceptions and safeguards. The employer must assess how the decision actually happens. A manager who routinely accepts an unexplained score is a weak basis for asserting meaningful human involvement. Articles 13–15, 16 and 21 can add information, access, correction and objection duties according to their conditions. GDPR.
The AI Act separately prohibits covered workplace emotion inference, subject to the medical or safety exception, from 2 February 2025. Its emotion-recognition definition concerns inference from biometric data. Ordinary productivity, enthusiasm or conduct scoring should not be relabelled “safety” to obtain an exception. Biometric categorisation to infer specified sensitive traits is separately restricted. A text-sentiment function outside that precise definition still requires privacy, discrimination and employment analysis. AI Act, Articles 3(39) and 5(1)(f)–(g).
The enacted Regulation (EU) 2026/1744 changed the timetable. Chapter III, Sections 1–3, except Article 6(5), applies from 2 December 2027 for Annex III systems, including the specified worker-management uses; the corresponding Article 6(1) product-safety route applies from 2 August 2028. The amendment does not postpone the GDPR, national consultation law or the existing prohibited-practice rules. Article 86 is outside the postponed sections and retains the general 2 August 2026 application date for its qualified explanation right. Its application to a particular system nevertheless depends on classification and Article 111(2): that provision broadly limits the Regulation’s application to operators of high-risk systems placed on the market or put into service before the relevant Chapter III date unless significant design changes occur from that date, while preserving Article 5 and the public-authority 2030 rule. Record the actual system dates and changes before claiming either an unconditional current Article 86 duty or a legacy exemption. Existing GDPR information and decision safeguards remain independently relevant. AI Act, Articles 86, 111 and 113; Amending Regulation, Article 1(39)–(40).
Germany: complete the council route and examine the 2026 scoring provision
Where the Works Constitution Act applies and a works council exists, section 87(1)(6) gives co-determination over technical systems objectively capable of collecting and recording employee conduct or performance information, including relevant system changes. The employer’s subjective intention to monitor is irrelevant. BAG, 9 AZR 48/24, paras 27–29. Sections 80(3) and 90 also matter to expertise and planning involving AI. Worker notice and the employer's privacy assessment do not replace that participation. The approved work agreement should describe inputs, purposes, access, retention, permissible decisions and changes to the system. BetrVG.
The privacy basis needs particular care. Following the decision of the Court of Justice of the European Union (CJEU) in C-65/23, the Federal Labour Court's 8 May 2025 decision, 8 AZR 209/21, disapplied the general section 26(1) employment-data provision in the processing it examined and assessed the GDPR directly. An employer should not cite section 26(1) as a complete answer to a new monitoring rollout. Collective agreements also remain subject to GDPR necessity and other substantive requirements. CJEU, paragraphs 35–60; BAG, paragraphs 16–22.
Germany's Federal Data Protection Act also gained BDSG section 37a, effective 20 November 2026. It provides a conditional route for specified probability-based predictions used in contractual decisions, with restrictions on input categories, scientific relevance, purpose, explanation and challenge, including a natural-person decision on request. Its wording is not confined to credit scoring. Whether a particular productivity score falls within it, and its application consistently with EU law, requires a focused assessment; a retrospective activity count is not automatically a prediction of future behaviour. Do not treat section 37a as permission for unrestricted automatic discipline. Equality law, dismissal grounds and works-council hearing duties remain separate. Section 37a; commencement Act, Articles 3 and 16; BetrVG section 102.
France: relevance and prior participation constrain the product
French Labour Code Articles L1222-3 and L1222-4 require relevant evaluation methods, confidentiality of evaluation results and prior employee information about the relevant methods and personal-information collection devices. Article L2312-38 requires the applicable social and economic committee (CSE) information and consultation before the decision to implement employee-activity monitoring in businesses with at least 50 employees, subject to the applicable CSE coverage and competence rules. L1222-3; L1222-4; L2312-38.
The July 2026 guidance of the Commission nationale de l’informatique et des libertés (CNIL) treats permanent surveillance for productivity, including continuous webcam or keylogging arrangements, as disproportionate. Its June 2026 access/timekeeping guidance distinguishes genuine security access from ordinary attendance control, for which biometrics and systematic photographic checks are excessive. Vehicle geolocation can serve defined purposes but should not follow a worker outside working time; its use to measure working time is not freely interchangeable with less intrusive methods. These regulator interpretations apply to the specified purposes and monitoring designs. Monitoring guidance; access and timekeeping; vehicle geolocation. For biometric security access within its scope, CNIL’s binding 2019-001 standard requires documented necessity and inadequacy of less intrusive authentication, a prior DPIA, written information before enrolment, and template-control and security safeguards. Standard regulation, Articles 3 and 7–11.
For consequential employee decisions, French labour law adds concrete limits: L1132-1 prohibits discriminatory pay, scheduling, evaluation, promotion and dismissal; L1331-2 prohibits monetary disciplinary sanctions. L1332-1 requires written disciplinary allegations. A dismissal for personal reasons requires a real and serious cause under L1232-1 and the prior-meeting procedure in L1232-2. Validate the score and hear the employee before applying the relevant decision process. L1132-1; L1232-1; L1232-2; L1331-2; L1332-1.
United Kingdom: apply the changed automated-decision rules
The UK's Data (Use and Access) Act 2025 (DUAA) replaced the old Article 22 structure with Articles 22A–22D, effective 5 February 2026, subject to savings for specified earlier decisions. For ordinary personal data, the revised framework permits more solely automated significant decisions while requiring safeguards including information, representations, human intervention and contest. Special-category processing and decisions relying on the recognised-legitimate-interest basis face additional restrictions. Ordinary legitimate interests and the separately defined recognised-legitimate-interest basis must not be confused. DUAA section 80; SI 2026/82.
For scored pay or discipline in Great Britain, verify the actual wage entitlement and an authorised deduction route under Employment Rights Act (ERA) section 13, the Equality Act’s discrimination and reasonable-adjustment duties, and the relevant dismissal ground and fair process. Ordinary unfair-dismissal protection generally still requires two years’ service as at 21 November 2026; the enacted six-month period applies where the effective date of termination is on or after 1 January 2027. Automatically unfair grounds and discrimination follow separate conditions. Investigate disputed score data, let the employee answer the case and provide the applicable appeal and accompaniment rights. Northern Ireland requires its own employment-law assessment. ERA section 13; ERA section 108; SI 2026/559, regulations 3–4; Equality Act; ERA section 98; Acas Code; Employment Relations Act 1999, section 10.
The monitoring guidance of the Information Commissioner’s Office (ICO) remains useful for necessity, impact assessment, worker consultation and exceptional covert investigations, but, as at 21 November 2026, expressly warns that it is under review following the DUAA. Apply current legislation where the guidance’s older automation or transfer passages differ. ICO guidance.
UK international transfers also changed on 5 February 2026. Identify approval by regulations, appropriate safeguards or a qualifying derogation. For the ordinary safeguards route under amended Article 46, the exporter must provide the required safeguard and reasonably and proportionately assess whether protection after transfer would be not materially lower than the UK statutory standard. Map actual hosting, support and onward access before selecting the route. DUAA Schedule 7, new Articles 44A and 46; SI 2026/82, regulation 2(m) and (z9).
Digital labour platforms need a distinct European implementation check
The Platform Work Directive applies through its definition of a digital labour platform and persons performing platform work. Its algorithmic-management provisions address prohibited data uses, information, oversight and review; key protections extend beyond persons ultimately classified as employees. Article 10(5) requires a human decision for specified detrimental account or contractual actions, and Article 11 supplies a review framework. Its transposition deadline is 2 December 2026. That date does not prove identical present application to every employer or platform in every Member State. Establish the national implementing measure and commencement before relying on or applying the directive's rules to a launch. Directive (EU) 2024/2831, Articles 1–2, 7–11, 15 and 29.
Asia: employment exceptions do not eliminate purpose limits
India: the DPDP employment basis applies from 13 May 2027
India's commencement notification stages the Digital Personal Data Protection (DPDP) Act and Rules. The core processing and rights provisions, including the employment-use ground in section 7(i), and the repeal of IT Act section 43A commence on 13 May 2027. The consent-manager phase began on 13 November 2026. An employer deploying before 13 May 2027 cannot treat the future employment ground as its present authority. G.S.R. 843(E); official November 2026 consent-manager announcement.
As at 21 November 2026, the relevant legacy IT Act and Sensitive Personal Data or Information (SPDI) Rules analysis remains necessary. Sensitive personal data, including the specified biometric and health categories, engages requirements concerning consent, purpose, necessity, notice, disclosure, transfers and security. Classify ordinary app metadata against the specified sensitive-data categories and assess communications and employment restrictions separately. The governmental clarification of outsourced processing also requires the employer and supplier to identify their actual roles. SPDI Rules, rules 3–8; government clarification; IT Act.
India's labour-code transition is separate. The Industrial Relations Code has applied since 21 November 2025. Its section 40 notice-of-change mechanism applies to specified Third Schedule changes, with a 21-day condition and statutory exceptions; it is not a universal notice rule for every software update. The standing-orders chapter generally covers industrial establishments with at least 300 workers, including that number on any day in the preceding 12 months, subject to the statutory exceptions. The employer must apply the final 2026 Central Rules where the Central Government is the appropriate government and check the applicable State rules and collective terms. Pay deductions also require a ground permitted by Code on Wages sections 18–20; keyboard inactivity alone does not establish statutory absence or justify a fine. Final Central Rules; Code on Wages; wage-code commencement. A targeted incident investigation and a performance-management change may therefore need different approvals. Commencement notification; Industrial Relations Code, sections 28 and 40.
Singapore: distinguish employment, evaluation and investigation purposes
Singapore's Personal Data Protection Act (PDPA) provides different exceptions for reasonable management or termination of an employment relationship, evaluative purposes, and necessary investigations or proceedings. Current First Schedule Part 3 paragraph 10 is the employment provision; paragraph 2 concerns evaluative purposes and paragraph 3 investigations. These exceptions should be matched to the actual use. Employment-purpose notice under sections 20(4)–(5) remains relevant even where consent is not required. Current PDPA.
The practical configuration should state which work events are collected, what assessment follows and which private activity is excluded. An employer cannot assume that a supplier's separate model training is covered by the employer's employment exception. Nor should the policy promise unrestricted access to every evaluative opinion or correction of every derived score: the Fifth and Sixth Schedules contain specific exceptions, while other duties and rights continue to apply. PDPA, sections 18, 20–22 and Schedules; PDPC employment guidance; AI decision-system guidance.
Before misconduct dismissal, the employer must follow the applicable inquiry process. Platform-worker protections apply to their defined services and relationships. Singapore's Workplace Fairness legislation was, as at 21 November 2026, still scheduled for implementation at the end of 2027, so it should not be described as a current statutory prohibition already governing a deployment. Existing rules and official fair-employment expectations still need attention. MOM misconduct guidance; platform scope; November 2026 implementation statement.
South Korea: individual rights, consultation and AI duties can all apply
South Korea's Personal Information Protection Act (PIPA) requires an applicable basis, purpose limitation and additional conditions for sensitive information. Article 37-2 creates rights concerning fully automated decisions, including refusal in specified serious-impact circumstances and explanation or review-related measures. The refusal exceptions and explanation obligations are not identical; a contract or consent route should not be treated as extinguishing every right. Location and non-public conversation recording have separate statutory controls. PIPA Article 37-2; Enforcement Decree Articles 44-2–44-4; Location Information Act; communications secrecy rule.
Covered workplaces with at least 30 workers have a labour-management council framework, and monitoring installations can require consultation. Changing employment rules adversely can separately require majority-union or worker consent under the Labour Standards Act. These are different processes. The employer should give representatives the data fields, scoring use, retention and proposed consequences before deciding whether its monitoring change satisfies either route. Participation Act; MOEL workplace-monitoring response; Labour Standards Act.
The AI Basic Act has been in force since 22 January 2026. The announced ordinary enforcement grace does not turn it into uncommenced legislation or suspend PIPA and employment duties. Classify the vendor, platform and employer under Article 2’s developer, AI-using business and recipient-user definitions. The high-impact test combines the statutory risk condition with a listed domain, including judgments or evaluations that significantly affect rights or obligations. For a qualifying AI business operator, Article 34 requires risk management, appropriate explanation measures, user protection, human supervision and records; Decree Article 27 adds specified publication and five-year evidence retention. AI Basic Act; MSIT commencement announcement.
Middle East: identify the legal system before selecting a basis
UAE federal law: no general legitimate-interest shortcut
The UAE federal Personal Data Protection Law (PDPL) applies through its territorial and personal scope and has exclusions, including for free-zone entities subject to special data-protection legislation. Its Article 4 exceptions include processing necessary for legally established employment rights and obligations, but do not create a generic legitimate-interest basis for any efficiency objective. The employer must identify the particular exception or valid consent route and assess the exact data and purpose. Communications and criminal-law rules need their own assessment, and the correct employment jurisdiction must be determined separately. Federal PDPL, Articles 2 and 4; federal employment law.
Article 18(1) gives a right to object to decisions resulting from automated processing that have legal consequences or seriously affect the person, including profiling. Article 1 includes partial automation with limited human supervision, so the employer must examine the reviewer’s actual role. Article 18(2) provides specified contract, legal-necessity and prior-consent exceptions, while paragraphs (3)–(4) preserve safeguards and requested human review. Controlling Arabic PDPL, Articles 1 and 18.
DIFC: autonomous-system controls add a product-level gate
DIFC's Data Protection Law contains its own bases, special-category conditions and automated-decision rights. Regulation 10 adds controls for autonomous and semi-autonomous processing systems, including transparency, fairness, accountability and an Autonomous Systems Officer where required. Its high-risk commercial-use route includes applicable Commissioner audit and certification conditions and human-defined or approved purposes. The evidence file should identify how the particular system satisfies each applicable audit, certification, purpose and officer condition. DIFC Law; Regulations, Regulation 10; Commissioner FAQs.
The employer and vendor should determine whether the particular system and use fall within that route and obtain the relevant certification evidence. The Commissioner's framework exists; the actual product's status must still be verified. Amendments were proposed in June 2026. DIFC employment obligations remain separate from the data-protection analysis, including when the workforce arrangements create connections beyond the centre. Consultation Paper 3/2026; DIFC Employment Law.
ADGM: use its current privacy and employment provisions
ADGM's Data Protection Regulations have their own lawful-basis and special-category provisions and a section 20 automated-decision rule. The employer must apply ADGM’s exception and safeguard structure and the applicable request-response period. Processor terms, impact assessment, access and international transfers also need an ADGM-specific analysis. ADGM Regulations, sections 5, 7 and 20.
The Employment Regulations 2024 took effect on 1 April 2025 and, as at 21 November 2026, the text includes 28 October 2025 amendments. They expressly address remote employees and include their own discrimination, contract-change and termination provisions. Under section 58, the employer must provide written termination reasons within 21 calendar days after receiving the employee’s written request. A new consultation opened on 16 November 2026 is a proposal as at 21 November 2026. Current Employment Regulations; November consultation.
Saudi Arabia: sensitive data, sole automation and transfers need separate grounds
Saudi Arabia's PDPL and Implementing Regulation allow a conditional legitimate-interest route for non-sensitive processing, with an assessment of interests and rights. Article 16 of the Regulation excludes sensitive data from that route. Where consent is the legal route, Article 11(2)(c) requires it to be explicit for decisions based solely on automated processing. PDPL Article 6 separately provides consent exceptions, including qualifying processing pursuant to law, in implementation of a previous agreement, or for legitimate interests subject to its conditions. The employer must identify and substantiate the precise route; a general employment clause or an undocumented balancing assertion is insufficient. PDPL; Implementing Regulation, Articles 11 and 16; original Arabic Regulation.
A narrow work-event report should therefore be assessed separately from facial or health inference and automatic adverse action. Saudi labour law supplies its own disciplinary and termination conditions. Foreign support, cloud hosting and group human resources (HR) operations must also fit the current transfer framework: the revised 2024 Transfer Regulation contains specified safeguards and assessment rules, including a defined multinational-group HR route. It is not a general exemption for all group transfers. Labour Law; Transfer Regulation, Articles 4 and 7; original Gazette instrument.
Africa: make review and investigation procedures operational
South Africa: POPIA permission does not resolve interception or dismissal
The Protection of Personal Information Act (POPIA) requires lawful, reasonable and proportionate processing for a specified purpose, with separate conditions for special personal information. The employer is ordinarily the responsible party for its monitoring purpose; an instructed supplier can be an operator, while independent training changes the role analysis. POPIA section 71 restricts specified solely automated decisions with legal or substantial effects and provides defined routes and safeguards. It does not contain a free-standing general consent exception equivalent to the GDPR's. POPIA, sections 8–22, 26–33 and 71. The information officer must also ensure a personal information impact assessment establishes adequate measures and standards for lawful processing; this duty is not confined to processing classified as high risk. Include the assessment in the deployment record. POPIA Regulations, regulation 4(1)(b), retained by the 2025 amendment, item 4 and subitems 4.1–4.3, brought into effect by GN 6126, paragraphs 1–2.
Communications interception must separately fit the Regulation of Interception of Communications and Provision of Communication-Related Information Act (RICA). Its business-monitoring route has conditions concerning the communication, system, purpose, authority and information steps; installing a policy is not enough to approve every recording. Psychological or similar assessment also requires attention to the Employment Equity Act's testing rules where applicable. A biometric or health inference should be examined under the special-data conditions and relevant health-information regulations, rather than being bundled into a general productivity basis. RICA, section 6; Employment Equity Act, section 8; 2026 health-information Regulations.
When a score contributes to discipline or poor-performance action, the employer must establish the employment ground and fair procedure independently. The applicable Code of Good Practice: Dismissal, published 4 September 2025, replaced the former Schedule 8 code. Use its current process, including appropriate opportunity to respond and the relevant performance support and assessment, rather than a checklist citing only the superseded schedule. 2025 Code.
Kenya: the impact-assessment timetable can determine launch
Kenya's Data Protection Act requires an applicable basis, proportionate processing and safeguards. Section 31 requires a DPIA where the processing is likely to create high risk, and subsection (5) requires the report to be submitted 60 days before processing. The employer should incorporate that statutory step into the implementation sequence, rather than discover it after the monitoring pilot has begun. Data Protection Act, sections 25, 30 and 31. Registration is a separate launch condition for controllers and processors. The small-entity exemption requires both turnover/revenue below KES 5 million and fewer than ten employees, and specified purposes remain registrable regardless of size, including security closed-circuit television (CCTV) for crime prevention and transport services such as passenger-hailing platforms. Check the employer and vendor separately. Registration Regulations, regulations 4 and 13 and Third Schedule.
Section 35 addresses solely automated decisions with legal or similarly significant effects, while General Regulations regulation 22 supplies relevant safeguards. An employer needs an actual procedure for information, human intervention and challenge where required. Sensitive biometric processing needs its own route; the 2025 biometric guidance of the Office of the Data Protection Commissioner (ODPC) does not treat legitimate interest alone as sufficient. Sensitive-data exports require the section 49 consent and safeguard conditions, in addition to the broader transfer analysis. Act, sections 35 and 49; General Regulations, regulation 22; ODPC biometric guidance.
Employment Act sections 41, 43 and 45 separately govern the relevant hearing, reasons and fairness issues. A low productivity score can be evidence to examine, but it does not substitute for those conditions. Work-only collection, representative or worker engagement where required, a correction channel and a restricted investigation file should be built before the system supplies adverse evidence. Apply the current provisions together with the precise sector or collective conditions governing a launch. Employment Act.
Latin America: purpose restrictions can stop secondary disciplinary use
Brazil: notice does not cure excessive monitoring
Brazil's General Data Protection Law (LGPD) provides general and sensitive-data bases, purpose and necessity principles, rights and controller/operator duties. The legitimate-interest guidance of the National Data Protection Authority (ANPD) directly examines an employer collecting every keystroke and webcam images for productivity and leak prevention. In Example 7, the regulator rejects that justification because of excessiveness and the employment power imbalance despite prior notice. ANPD applies the LGPD’s necessity and balancing requirements to that intrusive configuration. A narrower design based on necessary work events and less intrusive alternatives requires its own assessment. LGPD, Articles 6, 7, 10 and 11; ANPD guidance, Example 7.
Article 20 gives a right to request review of qualifying solely automated decisions affecting interests, including professional profiles, and information about criteria and procedures subject to the statutory treatment of secrets. Article 20 does not expressly guarantee that every such review is performed by a natural person. Effective human review remains a prudent contractual and employment-process design, but it should not be quoted as containing words that were removed from the law. LGPD, Article 20.
The employer must also comply with labour restrictions on harmful changes and dismissal, and identify a valid international-transfer route. Assess the foreign service and its actual data flows against ANPD’s 2024 transfer regulation and standard clauses. Brazil's general AI bill remained a proposal as at 21 November 2026. CLT; ANPD Resolution 19/2024; PL 2338/2023 history.
Mexico: use the replacement privacy law and platform rules
Mexico replaced its federal private-sector personal-data law in March 2025, with a further amendment in November 2025. The current authority is the Secretaría Anticorrupción y Buen Gobierno. Old article numbering and references to the National Institute for Transparency, Access to Information and Personal Data Protection (INAI) should not be carried into a current monitoring policy without checking the new framework. The consent exception for obligations arising from a legal relationship is in Article 9(IV), while purpose, proportionality, notice, security and rights continue to apply. 2025 replacement law; amendment history.
Article 26(II) expressly provides an opposition route for specified automated evaluation without human intervention that produces unwanted legal effects or significantly affects interests, rights or freedoms, subject to its legal-obligation condition. The policy and vendor process should support that right. For telework within the Labour Act's defined regime, supervision must respect privacy; cameras and microphones are restricted to extraordinary cases or the nature of the functions. This does not authorise continuous home observation merely because the worker signed a telework agreement. Privacy law, Article 26; Labour Act, Article 330-I.
The digital-platform employment chapter has applied since 22 June 2025. It requires an algorithmic-management policy and, under Article 291-P, mechanisms for review by personnel with decision-making authority, rather than an exclusively algorithmic appeal. Status, covered platform work and the exact action still matter. Ordinary contractors outside that regime do not automatically acquire every platform-employment right. Platform decree; Labour Act, Articles 291-J and 291-P.
Chile: keep safety data out of productivity and discipline
Chile requires a close distinction between pre-reform and reformed privacy law. Law 19.628 governs as at 21 November 2026, alongside strong Labour Code limits. The reforms under Law 21.719, incorporating the February 2026 amendment, take effect on 1 December 2026. Law 21.719’s Article 8 bis automated-decision framework should not be narrowed by inserting a “solely automated” condition absent from its text. Law 21.719’s biometric, employment health/biology and transfer provisions also have specific conditions and exceptions. Current Law 19.628; Law 21.719.
For monitoring, the Dirección del Trabajo’s Dictamen 388/32 of 2 September 2026 sets out a preventive route for grave, concrete and objectively identifiable risks to life or physical integrity. It requires documented risk assessment, necessary and proportionate collection, worker information, use confined to prevention and timely alerts to the worker. An equally effective, less intrusive alternative defeats the claimed need for the more intrusive design. The technology supplements controls over hours, rest, staffing and work organisation. The opinion expressly excludes reuse of the resulting data for individual productivity or performance evaluation, discipline or termination and supersedes incompatible earlier administrative doctrine. Dictamen 388/32.
A fatigue-detection device can therefore have a possible safety route while its data remain unavailable for a productivity score. Calling the same data “performance evidence” later would contradict the assessed purpose. The employer must also apply the Labour Code's proportionality, internal-rule, confidentiality and telework protections. In the current code, the confidentiality provision is Article 154 ter, not the former 154 bis location. Platform workers have specific algorithmic non-discrimination and data-access protections, including the applicable route to their own ratings and information. Labour Code, Articles 5, 154, 154 ter, 152 quáter K–L and platform provisions.
Oceania: a federal privacy exemption is not a surveillance exemption
Australia: check the state and the record exemption separately
Australia's private-sector employee-record exemption is tied to an act or practice directly related to a current or former employment relationship and an employee record held by the employer. It does not automatically cover contractors, applicants, a separate software supplier or every collection and use. State and territory surveillance rules, employment obligations and the serious-invasion-of-privacy framework need separate attention. Privacy Act; OAIC employee-record guidance; OAIC privacy-tort guidance.
In New South Wales, the Workplace Surveillance Act contains prior-notice rules, camera, computer and tracking conditions, restrictions concerning private places and surveillance while a worker is not at work, and a covert-surveillance authorisation mechanism. Covert authority is issued by the relevant Judge under the current Act. Ordinary notice generally requires at least 14 days unless the statutory alternative applies; a computer-surveillance policy must be notified in advance in the prescribed way. These rules are not interchangeable with the Australian Capital Territory (ACT) regime or a nationwide employee-consent rule. NSW Act, Parts 2–4.
The ACT Workplace Privacy Act requires its own notice and good-faith consultation during the notice period, giving workers a genuine opportunity to influence implementation. For notified surveillance, section 22 requires advance notice of proposed adverse-action use. Section 23 provides access on written request; unjustified refusal prevents the employer using the record against the worker in the specified proceedings or adverse action, subject to the statutory exceptions. Audio recording still needs the separate surveillance-device and communications analysis. Maintain a state-specific feature and notice annex, with off-duty tracking disabled and remote/shared-device boundaries demonstrated. ACT Act, sections 13–14 and 22–23; NSW Surveillance Devices Act.
For covered employee-like digital-platform workers, the current Digital Labour Platform Deactivation Code has procedural requirements before relevant deactivation. Section 13(7) of the current Code expressly requires a human representative to consider the worker’s response. Statutory coverage and eligibility must still be established. Separate federal privacy-policy transparency duties concerning significant automated decisions begin on 10 December 2026. Fair Work Act; Deactivation Code; OAIC commencement guidance.
New Zealand: biometric rules already require a current assessment
New Zealand's Privacy Act principles address lawful purpose, necessary collection, notice, fairness, security, access, correction, accuracy, retention, use and disclosure. The employer should assess whether work-output evidence can serve its purpose without broad content capture and should make performance measures challengeable. Employment good faith and fair process remain separate from data-collection authority. Privacy Act; OPC employee-monitoring guidance; employment privacy guidance. Since 1 May 2026, general IPP 3A also requires reasonable steps to notify people of indirect collection as soon as reasonably practicable, unless they already know all prescribed matters or a specified exception applies. Map employer receipt of vendor-supplied information against that rule and the Act’s agency-processing distinction, and assign responsibility for the notice. OPC’s full IPP 3A text; commencement confirmation.
The Biometric Processing Privacy Code is already operative; the transition for qualifying existing processing ended on 3 August 2026. Rule 1 requires a lawful connected purpose, effectiveness and necessity, assessment of equally effective alternatives with lower privacy risk, safeguards and proportionality. For a private benefit, the benefit must outweigh the privacy risk to a substantial degree. Rule 10 restricts covered biometric emotion, personality, mood and mental-state categorisation, subject to its specified exceptions. Ordinary engagement or productivity scoring has no general consent exception. The separate fatigue, alertness or attention exception requires necessity to prevent or lessen the specified life, health or safety risk. Distinguish biometric characteristics and analysis from an ordinary image or activity count before applying those rules. Current Biometric Code, clauses 3–4 and rules 1, 10(5)–(9).
New Zealand’s contractor gateway began on 21 February 2026. It requires all prescribed conditions, including written contractor terms, permission for other work, qualifying freedom over timing or subcontracting, ability to decline additional work without ending the arrangement, and a reasonable opportunity for independent advice. A worker who fails that gateway still needs the true-nature assessment; pre-existing status proceedings have a separate transition exception. Separate dismissal changes concern employees meeting the NZ$200,000 annual-remuneration threshold, with a statutory calculation and written opt-back-in route. The transition preserves the specified protections for qualifying existing positions and restructuring continuity; its dismissal protection concerns qualifying dismissals before 21 February 2027, subject to written early application. The affected protections concern unjustified dismissal and dismissal-related disadvantage; other discrimination, privacy, contractual and remaining good-faith duties continue. Establish the remuneration, role-continuity and agreement facts before relying on the exclusion. Official contractor guidance; current high-income dismissal guidance; Employment Relations Act, sections 6, 67I–67J, 113A–113B and Schedule 1AA clauses 27–32.
A score needs a decision process that can withstand a challenge
Before using an activity score, the employer should be able to explain what it measures and what it leaves out. Time without keyboard input can include reading, thinking, a telephone call, an accessibility tool, approved leave or a software outage. Test those possibilities against the worker’s actual tasks and records. The decision record should show how the employer tested the explanation against relevant work evidence.
Review must match the applicable right. EU GDPR Article 22, the UK's amended regime, UAE federal Article 18, Brazil's Article 20, Kenyan regulation 22 and the relevant platform rules have different thresholds and remedies. A common operational design can provide a trained reviewer, access to the underlying work evidence, authority to change the outcome and a documented response. The employer should describe that as its chosen control where the statute does not expressly require a natural-person review. GDPR; UK amendment; UAE PDPL; LGPD; Kenyan Regulations.
The decision file should contain the score version and inputs, material limitations, relevant comparator and accommodation checks, the worker's explanation, the reviewer's independent reasons and the action taken. Use job-specific validation and decision evidence to assess whether the score measures the work and supports the proposed action. Retain enough evidence to answer the applicable access and challenge rights without retaining every raw feed indefinitely.
Dates that change the implementation plan
- EU workplace emotion prohibition. Status at 21 November 2026: Applicable since 2 February 2025. Deployment implication: Exclude covered inference unless the precise medical or safety exception is established. AI Act.
- UK revised automated-decision regime. Status at 21 November 2026: Commenced 5 February 2026, with savings. Deployment implication: Apply Articles 22A–22D and preserve special-data and other restrictions. DUAA; commencement.
- New Zealand biometric transition. Status at 21 November 2026: Relevant existing-user transition ended 3 August 2026. Deployment implication: Existing deployments need assessment under the current Code. Code.
- Connecticut monitoring amendment. Status at 21 November 2026: Effective 1 October 2026. Deployment implication: Update covered notices, location information and new-hire statements. PA 26-73.
- German BDSG section 37a. Status at 21 November 2026: Effective 20 November 2026. Deployment implication: Classify predictive scores and assess the new conditions alongside EU and labour law. Section 37a.
- Chile privacy reform. Status at 21 November 2026: Enacted; effective 1 December 2026. Deployment implication: Assess any continued or new deployment against the incoming framework. Law 21.719.
- EU Platform Work Directive. Status at 21 November 2026: Transposition due 2 December 2026. Deployment implication: Check actual national implementation and platform scope. Directive.
- Australian automated decision-making privacy-policy duties. Status at 21 November 2026: Begin 10 December 2026. Deployment implication: Prepare covered policy disclosures and confirm the statutory trigger. OAIC.
- California privacy ADMT. Status at 21 November 2026: Compliance from 1 January 2027. Deployment implication: Apply the final significant-decision, human-involvement, notice, access and opt-out conditions. Current risk-assessment duties have their own schedule. CPPA.
- Colorado replacement regime. Status at 21 November 2026: Principal duties apply by statute to decisions on/after 1 January 2027. Deployment implication: Apply SB 26-189’s material-influence and adverse-outcome tests. Session law; AG status.
- India's core DPDP processing provisions. Status at 21 November 2026: Commence 13 May 2027. Deployment implication: Use current law until 13 May 2027; prepare the future employment and rights route separately. Notification.
- California SB 947 workplace ADS rules. Status at 21 November 2026: Operative 1 July 2027. Deployment implication: Build corroboration, description and post-use notice processes for covered decisions. Chaptered law.
- Specified EU Annex III high-risk duties. Status at 21 November 2026: Deferred to 2 December 2027. Deployment implication: Maintain a version-specific plan; other current duties and legacy rules remain separate. Omnibus.
Remote work and bring-your-own-device arrangements need enforceable collection boundaries
For personal or shared devices, prefer a managed work profile or a work-application integration that prevents the monitoring agent from reading personal sessions. Limit collection to necessary working periods and functions. Where location is justified, choose the least precise useful signal and stop off-duty collection. Screen masking should exclude credentials, private messages, health or union communications and unrelated customer or household data before the employer receives them.
The employer should test those controls on the actual supported operating systems, applications and shared-device arrangements. Test account switching, a locked screen, offline work, a lost connection and a worker exercising a permitted pause. If the software cannot maintain the promised separation, narrow the feature or change the product before collecting the data. This is a recommended way to implement the purpose, minimisation, fairness and accuracy requirements discussed above; each country's mandatory controls still govern.
Access should follow the purpose. A supervisor may need a work-output trend without access to raw screenshots. Security personnel may need a restricted incident file without authority to feed it into routine performance ranking. Chile's preventive safety restriction is an express example of why such separation can be legally decisive. Dictamen 388/32.
Retention should distinguish raw events, diagnostic records, individual scores, incident evidence and employment decisions. Set a necessary period for each category, identify any statutory preservation duty or litigation hold, and test deletion, including vendor backups. For continuous webcam or keyboard content, justify retention against its lawful collection and purpose even where other employment records have a prescribed retention period.
Allocate vendor roles, reuse and international access explicitly
The employer ordinarily determines its monitoring purposes. A supplier processing only on instructions can occupy a processor or operator role under the relevant regime. A supplier deciding to use worker records for its own model training may have a separate role and needs its own lawful route. The contract should disclose that purpose rather than hide it in a general service-improvement clause. GDPR Article 28, Singapore's intermediary framework, POPIA's operator rules and the other country provisions require application to actual functions. GDPR; Singapore PDPA; POPIA.
Map production storage, support access, backups, subprocessors and model-training locations. Include foreign administrative access in the data-flow assessment even when the production server is local. Select the required transfer mechanism and assessment for each relevant flow. EU GDPR Chapter V, UK law, Saudi transfer rules, Kenyan sensitive-data export conditions and Brazil's ANPD instruments are different regimes. GDPR; UK GDPR; Saudi Transfer Regulation; Kenyan Act; ANPD Resolution 19/2024.
Investigation capability also needs contractual support. The employer should be able to reproduce the relevant model version, inputs, output and reviewer action and obtain assistance with lawful rights requests. Apply the relevant confidentiality and disclosure procedure to vendor trade-secret claims, including worker and authority requests for explanations.
An incident involving an employee's upload to an external AI service raises a separate confidentiality and permission inquiry. Licentium's employee-AI and trade-secrets analysis explains that issue. The response still needs a lawful monitoring route; suspicion of a leak does not create unlimited inspection authority.
Implement the controls in a defined order
- HR and the business owner define the decision. Identify the actual work problem, affected workers, countries, data needed and consequences a score can trigger.
- Privacy and employment owners map the applicable law. Establish status, employing and vendor entities, state or province, representative arrangements, sector and applicable commencement dates. Complete any applicable controller or processor registration, checking each entity separately.
- The business owner demonstrates necessity. Compare completed-work measures, sampling and aggregation with the proposed capture. Record why any more intrusive feature is needed.
- Privacy, security and the responsible information officer complete the impact process. Include household capture, sensitive inference, discrimination, error, reuse and transfers. Apply the jurisdiction’s actual assessment trigger, including South Africa’s information-officer duty, and complete required filing or regulatory consultation before processing.
- HR completes worker and representative participation. Distinguish prior information, consultation, co-determination and consent. Supply enough technical information for the relevant process to be meaningful.
- Engineering demonstrates the limits. Test work profiles, masks, off-duty controls, access, correction and deletion. Retain the approved configuration and results.
- Procurement binds the vendor. Agree purposes, instructions, reuse restrictions, locations, subprocessors, security, rights assistance, evidence, change control and exit.
- HR delivers the policy and notice. Explain actual collection and scoring, recipients, consequences, retention and review. Match local language and delivery requirements.
- The decision owner validates the use. Test job relevance and errors, ensure reviewers can change outcomes, and pilot within the approved legal and participation boundaries.
- Management approves the specific release. Record its purpose, version, permitted decisions and conditions. Reassess material changes before activation.
This sequence fits within a broader governance programme. Licentium's AI Governance Compliance Stack covers the organisational inventory, assessment, vendor and incident framework; the monitoring file adds the worker, feature and employment-decision evidence.
Annotated monitoring-policy outline
- Purpose and coverage. What the employer should state: Named entities, workers, locations, authorised purposes and local annexes. Supporting record: Role, territory and worker-status map.
- Collection and exclusions. What the employer should state: Fields, applications, capture frequency, working periods, personal/private exclusions and pause rules. Supporting record: Data dictionary, approved settings and technical tests.
- Basis and participation. What the employer should state: Applicable legal basis, required representative process and any genuine consent choice. Supporting record: Necessity assessment, DPIA, consultation or agreement, consent evidence where applicable.
- Scores and consequences. What the employer should state: What the score measures, limitations, allowed decisions, reviewer authority and prohibited uses. Supporting record: Validation report, decision procedure and training.
- Rights and challenges. What the employer should state: Notice, access, correction, objection, explanation and appeal routes with applicable exceptions. Supporting record: Request workflow and response records.
- Investigations. What the employer should state: Approval authority, grounds, scope, duration, confidentiality and lawful notice restrictions. Supporting record: Investigation mandate and evidence-access log.
- Vendors and transfers. What the employer should state: Recipients, roles, locations, permitted reuse and security responsibilities. Supporting record: Executed terms, subprocessor list and transfer assessment.
- Retention and changes. What the employer should state: Category-specific deletion, justified holds, review triggers and suspension authority. Supporting record: Retention schedule, deletion tests and version history.
Vendor information request
Before enabling the relevant features, ask the supplier to provide:
- Collection evidence: every field, capture permission, default, trigger and exclusion, including screens, keystrokes, clipboard, location, audio and administrative access.
- Boundary tests: what happens in personal accounts, private profiles, shared sessions, password fields and outside working hours, with demonstrable controls.
- Inference details: whether the system identifies people biometrically or infers emotion, health, protected characteristics, fatigue or personality, and how it does so.
- Score evidence: the claimed work outcome, material inputs, labels, data sources, known limitations, job-relevance testing, error patterns and explanation method.
- Decision controls: every automated action and threshold, options to disable it, reviewer evidence and authority, worker representations and correction or appeal support.
- Reuse terms: all training, improvement, retention, disclosure and independent-controller purposes, including upstream model-provider terms.
- Data-flow evidence: hosting, backups, support, training and administrator countries, subprocessors and onward access.
- Security and rights support: access controls, incident cooperation, audit evidence, request assistance and deletion or return on exit.
- Reproducibility: versioned inputs, outputs, configuration, timestamps, reviewer actions and exportable records suited to a lawful investigation or challenge.
- Change and classification evidence: applicable AI, biometric or autonomous-system classification and certification, model and feature changes, approval arrangements and rollback.
Prepare for a scoped review
For a scoped review, assemble the supplier’s responses with the workforce-location and status map, draft policy, proposed settings, collective arrangements, data flow and intended decision process. Licentium's AI Governance & Documentation describes the governance, assessment and documentation work relevant to that file. The release decision should identify the functions that can operate under the completed conditions and keep the remaining functions disabled until their own requirements are met.