Data protection rights

Data protection rights

The Federal Data Protection Act, as well as EU Regulation 679/2016 (hereinafter also referred to simply as the โ€œGDPRโ€), recognize important rights regarding the protection of personal data that may be exercised by contacting the Data Controller. The Data Controller must facilitate the exercise of these rights by the data subject by adopting all appropriate technical and organizational measures for this purpose (for example, by providing means to submit requests electronically, particularly when personal data is processed by electronic means). The Data Controller is also required to respond to the data subjectโ€™s requests without undue delay and no later than one month, and to provide reasons for any decision not to grant such requests.

The Federal Data Protection Act, as well as EU Regulation 679/2016 (hereinafter also referred to simply as the โ€œGDPRโ€), recognize important rights regarding the protection of personal data that may be exercised by contacting the Data Controller. The Data Controller must facilitate the exercise of these rights by the data subject by adopting all appropriate technical and organizational measures for this purpose (for example, by providing means to submit requests electronically, particularly when personal data is processed by electronic means). The Data Controller is also required to respond to the data subjectโ€™s requests without undue delay and no later than one month, and to provide reasons for any decision not to grant such requests.

Index

Index

1. SCOPE

1. SCOPE

The purpose of this document is to describe the operating procedures adopted by WellD Sagl (hereinafter also referred to simply as โ€œWellDโ€ or โ€œCompanyโ€ o โ€œOwnerโ€) headquartered in Lugano, Via Pessina No. 9, in order to process requests from data subjects to exercise their rights correctly and in a timely manner, ensuring, in particular, compliance with the principles and provisions contained in the Federal Data Protection Act (LPD) of September 25, 2020, the Data Protection Ordinance (OPDa) of August 31, 2022, and the GDPR.

2. Regulations and Reference Documents

2. Regulations and Reference Documents

Federal Data Protection Act (LPD) โ€“ September 25, 2020, Articles 5, 24, 49.

Data Protection Ordinance (OPDa) โ€“ August 31, 2022

EU Regulation 679/2016 (hereinafter also referred to as โ€œGDPRโ€)

EDPB Guidelines 1/2022 on the Rights of Data Subjects, adopted on March 28, 2023

  1. Rights of Data Subjects

  1. Rights of Data Subjects

This procedure specifically describes the operational procedures regarding the exercise of rights by data subjects, taking into account that:

โ€ข the data subject has the right to be informed about processing activities concerning him or her (Art. 19 LPD);

โ€ข the data subject has the right to be informed in the event of a data security breach (Art. 24 LPD). Specifically, requests from data subjects may concern the following rights set forth in the LPD, the OPDa โ€“ August 31, 2022, and the GDPR, namely:

3.1 Right of Access of the Data Subject (Art. 25 LPD, Art. 16 OPDa)

3.1 Right of Access of the Data Subject (Art. 25 LPD, Art. 16 OPDa)

The data subject has the right to obtain confirmation from the Data Controller as to whether personal data concerning him or her is being processed, and, if so, to access the personal data and the following information:

โ€ข the purposes of the processing;

โ€ข the categories of personal data in question;

the recipients or categories of recipients to whom the personal data have been or will be disclosed, in particular if they are recipients in third countries or international organizations;

โ€ข the intended retention period for personal data, or, if that is not possible, the criteria used to determine that period.


The right to obtain a copy must not infringe upon the rights and freedoms of others.


If personal data is transferred to a third country or to an international organization, the data subject has the right to be informed of the existence of appropriate safeguards regarding the transfer.


The request must be submitted by the data subject in writing (including electronically), unless the Data Controller consents to the request being made orally.


The information is provided by the Data Controller in writing or in the form in which the data is available. In agreement with the Data Controller, the data subject may review their data on site. The information may be provided orally if the data subject agrees. Where the data subject submits the request via electronic means, and unless the data subject specifies otherwise, the information is provided in a commonly used electronic format.


The deadline for responding to the data subject, for all rights, is 30 days from receipt of the request, extendable to a maximum of three months in particularly complex cases.


In any case, the data controller must respond to the data subject within 1 month of the request, even in the event of a denial, restriction, or postponement of the information.


The data controller must provide a copy of the personal data being processed. If the data subject requests additional copies, the data controller may charge a reasonable fee based on administrative costs.


It is up to the Data Controller to assess the complexity of the response to the data subject and to determine the amount of any contribution to be requested from the data subject pursuant to Art. 19 of the OPDa (see Exceptions to Free Access). If providing the information entails a disproportionate burden, the Data Controller may request that the data subject contribute appropriately toward the costs. This contribution shall not exceed 300 francs. In such a case, the data controller shall inform the data subject of the amount of the contribution before the information is provided. If the data subject does not confirm the request within ten days, the request is deemed withdrawn without incurring any costs. The 30-day deadline for processing the data subjectโ€™s request begins at the end of the ten-day reflection period.

3.2 Correction of Data (Art. 32, Annexes 1, 3โ€“4 of the Data Protection Act)

3.2 Correction of Data (Art. 32, Annexes 1, 3โ€“4 of the Data Protection Act)

The data subject has the right to obtain from the data controller the rectification of inaccurate personal data concerning him or her without undue delay, taking into account the purposes of the processing. The data subject has the right to have incomplete personal data completed, including by providing a supplementary statement.


The law does not expressly specify a deadline for processing a request for correction submitted by the data subject, but it is recommended to respond within the same timeframe established for processing requests regarding the right of access.


The right to rectification cannot be exercised if a legal provision prohibits such modification or if the personal data is processed for public record-keeping purposes. The justifying grounds set forth in Article 31 of the LPD do not constitute a relevant legal provision in this regard.


Exercising the right to correction is free of charge, and no financial contribution is required.

3.3 Right to Erasure - (Art. 32, para. 2, subpar. c, of the Data Protection Act)

3.3 Right to Erasure - (Art. 32, para. 2, subpar. c, of the Data Protection Act)

The data subject has the right to obtain from the data controller the erasure of personal data concerning him or her without undue delay, and the data controller is obligated to erase such personal data without undue delay if any of the following grounds apply:

  • the personal data is no longer necessary for the purposes for which it was collected or otherwise processed;

  • The data subject may withdraw the consent on which the processing is based if there is no other legal basis for the processing;

  • The data subject objects to the processing;

  • the personal data was processed unlawfully;

  • Personal data must be erased to comply with a legal obligation under applicable law to which the data controller is subject.


These are grounds derived from the GDPR 679/2016 but are equally valid under Swiss law.


Where the data controller has made personal data public and is required to erase it, taking into account the available technology and the costs of implementation, the data controller shall take reasonable measures, including technical measures, to inform the data controllers who are processing the personal data of the data subjectโ€™s request to remove any links, copies, or reproductions of his or her personal data.


A request for deletion may pertain to:

  • The rights that are processed by a data controller;

  • The rights associated with backup systems, archives, and the cloud;

  • Rights retained in digital, paper, or other formats;

  • Copies of the rights.


The law does not expressly specify a deadline for processing a request for erasure submitted by the data subject, but it is recommended to respond within the same timeframe established for processing requests regarding the right of access.


The foregoing provisions do not apply to the extent that the processing is necessary:

  • for the exercise of the right to freedom of expression and information;

  • for compliance with a legal obligation that requires the processing under the law of the Union or of the Member State to which the data controller is subject, or for the performance of a task carried out in the public interest or in the exercise of official authority vested in the data controller;

  • for reasons of public interest in the area of public safety;

  • for reasons of public interest, for historical or scientific research purposes, or for statistical purposes, since the applicable law may make it impossible or seriously impair the achievement of the objectives of such processing;

  • for the purpose of establishing, exercising, or defending a right in court.


Although these scenarios are expressly provided for in the GDPR, it is believed that they may also be applicable under Swiss law.


Exercising the right to erasure is free of charge, and no financial contribution is required.

3.4 Right to Restriction of Processing

3.4 Right to Restriction of Processing

This is a right that is not formally regulated in the LPD but applies in cases where the data subject who has exercised his or her right to object or to have data corrected makes such a request.


The data subject has the right to obtain from the data controller the restriction of processing when one of the following circumstances applies:


  • the data subject disputes the accuracy of the personal data, for the period necessary for the data controller to verify the accuracy of the personal data;

  • The data subject has objected to the processing, pending verification of whether the data controllerโ€™s legitimate grounds override those of the data subject.


The restriction on processing must be implemented as quickly as possible in order to protect the rights, interests, and privacy of the data subject.


This is because, if the restriction is not implemented promptly, the processing could be detrimental to the data subject.


Exercising the right to restriction is free of charge.

3.5 Right to Data Portability - (Art. 28 of the Data Protection Act)

3.5 Right to Data Portability - (Art. 28 of the Data Protection Act)

The data subject has the right to receive the personal data concerning him or her that has been provided to a data controller in a structured, commonly used, and machine-readable format, and has the right to transmit such data to another data controller without hindrance from the data controller to whom the data was provided, provided that:


  • The data controller processes personal data by automated means (Art. 28(1)(a) of the Data Protection Act), and therefore personal data processed on paper are excluded from the right to data portability;

  • The processing is carried out with the consent of the data subject or is directly related to the conclusion or performance of a contract between the data controller and the data subject (Art. 28(1)(B) of the Data Protection Act), thereby excluding from the right to data portability all processing operations based on the legitimate interests of the data controller or a third party, on the public interest, on a legal provision, or on the vital interests of the data subject;

  • The data must be information that the data subject has knowingly and intentionally made available to the data controller, or that the data controller has collected about the data subject and his or her behavior in connection with the use of a service or device (see Art. 20 of the OPDa);

  • The data in question must be personal data subject to the provisions of the LPD; therefore, anonymous personal data is excluded.


The data subject may also request that the data controller transfer the personal data concerning him or her to another data controller, provided that such transfer does not entail a disproportionate burden.


The data controller shall provide or transmit personal data free of charge. The Federal Council may provide for exceptions to this requirement, particularly if the provision or transmission of personal data would entail a disproportionate burden. The right to the provision or transmission of data does not oblige the data controller to adopt or maintain technically compatible data processing systems.


The burden is disproportionate if the transfer of personal data to another data controller is not possible for technical reasons (see Art. 21(3) of the OPDa).


When exercising their rights regarding data portability, the data subject has the right to obtain the direct transmission of personal data from one data controller to another, where technically feasible. The right to data portability does not affect the right to erasure. This right does not apply to processing necessary for the performance of a task carried out in the public interest or in the exercise of official authority vested in the data controller. The right to data portability does not infringe upon the rights and freedoms of others.


It is the Data Controllerโ€™s responsibility to assess the complexity of the response to the data subject and to determine the amount of any fee to be charged to the data subject pursuant to Article 19 of the OPDa (see โ€œExceptions to Free Accessโ€).


If providing the information involves a disproportionate burden, the data controller may require the data subject to contribute an appropriate portion of the costs. This contribution shall not exceed 300 francs.

3.6 Right to Object - (Art. 30, para. 2, subpara. B and 3 of the Data Protection Act)

3.6 Right to Object - (Art. 30, para. 2, subpara. B and 3 of the Data Protection Act)

The data subject has the right to object at any time to the processing of personal data concerning him or her if such data is processed in violation of the principles set forth in Articles 6 and 8 of the LPD, as well as if personal data is processed against the data subjectโ€™s express will. Article 30(3) of the LPD expressly provides that there is no infringement of privacy if the data subject has made their personal data accessible to anyone and has not expressly objected to the processing.


In response to such a request, the data controller shall refrain from further processing the personal data unless it demonstrates that the processing is lawful by invoking a legitimate ground.


The law does not expressly specify a deadline for processing an objection request submitted by the data subject, but it is recommended to respond within the same timeframe established for processing requests regarding the right of access.


Exercising the right to object is free of charge.

3.7. Right not to be subject to an automated individual decision - (Art. 21 of the Data Protection Act)

3.7. Right not to be subject to an automated individual decision - (Art. 21 of the Data Protection Act)

This refers to the data subjectโ€™s right to express their point of view regarding automated decisions and, in particular, the right to request that a human review the decision.


Specifically, the data controller shall inform the data subject of any decision based solely on automated processing of personal data that produces legal effects concerning the data subject or significantly affects him or her (automated individual decision) (Art. 21, para. 1).


The data controller shall, upon request, give the data subject the opportunity to express an opinion. If the data subject so requests, the automated individual decision must be reviewed by a natural person (Art. 21, para. 2).


Article 21, paragraphs 1 and 2, do not apply if:


  • the automated individual decision is directly related to the conclusion or performance of a contract between the data controller and the data subject, and the data subjectโ€™s request is granted;

  • The data subject has given his or her explicit consent to the decision being made by automated means.


If an automated individual decision is made by a federal agency, the agency shall designate it as such. Paragraph 2 does not apply in cases where, pursuant to Article 30, paragraph 2, of the Federal Act of December 20, 1968, on Administrative Procedure (PA) or another federal law, the federal agency is not required to hear the person concerned before making the decision.


Exercising this right is free of charge

3.8. Right to Notification - (Art. 31, No. 4, LPD)

3.8. Right to Notification - (Art. 31, No. 4, LPD)

The data controller shall notify each recipient to whom the personal data has been disclosed of any corrections (see Art. 32(4) of the Data Protection Act) or deletions that have been made

  1. Additional Information for Interested Parties in the European Union

  1. Additional Information for Interested Parties in the European Union

With regard to data subjects in the European Union, the rights recognized under the GDPR are set forth below:


Right of Access - (Art. 15 GDPR and Art. 12 GDPR)

European law imposes certain limitations on the exercise of the right of access, as outlined above, which are based on:


a) Article 12(5) of the GDPR, which states: โ€œThe information provided pursuant to Articles 13 and 14 and any communications and actions taken pursuant to Articles 15 through 22 and Article 34 shall be free of charge. If the data subjectโ€™s requests are manifestly unfounded or excessive, in particular because of their repetitive nature, the data controller may: (a) charge a reasonable fee, taking into account the administrative costs incurred in providing the information, communication, or taking the requested action; or (b) refuse to comply with the request. The burden of proving that the request is manifestly unfounded or excessive lies with the data controllerโ€;


(b) Article 23 of the GDPR, which states: โ€œThe law of the Union or of the Member State to which the controller or processor is subject may, by means of legislative measures, the scope of the obligations and rights set forth in Articles 12 through 22 and 34, as well as in Article 5, to the extent that the provisions contained therein correspond to the rights and obligations set forth in Articles 12 through 22, provided that such limitation respects the essence of fundamental rights and freedoms and is a necessary and proportionate measure in a democratic societyโ€;


(c) Article 89(2) of the GDPR: โ€œWhere personal data are processed for scientific or historical research purposes or for statistical purposes, Union or Member State law may provide for derogations from the rights referred to in Articles 15, 16, 18, and 21, subject to the conditions and safeguards set forth in paragraph 1 of this Article, to the extent that such rights are likely to render impossible or seriously impair the achievement of the specific purposes and such derogations are necessary for the achievement of those purposesโ€;


d) Article 89(3) of the GDPR: โ€œWhere personal data are processed for archiving purposes in the public interest, Union or Member State law may provide for derogations from the rights set forth in Articles 15, 16, 18, 19, 20, and 21, subject to the conditions and safeguards set forth in paragraph 1 of this Article, to the extent that such rights are likely to render impossible or seriously impair the achievement of the specific purposes and such exceptions are necessary for the achievement of those purposesโ€;


e) Article 85 of the GDPR: โ€œFor the purposes of processing carried out for journalistic purposes or for academic, artistic, or literary expression, Member States shall provide for exemptions or derogations from Titles II (Principles), III (Rights of the Data Subject), IV (Data Controller and Data Processor), V (Transfer of Personal Data to Third Countries or International Organizations), VI (independent supervisory authorities), VII (cooperation and consistency), and IX (specific data processing situations) where necessary to reconcile the right to the protection of personal data with the freedom of expression and information.โ€


The provisions of the GDPR stipulate that a response must be provided within one month of receiving the request and that this deadline may be extended by two months if the request is complex (Art. 13(3) GDPR). With specific regard to financial contributions, the GDPR does not set a maximum limit on such contributions but merely states that the data controller may charge a reasonable fee based on the administrative costs incurred in providing the information, communication, or taking the requested action (see Article 12(5) and Article 15(3) of the GDPR).


Rectification of Data - (Art. 16 of the GDPR)

The data subject has the right to obtain from the Data Controller the rectification of inaccurate personal data concerning him or her without undue delay, taking into account the purposes of the processing. The data subject has the right to have incomplete personal data completed, including by providing a supplementary statement. The provisions of the GDPR stipulate that a response must be provided within one month of receiving the request and that this period may be extended by two months if the request is complex (Art. 13(3) GDPR). Exercising the right to rectification is free of charge and may involve a contribution from the data subject based on the administrative costs incurred in taking the requested action or providing the necessary communications.


Right to Erasure - (Art. 17 of the GDPR)

The data subject has the right to obtain from the data controller the erasure of personal data concerning him or her without undue delay, and the data controller is obligated to erase such personal data without undue delay if any of the following grounds apply:


a) the personal data are no longer necessary in relation to the purposes for which they were collected or otherwise processed;


b) the data subject withdraws the consent on which the processing is based, if there is no other legal basis for the processing (The data subject has the right to withdraw consent if: โ€ข the data subject has given consent to the processing of his or her personal data for one or more specific purposes; or โ€ข the personal data reveals racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, or involves the processing of genetic data, biometric data for the purpose of uniquely identifying a natural person, health data, or data concerning the data subjectโ€™s sex life or sexual orientation: the data subject has given explicit consent to the processing of such personal data for one or more specific purposes, except where Union or Member State law provides that the prohibition on the processing of special categories of personal data cannot be withdrawn by the data subject);


c) the data subject objects to the processing;


d) the personal data has been processed unlawfully;


e) personal data must be erased to comply with a legal obligation under European Union law or the law of the Member State to which the data controller is subject;


f) A parent may request the deletion of the personal data of a minor child or a child over whom the parent exercises parental authority.


Where the data controller has made personal data public and is required to erase it, taking into account the available technology and the costs of implementation, it shall take reasonable measures, including technical measures, to inform other data controllers processing the personal data of the data subjectโ€™s request to remove any links, copies, or reproductions of their personal data. The provisions of the GDPR stipulate that a response must be provided within one month of receiving the request and that this period may be extended by two months if the request is complex (Art. 13(3) GDPR). The right to erasure, pursuant to Art. 17(3) GDPR, is subject to restrictions in cases where processing is necessary:


a) for the exercise of the right to freedom of expression and information;


b) for compliance with a legal obligation that requires the processing under the law of the Union or of the Member State to which the data controller is subject, or for the performance of a task carried out in the public interest or in the exercise of official authority vested in the data controller;


c) for reasons of public interest in the area of public safety;


d) for reasons of public interest, for historical or scientific research purposes, or for statistical purposes, where the applicable law is likely to make it impossible or seriously impair the achievement of the objectives of such processing;


e) for the establishment, exercise, or defense of a right in court


Exercising the right to erasure is free of charge and may involve a contribution from the data subject based on the administrative costs incurred in taking the requested action or providing the necessary communications.


Right to Restriction of Processing - (Art. 18 of the GDPR)

The data subject has the right to obtain from the data controller the restriction of processing when one of the following circumstances applies:


a) the data subject disputes the accuracy of the personal data, for the period necessary for the data controller to verify the accuracy of the personal data;


b) the processing is unlawful, and the data subject objects to the erasure of the personal data and requests, instead, that its use be restricted;


c) although the Data Controller no longer needs the personal data for the purposes of processing, the data is necessary for the data subject to establish, exercise, or defend a legal claim;


d) the data subject has objected to the processing, pending verification of whether the legitimate grounds of the data controller override those of the data subject.


If processing is restricted, these rights may be exercised only if the data subject has given consent, the processing is necessary to establish, exercise, or defend legal claims, to protect a natural or legal person, or for reasons of substantial public interest in the Union or in a Member State. Exercising the right to restriction is free of charge and may entail a contribution from the data subject based on the administrative costs incurred in taking the requested action or providing the notification.


Right to Data Portability - (Art. 20 of the GDPR)

The data subject has the right to receive the personal data concerning him or her that has been provided to a data controller in a structured, commonly used, and machine-readable format, and has the right to transmit such data to another data controller without hindrance from the data controller to whom the data was provided, provided that:


  • The treatment is based on:

    • the data subjectโ€™s consent to the processing of their personal data for one or more specific purposes;

    • the data subjectโ€™s specific consent to the processing of personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, and to the processing of genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health, or data concerning a natural personโ€™s sex life or sexual orientation;

    • a processing agreement necessary for the performance of a contract to which the data subject is a party or to take steps at the data subjectโ€™s request prior to entering into a contract;

  • the processing is carried out by automated means.


When exercising their rights regarding data portability, the data subject has the right to obtain the direct transmission of personal data from one data controller to another, where technically feasible. The right to data portability does not affect the right to erasure. This right does not apply to processing necessary for the performance of a task carried out in the public interest or in the exercise of official authority vested in the data controller. The right to data portability does not infringe upon the rights and freedoms of others. The exercise of the right to restriction is free of charge and may entail a contribution from the data subject based on the administrative costs incurred in taking the requested action or providing the requested communication.


Right to Object (Art. 21 of the GDPR)

The data subject has the right to object at any time, on grounds relating to his or her particular situation, to the processing of personal data concerning him or her, including profiling based on such provisions. In particular, the data subject may exercise the right to object


a) for reasons related to his or her particular circumstances;


b) if the processing is based on the legal basis of legitimate interests or the public interest;


c) if the processing is carried out for scientific, historical, or statistical research purposes.


The Data Controller shall refrain from further processing personal data unless it demonstrates compelling legitimate grounds for the processing that override the interests, rights, and freedoms of the data subject, or where the processing is necessary for the establishment, exercise, or defense of legal claims (see Art. 21, paras. 2 and 3 of the GDPR). Where personal data are processed for direct marketing purposes, the data subject has the right to object at any time to the processing of personal data concerning him or her carried out for such purposes, including profiling to the extent that it is related to such direct marketing. If the data subject objects to processing for direct marketing purposes, the personal data shall no longer be processed for such purposes. The right to object is explicitly brought to the data subjectโ€™s attention and is presented clearly and separately from any other information. In the context of using information society services, the data subject may exercise his or her right to object through automated means that use specific technical measures. Where personal data are processed for scientific or historical research purposes or for statistical purposes, the data subject has the right, on grounds relating to his or her particular situation, to object to the processing of personal data concerning him or her, unless the processing is necessary for the performance of a task carried out in the public interest. The provisions of the GDPR stipulate that a response must be provided within one month of receiving the request and that this period may be extended by two months if the request is complex (Art. 13(3) GDPR). With specific regard to financial contributions, the provisions of the GDPR do not set a maximum limit on such contributions but merely state that the data controller may charge a reasonable fee based on the administrative costs incurred in providing the information, communication, or taking the requested action (see Art. 12(5) GDPR and Art. 15(3) GDPR).


Right not to be subject to an automated individual decision (Art. 22 of the GDPR)

This refers to the data subjectโ€™s right not to be subject to an automated decision, including profiling, that produces legal effects concerning the data subject or that significantly affects the data subject. The data subject may be subject to an automated decision if:


a) is necessary for the conclusion or performance of a contract between the data subject and a data controller;


b) is authorized under the law of the European Union or of the Member State to which the data controller is subject, which also specifies appropriate measures to protect the rights, freedoms, and legitimate interests of the data subject;


c) is based on the explicit consent of the data subject. In the cases referred to in subparagraphs (a) and (c), the data subject has the right to request human intervention by the data controller and to express his or her opinion, challenging the decision.


With specific regard to financial contributions, the provisions of the GDPR do not set a maximum limit on such contributions but merely state that the data controller may charge a reasonable fee based on the administrative costs incurred in providing the information or communication or in taking the requested action (see Art. 12(5) and Art. 15(3) of the GDPR).


Right to Notification - (Art. 19 of the GDPR)

The Data Controller shall notify each recipient to whom personal data have been disclosed of any rectifications, erasures, or restrictions on processing carried out in accordance with Article 16, Article 17(1), and Article 18 of the GDPR 679/2016, unless this proves impossible or involves a disproportionate effort. The Data Controller shall inform the data subject of such recipients if the data subject so requests.

  1. Roles

  1. Roles

The following are the roles and responsibilities involved in the process of handling requests from data subjects:


Designated Person: This is the individual identified by the Data Controller who is responsible for receiving, managing, and processing requests from data subjects regarding the exercise of their rights under the LPD, the OPDa โ€“ August 31, 2022, and the GDPR. This individual is the same as the Privacy Contact appointed by the Data Controller.


Data controller: the natural or legal person, public authority, agency, or other body that, alone or jointly with others, determines the purposes and means of the processing of personal data (see Art. 5 of the LPD and Art. 4 of the GDPR). In this context, the data controller is WellD Sagl;


Authorized/Designated Data Processor: the natural person who has been expressly designated to act under the authority of the Data Controller and who performs specific tasks and functions related to the processing of personal data;


Data Processor: the natural or legal person, public authority, agency, or other body that processes personal data on behalf of the Data Controller (Art. 9 of the LPD and Art. 28 of the GDPR);


Privacy Contact: the individual (directly or indirectly) affiliated with the Company who is operationally responsible for the privacy policy and, specifically, proposes the drafting of privacy and data processing regulations, and conducts and evaluates compliance checks on them;


Data Protection Officer (DPO): the natural person designated as the Data Protection Officer pursuant to the LPD (Art. 10) and the GDPR (Art. 37).


Federal Data Protection and Information Commissioner (FDPIC): the independent supervisory authority in Switzerland responsible for matters related to the protection of personal data, which may conduct investigations and, in the event of a violation of data protection regulations, recommend that certain data processing activities be modified or discontinued.

  1. Applicants

The request may be submitted:

  • directly from the individual concerned;

  • by another individual or organization to which the data subject has granted written authorization or power of attorney (in which case it is necessary to review the relevant power of attorney or authorization, as well as a copy of the signatoryโ€™s identification document);

  • by those exercising parental authority, legal guardianship, or custody over minors and incapacitated persons;

  • heirs of the deceased individual who have an interest in accessing the information that is deemed to outweigh the interests of any third parties.


In general, a request to exercise the aforementioned rights must pertain to information concerning the data subject and not to data relating to third parties.

  1. Workflow for handling requests related to the exercise of data subjectsโ€™ rights

This section describes the procedures established by the Data Controller to ensure that data subjects can exercise their rights.

7.1 Request and Receipt of the Request

7.1 Request and Receipt of the Request

As indicated in the privacy notices provided to data subjects, requests may be submitted in writing to the contacts specified by the Data Controller via email (to the dedicated privacy email address privacy@welld.ch) or by mail.


The request may be sufficiently specific (e.g., regarding access, rectification, erasure, restriction, or objection to specific personal data) or general (regarding access, erasure, or portability of all personal data processed) and need not contain a specific reference to a legal provision.


The request may also be submitted using the designated form titled โ€œForm for the Exercise of Rights by the Data Subject,โ€ which is made available by the Company and will be published on its website at www.welld.ch.


Upon receipt of a request from a data subject, the Designated Officer must immediately process the request and notify the data subject that it has been received by the data controller.


If the request is sent to a contact other than the one listed in the privacy notice, the authorized person who receives the request must report it immediatelyโ€”and in any case within 24 hoursโ€”to the Data Protection Officer by sending an email containing all the materials received in the request. Upon receiving the request, the Data Protection Officer must notify the data subject that the request has been โ€œacknowledged.โ€

7.2 Processing the Request

7.2 Processing the Request

In order to properly handle a request by the data subject to exercise one of the rights provided for by law, the Data Controller must, if deemed appropriate, also involve any external data processors.


Following an analysis of the request received from the data subject, the request may be classified as:


  • Accepted:In this case, the request is legitimate, the information and supporting documentation provided are clear and complete, and the requester has been identified. It is therefore possible to proceed with processing the request.

  • Pending due to missing information: The request is valid, but the information and documentation provided in support of the request are incomplete and/or unclear, or the individual has not clearly identified themselves (e.g., the identification document of the data subject or the requester, or the power of attorney granted to the requester, as well as documentation attesting to parental or other forms of responsibility, has not been attached). The request cannot be processed immediately and is therefore suspended for the time necessary to obtain the additional information.

  • Rejected:The request does not meet the minimum requirements to be considered valid and is therefore rejected.

7.3 Request Management and Processing

7.3 Request Management and Processing

The Companyโ€™s handling and processing of the request is carried out by the Designated Officer, who:


  • Verify that the request pertains exclusively to personal data. Unlike anonymous data (which is not personal data), pseudonymized dataโ€”which could be attributed to a natural person through the use of additional informationโ€”constitutes personal data. Consequently, pseudonymized data that can be linked to a data subjectโ€”for example, when the data subject provides an identifier that allows for their identification, or when the data controller is able to link the data using its own resourcesโ€”must be considered to fall within the scope of the request;

  • Using appropriate methods, and taking into account the principle of โ€œdata minimization,โ€ verify the applicantโ€™s identity and the completeness of the request. In the case of a request made by a third party acting on behalf of the data subject, the third party must also present a power of attorney signed by the data subject or, alternatively, documentation attesting to parental or other legal authority. If the data subject has previously created an online account, the data controller may ask the data subject to authenticate themselves by logging into the account, or ask (non-intrusive) security questions that only the data subject would be able to answer, or use multi-factor authenticationโ€”all of which were configured when the data subject registered their accountโ€”or use other existing means of communication known to belong to the data subject, such as an email address or phone number, to send a login password;

  • search databases and/or physical archives for the presence and type of personal dataand the information necessary to effectively fulfill the right that has been exercised. To this end, it may consult the various departments/services directly or indirectly involved in the processing of personal data (e.g., the IT Department) or the data processors it engages;

    reviews the personal data collected and stored by the various internal and/or external departments;

  • assesses the appropriateness and admissibility of the request;

  • Report any issues to the Data Controller identified in the course of carrying out activities;


If the Designated Person is unable to independently handle or process the access request submitted by the data subject (for example, because a right other than those listed has been exercised), the Designated Person must notify the CPD-DPO, if appointed, or, in the absence of a CPD-DPO, the Data Controller, in order to determine how to process the request.


Once the necessary information has been gathered, the Data Protection Officer shall, without undue delay and no later than one month after receiving the request, provide a detailed response setting forth the outcome of the procedure, which will vary depending on the right exercised by the data subject (as specified in the table below).

7.4. Request Processing Times

7.4. Request Processing Times

Following an assessment of the request received from the data subject, which has been classified as actionable (including after receiving additional information), the Data Controller will provide the data subject with the information requested without undue delay and, at the latest, within 30 days of receiving the request.


This deadline may be extended by two months, if necessary, taking into account the complexity and number of requests.


In any case, the Data Controller shall inform the data subject of such an extension and the reasons for the delay within one month of receiving the request.

7.5. Procedures and Costs for Processing the Request

7.5. Procedures and Costs for Processing the Request

The verification must take place:

  • in writing, including by electronic means, if the request was made by such means;

  • in a concise, transparent, and understandable manner, using simple and clear language;

  • free of charge. Therefore, the Data Controller must comply with requests for information without charging the data subject any fees. If providing the information involves a disproportionate burden, the Data Controller may request that the data subject contribute appropriately to the costs, as further detailed in points 3 and 4 with respect to each individual right that may be exercised.


With specific reference to the right of access and the right to data portability, it is the responsibility of the Data Controller to assess the complexity of the response to the data subject and to determine the amount of any fee to be charged to the data subject pursuant to Article 19 of the OPDa (see Exceptions to Free Access). If providing the information entails a disproportionate burden, the Data Controller may require the data subject to contribute appropriately toward the costs. This contribution shall not exceed 300 francs. In such a case, the data controller shall inform the data subject of the amount of the contribution before the information is provided. If the data subject does not confirm the request within ten days, the request is deemed withdrawn without incurring any costs. The 30-day deadline for processing the data subjectโ€™s request begins at the end of the ten-day reflection period;


  • The data controller may not refuse to comply with a data subjectโ€™s request to exercise their rights, except in cases where the data subject cannot be identified, where the request(s) are manifestly unfounded or excessive (for example, due to their repetitive nature), or in the additional specific cases identified in point 3.

  • an automated process for managing access requests, which allows data subjects to access their personal data from their user account. To retrieve their personal data, users can select the โ€œDownload Your Personal Dataโ€ option after logging into their user account. This self-service option allows users to download a file containing their personal data directly from their user account to their computer;

  • Only data pertaining to the data subject who made the request shall be disclosed, and not data pertaining to other individuals, in order to avoid infringing on the rights and freedoms of others;

  • With regard to the minimum content of the response, particularly concerning the right of access, the response must include the following information: the identity and contact information of the data controller; the personal data being processed; the purpose of the processing; the retention period for the personal data or, if this is not possible, the criteria for determining that period; information available regarding the source of personal data that was not collected directly from the data subject; where applicable, the existence of an automated individual decision and the logic on which the decision is based; where applicable, the recipients or categories of recipients to whom personal data are disclosed, as well as the information referred to in Article 19, paragraph 4 of the FADP (processor, e.g., cloud provider).

7.6. Summary Table of Request Management and Processing

7.6. Summary Table of Request Management and Processing

The following outlines, depending on the right being exercised and subject to specific exceptions provided for by applicable privacy laws, the guidelines that the designated individual may follow when processing the request

Right to Restriction

Definition
Request Management
Request Rejected
The right to restrict processing allows the data subject to mark the personal data that is stored in order to restrict its processing in the future.Verify whether or not the data subjectโ€™s personal data is being processed; โ€ข Verify whether the conditions necessary to request restriction of processing are met: a) the data subject contests the accuracy of the personal data, for the period necessary for the Data Controller to verify the accuracy of such personal data; b) the data subject has objected to the processing pending verification of whether the Data Controllerโ€™s legitimate grounds override those of the data subject. โ€ข Notify and flag the processing operations subject to restriction to the relevant internal departments/functions and/or Data Processors, stating that the only permitted type of processing is the retention of personal dataIf possible: โ€ข Notify the data subject of the outcome of the request for restriction, detailing the actions taken and indicating the cases in which it will still be possible to process the restricted dataโ€”namely, โ€œfor storage, only with the data subjectโ€™s consent, or for the establishment, exercise, or defense of a legal claim.โ€ โ€ข Notify the recipients of the request for restriction, unless this is impossible or would involve a disproportionate effort โ€ข Provide the data subject (upon request) with the names of the recipients to whom the requests for restriction have been forwarded; if this is impossible, inform the data subject of the results of the assessment conducted and the reasons for non-compliance; if no processing is taking place, inform the data subject that no processing of personal data concerning them is currently underway

Right to Data Portability

Definition
Request Management
Request Rejected
The right to data portability allows the data subject to reuse their personal dataโ€”which has already been processed by the data controllerโ€”by requesting that it be returned or that it be transferred to another data controller.Verify whether or not the data subjectโ€™s personal data is being processed; โ€ข Verify that the following conditions are met: a) the data controller processes personal data by automated means; and b) the processing is carried out with the data subjectโ€™s consent or is directly related to the conclusion or performance of a contract between the data controller and the data subject. โ€ข Verify that it is technically possible to transfer the personal data from one data controller to another.If possible: โ€ข The data controller shall provide the data subject with their personal data in a structured, commonly used, and machine-readable format. The communication must specify that the right to data portability does not preclude the independent right to erasure; or โ€ข Transmit the personal data to another data controller, upon the data subjectโ€™s instruction, if technically feasible; if this is not possible, inform the data subject of the results of the assessment conducted and the reasons for non-compliance; if no processing is taking place, inform the data subject that no processing of personal data concerning them is currently underway

Right to Object

Definition
Request Management
Request Rejected
The right to object allows the data subject to object at any time, on grounds related to his or her particular situation, to the processing of personal data concerning him or herVerify whether or not the data subjectโ€™s personal data is being processed; โ€ข Verify whether a specific situation applies to the data subject; โ€ข Verify whether any of the following conditions apply: a) the processing is necessary for the performance of tasks carried out in the public interest or in the exercise of official authority, including profiling; b) the processing is necessary for a legitimate interest of the Data Controller.If possible, inform the data subject of the outcome of the findings, detailing the actions taken. If this is not possible, inform the data subject of the results of the assessment conducted and the reasons for non-compliance. To this end, it should be noted that a request for objection may be denied: - if there are legitimate, compelling reasons that take precedence over the exercise of the right; - for the exercise of rights in court; - for the performance of a task in the public interest. If no processing is taking place, the data controller shall inform the data subject that no processing of personal data concerning him or her is currently underway.

7.7 Case Studies Regarding the Right of Access and Recommendations for Handling Such Requests โ€“ EDPB Guidelines 1/2022 on Data Subjectsโ€™ Rights โ€“ Right of Access.

7.7 Case Studies Regarding the Right of Access and Recommendations for Handling Such Requests โ€“ EDPB Guidelines 1/2022 on Data Subjectsโ€™ Rights โ€“ Right of Access.

Example 1: An employer terminated an employee. A week later, the employee decided to gather evidence in order to file a lawsuit against the former employer for wrongful termination. To that end, the employee wrote to the former employer requesting access to all personal data concerning him or her, as the data subject; data that the former employer processes in its capacity as the data controller. The data controller does not assess the data subjectโ€™s intentions, and the data subject is not required to disclose the reason for the request to the data controller. Therefore, if the request meets all other requirements, the data controller must comply with it, unless the request is manifestly unfounded or excessiveโ€”a circumstance that the data controller is required to demonstrate.


Example 2: The data subject exercises the right of access with respect to personal data concerning him or her during the legal proceedings. National law governing the employment relationship between the data controller and the data subject may contain provisions that limit the scope of information to be provided or exchanged between the parties to ongoing or potential legal proceedings, and these provisions apply to the legal action for wrongful termination brought by the data subject. In this context, the data subject is not entitled to obtain more information from the data controller than is provided for under the provisions of national law governing the exchange of information between the parties to a legal dispute.


Example 3: A customer submits a request for access to a commercial company. One year after the companyโ€™s response, the same customer submits another request for access to the same company. Regardless of whether there have been new business transactions or other contacts between the parties since the previous request, this second request must be considered a new request. Even if there have been no changes in the companyโ€™s processing of the dataโ€”which is not necessarily apparent to the data subjectโ€”the data subject has the right to receive a free copy of the data.


Example 4: Even if the customer in question in the preceding cases submits the new requestโ€”for example, only one week after the first oneโ€”it may be considered a new request if it is not interpreted as a mere follow-up to the first request. The determination of whether the request is excessive depends on the brevity of the interval and the specific circumstances of the new request.


Example 5: A request for a โ€œnew copyโ€ of information already provided in the form of a copy in response to a previous requestโ€”for example, if the customer has lost the copy previously receivedโ€”should normally be considered a request for an additional copy, since it relates, in terms of the scope and duration of the processing, to the previous request


Example 6: A public authority processes data concerning the data subject across different departments in various contexts. The management and storage of files are carried out in part using non-automated means, and a large portion of the data is stored solely in paper files. With regard to the general wording of the request, the public authority doubts that the data subject is aware of the scope of the request itself, and in particular of the variety of processing operations it would entail, the amount of information, and the number of pages the data subject would receive. If the data controller decides to ask the data subject to clarify the request in order to fulfill its obligation to facilitate the exercise of the right of access, the data controller shall, at the same time, provide meaningful information about the processing operations that may concern the data subject, informing the data subject about the relevant areas of its activities, databases, etc.


Example 7: A large insurance company receives a letter containing a general request for access from a person who has been a customer for many years. Although the deletion terms are fully complied with, the company does in fact process a significant amount of data concerning the customer, since the processing is still necessary to fulfill contractual obligations arising from the contractual relationship with the customer (including, for example, ongoing obligations, communications regarding disputed issues with the customer and third partiesโ€ฆ) or legal obligations (archived data that must be retained for tax purposes, etc.). The insurance company might doubt whether the request, which is phrased in very general terms, truly intends to include all these types of data. This could prove particularly problematic if the insurance company only has the data subjectโ€™s mailing address and must therefore send the information in paper form. However, the same concerns may also arise when information is communicated by other means. If the data controller decides to ask the data subject to clarify the request in order to fulfill its obligation to facilitate the exercise of the right of access, the data controller shall, at the same time, provide meaningful information about the processing operations that may concern the data subject, informing the data subject about the relevant areas of its activities, databases, and so on.


Example 8: In an employment relationship, when an access request is phrased in general terms, it is not clear on its own that the employee wishes to receive all user login credentials, data regarding access to a workplace, data related to payments made in the cafeteria, data on salary payments, and so on. A request for clarification from the employer could, for example, make it clear that the employee is interested in understanding or verifying to whom their performance evaluation was sent. Without such a request for clarification, the employee would receive a significant amount of information, much of which would be of no interest to them. At the same time, the employer should provide information on the various processing contexts that may concern the employee, to enable the employee to refine the request in a rational manner.


Example 9: While processing a request for access, a data controller discovers that an application submitted by the data subject in connection with a job opening at the data controllerโ€™s company has been retained beyond the retention period. In such a case, the data controller may not delete the data and then inform the data subject that no data (regarding the application) has been processed. The data controller must first grant the data subject access and only then delete the data. To avoid a subsequent request for erasure, it is recommended to include information regarding the circumstances and the timing of the erasure.


Example 10: The data subject, X, works as a department manager for a company that provides parking spaces to its executives in the companyโ€™s own parking lot. Although X has a permanent parking space, when he arrives at the company for the second shift, he often finds his space already occupied by another car. Since this situation occurs repeatedly, in order to identify the driver who is occupying his space without authorization, X asks the data controller of the video surveillance system responsible for the company parking lot for access to that driverโ€™s personal data. In this case, Xโ€™s request is not a request for access to his own personal data, as it does not concern the requesterโ€™s data but rather the data of another person; therefore, it should not be considered a request related to the exercise of the right of access.


Example 11: Data controller X lists two email addresses both on its website and in its privacy policy: its general email address (CONTACT@X.COM) and the email address of the data controllerโ€™s data protection contact (QUERIES@X.COM). Data Controller X also states on its website that, to ask any questions or submit a request regarding the processing of personal data, individuals should contact the data protection contact points at the email address provided. However, the data subject sends a request to the data controllerโ€™s general email address: CONTACT@X.COM-. In this case, the data controller should make every reasonable effort to notify its departments of the requestโ€”which was submitted via the general email addressโ€”in order to forward it to the data protection contact point and respond to it within the specified time limits. Furthermore, the data controller does not have the right to extend the timeframe for responding to a request simply because the data subject sent the request to the data controllerโ€™s general email address rather than to that of the data controllerโ€™s data protection contact point.


Example 12: Data controller Y, which operates a network of fitness centers, informs the fitness centerโ€™s customers on its website and in its privacy policy that, to ask any questions or submit a request regarding the processing of personal data, they must contact the data controller using the email address QUERIES@Y.COM. However, the data subject sends his request to an email address found in the locker room, where a notice read: โ€œIf you are not satisfied with the cleanliness of the facilities, please contact us at CLEANERS@Y.COM,โ€ which is the email address of Yโ€™s cleaning staff. Obviously, the cleaning staff does not handle matters related to the exercise of rights by data subjects who are customers of the fitness center. Although the email address was posted on the fitness centerโ€™s premises, the data subject could not reasonably have expected it to be an appropriate contact address for such requests, since the website and the privacy policy clearly specified the communication channel to be used for exercising data subjectsโ€™ rights.


Example 13: X is the data controller for personal data processed in connection with video surveillance of a building. The data controller is not required to identify all individuals captured on video by a security camera as part of the monitoring (a purpose that does not require identification). The data controller receives a request for access to personal data from an individual who claims to have been captured on video by the data controllerโ€™s video surveillance system. The data controllerโ€™s actions will depend on the additional information provided. If the requester specifies a precise date and time when the cameras may have recorded the event in question, the data controller will likely be able to provide that information. However, if the data controller is unable to identify the data subject (for example, if it is impossible for the data controller to be certain that the requester is in fact the data subject, or if the request concerns a long period of recorded footage and the data controller is unable to process such a large volume of data), the data controller may refuse to comply with the data subjectโ€™s request if it demonstrates that it is unable to identify the data subject.


Example 14: A data subject, Ms. X, requests access to her data during a phone conversation with a representative of an electric utility company with which she has a contract. The representative has doubts about the identity of the person making the request and therefore generates, within the companyโ€™s system, a unique one-time code that is sent to the userโ€™s cell phone numberโ€”provided at the time the account was createdโ€”as part of the two-factor authentication process; in this case, this action should be considered proportionate.


Example 15: The user, Ms. Y, created a password-protected account on an online store by providing her email address and/or username. Subsequently, the account holder asked the data controller to inform her whether it was processing her personal data; if so, she requested access to that data. The data controller requests the applicantโ€™s identification document to verify her identity. In this case, the data controllerโ€™s action is disproportionate and results in unnecessary data collection. To verify the applicantโ€™s identity while avoiding unnecessary data collection, the data controller could ask her to authenticate herself by logging into her account, or ask her (non-intrusive) security questions that only she would be able to answer, or use multi-factor authenticationโ€”all of which were configured when she registered her accountโ€”or use other existing means of communication known to belong to her, such as her email address or phone number, to send a login password.


Example 16: a person has a job interview with a company. In this context, the applicant submits a CV and a cover letter. During the interview, the HR manager takes notes on the computer to document the interview. Later, the applicant, as the data subject, asks to access the personal data concerning them that the company, as the data controller, collected during the selection process. The data controller must provide the data subject with the personal data they actively provided in the CV and cover letter. The data controller must also provide the data subject with a summary of the interview, including the subjective observations on the data subjectโ€™s behavior that the HR manager noted during the job interview, subject to any exemptions provided for by national law.


Example 17: The factors used to make decisionsโ€”for example, regarding an employeeโ€™s promotion, pay raise, or new assignment (annual performance reviews, training requests, disciplinary history, professional level, career potential)โ€”are personal data concerning that employee. The data subject may therefore access this information upon request and in accordance with the principles governing the exercise of the right of access; however, if the personal data also pertains to another person (for example, the identity or information revealing the identity of another employee whose assessment of professional performance is included in the annual performance review), such information may be subject to restrictions and may not be disclosed to the data subject in order to protect the rights and freedoms of that employee..


Example 18: A company processed personal data relating to a data subject in order to fulfill a purchase order and arrange for shipment to the data subjectโ€™s home address. When these initial purposes, for which the personal data were collected, no longer exist, the data controller retains certain personal data solely to comply with certain legal obligations regarding record-keeping. The data subject requests access to the personal data concerning him or her. To fulfill this obligation, the data controller must provide the data subject with the requested personal data that it has retained in compliance with its legal obligations.


Esempio 19: The data controller appoints an administrator to handle the practical matters related to access requests. When the administrator receives a request, he or she sends an inquiry via email to the various departments within the organization, asking them to collect the personal data pertaining to the data subject. Representatives from each department forward the personal data processed by their respective departments to the administrator. The administrator then sends all the personal data to the data subject along with any necessary additional information, for example, via email, if applicable.


Example 20: A social media service has an automated process for handling access requests, which allows data subjects to access their personal data from their user account. To retrieve their personal data, social media users can select the โ€œDownload Your Personal Dataโ€ option after logging into their user account. This self-service option allows users to download a file containing their personal data directly from their user account to their computer.


Example 21: A social media provider processes a large amount of information relating to a data subject. Much of this personal data consists of information contained in hundreds of pages of log files, which record the data subjectโ€™s activities on the website. If the data subject requests access to their personal data, the personal data contained in these log files does indeed fall within the scope of the right of access. The right of access would therefore be formally satisfied by providing the data subject with these hundreds of pages of log files. However, without measures to facilitate understanding of the information contained in the log files, the data subjectโ€™s right of access would not be satisfied in practice, since no meaningful insights can be easily derived from the log files. The data controller must therefore exercise meticulous care in choosing how information and personal data are presented to the data subject.


Example 22: An e-commerce website collects data on items viewed or purchased on the site for marketing purposes. Some of this data consists of unanalyzed data that may have no direct meaning for the reader (codes, activity logs, etc.). Such data relating to the data subjectโ€™s activities also fall within the scope of the right of access and should therefore be provided to the data subject in response to a request for access. If the data is provided in raw format, it is important that the data controller take the necessary measures to ensure that the data subject understands the data, for example by providing an explanatory document that translates the raw format into a form that is easily understandable to the user. In addition, this document could explain the meaning of abbreviations and other acronyms: for example, โ€œAโ€ means that the purchase was interrupted, while โ€œBโ€ means that the purchase was successful.


Example 23: A data controller analyzes large datasets to categorize customers into different segments based on their online behavior. In such a situation, it can be assumed that the most important information for the data subjects is that concerning the segment to which they have been assigned. Consequently, this information should be included in the first layer. Raw data that has not yet been analyzed or further processedโ€”such as a userโ€™s activity on a websiteโ€”is also personal data that falls within the scope of the right of access; in some cases, however, it may be sufficient to provide this information in a different layer.


Example 24: A social media platform whose primary activity consists of collecting and/or processing the personal data of data subjects carries out complex and ongoing processing activities on a large scale. A data subject who uses the platformโ€™s services submits access requests every three months. In this case, frequent changes to the data subjectโ€™s personal data are highly likely (first point above); the wide range of data collected includes sensitive inferential personal data (second point above) processed for the purpose of showing the data subject relevant content and network members (third point). Under these circumstances, access requests submitted every three months cannot, in principle, be considered excessive due to their repetitive nature.

  1. Record of Requests and Retention of Documentation

The entire management process must be documented by completing the following document, โ€œRegister of Data Subjectsโ€™ Requests,โ€ which must include the following details:


  • Sequential number;

  • Date of request;

  • Date received, if different;

  • Method of communication (email, certified email, certified mail);

  • Name of the data subject;

  • Type of request;

  • Status and notes;

  • Date response was sent to the data subject;

  • Closure date;

  • Notes;


Finally, the Designated Person must retain all documentation related to the handling of the case (the data subjectโ€™s request, various communications exchanged among individuals within the Company regarding the processing of the data subjectโ€™s request, and the response provided to the data subject).

9. Checks

9. Checks

If the data is processed by one or more data processors, the data controller must set forth in a contract the procedures for ensuring that appropriate technical and organizational measures are in place to respond to requests to exercise the data subjectโ€™s rights.

10. Penalties

10. Penalties

In accordance with current privacy laws, a violation of the rights of data subjects constitutes a serious violation, for which penalties of up to 250,000 francs may be imposed. Specifically, pursuant to Article 60 of the Data Protection Act (LPD), private individuals who, upon complaint by an affected party, are subject to a fine of up to 250,000 francs if they: a) Violate the obligations set forth in Articles 19 (notification), 21 (automated decisions), and 25โ€“27 (access) by intentionally providing inaccurate or incomplete information; b) Intentionally fail to: 1) inform the data subject about the collection of data (Art. 19, para. 1) and about automated decisions (Art. 21, para. 1); or 2) provide information regarding the rights of data subjects (Art. 19, para. 2).


Effective Date: January 1, 2026