Gegevensverwerkingsovereenkomst

Gegevensverwerkingsovereenkomst

Versie van 09.08.2023

Deze Gegevensverwerkingsovereenkomst (Data Processing Agreement, “DPA”) is onderdeel van de overeenkomst, hierna omschreven als de "Overeenkomst", tussen OVH BV (“OVHcloud”) en de Klant, waarin de voorwaarden zijn vastgelegd die van toepassing zijn op de door OVHcloud uitgevoerde diensten (de "Diensten"). Deze DPA en de andere bepalingen van de Overeenkomst zijn complementair. In het geval van tegenstrijdigheid zal deze DPA echter prevaleren.

Uitdrukkingen die beginnen met een hoofdletter en die niet in deze DPA zijn gedefinieerd, hebben de betekenis zoals uiteengezet in de Overeenkomst. “Gegevensbetrokkene”, "Bindende Bedrijfsvoorschriften", "Verantwoordelijke", "Persoonsgegevens", "Beveiligingsinciden", "Verwerking", "Verwerker", "Toezichthoudende Autoriteit" worden geïnterpreteerd in de zin van Verordening (EU) nr. 2016/679 van het Europees Parlement en de Raad van 27 april 2016 betreffende de bescherming van natuurlijke personen in verband met de verwerking van persoonsgegevens en betreffende het vrije verkeer van die gegevens ("Algemene verordening inzake gegevensbescherming" of "AVG").

Het doel van deze Gegevensverwerkingsovereenkomst is om, overeenkomstig artikel 28 van de AVG, de voorwaarden vast te stellen waaronder OVHcloud, als Verwerker en als onderdeel van de in de Overeenkomst omschreven Diensten, het recht heeft om namens en in opdracht van de Klant de Persoonsgegevens te verwerken, de verwerkingsactiviteiten van persoonsgegevens door OVHcloud als verantwoordelijke niet inbegrepen. De voorwaarden waaronder OVHcloud als Verantwoordelijke de Persoonsgegevens van de Klant verwerkt (waaronder ook de agenten van de Klant), worden gedefinieerd in het Beleid van OVHcloud inzake Gegevensgebruik.

In het kader van deze Gegevensverwerkingsovereenkomst kan de Klant als "Verantwoordelijke" of "Verwerker" optreden met betrekking tot Persoonsgegevens. Indien de Klant als verwerker optreedt ten behoeve van een externe verantwoordelijke, komen de Partijen uitdrukkelijk de volgende voorwaarden overeen:

(a) De Klant draagt er zorg voor dat (i) alle noodzakelijke autorisaties voor het aangaan van deze DPA, waaronder de aanwijzing van OVHcloud door de Klant als subverwerker, van de Verantwoordelijke zijn verkregen, (ii) een overeenkomst, die volledig in overeenstemming is met de voorwaarden van de Overeenkomst, waaronder deze DPA, is aangegaan met de Verantwoordelijke op grond van voornoemd artikel 28 van de AVG, (iii) eventuele instructies die OVHcloud ter uitvoering van de Overeenkomst en deze DPA van de Klant ontvangt volledig in overeenstemming zijn met de opdracht van de Verantwoordelijke en (iv) alle informatie die OVHcloud op grond van deze DPA verstrekt of beschikbaar stelt, waar nodig en naar behoren aan de Verantwoordelijke wordt verstrekt.

(b) OVHcloud zal (i) Persoonsgegevens uitsluitend in opdracht van de Klant verwerken en (ii) geen instructies rechtstreeks van de Verantwoordelijke ontvangen, behalve in gevallen waarin de Klant feitelijk is verdwenen of heeft opgehouden rechtens te

bestaan zonder dat een opvolger de rechten en verplichtingen van de Klant overneemt.

(c) De Klant, die jegens OVHcloud volledig verantwoordelijk is voor de correcte nakoming van de verplichtingen van de Verantwoordelijke op grond van deze DPA, vrijwaart OVHcloud van (i) iedere tekortkoming van de Verantwoordelijke in de nakoming van toepasselijke wet- en regelgeving en (ii) iedere actie, vordering of klacht van de Verantwoordelijke met betrekking tot de bepalingen van de Overeenkomst (waaronder deze DPA) of enige opdracht die OVHcloud van de Klant ontvangt.

1. Bereik

1.1 OVHcloud is bevoegd , als in opdracht van de Klant handelende Verwerker, de Persoonsgegevens van de Verantwoordelijke te verwerken voor zover dit noodzakelijk is voor het uitvoeren van de Diensten.

1.2 De aard van de door OVHcloud met betrekking tot Persoonsgegevens verrichte handelingen kunnen computing, opslag en/of andere Diensten omvatten die omschreven worden in de Overeenkomst.

1.3 Het type Persoonsgegevens en de categorieën Gegevensbetrokkenen worden door de Klant naar eigen goeddunken vastgesteld en beheerd.

1.4 De verwerkingsactiviteiten worden door OVHcloud uitgevoerd gedurende de looptijd die in de Overeenkomst is vastgelegd.

2. Selectie van de Diensten

2.1 De Klant is als enige verantwoordelijk voor de selectie van de Diensten. De Klant draagt er zorg voor dat de geselecteerde Diensten de vereiste kenmerken en voorwaarden hebben om te voldoen aan de activiteiten en verwerkingsdoeleinden van de Verantwoordelijke, alsmede de soort Persoonsgegevens die binnen de Diensten moet worden verwerkt, met inbegrip van, maar niet beperkt tot wanneer de Diensten worden gebruikt voor de verwerking van Persoonsgegevens die onderworpen zijn aan specifieke voorschriften of normen (bijvoorbeeld, gezondheids- of bankgegevens in sommige landen). De Klant wordt ervan op de hoogte gesteld dat OVHcloud bepaalde Diensten aanbiedt met organisatorische en beveiligingsmaatregelen die specifiek zijn ontworpen voor de verwerking van zorg- of bankgegevens.

2.2 Indien de verwerking door de Verantwoordelijke een groot risico voor de rechten en vrijheid van natuurlijke personen met zich mee kan brengen, dient de Klant zijn Diensten zorgvuldig te kiezen. Bij de beoordeling van het risico wordt met name, maar niet uitsluitend, rekening gehouden met de volgende criteria: evaluatie of beoordeling van de Gegevensbetrokkenen; geautomatiseerde besluitvorming met een juridisch of soortgelijk significant effect; systematische controle van de Gegevensbetrokkenen; verwerking van gevoelige of zeer persoonlijke gegevens; verwerking op grote schaal; matchen of

combineren van gegevensverzamelingen; verwerking van gegevens over kwetsbare Gegevensbetrokkenen; gebruik van niet door het publiek erkende innoverende nieuwe technologieën voor de verwerking.

2.3 OVHcloud stelt informatie ter beschikking aan de Klant, onder de voorwaarden zoals hieronder uiteengezet in artikel “Audits”, met betrekking tot de in het kader van de Diensten geïmplementeerde beveiligingsmaatregelen, voor zover dit nodig is om te beoordelen of deze maatregelen in overeenstemming zijn met de verwerkingsactiviteiten van de Verantwoordelijke.

3. Naleving van geldende voorschriften

Elke partij leeft de toepasselijke gegevensbeschermingsvoorschriften na (met inbegrip van de Algemene Verordening Gegevensbescherming).

4. Verplichtingen van OVHcloud

4.1 OVHcloud verbindt zich ertoe:

a) Persoonsgegevens te verwerken die door de Klant zijn geüpload, opgeslagen en gebruikt binnen de Diensten alleen voor zover noodzakelijk en proportioneel voor het leveren van de Diensten zoals gedefinieerd in de Overeenkomst;

b) geen toegang te krijgen tot of gebruik te maken van de Persoonsgegevens voor enig ander doel dan nodig is voor het uitvoeren van de Diensten (met name met betrekking tot Incidentbeheer-doeleinden);

c) de in de Overeenkomst beschreven technische en organisatorische maatregelen te treffen om de beveiliging van persoonsgegevens binnen de dienst te waarborgen;

d) te waarborgen dat werknemers van OVHcloud die bevoegd zijn tot het verwerken van Persoonsgegevens in het kader van de Overeenkomst, onderworpen zijn aan een geheimhoudingsplicht en de nodige training krijgen met betrekking tot de bescherming van Persoonsgegevens;

e) de Klant op de hoogte te stellen, indien naar zijn mening en op basis van de informatie waarover hij beschikt, de instructie van de Klant in strijd is met de bepalingen van de AVG of andere gegevensbeschermingsbepalingen van de Europese Unie of de lidstaat van de Europese Unie.

4.2 In geval van verzoeken ontvangen van een juridische, administratieve of andere bevoegde autoriteit die betrekking hebben op Persoonsgegevens die in het kader van deze Overeenkomst worden verwerkt door OVHcloud, zal OVHcloud redelijke inspanningen leveren om (i) de bevoegdheid van de verzoekende instantie en de geldigheid van het verzoek te analyseren, (ii) enkel een antwoord te geven aan de bevoegde autoriteiten en te reageren op verzoeken die niet duidelijk onbevoegd en ongeldig zijn, (iii) de mededeling van gegevens te beperken tot waar de autoriteit uitdrukkelijk om heeft verzocht en (iv) de Klant op voorhand te informeren (tenzij verboden door de toepasselijke wetgeving).

4.3 Indien het verzoek afkomstig is van een niet-Europese instantie om berichtgeving of

persoonsgegevens te verkrijgen die in het kader van deze Overeenkomst worden verwerkt door OVHcloud in naam van een Europese Klant, zal OVHcloud bezwaar aantekenen tegen dit verzoek, onder voorbehoud van de volgende gevallen:

(x) het verzoek wordt gedaan in overeenstemming met een internationale overeenkomst, zoals een verdrag inzake wederzijdse rechtshulp, die van kracht is tussen het verzoekende land en de Europese Unie of de lidstaat waar de persoonsgegevens zich bevinden of de lidstaat van de OVHcloud-entiteit waarbij de klant zijn OVHcloud-klantenaccount heeft geregistreerd;

(y) de verzochte Persoonsgegevens zijn opgeslagen in een datacentrum dat zich buiten de Europese Unie bevindt;

(z) het verzoek wordt gedaan in overeenstemming met artikel 49 van de AVG, waarbij het in het bijzonder een belangrijke reden van algemeen belang nastreeft die erkend wordt door het recht van de Unie of van de lidstaten van de Europese Unie, of noodzakelijk is om vitale belangen van de betrokkene of van andere personen in stand te houden.

4.4 op schriftelijk verzoek van de Klant zal OVHcloud de Klant redelijke assistentie verlenen bij het uitvoeren van gegevensbeschermingseffectbeoordelingen en het voeren van overleg met de bevoegde toezichthoudende instantie, indien de Klant hiertoe krachtens het toepasselijke recht inzake gegevensbescherming verplicht is, en in elk geval uitsluitend voor zover deze assistentie noodzakelijk is en betrekking heeft op de verwerking van persoonsgegevens door OVHcloud op grond van dit artikel. Dergelijke assistentie zal bestaan uit het verschaffen van transparantie over de beveiligingsmaatregelen die OVHcloud ten behoeve van haar Diensten heeft getroffen.

4.5 OVH verbindt zich ertoe de volgende technische en organisatorische maatregelen te treffen:

(a) fysieke veiligheidsmaatregelen om te voorkomen dat onbevoegden toegang krijgen tot de infrastructuur waarin de gegevens van de Klant zijn opgeslagen;

(b) identiteits- en toegangscontroles aan de hand van een authenticatiesysteem en een wachtwoordbeleid;

(c) een toegangsbeheersysteem dat de toegang tot de gebouwen beperkt tot de personen die er toegang toe moeten hebben in het kader van de uitoefening van hun taken en binnen hun verantwoordelijkheid;

(d) beveiligingspersoneel dat verantwoordelijk is voor het toezicht op de fysieke beveiliging van de OVHcloud-gebouwen;

(e) een systeem dat klanten fysiek en logistiek van elkaar isoleert;

(f) authenticatieprocessen voor gebruikers en beheerders, alsmede maatregelen ter bescherming van de toegang tot beheerfuncties;

(g) een toegangsbeheersysteem voor ondersteunings- en onderhoudsactiviteiten dat werkt volgens de beginselen van 'least privilege' en 'need-to-know', en;

(h) processen en maatregelen om op haar informatiesysteem verrichte handelingen te traceren.

4.6 Deze technische en organisatorische maatregelen worden verder uiteengezet op de

Website van OVHcloud.

5. Beveiligingsincidenten

5.1 Indien OVHcloud kennis krijgt van een incident dat gevolgen heeft voor de Persoonsgegevens van de Verantwoordelijke (zoals onbevoegde toegang, verlies, bekendmaking of wijziging van gegevens), stelt OVHcloud de Klant daarvan onverwijld in kennis.

5.2 De kennisgeving beschrijft (i) de aard van het incident, (ii) de vermoedelijke gevolgen van het incident, (iii) de maatregelen die OVHcloud heeft genomen of voornemens is te nemen naar aanleiding van het incident en (iv) het aanspreekpunt van OVHcloud.

6. Locatie en overdracht van Persoonsgegevens

6.1 In gevallen waarin de Diensten het de Klant mogelijk maken Inhoud en met name Persoonsgegevens op te slaan, wordt/worden op de Website van OVHcloud de locatie(s) of het geografisch gebied van het/de beschikbare Datacentrum/centra opgegeven. Indien meerdere locaties of geografische gebieden beschikbaar zijn, zal Klant bij het plaatsen van zijn Order de locatie(s) kiezen die zijn voorkeur genieten. Behoudens tegenstrijdige bepalingen in de van toepassing zijnde Bijzondere Dienstverleningsvoorwaarden zal OVHcloud zonder toestemming van de Klant de bij het plaatsen van de Order gekozen locatie of geografische gebied, niet wijzigen.

6.2 Behoudens de bovengenoemde bepaling inzake de locatie van Datacenters, kunnen OVHcloud en gemachtigde Subverwerkers ingevolge het onderstaande artikel 7 de Klantinhoud op afstand verwerken, mits dergelijke verwerkingen plaatsvinden indien dit noodzakelijk is voor het uitvoeren van de Diensten, en in het bijzonder met het oog op beveiliging en onderhoud van de Dienst.

6.3 Wat betreft het gebruik van Diensten die zich in niet-Europese Datacenters bevinden, (a) kunnen de Datacenters zich bevinden in landen waarvoor geen adequaatheidsbesluit van de Europese Commissie geldt overeenkomstig artikel 45 van de AVG ("Adequaatheidsbesluit") en/of (b) kan de Klantinhoud, overeenkomstig de artikelen 6.2 en 7 van deze DPA, worden verwerkt vanuit landen waarvoor geen Adequaatheidsbesluit geldt.

6.4 In het geval dat de Klant de in de bovenstaande alinea vermelde Services gebruikt voor de verwerking van persoonsgegevens die onder de AVG (GDPR) vallen, dan wordt de Klant beschouwd als de Verwerkingsverantwoordelijke, OVHcloud als zijn verwerker en OVHcloud-dochterondernemingen als subverwerkers. Als persoonsgegevens worden overgedragen aan dochterondernemingen in landen waarvoor geen adequaatheidsbesluit is genomen, dan wordt OVHcloud volgens de AVG beschouwd als een Gegevensexporteur en haar dochterondernemingen als een Gegevensimporteur. In deze context hebben OVHcloud en haar dochterondernemingen standaardcontractbepalingen afgesloten, die met het Uitvoeringsbesluit (EU) 2021/914 van de Europese Commissie van 4 juni 2021 zijn ingevoerd (hierna "Standaardcontractbepalingen" genoemd). Deze zijn als bijlage bij deze Gegevensbeschermingsovereenkomst bijgevoegd en dienen op de hierboven vermelde overdrachten van toepassing te zijn.

6.5 Voor Services in datacenters binnen de Europese Unie zijn de bovenvermelde Types Contractbepalingen van toepassing, indien de toepasselijke Servicevoorwaarden bepalen dat de verwerking van de Persoonsgegevens die onder deze Gegevensbeschermingsovereenkomst vallen, kan worden uitgevoerd vanuit een of meerdere landen waarvoor geen adequaatheidsbesluit geldt.

6.6 Indien Standaardcontractbepalingen geïmplementeerd worden volgens de secties 6.3,

6.4 en 6.5 van deze Gegevensbeschermingsovereenkomst is de Klant verantwoordelijk voor

(i) het beoordelen van de effectiviteit van de Standaardcontractbepalingen (inclusief de relevante technische en organisatorische maatregelen), met name rekening houdend met de categorieën gegevens die de Klant voornemens is met de Services te verwerken en met de wetten en gebruiken van de ontvangende landen, zodat hij kan vaststellen of de genoemde wetgeving of gebruiken de effectiviteit van de Standaardcontractbepalingen kan aantasten, en (ii) indien de Standaardcontractbepalingen als ineffectief worden beoordeeld, voor het implementeren van alle mogelijke aanvullende maatregelen om een beschermingsniveau te verzekeren dat in wezen gelijkwaardig is aan het niveau dat in de Europese Unie wordt gewaarborgd, zoals aanbevolen door het Europese Comité voor gegevensbescherming. XXXxxxxx spant zich in de Klant te helpen door, op verzoek, alle in haar bezit zijnde informatie te verstrekken die nuttig kan zijn voor de evaluatie door de Klant. Bovendien blijft de Klant verantwoordelijk voor het uitvoeren van alle formaliteiten en/of het verkrijgen van alle autorisaties of toestemmingen die, waar van toepassing, vereist kunnen zijn om de overdracht van persoonsgegevens mogelijk te maken naar landen die geen Adequaatheidsbesluit hebben.

6.7 Alle toepasselijke Modelcontractbepalingen worden aangevuld met de andere toepasselijke Dienstenvoorwaarden (met inbegrip van deze DPA) die mutatis mutandis van toepassing zijn op zowel de Gegevensimporteur(s) als de Gegevensexporteur(s), voor zover zij niet in strijd zijn met de Modelcontractbepalingen. In het geval van strijdigheid hebben de Modelcontractbepalingen voorrang.

7. Subverwerking

7.1 Met inachtneming van het bepaalde in het bovenstaande artikel “Locatie en overdracht van Persoonsgegevens”, is OVHcloud bevoegd om subcontractanten in te schakelen om haar bij de verlening van de Diensten bij te staan. In het kader van deze assistentie kunnen de subcontractanten deelnemen aan de gegevensverwerkingsactiviteiten die OVHcloud in opdracht van de Klant uitvoert.

7.2 De lijst van subcontractanten die bevoegd zijn om deel te nemen aan de verwerkingsactiviteiten die OVHcloud in opdracht van de Klant uitvoert ("Subverwerker(s)"), met inbegrip van de betreffende Dienst(en) en de plaats van waaruit zij de Persoonsgegevens van de Klant in overeenstemming met deze Overeenkomst mogen verwerken, is opgenomen in (a) de Website van OVHcloud (b) wanneer een Subverwerker uitsluitend aan een specifieke Dienst deelneemt, in de relevante toepasselijke Specifieke Voorwaarden.

7.3 Indien OVHcloud besluit een Subverwerker te wijzigen of een nieuwe Subverwerker toe te voegen ("Subverwerkerswijziging "), stelt OVHcloud de Klant daarvan dertig (30) dagen van tevoren per e-mail in kennis (op het e-mailadres dat op de Account van de Klant is geregistreerd) (a) indien de Subverwerker een OVHcloud Verwante Onderneming is die gevestigd is (i) in de Europese Unie, of (ii) in een land waarop een Adequaatheidsbesluit van toepassing is, of in elk ander geval (b) negentig (90) dagen van tevoren. De Klant heeft het recht om bezwaar te maken tegen een Subverwerkerswijziging zoals voorzien onder de AVG. Het bezwaar moet worden gemeld binnen vijftien (15) dagen nadat OVHcloud de Subverwerkerwijziging aan de Klant heeft gemeld en moet de reden voor bezwaar vermelden. Een dergelijk bezwaar wordt door de Klant via haar Management Interface kenbaar gemaakt door middel van de categorie “Verzoek om Gegevensbescherming” of schriftelijk aan de functionaris voorgegevensbescherming (Data protection Officer), OVH SAS, 0, xxx Xxxxxxxxxx 00000 Xxxxxxx (Xxxxxxxxx). OVHcloud is in geen geval verplicht om af te zien van de Subverwerkerswijziging. Indien OHVcloud naar aanleiding van een bezwaar van de Klant geen afstand doet van de Subverwerkerswijziging, heeft de Klant het recht om de betrokken Dienst te beëindigen.

7.4 OVHcloud draagt er zorg voor dat elke Subverwerker minimaal kan voldoen aan de verplichtingen die OVHcloud in deze DPA is aangegaan ten aanzien van de verwerking van Persoonsgegevens door de Subverwerker. OVHcloud sluit daartoe een overeenkomst met de Subverwerker. OVHcloud blijft jegens de Klant volledig aansprakelijk voor de nakoming van dergelijke verplichtingen die de Subverwerker niet nakomt.

7.5 OVHcloud is hierbij bevoegd om zonder voorafgaande kennisgeving aan of toestemming van de Klant derde aanbieders (zoals energieaanbieders, netwerkaanbieders, beheerders van netwerkinterconnectiepunten of gegroepeerde datacenters, materiaal- en softwareaanbieders, carriers, technische aanbieders, beveiligingsbedrijven), waar zij zich ook bevinden, in te schakelen, zonder informatieplicht jegens de Klant noch vereiste voorafgaande toestemming van die laatste, mits deze derden de Persoonsgegevens van de Klant niet verwerken.

8. Verplichtingen van klant

8.1 Ten behoeve van de verwerking van Persoonsgegevens zoals voorzien in de Overeenkomst, verstrekt de Klant OVHcloud schriftelijk (a) alle relevante instructies en (b) alle informatie die nodig is voor het maken van de registers van de verwerkingsactiviteiten van de Verwerker. De Klant blijft als enige verantwoordelijk voor de aan OVHcloud verstrekte verwerkinginformatie en-instructies.

8.2 De Klant is ervoor verantwoordelijk te waarborgen dat:

a) er een passende rechtsgrondslag is voor de verwerking van Persoonsgegevens van de Klant in het kader van de uitvoering van de Dienst (bv. toestemming van de Gegevensbetrokkene, toestemming van de Verantwoordelijke, geverechtvaardigde belangen, toestemming van de bevoegde Toezichthoudende Autoriteit enz.);

b) elke vereiste procedure en formaliteit (zoals gegevensbeschermingseffectbeoordeling, kennisgeving en autorisatieverzoek aan de bevoegde autoriteit voor gegevensbescherming of een andere bevoegde instantie indien vereist) is uitgevoerd;

c) de Gegevensbetrokkenen in beknopte, transparante, begrijpelijke en gemakkelijk toegankelijke vorm wordt geïnformeerd over de verwerking van zijn Persoonsgegevens, in duidelijke en eenvoudige bewoordingen zoals bepaald in de AVG;

d) de Gegevensbetrokkenen op de hoogte worden gebracht van en te allen tijde de mogelijkheid hebben om hun in het kader van de AVG aan de Klant verleende rechten gemakkelijk rechtstreeks uit te oefenen.

8.3 De Klant is verantwoordelijk voor de implementatie van de passende technische en organisatorische maatregelen ter beveiliging van de middelen, systemen, applicaties en operaties die niet binnen het in de Overeenkomst vastgelegde verantwoordelijkheidsgebied van OVHcloud vallen (met name systemen en software die door de Klant of de Gebruikers binnen de Diensten worden ingezet en geëxploiteerd).

9. Rechten van Gegevensbetrokkenen

9.1 De Verantwoordelijke is volledig verantwoordelijk voor het informeren van de Gegevensbetrokkenen over hun rechten en voor de eerbiediging van die rechten, met inbegrip van het recht van toegang, rectificatie, verwijdering, beperking of overdraagbaarheid .

9.2 OVHcloud zal redelijke medewerking en assistentie verlenen, zoals redelijkerwijs vereist is voor het beantwoorden van verzoeken van Gegevensbetrokkenen. Dergelijke redelijke samenwerking en bijstand kan eruit bestaan (a) de Klant in kennis te stellen van elk rechtstreeks van de gegevensbetrokkene ontvangen verzoek en (b) de Verantwoordelijke in staat te stellen de technische en organisatorische maatregelen te ontwerpen en uit te voeren die nodig zijn om de verzoeken van de gegevensbetrokkenen te beantwoorden. Alleen de Verantwoordelijke is verantwoordelijk voor het beantwoorden van die verzoeken.

9.3 De Klant erkent en stemt ermee in dat indien deze samenwerking en bijstand aanzienlijke middelen van de zijde van de Verwerker vereist, deze inspanning in rekening zal worden gebracht na voorafgaande kennisgeving aan en instemming met de Klant.

10. Verwijderen en retourneren van Persoonsgegevens

10.1 Na afloop van een Dienst (met name in geval van beëindiging of niet-verlenging), verbindt OVHcloud zich ertoe om in de voorwaarden waarin de Overeenkomst voorziet, alle Inhoud (met inbegrip van informatie, gegevens, bestanden, systemen, toepassingen, websites en andere items) te verwijderen die door de Klant in het kader van de Diensten wordt gereproduceerd, opgeslagen, gehost of anderszins gebruikt, tenzij een verzoek van een bevoegde juridische of gerechtelijke instantie of het toepasselijke recht van de Europese Unie of van een lidstaat van de Europese Unie anders bepaalt.

10.2 De Klant is er als enige verantwoordelijk voor dat de nodige handelingen (zoals back- up, overdracht naar een oplossing van een derde, Snapshots, enz.) ter bewaring van Persoonsgegevens worden uitgevoerd, met name vóór de beëindiging of afloop van de Diensten, en alvorens over te gaan tot het verwijderen, bijwerken of opnieuw installeren van de Diensten.

10.3 In dit verband wordt de Klant ervan op de hoogte gebracht dat de beëindiging en het aflopen van een Dienst om welke reden dan ook (met inbegrip van maar niet beperkt tot de niet-verlenging), evenals bepaalde operaties om de Diensten bij te werken of opnieuw te installeren, automatisch kan leiden tot de onomkeerbare verwijdering van alle Inhoud (met inbegrip van informatie, gegevens, bestanden, systemen, toepassingen, websites en andere items) die wordt gereproduceerd, opgeslagen, gehost of anderszins gebruikt door de Klant in het kader van de Diensten, met inbegrip van een eventuele back-up.

11. Aansprakelijkheid

11.1 OVHcloud is slechts aansprakelijk voor schade veroorzaakt door verwerking waarvoor zij (i) niet heeft voldaan aan de verplichtingen van de AVG die specifiek betrekking hebben op verwerkers of (ii) in strijd heeft gehandeld met wettelijke schriftelijke instructies van de Klant. In dergelijke gevallen is de aansprakelijkheidsbepaling van de Overeenkomst van toepassing.

11.2 Indien OVHcloud en de Klant betrokken zijn bij een verwerking op grond van deze Overeenkomst die schade heeft berokkend aan de betrokkene, neemt de Klant in eerste instantie de volledige schadeloosstelling (of enige andere vergoeding) die aan de betrokkene verschuldigd is voor zijn rekening en vordert hij voor de tweede keer van OVHcloud dat deel van de vergoeding van de betrokkene terug dat overeenkomst met het aandeel van OVHcloud in de verantwoordelijkheid voor de schade, met dien verstande dat eventuele aansprakelijkheidsbeperkingen op grond van de Overeenkomst van toepassing zijn.

12. Audits

12.1 OVHcloud stelt de Klant alle informatie ter beschikking die nodig is om (a) aan te tonen dat is voldaan aan de eisen van de AVG en (b) audits mogelijk te maken. Dergelijke informatie is beschikbaar in de standaarddocumentatie op de Website van OVHcloud. Op verzoek van OVHcloud Ondersteuning kan aan de Klant aanvullende informatie worden verstrekt.

12.2 Indien een Dienst is gecertificeerd, voldoet aan een gedragscode of onderworpen is aan specifieke auditprocedures, stelt OVHcloud de betreffende certificaten en auditrapporten op schriftelijk verzoek ter beschikking aan de Klant.

12.3 Indien voornoemde informatie, rapport en certificaat onvoldoende blijken te zijn om de Klant in staat te stellen aan te tonen dat hij voldoet aan de verplichtingen die de AVG hem

oplegt, zullen OVHcloud en de Klant in overleg treden over de operationele, financiële en veiligheidscondities van een technische controle ter plaatse. De voorwaarden van deze inspectie mogen in geen geval de veiligheid van de andere klanten van OVHcloud aantasten.

12.4 De voormelde controle ter plaatse, alsook de mededeling van certificaten en auditrapporten, kunnen aanleiding geven tot een redelijke bijkomende facturatie.

12.5 Alle informatie die op grond van dit artikel aan de Klant wordt verstrekt en die niet beschikbaar is op de Website van XXXxxxxx, wordt beschouwd als vertrouwelijke informatie van OVHcloud op grond van de Overeenkomst. Van de Klant kan worden verlangd dat zij een specifieke geheimhoudingsovereenkomst afsluit voordat dergelijke informatie wordt doorgegeven.

12.6 Desalniettemin is de Klant bevoegd verzoeken van bevoegde toezichthoudende autoriteiten te beantwoorden, mits de openbaarmaking van informatie strikt is beperkt tot hetgeen door die toezichthoudende autoriteit wordt verlangd. In een dergelijk geval zal de Klant, tenzij dit door de toepasselijke wetgeving is verboden, eerst met OVHcloud overleggen over een dergelijke vereiste openbaarmaking.

13. OVHcloud-contact

Voor vragen over persoonlijke gegevens (incident, gebruiksvoorwaarden, enz.) Kan de Klant als volgt contact opnemen met OVHcloud:

(a) Creatie van een ticket in zijn Client Account Management Interface,

(b) Gebruik van het contactformulier dat voor dit doel op de OVHcloud-website wordt verstrekt,

(c) Door contact op te nemen met haar OVHcloud-ondersteuningsdienst,

(d) Per post naar het adres: OVH SAS, functionaris voor gegevensbescherming, 0 xxx Xxxxxxxxxx, 00000 Xxxxxxx (Xxxxxxxxx).

PREAMBLE

STANDARD CONTRACTUAL CLAUSES

Transfers from processor to processor

OVH SAS is the (direct or indirect) parent company of the OVH European Affiliates.

OVH SAS and the OVH European Affiliates are selling services, including without limitation infrastructure as

a service and cloud services (together the “Services”).

As part of their activities and notably the execution of the Services, OVH SAS and the OVH European Affiliates are processing personal data subjected to the Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data (the “GDPR”), notably personal data of their Clients.

Such personal data processing activities are performed by OVH SAS and the OVH European Affiliates either

(a) as controller or (b) as a processor under their Clients’ instructions.

OVH SAS and the OVH European Affiliates, at the express request of their Clients, may transfer the aforementioned processing activities to one or more data importers located in a country which is not considered by the European Commission as a third country that ensures an adequate level of protection according to article 45 of the GDPR. Such processing activities will be performed by the relevant data importer as a processor under instruction of the relevant data exporter. The performance of such processing activities implies a transfer of personal data to the data importer (including remote access from its country).

The data importer’s country is not considered by the European Commission as a third country that ensures

an adequate level of protection according to article 45 of the GDPR.

For the purposes of Articles 28 (7) and 46 (c) of the Regulation (EU) 2016/679,, the parties have agreed on the following Contractual Clauses adopted by Decision n°2021/914/EU dated 4 June 2021 of the European Commission, which integrates the clauses of Module 3 applicable to transfers from processor to processor (the “Clauses”) in order to adduce adequate safeguards with respect to the protection of privacy and fundamental rights and freedoms of individuals for the transfer by the data exporter to the data importer of the personal data specified in Appendix 1.

The following Clauses are only applicable to personal data processing activities performed by OVH SAS and the OVH European Affiliates as processor under their Clients’ instructions entrusted to the relevant data importer as a processor.

SECTION I

Clause 1

Purpose and scope

(a) The purpose of these standard contractual clauses is to ensure compliance with the requirements of Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data (General Data Protection Regulation) for the transfer of personal data to a third country.

(b) The Parties:

(i) the legal persons (hereinafter ‘entities’) transferring the personal data, as listed in Annex I.A

(hereinafter each ‘data exporter’), and

(ii) the entities in a third country receiving the personal data from the data exporter, directly or indirectly via another entity also Party to these Clauses, as listed in Annex I.A (hereinafter each ‘data importer’)

have agreed to these standard contractual clauses (hereinafter: ‘Clauses’).

(c) These Clauses apply with respect to the transfer of personal data as specified in Annex I.B.

(d) The Appendix to these Clauses containing the Annexes referred to therein forms an integral part of these Clauses.

Clause 2

Effect and invariability of the Clauses

(a) These Clauses set out appropriate safeguards, including enforceable data subject rights and effective legal remedies, pursuant to Article 46(1) and Article 46(2)(c) of Regulation (EU) 2016/679 and, with respect to data transfers from processors to processors, standard contractual clauses pursuant to Article 28(7) of Regulation (EU) 2016/679, provided they are not modified, except to select the appropriate Module(s) or to add or update information in the Appendix. This does not prevent the Parties from including the standard contractual clauses laid down in these Clauses in a wider contract and/or to add other clauses or additional safeguards, provided that they do not contradict, directly or indirectly, these Clauses or prejudice the fundamental rights or freedoms of data subjects.

(b) These Clauses are without prejudice to obligations to which the data exporter is subject by virtue of Regulation (EU) 2016/679.

Clause 3

Third-party beneficiaries

(a) Data subjects may invoke and enforce these Clauses, as third-party beneficiaries, against the data exporter and/or data importer, with the following exceptions:

(i) Clause 1, Xxxxxx 2, Xxxxxx 3, Xxxxxx 6, Xxxxxx 7;

(ii) Clause 8.1(a), (c) and (d) and Clause 8.9(a), (c), (d), (e), (f) and (g);

(iii) Clause 9(a), (c), (d) and (e);

(iv) Clause 12(a), (d) and (f);

(v) Clause 13;

(vi) Clause 15.1(c), (d) and (e);

(vii) Clause 16(e);

(viii) Clause 18(a) and (b).

(b) Paragraph (a) is without prejudice to rights of data subjects under Regulation (EU) 2016/679.

Clause 4

Interpretation

(a) Where these Clauses use terms that are defined in Regulation (EU) 2016/679, those terms shall have the same meaning as in that Regulation.

(b) These Clauses shall be read and interpreted in the light of the provisions of Regulation (EU) 2016/679.

(c) These Clauses shall not be interpreted in a way that conflicts with rights and obligations provided for in Regulation (EU) 2016/679.

Clause 5

Hierarchy

In the event of a contradiction between these Clauses and the provisions of related agreements between the Parties, existing at the time these Clauses are agreed or entered into thereafter, these Clauses shall prevail.

Clause 6

Description of the transfers

The details of the transfers, and in particular the categories of personal data that are transferred and the purposes for which they are transferred, are specified in Annex I.B.

Clause 7

Docking clause

(a) An entity that is not a Party to these Clauses may, with the agreement of the Parties, accede to these Clauses at any time, either as a data exporter or as a data importer, by completing the Appendix and signing Annex I.A.

(b) Once it has completed the Appendix and signed Annex I.A, the acceding entity shall become a Party to these Clauses and have the rights and obligations of a data exporter or data importer in accordance with its designation in Annex I.A.

(c) The acceding entity shall have no rights or obligations arising under these Clauses from the period prior to becoming a Party.

SECTION II – OBLIGATIONS OF THE PARTIES

Clause 8

Data protection safeguards

The data exporter warrants that it has used reasonable efforts to determine that the data importer is able, through the implementation of appropriate technical and organisational measures, to satisfy its obligations under these Clauses.

8.1 Instructions

(a) The data exporter has informed the data importer that it acts as processor under the

instructions of its controller(s), which the data exporter shall make available to the data importer prior to processing.

(b) The data importer shall process the personal data only on documented instructions from the controller, as communicated to the data importer by the data exporter, and any additional documented instructions from the data exporter. Such additional instructions shall not conflict with the instructions from the controller. The controller or data exporter may give further documented instructions regarding the data processing throughout the duration of the contract.

(c) The data importer shall immediately inform the data exporter if it is unable to follow those instructions. Where the data importer is unable to follow the instructions from the controller, the data exporter shall immediately notify the controller.

(d) The data exporter warrants that it has imposed the same data protection obligations on the data importer as set out in the contract or other legal act under Union or Member State law between the controller and the data exporter.

8.2 Purpose limitation

The data importer shall process the personal data only for the specific purpose(s) of the transfer, as set out in Annex I. B., unless on further instructions from the controller, as communicated to the data importer by the data exporter, or from the data exporter.

8.3 Transparency

On request, the data exporter shall make a copy of these Clauses, including the Appendix as completed by the Parties, available to the data subject free of charge. To the extent necessary to protect business secrets or other confidential information, including personal data, the data exporter may redact part of the text of the Appendix prior to sharing a copy, but shall provide a meaningful summary where the data subject would otherwise not be able to understand its content or exercise his/her rights. On request, the Parties shall provide the data subject with the reasons for the redactions, to the extent possible without revealing the redacted information.

8.4 Accuracy

If the data importer becomes aware that the personal data it has received is inaccurate, or has become outdated, it shall inform the data exporter without undue delay. In this case, the data importer shall cooperate with the data exporter to rectify or erase the data.

8.5 Duration of processing and erasure or return of data

Processing by the data importer shall only take place for the duration specified in Annex I.B. After the end of the provision of the processing services, the data importer shall, at the choice of the data exporter, delete all personal data processed on behalf of the controller and certify to the data exporter that it has done so, or return to the data exporter all personal data processed on its behalf and delete existing copies. Until the data is deleted or returned, the data importer shall continue to

ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit return or deletion of the personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process it to the extent and for as long as required under that local law. This is without prejudice to Clause 14, in particular the requirement for the data importer under Clause 14(e) to notify the data exporter throughout the duration of the contract if it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under Clause 14(a).

8.6 Security of processing

(a) The data importer and, during transmission, also the data exporter shall implement appropriate technical and organisational measures to ensure the security of the data, including protection against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access to that data (hereinafter ‘personal data breach’). In assessing the appropriate level of security, they shall take due account of the state of the art, the costs of implementation, the nature, scope, context and purpose(s) of processing and the risks involved in the processing for the data subject. The Parties shall in particular consider having recourse to encryption or pseudonymisation, including during transmission, where the purpose of processing can be fulfilled in that manner. In case of pseudonymisation, the additional information for attributing the personal data to a specific data subject shall, where possible, remain under the exclusive control of the data exporter or the controller. In complying with its obligations under this paragraph, the data importer shall at least implement the technical and organisational measures specified in Annex II. The data importer shall carry out regular checks to ensure that these measures continue to provide an appropriate level of security.

(b) The data importer shall grant access to the data to members of its personnel only to the extent strictly necessary for the implementation, management and monitoring of the contract. It shall ensure that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.

(c) In the event of a personal data breach concerning personal data processed by the data importer under these Clauses, the data importer shall take appropriate measures to address the breach, including measures to mitigate its adverse effects. The data importer shall also notify, without undue delay, the data exporter and, where appropriate and feasible, the controller after having become aware of the breach. Such notification shall contain the details of a contact point where more information can be obtained, a description of the nature of the breach (including, where possible, categories and approximate number of data subjects and personal data records concerned), its likely consequences and the measures taken or proposed to address the data breach, including measures to mitigate its possible adverse effects. Where, and in so far as, it is not possible to provide all information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.

(d) The data importer shall cooperate with and assist the data exporter to enable the data exporter to comply with its obligations under Regulation (EU) 2016/679, in particular to notify its controller so that the latter may in turn notify the competent supervisory authority and the affected data subjects, taking into account the nature of processing and the information available to the data importer.

8.7 Sensitive data

Where the transfer involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data, or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person’s sex life or sexual orientation, or data relating to criminal convictions and offences (hereinafter ‘sensitive data’), the data importer shall apply the specific restrictions and/or additional safeguards set out in Annex I.B.

8.8 Onward transfers

The data importer shall only disclose the personal data to a third party on documented instructions from the controller, as communicated to the data importer by the data exporter. In addition, the data may only be disclosed to a third party located outside the European Union (in the same country as the data importer or in another third country, hereinafter ‘onward transfer’) if the third party is or agrees to be bound by these Clauses, under the appropriate Module, or if:

(i) the onward transfer is to a country benefitting from an adequacy decision pursuant to Article 45 of Regulation (EU) 2016/679 that covers the onward transfer;

(ii) the third party otherwise ensures appropriate safeguards pursuant to Articles 46 or 47 of Regulation (EU) 2016/679;

(iii) the onward transfer is necessary for the establishment, exercise or defence of legal claims in the context of specific administrative, regulatory or judicial proceedings; or

(iv) the onward transfer is necessary in order to protect the vital interests of the data subject or of another natural person.

Any onward transfer is subject to compliance by the data importer with all the other safeguards under these Clauses, in particular purpose limitation.

8.9 Documentation and compliance

(a) The data importer shall promptly and adequately deal with enquiries from the data exporter or the controller that relate to the processing under these Clauses.

(b) The Parties shall be able to demonstrate compliance with these Clauses. In particular, the data importer shall keep appropriate documentation on the processing activities carried out on behalf of the controller.

(c) The data importer shall make all information necessary to demonstrate compliance with the obligations set out in these Clauses available to the data exporter, which shall provide it to the controller.

(d) The data importer shall allow for and contribute to audits by the data exporter of the processing activities covered by these Clauses, at reasonable intervals or if there are indications of non- compliance. The same shall apply where the data exporter requests an audit on instructions of the controller. In deciding on an audit, the data exporter may take into account relevant certifications held by the data importer.

(e) Where the audit is carried out on the instructions of the controller, the data exporter shall make the results available to the controller.

(f) The data exporter may choose to conduct the audit by itself or mandate an independent auditor. Audits may include inspections at the premises or physical facilities of the data importer and shall, where appropriate, be carried out with reasonable notice.

(g) The Parties shall make the information referred to in paragraphs (b) and (c), including the results of any audits, available to the competent supervisory authority on request.

Clause 9

Use of sub-processors

(a)

The data importer has the controller’s general authorisation for the engagement of sub-processor(s) from an agreed list. The data importer shall specifically inform the controller in writing of any intended changes to that list through the addition or replacement of sub-processors at least 90 days in advance, thereby giving the controller sufficient time to be able to object to such changes prior to the engagement of the sub-processor(s). The data importer shall provide the controller with the information necessary to enable the controller to exercise its right to object. The data importer shall inform the data exporter of the engagement of the sub-processor(s).

(b) Where the data importer engages a sub-processor to carry out specific processing activities (on behalf of the controller), it shall do so by way of a written contract that provides for, in substance, the same data protection obligations as those binding the data importer under these Clauses, including in terms of third-party beneficiary rights for data subjects. The Parties agree that, by complying with this Clause, the data importer fulfils its obligations under Clause 8.8. The data importer shall ensure that the sub-processor complies with the obligations to which the data importer is subject pursuant to these Clauses.

(c) The data importer shall provide, at the data exporter’s or controller’s request, a copy of such a sub- processor agreement and any subsequent amendments. To the extent necessary to protect business secrets or other confidential information, including personal data, the data importer may redact the text of the agreement prior to sharing a copy.

(d) The data importer shall remain fully responsible to the data exporter for the performance of the sub- processor’s obligations under its contract with the data importer. The data importer shall notify the data exporter of any failure by the sub-processor to fulfil its obligations under that contract.

(e) The data importer shall agree a third-party beneficiary clause with the sub-processor whereby – in the event the data importer has factually disappeared, ceased to exist in law or has become insolvent

– the data exporter shall have the right to terminate the sub-processor contract and to instruct the sub-processor to erase or return the personal data.

Clause 10

Data subject rights

(a) The data importer shall promptly notify the data exporter and, where appropriate, the controller of any request it has received from a data subject, without responding to that request unless it has been authorised to do so by the controller.

(b) The data importer shall assist, where appropriate in cooperation with the data exporter, the controller in fulfilling its obligations to respond to data subjects’ requests for the exercise of their rights under Regulation (EU) 2016/679 or Regulation (EU) 2018/1725, as applicable. In this regard, the Parties shall set out in Annex II the appropriate technical and organisational measures, taking into account the nature of the processing, by which the assistance shall be provided, as well as the scope and the extent of the assistance required.

(c) In fulfilling its obligations under paragraphs (a) and (b), the data importer shall comply with the instructions from the controller, as communicated by the data exporter.

Clause 11

Redress

(a) The data importer shall inform data subjects in a transparent and easily accessible format, through individual notice or on its website, of a contact point authorised to handle complaints. It shall deal promptly with any complaints it receives from a data subject.

(b) In case of a dispute between a data subject and one of the Parties as regards compliance with these Clauses, that Party shall use its best efforts to resolve the issue amicably in a timely fashion. The Parties shall keep each other informed about such disputes and, where appropriate, cooperate in resolving them.

(c) Where the data subject invokes a third-party beneficiary right pursuant to Clause 3, the data importer shall accept the decision of the data subject to:

(i) lodge a complaint with the supervisory authority in the Member State of his/her habitual residence or place of work, or the competent supervisory authority pursuant to Clause 13;

(ii) refer the dispute to the competent courts within the meaning of Clause 18.

(d) The Parties accept that the data subject may be represented by a not-for-profit body, organisation or association under the conditions set out in Article 80(1) of Regulation (EU) 2016/679.

(e) The data importer shall abide by a decision that is binding under the applicable EU or Member State law.

(f) The data importer agrees that the choice made by the data subject will not prejudice his/her substantive and procedural rights to seek remedies in accordance with applicable laws.

Liability

(a) Each Party shall be liable to the other Parties for any damages it causes the other Parties by any breach of these Clauses.

(b) The data importer shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages the data importer or its sub-processor causes the data subject by breaching the third-party beneficiary rights under these Clauses.

(c) Notwithstanding paragraph (b), the data exporter shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages the data exporter or the data importer (or its sub- processor) causes the data subject by breaching the third- party beneficiary rights under these Clauses. This is without prejudice to the liability of the data exporter and, where the data exporter is a processor acting on behalf of a controller, to the liability of the controller under Regulation (EU) 2016/679 or Regulation (EU) 2018/1725, as applicable.

(d) The Parties agree that if the data exporter is held liable under paragraph (c) for damages caused by the data importer (or its sub-processor), it shall be entitled to claim back from the data importer that part of the compensation corresponding to the data importer’s responsibility for the damage.

(e) Where more than one Party is responsible for any damage caused to the data subject as a result of a breach of these Clauses, all responsible Parties shall be jointly and severally liable and the data subject is entitled to bring an action in court against any of these Parties.

(f) The Parties agree that if one Party is held liable under paragraph (e), it shall be entitled to claim back from the other Party/ies that part of the compensation corresponding to its/their responsibility for the damage.

(g) The data importer may not invoke the conduct of a sub-processor to avoid its own liability.

Clause 13

Supervision

(a) The supervisory authority with responsibility for ensuring compliance by the data exporter with Regulation (EU) 2016/679 as regards the data transfer, as indicated in Annex I.C, shall act as competent supervisory authority.

(b) The data importer agrees to submit itself to the jurisdiction of and cooperate with the competent supervisory authority in any procedures aimed at ensuring compliance with these Clauses. In particular, the data importer agrees to respond to enquiries, submit to audits and comply with the measures adopted by the supervisory authority, including remedial and compensatory measures. It shall provide the supervisory authority with written confirmation that the necessary actions have been taken.

SECTION III – LOCAL LAWS AND OBLIGATIONS IN CASE OF ACCESS BY PUBLIC AUTHORITIES

Local laws and practices affecting compliance with the Clauses

(a) The Parties warrant that they have no reason to believe that the laws and practices in the third country of destination applicable to the processing of the personal data by the data importer, including any requirements to disclose personal data or measures authorising access by public authorities, prevent the data importer from fulfilling its obligations under these Clauses. This is based on the understanding that laws and practices that respect the essence of the fundamental rights and freedoms and do not exceed what is necessary and proportionate in a democratic society to safeguard one of the objectives listed in Article 23(1) of Regulation (EU) 2016/679, are not in contradiction with these Clauses.

(b) The Parties declare that in providing the warranty in paragraph (a), they have taken due account in particular of the following elements:

(i) the specific circumstances of the transfer, including the length of the processing chain, the number of actors involved and the transmission channels used; intended onward transfers; the type of recipient; the purpose of processing; the categories and format of the transferred personal data; the economic sector in which the transfer occurs; the storage location of the data transferred;

(ii) the laws and practices of the third country of destination– including those requiring the disclosure of data to public authorities or authorising access by such authorities – relevant in light of the specific circumstances of the transfer, and the applicable limitations and safeguards;

(iii) any relevant contractual, technical or organisational safeguards put in place to supplement the safeguards under these Clauses, including measures applied during transmission and to the processing of the personal data in the country of destination.

(c) The data importer warrants that, in carrying out the assessment under paragraph (b), it has made its best efforts to provide the data exporter with relevant information and agrees that it will continue to cooperate with the data exporter in ensuring compliance with these Clauses.

(d) The Parties agree to document the assessment under paragraph (b) and make it available to the competent supervisory authority on request.

(e) The data importer agrees to notify the data exporter promptly if, after having agreed to these Clauses and for the duration of the contract, it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under paragraph (a), including following a change in the laws of the third country or a measure (such as a disclosure request) indicating an application of such laws in practice that is not in line with the requirements in paragraph (a). The data exporter shall forward the notification to the controller.

(f) Following a notification pursuant to paragraph (e), or if the data exporter otherwise has reason to believe that the data importer can no longer fulfil its obligations under these Clauses, the data exporter shall promptly identify appropriate measures (e.g. technical or organisational measures to ensure security and confidentiality) to be adopted by the data exporter and/or data importer to address the situation, if appropriate in consultation with the controller. The data exporter shall suspend the data transfer if it considers that no appropriate safeguards for such transfer can be ensured, or if instructed by the controller or the competent supervisory authority to do so. In this case, the data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses. If the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise. Where the contract is terminated pursuant to this Clause, Clause

16(d) and (e) shall apply.

Clause 15

Obligations of the data importer in case of access by public authorities

15.1 Notification

(a) The data importer agrees to notify the data exporter and, where possible, the data subject promptly (if necessary with the help of the data exporter) if it:

(i) receives a legally binding request from a public authority, including judicial authorities, under the laws of the country of destination for the disclosure of personal data transferred pursuant to these Clauses; such notification shall include information about the personal data requested, the requesting authority, the legal basis for the request and the response provided; or

(ii) becomes aware of any direct access by public authorities to personal data transferred pursuant to these Clauses in accordance with the laws of the country of destination; such notification shall include all information available to the importer.

The data exporter shall forward the notification to the controller.

(b) If the data importer is prohibited from notifying the data exporter and/or the data subject under the laws of the country of destination, the data importer agrees to use its best efforts to obtain a waiver of the prohibition, with a view to communicating as much information as possible, as soon as possible. The data importer agrees to document its best efforts in order to be able to demonstrate them on request of the data exporter.

(c) Where permissible under the laws of the country of destination, the data importer agrees to provide the data exporter, at regular intervals for the duration of the contract, with as much relevant information as possible on the requests received (in particular, number of requests, type of data requested, requesting authority/ies, whether requests have been challenged and the outcome of such challenges, etc.). The data exporter shall forward the information to the controller.

(d) The data importer agrees to preserve the information pursuant to paragraphs (a) to (c) for the duration of the contract and make it available to the competent supervisory authority on request.

(e) Paragraphs (a) to (c) are without prejudice to the obligation of the data importer pursuant to Clause 14(e) and Clause 16 to inform the data exporter promptly where it is unable to comply with these Clauses.

15.2 Review of legality and data minimisation

(a) The data importer agrees to review the legality of the request for disclosure, in particular whether it remains within the powers granted to the requesting public authority, and to challenge the request if, after careful assessment, it concludes that there are reasonable grounds to consider that the request is unlawful under the laws of the country of destination, applicable obligations

under international law and principles of international comity. The data importer shall, under the same conditions, pursue possibilities of appeal. When challenging a request, the data importer shall seek interim measures with a view to suspending the effects of the request until the competent judicial authority has decided on its merits. It shall not disclose the personal data requested until required to do so under the applicable procedural rules. These requirements are without prejudice to the obligations of the data importer under Clause 14(e).

(b) The data importer agrees to document its legal assessment and any challenge to the request for disclosure and, to the extent permissible under the laws of the country of destination, make the documentation available to the data exporter. It shall also make it available to the competent supervisory authority on request. The data exporter shall make the assessment available to the controller.

(c) The data importer agrees to provide the minimum amount of information permissible when responding to a request for disclosure, based on a reasonable interpretation of the request.

SECTION IV – FINAL PROVISIONS

Clause 16

Non-compliance with the Clauses and termination

(a) The data importer shall promptly inform the data exporter if it is unable to comply with these Clauses, for whatever reason.

(b) In the event that the data importer is in breach of these Clauses or unable to comply with these Clauses, the data exporter shall suspend the transfer of personal data to the data importer until compliance is again ensured or the contract is terminated. This is without prejudice to Clause 14(f).

(c) The data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses, where:

(i) the data exporter has suspended the transfer of personal data to the data importer pursuant to paragraph (b) and compliance with these Clauses is not restored within a reasonable time and in any event within one month of suspension;

(ii) the data importer is in substantial or persistent breach of these Clauses; or

(iii) the data importer fails to comply with a binding decision of a competent court or supervisory authority regarding its obligations under these Clauses.

In these cases, it shall inform the competent supervisory authority and the controller of such non- compliance. Where the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise.

(d) Personal data that has been transferred prior to the termination of the contract pursuant to paragraph (c) shall at the choice of the data exporter immediately be returned to the data exporter or deleted in its entirety. The same shall apply to any copies of the data. The data importer shall certify the deletion of the data to the data exporter. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit the return or deletion of the transferred personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process the data

to the extent and for as long as required under that local law.

(e) Either Party may revoke its agreement to be bound by these Clauses where (i) the European Commission adopts a decision pursuant to Article 45(3) of Regulation (EU) 2016/679 that covers the transfer of personal data to which these Clauses apply; or (ii) Regulation (EU) 2016/679 becomes part of the legal framework of the country to which the personal data is transferred. This is without prejudice to other obligations applying to the processing in question under Regulation (EU) 2016/679.

Clause 17

Governing law

These Clauses shall be governed by the law of the EU Member State in which the data exporter is established. Where such law does not allow for third-party beneficiary rights, they shall be governed by the law of another EU Member State that does allow for third-party beneficiary rights. The Parties agree that this shall be the law of France.

Clause 18

Choice of forum and jurisdiction

(a) Any dispute arising from these Clauses shall be resolved by the courts of an EU Member State.

(b) THE PARTIES AGREE THAT THOSE SHALL BE THE COURTS OF FRANCE.

(c) A data subject may also bring legal proceedings against the data exporter and/or data importer before the courts of the Member State in which he/she has his/her habitual residence.

(d) The Parties agree to submit themselves to the jurisdiction of such courts.

ANNEX I

A. LIST OF PARTIES Data exporter (processor)

OVH SAS

Company incorporated under French Law whose registered office is located at 0 xxx Xxxxxxxxxx 00000 Xxxxxxx (Xxxxxx),

OVH Hispano

Company incorporated under Spanish law whose registered office is located et X/ Xxxxxx 00, 0x xxxxxx, 00000 Xxxxxx (Xxxxx),

OVH SRL

Company incorporated under Italian law whose registered office is located et Xxx Xxxxx Xxxxxxxx 00, XXX 00000 Xxxxxx (Xxxxx),

OVH GmbH

Company incorporated under German law whose registered office is located at Xxxxxxxxxxxxxxx 00, 00000 Xxxx (Xxxxxxx),

XXX Hosting Limited

Company incorporated under Irish law whose registered office is located at 00/00 Xxxxxxxxxxx Xxxxxx Xxxx Xxxxxx 0 X00 XX00 (Xxxxxxx),

OVH Sp. Zo.o.

Company incorporated under Polish law whose registered office is located at xx. Xxxxxxxx 0, 00-000

Xxxxxxx (Xxxxxx),

OVH Hosting Sistemas informaticos unipessoal

Company incorporated under Portuguese law whose registered office is located at Xxxxx xx Xxxxxxxx, xx 0, 0x xxx 0000 000 Xxxxxx (Xxxxxxxx),

OVH BV

Company incorporated under Dutch law whose registered office is located at Xxxxxxxxxx 00, 0000 XX Xxxxxxxxx-Xxxxxxxx, (Xxxxxxxxxxx),

OVH SAS and OVH European Affiliates contact point for standard contractual clauses : OVH - Data Protection Xxxxxxx - 0 xxx Xxxxxxxxx 00000 Xxxxxxx Xxxxxx

Activities relevant to the data transferred under these Clauses:

Computing, storage and/or any such other Services as described in the agreement concluded with the Clients.

Data importer (processor)

OVH Singapore PTE Ltd,	Altimat Data Center Singapore PTE. Ltd,
Company incorporated under Singaporean law whose registered office is located 000 Xxxxx xxxxxx #00-00, Xxxxxxxxxx xxxxxxxx xxxxxxxx, 000000 (Xxxxxxxxx).	Company incorporated under Singaporean law whose registered office is located 000 Xxxxx xxxxxx #00-00, Xxxxxxxxxx xxxxxxxx xxxxxxxx, 000000 (Xxxxxxxxx)
Activities relevant to the data transferred under these Clauses: Computing, storage and/or any such other Services (i) hosted in Datacenter(s) located in Asia-Pacific area or (ii) for which the applicable Specific Terms and Conditions provide these OVH Affiliates may participate to carry out such Services	Activities relevant to the data transferred under these Clauses: Computing, storage and/or any such other Services (i) hosted in Datacenter(s) located in Asia-Pacific area or (ii) for which the applicable Specific Terms and Conditions provide these OVH Affiliates may participate to carry out such Services
OVH Australia PTY Ltd,	Data Center Sydney PTY Ltd,
Company incorporated under Australian law whose registered office is located Xxxxx 00 - 00 Xxxxxx Xxxxxx, Xxxxx Xxxxxx XXX 0000, registered under company number 612612754. (Australia)	Company incorporated under Australian law whose registered office is located Xxxxx 00 - 00 Xxxxxx Xxxxxx, Xxxxx Xxxxxx XXX 0000 (Australia).
Activities relevant to the data transferred under these Clauses: Computing, storage and/or any such other Services (i) hosted in Datacenter(s) located in Asia-Pacific area or (ii) for which the applicable Specific Terms and Conditions provide these OVH Affiliates may participate to carry out such Services	Activities relevant to the data transferred under these Clauses: Computing, storage and/or any such other Services (i) hosted in Datacenter(s) located in Asia-Pacific area or (ii) for which the applicable Specific Terms and Conditions provide these OVH Affiliates may participate to carry out such Services
Contact point for Singapore and Australia entities: OVH Singapore PTE Ltd, 000 Xxxxx xxxxxx #00-00, Xxxxxxxxxx xxxxxxxx xxxxxxxx, 000000 (Xxxxxxxxx).
OVH Tech R&D Private Limited,	Altimat Data Center India Private Limited,
Company incorporated under Indian law, whose registered office is located at Xxxxxxxxx Xxxxxxxxx, Xxxxx Xxxxxxx, Xxxxx Xxxxx, Xxxxxxxxxxxx Xxxx, Xxxxxxxxx, Xxxxxxxxx, 000000 Xxxxx	Company incorporated under Indian law, whose registered office is located at H No. 215, A102 1st Floor A Wing, Narpoli, Xxxxxx Xxxx, Xxxxxxx Xxx Xxxx, Xxxxx Xxxxx, Xxxxxxxx, Xxxxx, Xxxxxxxxxxx, Xxxxx, 000000
Contact point: Xxxxxxxxx Xxxxxxxxx, Xxxxx Xxxxxxx, Xxxxx Xxxxx, Xxxxxxxxxxxx Xxxx, Xxxxxxxxx, Xxxxxxxxx, 000000 Xxxxx	Contact point: Xxxxxxxxx Xxxxxxxxx, Xxxxx Xxxxxxx, Xxxxx Xxxxx, Xxxxxxxxxxxx Xxxx, Xxxxxxxxx, Xxxxxxxxx, 000000 Xxxxx
Activities relevant to the data transferred under these Clauses: Computing, storage and/or any such other Services (i) hosted in Datacenter(s) located in Asia-Pacific area or (ii) for which the applicable Specific Terms and Conditions provide these OVH Affiliates may participate to carry out such Services	Activities relevant to the data transferred under these Clauses: Computing, storage and/or any such other Services (i) hosted in Datacenter(s) located in Asia-Pacific area or (ii) for which the applicable Specific Terms and Conditions provide these OVH Affiliates may participate to carry out such Services

B. DESCRIPTION OF TRANSFER

Categories of data subjects whose personal data is transferred

The categories of data subjects are determined and controlled by the Clients, at their sole discretion.

Categories of personal data transferred

Personal data used by the Clients within the Services including but not limited to any personal data stored by the Clients on, and/or computed by the Clients using, OVH SAS’ and OVH European Affiliates’ infrastructures. The categories of such personal data are determined and controlled by the Clients, at their sole discretion.

Sensitive data transferred (if applicable) and applied restrictions or safeguards that fully take into consideration the nature of the data and the risks involved, such as for instance strict purpose limitation, access restrictions (including access only for staff having followed specialised training), keeping a record of access to the data, restrictions for onward transfers or additional security measures.

The categories of such personal data are determined and controlled by the Client, at its sole discretion.

The frequency of the transfer (e.g. whether the data is transferred on a one-off or continuous basis).

The frequency of the transfer is determined by the Clients, at their sole discretion.

Nature of the processing

The nature of processing activities carried out by the data importer on personal data may be computing, storage and/or any such other Services as provided in the agreement in force between OVH SAS or the OVH European Affiliates and the respective Client.

Purposes of the data transfer and further processing

Process the personal data to the extent necessary to provide the Services.

The period for which the personal data will be retained, or, if that is not possible, the criteria used to determine that period

The processing activities are performed for the duration provided in the Agreement

For transfers to (sub-) processors, also specify subject matter, nature and duration of the processing

When processors external to the OVH Group are involved in the processing of personal data carried out, this is mentioned in the terms and conditions applicable to the services concerned.

C. COMPETENT SUPERVISORY AUTHORITY

Identify the competent supervisory authority in accordance with Clause 13

France - Commission Nationale de l'Informatique et des Libertés - CNIL

8 rue Vivienne, CS 30223 F-75002 Paris, Cedex 02

Tel. x00 0 00 00 00 00

Spain - Agencia de Protección de Datos

X/Xxxxx Xxxx, 0 00000 Xxxxxx

Tel. x00 00000 0000 • e-mail: xxxxxxxxxxxxx@xxxx.xx

Portugal - Comissão Nacional de Protecção de Dados - CNPD

X. xx Xxx. Xxxxx, 000-0x 0000-000 Xxxxxx

Tel. x000 00 000 00 00 • e-mail: xxxxx@xxxx.xx

Italy - Garante per la protezione dei dati personali

Xxxxxx xx Xxxxx Xxxxxxx, 000 00000 Xxxx

Tel. x00 00 00000 0 • e-mail: xxxxxxx@xxxxxxxxxxxxxx.xx

Germany - Die Bundesbeauftragte für den Datenschutz und die Informationsfreiheit

Xxxxxxxxxxxxx 00 - 00000 Xxxx

Xxx. x00 000 000000 0 • e-mail: xxxxxxxxxx@xxxx.xxxx.xx

Netherlands - Autoriteit Persoonsgegevens

Xxxxx Xxxxxxxxx 00 P.O. Box 93374 0000 XX Xxx Xxxx/Xxx Xxxxx Tel. x00 00 000 0000 • e-mail: xxxx@xxxxxxxxxxxxxxxxxxxxxxxxxx.xx

ANNEX II

TECHNICAL AND ORGANISATIONAL MEASURES INCLUDING TECHNICAL AND ORGANISATIONAL MEASURES TO ENSURE THE SECURITY OF THE DATA

The applicable security principles and rules are defined by the security team in partnership with OVHcloud top management. The security team, under the responsibility of the CISO, is itself composed of 4 teams:

The xxxxxxxx.xxxxx team in charge of developing the security tool used within OVHcloud. This team designs and operates the tools to support certain security measures deployed on all OVHcloud information systems. These tools include the management of the identities and accesses of employees and service providers, authentication mechanisms made available to clients, identification of vulnerabilities on systems and security monitoring. This team also assists other business teams in the design and deployment of architectures by ensuring security from the definition phase onwards.

The security.operations team is responsible for supporting teams in the implementation of good security practices within operations, the implementation of formal security management processes, the support in the integration of security tools and the alignment of security devices within OVHcloud. The security.ops team puts in place an internal control system, both organizational and technical on security and assists the product teams in the implementation of formal information security management systems and in their certification.

The security.cert team is responsible for monitoring threat sources, identifying attack tools and methods to anticipate them, and managing malicious security incidents. This team manages the OVHcloud CSIRT and exchanges with international expert communities to provide the best sources of information to anticipate attacks.

The security.customer team is in charge of adapting the products offered by OVHcloud to the specific needs of specific business sectors (healthcare, finance, etc.). The team values the expectations of these business sectors, and coordinates OVHcloud’s response to contractual and standard compliance. It also provides level 3 support for customer questions about compliance and information security.

The security team is accompanied by the physical security management teams and the privacy teams. These three teams work together to ensure optimal effectiveness of actions on these subjects with strong adherence.

In addition, security referees are deployed within OVHcloud teams. These focal points enable the dissemination of good practices within teams, provide an identified point of contact for incident and crisis management, and enable the gathering of information from operations to the security team.

A security committee led by the CISO and the managers of the security team ensures communication with the Executive Committee (ComEx) of OVHcloud. This semi-annual committee presents the main threats under surveillance, the major risks, the monitoring metrics, the progress of the ongoing actions and the updated roadmap. This committee also ensures that the ISSP is aligned with OVHcloud's strategic and operational objectives.

Security compliance management

The ISMS aims to ensure that the security requirements of the various interested parties of OVHcloud

are taken into account. These requirements are of different kinds:

• legal or regulatory requirements

• contractual commitments

• good practices on which OVHcloud is committed explicitly

OVHcloud must identified and consolidate those requirements and implement the management system in support for the compliance to these requirements.

Documentation

OVHcloud must deploy a formal documented management system to :

• provide a comprehensive framework for policy rules, guideline, operational documentation, records and indicators

• ensure formalism and follow-up of activities implemented to reduce risks

• demonstrate compliance with applicable legal, regulatory or contractual requirements

• demonstrate compliance with the rules set out in the detailed security policies

Assets management

OVHcloud must deploy a formal approach for managing assets carrying security risks or in support for security management to ensure appropriate security controls over them:

• Maintain accurate inventories of those assets

• Define and maintain ownership for those assets

• Classification of those assets based on appropriate criteria to support security decision

• Definition of security rules adapted to their criticality

Security risks management

OVHcloud must deploy a risk management approach to structure operational decisions affecting security. This risk management approach is based on the principles of ISO/IEC 31000 and ISO/IEC 27005 standards. It is based on:

• In-depth knowledge of systems through asset cartography, asset classifications and valuations from a security perspective

• Ongoing analysis of feared events, vulnerabilities, and the threat environment

• uniform formalization of security risks to make them explicit to technical experts and decision- makers for reasonable and informed decision-making

• follow-up of decisions and action plans following the identification of a risk

The establishment of formal risk management enables the operational specificity of a project or product to be taken into account and the achievement of specific security objectives. Failure to comply with a ISSP rule results in an analysis of the risks resulting from the introduction of compensatory security measures to achieve at least an equivalent level of safety or acceptance of risk.

Privacy

The legislation applicable to the protection of personal data and our privacy policy constitute the framework for the processing of this data that OVHcloud applies. ISMS complements this

framework by consistently defining, implementing, and improving security arrangements that ensure the protection of hosted personal data.

This commitment is reflected in particular in:

• The implementation of a Personal Information Management System (PIMS) integrated with ISMS

• Setting up a joint management instance between the security and privacy teams

• Alignment of security and data usage policies

• Integrating security measures within ISMS into contractual commitments on personal information protection with customers

• The privacy team's participation in ISMS management

• Involvement of the security team in efforts to identify privacy risks

• Joint participation in resolving security incidents that impact personal information

• Joint definition of security objectives and measures to be implemented in the context of projects.

Customer Protection

OVH implements means of protection on the tools made available to these customers as well as on the communication channels between them and OVHcloud such as: :

• Customer interfaces through the use of identification factors ;

• Tools of detection and alerting when customer credentials are used for illegitimate purpose;

• Protection of customer infrastructures and services against external threats

• data related to customer managed by OVHcloud

Moreover, OVHcloud protects its communications with customers with adequate means according to the context like encrypted channels, collaborative tools with access and security controls or any other means defined with customers.

Customer trust

OVHcloud must provide the adequate transparency to customer in order the assist them in defining the right product for their needs. In particular, OVHcloud must provide information about :

• Physical location of the data and workloads hosting

• Physical location of the control plane and administrators

• Physical location of the support teams

• Applicable law for the service contract

• Supply chain and technical dependencies (Hardware, Software, Subcontractors)

• Reversibility capabilities information

• Certification and assurance mechanisms in place

Customer in cloud security

OVHcloud must produce a clear definition of responsibilities between OVHcloud and customer:

• Assets ownership

• Operations responsibility

• Security risk ownership

• Recommendation of security controls to implement by customer with OVHcloud included features and configuration

• Recommendation of security controls to implement by customer with optional features or external means when relevant

Security Ecosystem

OVHcloud must maintain close relationship with security communities to improve the quality of risk mitigation and accelerate response time to security threats. Security communities are covering but not limited to :

• Security experts, internally and externally

• Security team from hardware manufacturers

• Security team of software editors

• Open source groups

• Security software editors

• Security professional services providers

External technical reputation

OVHcloud must implement a set of processes to ensure the technical reputation of all systems exposed on public networks, since OVHcloud customers are relying on OVHcloud assets for their own information system. This covers:

• IP reputation to ensure that IP allocated to a customer infrastructure are usable for all legitimate purposes

• Abuse process to handle the dispute process when customer infrastructures are used for malicious activities

• Anti-fraud process to ensure all infrastructure usage is legitimate

• Anti-hack process to take down customer compromised infrastructures

• Spam, phishing, malware and dDoS detection and mitigation to protect the public from threats that might be hosted on OVHcloud infrastructure

• Protection and management of all assets under OVHcloud responsibility connected to public networks

Information system user

OVHcloud must protect information and systems by ensuring the information system is adequately operated:

• users are aware of the rules applicable to IS usage

• Company owned device management

• Employee owned device management

• Access to IS from external devices

• Collaborative tools

• Workstation security

• Mobile devices

Human resources

OVHcloud must integrate security topic into HR processes to ensure adapted resources are available to meet security objectives. This includes:

• security investments and human resources related to security priorities

• development of roadmaps of other OVHcloud teams to integrate security needs (investment and human resources)

• skills and training requirements for teams and inclusion in the training plan

• identifying gaps between needs and available resources for the adaptation of roadmaps and taking into account in risk management.

OVHcloud must educate employees on security as soon as they are integrated and throughout their presence in OVHcloud. This awareness is realized by:

• IT policy document to define the rules of usage of information system

• On boarding awareness session for all employees

• Formal threat presentation sessions targeting OVHcloud and security features in place

• Regular communications on good practices and risks

• Communications focused on a specific threat, related to current events or our detection activities

• Tests of the reflexes and the reaction capabilities of the collaborators

• Sharing information resources and feedback on cloud threats and vulnerabilities OVHcloud must manage security in the complete employee life-cycle:

• Background check fitted to position criticality

• On boarding management including contractual commitment and awareness management

• Specific security training depending of position criticality

• Regular awareness session

• Disciplinary process for security violation

• Termination of contract management

Identity and access management

OVHcloud must maintain a strict policy of logical access rights management for employees :

• all employees use nominative user accounts to access any system

• generic and anonymous accounts is prohibited for any human access

• authorizations are issued and monitored by managers, following the principle of least privilege and the principle of gradually gaining trust

• to the greatest extent possible, all authorizations should be based on roles rather than unit rights

• a formal, fully auditable process is in place for account creation, modification, deletion and password change

• connection sessions systematically have an expiry period suited to each application

• user accounts are automatically deactivated if the password is not renewed after 90 days

• password complexity is mandatory based on best practices and recommendations from authorities:

o users use automatic password generators rather than choosing their own passwords

o Complexity rules are defined and communicated to all employees, and when possible technically enforced on systems

o passwords must be renewed regularly, with a maximum of 90 days

• storing passwords in unencrypted files, on paper or in web browsers is prohibited OVHcloud must maintain a strict policy of for managing administrator access rights for platforms :

• all administrator access to live systems is realized via a bastion host

• administrators connect to the bastion hosts via SSH, using individual and nominative pairs of public and private keys

• connection to the target system is realized either via a shared service account or via a nominative account and bastion hosts; using default accounts on systems and equipment is prohibited;

• dual-factor authentication is mandatory for remote administrator access and for any employees accessing sensitive areas of the system, with such access being fully traced

• administrators have an account exclusively devoted to administration tasks, in addition to their standard user account;

• authorizations are granted and monitored by managers, in accordance with the principle of least privilege

• SSH keys are protected by a password that meets the requirements of the password policy

Cryptography

• Use strong cryptography to secure data at rest and in transit and administration operations.

o Manage cryptographic assets with automated process

o Monitor certificates and keys to ensure all systems have valid certificates at all time

Physical security

OVHcloud physical security is based on zoning. Each area within OVHcloud premises is categorized in a zone type dependent from the area usage and the sensitivity of operations and assets hosted. At each zone type, according to it's sensitivity is defined security controls on:

• Environmental protection against fire, flood, weather conditions our any applicable environmental hazard related to premises location

o Monitoring of any malicious or accidental events with automated (CCTV, sensors) or human (security watch)

o Zone control, with a formal definition of all zones interfaces and gateway

o Access control to ensure only authorized people access each zone for legitimate purpose

Supply Chain

OVHcloud’s product teams rely mainly on other OVHcloud teams, but also on partners, subcontractors and suppliers to manage operations, and to compose products and services delivered to customers. The match between the outsourced activities and OVHcloud’s security commitment must be managed:

• Identify dependencies between OVHcloud teams and subcontractors, suppliers and partners

o Classification of criticality dependencies

o Risk analysis and risk reduction where necessary

o Service level cascade and security commitments

o Integrating security into projects

o Security insurance plan for subcontractors

Architecture

OVHcloud must ensure that cloud architecture is designed to be and stay secure taking into account the complexity of information system required to deliver the service, the factorization of information systems assets to optimize ressources and the management of several generations of technologies. We rely on several pillars to achieve this objective:

• Strong segregation of systems by criticality

• Mutualization of security primitives under the management of security team

• Harmonization of management of specific security assets and processes under common management rules

• Strong automation for security deployment

OVHcloud security team maintain a list of basic security architecture guidelines for systems. Architecture principles must be defined and documented for each type of infrastructure internally. OVHcloud uses several classification scheme for IT architecture depending of needs.

Exemples of classification:

• Tiers 0, Tiers 1, Tiers 2 for internal IS, depending of the internal usage

• Mutualized control plane

• Product dedicated control plane

• Customer infrastructure (Data plane)

Classification scheme must be used to define the set of security controls to apply according to the threat environment relevant to the classification characteristics.

Configuration and hardening

• Use OS patterns with system exposure minimization and baseline of security tools

• Use hardened kernels

• Follow best practices for configuration

• Deploy system as code with automated deployment tools

• Regularly review configurations for security

Administration

OVHcloud maintain those rules for administration activities:

• all administrator access to live systems is realized via a bastion host

• administrators connect to the bastion hosts via SSH, using individual and nominative pairs of public and private keys

• connection to the target system is realized either via a shared service account or via a nominative account and bastion hosts; using default accounts on systems and equipment is prohibited

• dual-factor authentication is mandatory for remote administrator access and for any employees accessing sensitive areas of the system, with such access being fully traced

• administrators have an account exclusively devoted to administration tasks, in addition to their standard user account

• authorizations are granted and monitored by managers, in accordance with the principle of least privilege and the principle of gaining trust

• SSH keys are protected by a password that meets the requirements of the password policy; access rights are reviewed on a regular basis, in collaboration with the departments concerned

Vulnerability and patch management

OVHcloud must ensure a systematic deployment of available security patches within a time frame defined by system based on its criticality. Vulnerabilities on systems must be identified and evaluated as soon as the associated patch is available. The application of the patch outside the predefined time limit must be justified on the basis of the level of risk associated with the corrected vulnerability or the existence of compensatory controls reducing the risk to an acceptable level.

• System owners are responsible of vulnerabilities management of their systems

• Assets shall be classified in terms of criticality

• Patch deployment is based on asset criticality and prioritization of patch deployment is based on risk level

• Vulnerability mitigation can be achieve without patch deployment, in that case, a complete analysis of the situation must be performed

OVHcloud must complete this process by a threat intelligence process and vulnerabilities monitoring to ensure all vulnerabilities that could put systems at risk are mitigated.

Monitoring and detection

OVHcloud must log all records necessary to understand any security events:

• logs are backed up and not limited to local storage

• logs are consulted and analyzed by a limited number of authorized personnel, in accordance with the authorization and access management policy

• tasks are divided up between the teams responsible for operating the monitoring infrastructure and the teams responsible for operating the service

The list of activities that are logged includes the following:

• logs of storage servers hosting customer data;

• logs of the machines managing the customer’s infrastructure;

• logs of the machines monitoring the infrastructures;

• logs of the antivirus software installed on all equipped machines;

• integrity checks of logs and systems, where appropriate;

• tasks and events carried out by the customer on their infrastructure;

• network intrusion detection logs and alerts, if appropriate;

• logs of network equipment;

• logs of the infrastructure of the surveillance cameras;

• logs of administrator machines;

• logs of time servers;

• logs of badge readers;

• logs of bastion hosts.

OVHcloud implement tools and process to ensure:

• Fast detection of security events to minimize the occurrence of incidents and minimize impacts

• Adapted capabilities to investigate in post mortem

Change management

OVHcloud must maintain a formal change management principles including security :

• roles and responsibilities in security are clearly defined

• All changes are documented in tracking tool

• criteria for classification are set out in order to identify the security analysis to follow

• the risks associated with the changes are analyzed (if a risk is identified, the security manager and risk manager work together to validate the change)

• intrusion tests may be carried out (where applicable); the change is planned and scheduled with the customers (where applicable)

• the change is rolled out gradually (1/10/100/1000) and, if there is a risk, a rollback procedure is planned

• a retrospective review of the change is carried out

Each unit within OVHcloud implement its own change management procedure according to this principles.

Project management

OVHcloud integrates security within evolution and transformation projects. Compliance with ISSP and data protection is a general requirement for all OVHcloud activities. The security team assists OVHcloud project teams in the full lifecycle of all projects to ensure that the security means are adequate and properly implemented. This support consists of:

• Determine the security criticality of the data and processes involved in the project

o Accompany project managers in the definition of technical and functional architecture

o Support project teams in integration into the OVHcloud IS

o Ensure compliance with the security base in the context of the project and the specific security measures to be put in place

o Assist sponsors and project leaders in arbitrating specific measures against financial and operational constraints

o Evaluate the security level of the project before production phase and after go-live

o Identify residual risks and monitor them over time

Incident management

OVHcloud deploys a unified approach to security incident management by putting in place the organizational and technical means to:

• Detect and consolidate events that can impact the security of information systems and services

o Correlate events that indicate a possible breach of information security and trigger incident handling as soon as possible

o Mobilize experts and decision-makers in charge of resolving the incident

o Support the incident with the following objectives

▪ Reduce operational impacts

▪ Preserve evidences to support possible judicialization or internal sanctions

▪ Return to nominal situation

o Inform interested parties in accordance with legal and contractual obligations

o Identify root causes, update risk analysis, and define potential action plans to reduce the risk of a new occurrence

Network security

OVHcloud is managing a worldwide backbone to connect all infrastructures hosted in the datacenters and local networking to ensure the appropriate functioning and administration of the systems. The network security relies on:

• segmentation and segregation of network zones

• all networks equipment's are administered via a bastion host, applying the principle of least privilege

• access to the administration interfaces and administrator features for equipment is reserved to staff listed on control lists

• Network device inventory and automatized management

• Management of traffic and reaction to specific events

• Configuration of networks devices in terms of networking rules and access control

o Administration of network based on automation. Configurations are deployed automatically, based on validated templates

o Devices configuration are managed in a central configuration repository

o A process is in place for ensuring changes are controlled

• the logs are collected, centralized and monitored on a permanent basis by the network operations team

Continuity

Continuity management relies on all mechanisms to ensure Availability, Rescue and Recovery.

Systems criticality must be defined to determine acceptable Recovery Point Objective (RPO) and Recovery Time Objective (RTO).

System owners must implement controls to ensure the effectiveness ot continuity mechanisms.

Internal controls

First-level internal controls are deployed by the operational teams and the security team. These monitoring activities are mainly carried out in the form of:

• automated systems monitoring mechanisms

• operational checkpoints integrated into processes to ensure team coordination, risk accounting, and possible validations of risky activities. Where possible, these control points are integrated into the tools.

• ad hoc operational controls by security experts

Second-level internal control is carried out by the security teams to ensure the effectiveness of the first- level controls. These activities are formal. The effectiveness of ISMS is also monitored in the context of steering activities.

Internal audits

OVHcloud relies on internal audit approaches to assess the effectiveness of internal control activities. These audits are performed by teams independent of audited operations and systems. Internal audit approaches include:

• Organizational and technical audit of the rules defined within ISSP

• Technical audit of architecture review, deployment, project

• Source code audit

• Intrusion tests

These steps are carried out by OVHcloud personnel or external contractors.

OVHcloud is implementing a public Bug Bounty program that will enable the permanent testing of our systems exposed on the internet.

These activities help identify vulnerabilities, non-conformities and opportunities for improvement and fuel the process of continuous improvement of security.

External audits

OVHcloud implements an external audit program on certified perimeters. We rely on:

• general security framework: ISO 27001, AICPA TSP (SOC)

• Cloud Provider-specific security framework: ISO 27017, CISPE, CSA CCM

• repositories dedicated to specific issues such as privacy: CISPE, ISO 27018, ISO 27701

• industry or geographical specific security framework: PCI DSS, HDS, PSEE, SecNumCloud, AGID, ENS, C5

For each framework, we determine the most appropriate certification or audit organization to strengthen our clients' confidence in our ability to meet the requirements that meet their expectations.

Audits by customers and authorities

OVHcloud allows its customers, under certain conditions, to perform security audits on systems. Such audits may be:

• Technical, performed remotely (Intrusion Test, Vulnerability Scan) without OVHcloud teams intervention

• Organizational and technical in asynchronous way through questionnaires and written exchanges with OVHcloud

• On-site organizational and technical, including installation visits, interviews with operational staff, and access to documentation and configurations.

As with internal and external audits, these evaluations provide input to the security continuous improvement.

Continuous improvement

OVHcloud is implementing a continuous improvement of security and management processes. Opportunities for improvement are identified by:

• Internal control activities

• Internal and external audits

• Security Incident Analysis

• Identification of security risks

• Stakeholders involved in security management processes

• OVHcloud Security Interested Parties

• Analysis of root causes of non-conformities, vulnerabilities and incidents

These opportunities for improvement are evaluated before implementation and where appropriate prioritized and arbitrated. Consecutive action plans are formally followed in the project management tools used by teams

The processor adopts the same technical and organizational measures as the controller, listed above.