<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>María Camila Salazar-Larsen | OHRH</title>
	<atom:link href="https://ohrh.law.ox.ac.uk/author/maria-camila-salazar-larsen/feed/" rel="self" type="application/rss+xml" />
	<link>https://ohrh.law.ox.ac.uk</link>
	<description>Oxford Human Rights Hub</description>
	<lastBuildDate>Mon, 06 Jul 2026 11:23:55 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://ohrh.law.ox.ac.uk/wp-content/uploads/2018/08/cropped-globe-only-hi-res_CIRCULAR-110x110.png</url>
	<title>María Camila Salazar-Larsen | OHRH</title>
	<link>https://ohrh.law.ox.ac.uk</link>
	<width>32</width>
	<height>32</height>
</image> 
<site xmlns="com-wordpress:feed-additions:1">39401664</site>	<item>
		<title>Women and the Labour Market: Navigating Algorithm Decision Making</title>
		<link>https://ohrh.law.ox.ac.uk/women-and-the-labour-market-navigating-algorithm-decision-making/</link>
					<comments>https://ohrh.law.ox.ac.uk/women-and-the-labour-market-navigating-algorithm-decision-making/#respond</comments>
		
		<dc:creator><![CDATA[María Camila Salazar-Larsen]]></dc:creator>
		<pubDate>Mon, 06 Jul 2026 11:23:55 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Colombia]]></category>
		<category><![CDATA[European Union]]></category>
		<guid isPermaLink="false">https://ohrh.law.ox.ac.uk/?p=87298</guid>

					<description><![CDATA[AI is reshaping the labour market, influencing operations across organisations, as Eurostat shows. The ILO has stated that women are more likely than men to be affected by automation. As a matter of fact, the impact of AI in the workplace extends beyond job displacement. It is then suspected that AI can reinforce existing gender [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><strong>AI is reshaping the labour market, influencing operations across organisations, as <a href="https://ec.europa.eu/eurostat/web/products-eurostat-news/w/ddn-20250123-3">Eurostat</a> shows. The <a href="https://www.ilo.org/resource/news/ilo-director-general-calls-placing-decent-work-heart-automation-and-ai">ILO</a> has stated that women are more likely than men to be affected by automation. As a matter of fact, the impact of AI in the workplace extends beyond job displacement. It is then suspected that AI can reinforce existing gender gaps. Empirical studies have shown that the bias and stereotypes that arise from the caregiving responsibilities that have been historically assigned to women, hinder their access to the labour market since employers believe women will be more absent from work, as they are assumed to prioritize their family (<a href="https://searchworks.stanford.edu/view/in00000985966">Ramírez-Bustamante et al, 2024</a>). One could ask, how can existing gender gaps be reinforced by AI? </strong><strong>Algorithms now influence multiple aspects of employment relationships, including recruitment. Take for example the case of X, a woman who applied for a job. X has taken several leaves to take care of her family. Now, due to inconsistent gaps in her CV, she was rejected in the automated CV-screening process. Therefore, data‑protection frameworks become essential to ensure that women’s data is not used to hinder access to the labour market The present account argues that the failure to treat “sex”-related information as sensitive data within data‑protection frameworks creates a barrier to women’s access to the labour market. Data‑protection rules must therefore be developed through a law‑in‑context perspective that recognises the historical obstacles women have faced in accessing employment. Comparative examples show that defining sensitive data according to the potential impact of its use, rather than through exhaustive lists, may offer stronger protection for women.</strong></p>
<p>Data-protection regimes should be analysed within the broader legal framework in which they operate. In the European context, both primary law (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:12016M/TXT">TEU</a>, <a href="https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:12016E/TXT">TFEU</a>, <a href="https://www.europarl.europa.eu/charter/pdf/text_en.pdf">CFREU</a>) and secondary legislation (<a href="https://eur-lex.europa.eu/eli/dir/2000/78/oj/eng">Directives 2000/78/EC</a>, <a href="https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32006L0054">2006/54/EC</a>, <a href="https://eur-lex.europa.eu/eli/dir/2024/1500/oj/eng">2024/1500/EU</a>) establish gender equality as a core principle of the Union. It is within this landscape that the General Data Protection Regulation (<a href="https://gdpr-info.eu/">GDPR</a><u>)</u> operates. Nonetheless, gaps remain: <a href="https://gdpr-info.eu/art-22-gdpr/">Article 22 GDPR</a> permits automated CV‑screening, and <a href="https://gdpr-info.eu/art-9-gdpr/">Article 9 GDPR</a> does not classify “sex” as a special category of data, possibly indirectly enabling gender‑based discrimination in algorithmic recruitment.</p>
<p>Under <a href="https://gdpr-info.eu/art-22-gdpr/">Article 22 GDPR</a>, organisations may rely on automated decision‑making when necessary to enter an employment contract. The provision prohibits basing such decisions on special categories of personal data like race or trade‑union membership, unless explicit consent is provided. However, <a href="https://gdpr-info.eu/art-9-gdpr/">Article 9(1) GDPR</a> does not explicitly include “sex” within its list of special categories of data. The <a href="https://www.edpb.europa.eu/sme-data-protection-guide/data-protection-basics_en">E</a><a href="https://www.edpb.europa.eu/sme-data-protection-guide/data-protection-basics_en">uropean </a><a href="https://www.edpb.europa.eu/sme-data-protection-guide/data-protection-basics_en">D</a><a href="https://www.edpb.europa.eu/sme-data-protection-guide/data-protection-basics_en">ata </a><a href="https://www.edpb.europa.eu/sme-data-protection-guide/data-protection-basics_en">P</a><a href="https://www.edpb.europa.eu/sme-data-protection-guide/data-protection-basics_en">rotection </a><a href="https://www.edpb.europa.eu/sme-data-protection-guide/data-protection-basics_en">B</a><a href="https://www.edpb.europa.eu/sme-data-protection-guide/data-protection-basics_en"><u>oard</u></a> confirms that this list is exhaustive, meaning additional categories cannot be added by interpretation. As a result, “sex”-related information could be processed without explicit consent in automated CV‑screening scenarios.</p>
<p>In this context, an organisation cannot use algorithms to process data on race or trade‑union membership to decide whether to invite a candidate to an interview without explicit consent. Yet it may process “sex”-related data, such as motherhood status, age, or CV gaps, to make the same decision. Research shows that algorithms and generative AI tools reproduce biased language (<a href="https://www.researchgate.net/publication/356014794_Language_Interaction_and_Gender_Discrimination_in_Conversational_AI">Jiang, 2021</a>) and outdated gendered skill classifications (<a href="https://www.ftc.gov/system/files/documents/public_events/1582978/auditing_for_discrimination_in_algorithms_delivering_job_ads.pdf">Imana, Korolova &amp; Heidemann, 2021</a>; <a href="https://www.sciencedirect.com/science/article/pii/S0148296321009206">Jungyong, Jungwon &amp; Yongjun, 2022</a>; <a href="https://www.tandfonline.com/doi/full/10.1080/14680777.2023.2263659">Gorska &amp; Jemielniak, 2023</a>). For instance, the <a href="https://www.washington.edu/news/2024/10/31/ai-bias-resume-screening-race-gender/">University of Washington (2024)</a> discovered that when using AI tools to screen CVs, the systems preferred male-associated names 52% of the time versus female-associated names 11% of the time. While <a href="https://gdpr-info.eu/art-6-gdpr/">Article 6 GDPR</a> principles such as purpose limitation and data minimisation offer some protection, persistent structural gender stereotypes and bias suggest that “sex”-related data should receive the heightened safeguards afforded to special categories.</p>
<p>Other legal systems in the Global South offer alternative approaches. In Colombia, “sex” is not explicitly listed as sensitive data under <a href="https://www.funcionpublica.gov.co/eva/gestornormativo/norma.php?i=49981">Statutory Law 1581 of 2012</a>. However, the Constitutional Court in <a href="https://www.funcionpublica.gov.co/eva/gestornormativo/norma.php?i=50042">Judgment C‑748/11</a> confirmed that the list of sensitive data is not exhaustive. <a href="https://www.funcionpublica.gov.co/eva/gestornormativo/norma.php?i=49981">Statutory Law 1581 of 2012</a> defines sensitive data as information that may affect privacy or expose individuals to discrimination. Then the focus is on the impact of the data rather than its formal classification.</p>
<p>In today’s labour market, gender continues to shape access to opportunities. Data‑protection frameworks should therefore adopt a gender‑sensitive approach to mitigate the barriers faced by women. Colombia’s impact‑based model may offer stronger protection, as organisations must assess whether “sex”-related information could function as sensitive data and thus require heightened safeguards. On the other hand, the EU framework excludes “sex” from the outset, reducing the scrutiny applied to such data under the GDPR.</p>
<p><em>Note: This blog post has been written as a result of the research conducted for the book “Gender, Sexuality and Law: South-South Perspectives” which will be published by Springer in 2026 and contains the full law-in-context analysis.</em></p>
]]></content:encoded>
					
					<wfw:commentRss>https://ohrh.law.ox.ac.uk/women-and-the-labour-market-navigating-algorithm-decision-making/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">87298</post-id>	</item>
	</channel>
</rss>
