Skip to content

Privacy Policy

Last updated: October 14, 2026

This privacy policy is provided pursuant to Art. 13 of Regulation (EU) 2016/679 (hereinafter "GDPR") and describes how personal data collected through the website www.operalife.eu and its subdomains (hereinafter the "Website"), and through the email addresses published by the Data Controller, is processed. We invite you to read this document carefully before providing any personal data.

1. Data Controller

The Data Controller is OPERA S.r.l., with registered office at Via Aretina 155/1, 50136 Firenze (FI), Italy — VAT and Tax Code: 07502760486 — REA: FI-707988 — Certified email (PEC): operalife@pecaruba.it — Email for privacy matters: privacy@operalife.eu.

For any question regarding the protection of personal data, you may contact the Data Controller at privacy@operalife.eu. As of the last update, the Data Controller has not appointed a Data Protection Officer (DPO).

2. Types of Data Collected

Through the Website and the published email addresses, the Data Controller processes the following categories of personal data:

Data provided through the contact form

By filling in the contact form on the Website, you voluntarily provide the following data: name, email address, organization (optional), and message text. Submitting the form also records confirmation that you have reviewed this privacy policy.

Providing your name, email address and message text is necessary to allow the Data Controller to respond to your inquiry: without them the form cannot be submitted. Providing your organization is optional and its omission has no consequence. Ticking the box confirming that you have reviewed this privacy policy is likewise required in order to submit, and serves solely to document that the policy was made available to you.

Email communications

The Website publishes certain contact email addresses. By writing directly to these addresses, you provide the Data Controller with your email address and any data contained in your message. Such data is processed for the same purposes and on the same legal bases as inquiries submitted through the contact form, and is retained for the period set out in section 6. Unsolicited job applications are governed by the following paragraph.

Unsolicited job applications

If you send an unsolicited application to one of the email addresses published by the Data Controller, the Data Controller processes the data contained in your message and in your curriculum vitae — typically identification and contact details, education, professional experience and any other information you choose to include — solely in order to assess the application and, where appropriate, to contact you with a view to possibly entering into an employment or collaboration relationship. The Website has no dedicated application form and does not allow files to be uploaded; this paragraph nevertheless applies to any application sent through the contact form, without prejudice to what section 4 says about the delivery of contact form messages. Pursuant to Art. 111-bis of Italian Legislative Decree 196/2003, within the limits of the purposes referred to in Art. 6(1)(b) of the GDPR, consent is not required for the processing of the data contained in spontaneously submitted curricula; the information required by Art. 13 of the GDPR is contained in this privacy policy, to which the Data Controller refers in its first reply to the candidate.

To assess an application the Data Controller does not request special categories of personal data (Art. 9 of the GDPR) or data relating to criminal convictions and offences (Art. 10): please do not include them. Any data relating to criminal convictions or offences that is nevertheless present is not used and no decision is based on it. The same applies to special categories of data that are not relevant to the application: the Data Controller does not use them, does not extract them from the document and does not copy them elsewhere, and they remain in the document received until it is deleted. Only those special categories of data that you have chosen to disclose because they are necessary for carrying out obligations or exercising rights in the field of employment law — for example, belonging to the protected categories referred to in Italian Law 68/1999 — are processed for that purpose pursuant to Art. 9(2)(b) of the GDPR, in compliance with the requirements laid down by the Italian Data Protection Authority (provision no. 146 of 5 June 2019). This is without prejudice, as regards special categories of data, to the case where such data is strictly necessary for the establishment, exercise or defence of legal claims in a dispute that has already arisen (Art. 9(2)(f) GDPR).

Sending an application is entirely voluntary. Failure to provide the data, or providing it only in part, has the sole consequence that the Data Controller will be unable to assess the application in whole or in part.

Special categories of data

The contact form and the published email addresses are intended for professional and business communications. For communications received through these channels the Data Controller neither requests nor requires special categories of personal data within the meaning of Art. 9 of the GDPR — in particular health data — or data relating to criminal convictions and offences (Art. 10): please do not include them in your messages. The Data Controller bases no decision on such data, does not extract it from the communication or organise it in dedicated archives, and deletes it as soon as the inquiry has been answered, without waiting for the ordinary retention period set out in section 6. Between receipt and deletion, no operation is carried out on such data other than deleting it. The only exception, limited to special categories of data, is where such data is strictly necessary for the establishment, exercise or defence of legal claims in a dispute that has already arisen (Art. 9(2)(f) GDPR). The foregoing does not concern unsolicited job applications, which are governed by the dedicated paragraph.

IP address used to limit contact form submissions

To prevent abusive or automated submissions, on each request to submit the contact form the Website's server reads the IP address the request comes from and uses it to limit submissions from the same address to three per minute; for IPv6 addresses the limit applies to the network prefix (the first 64 bits of the address) rather than to the full address. The count is entrusted to a service of Cloudflare, the provider on whose network the Website runs (section 4): on each request to submit the form the server passes that service the address, or the prefix, as the key to count on, and receives back only whether the limit has been exceeded. The counters are kept by Cloudflare at the data centre that received the request; as part of this limit the Website does not write the address to any other store or database and does not associate it with the data entered in the form. Only where that service is unavailable does the count take place in the server's volatile memory. As part of this limit the IP address is not disclosed to anyone other than Cloudflare. The anti-abuse check, in which Cloudflare receives the IP address directly from your browser, is described in the following paragraph. The submission request is also recorded in the server's logs like any other request that reaches it, as described in the paragraph "Navigation data".

This processing is automatic and takes place on every submission of the form: the form cannot be submitted without the IP address being read for this purpose.

Data processed by the anti-abuse check on the contact form

The contact form is protected by Cloudflare Turnstile, a service of Cloudflare, Inc. that checks that the form is being used by a person and not by an automated program. The service is not loaded when the page opens: your browser downloads it from Cloudflare's servers (domain challenges.cloudflare.com) only when, after a page has loaded, you first change one of the fields of the form — name, email, organization, message — or the checkbox: when you type the first character, paste or dictate text, tick the checkbox, or when the browser fills in a field on your behalf (autofill). It does not download it when you merely select a field — with the mouse, by touch or with the keyboard — without changing it. With one exception: if the fields were filled in before the page had finished loading, or were restored by the browser when the page was reloaded, and are not changed again, the browser downloads the service when you submit the form. A line at the top of the form, before the fields, gives notice of the check and of the saving of a code in the browser. From the moment the service is loaded Cloudflare receives, directly from your browser, the technical information (so-called signals) the service relies on; in the course of the check the browser exchanges data with that domain and, from what we observed, with one of its subdomains. According to what Cloudflare states in its own notice on the service (the Turnstile Privacy Addendum), these include the IP address, the fingerprint of the encrypted connection (TLS fingerprint), the browser's User-Agent header, the key that identifies the Website to the service, and the address of the Website; according to the technical documentation of the service, the check also runs programs in the browser which detect its technical characteristics and the signs of its being used by a person. In requesting the service your browser also tells Cloudflare, as the Website configures it, the language of the page, the theme the page is shown in, the format of the check's box and a label saying that the check concerns the contact form. According to the documentation of the service, the verification code described below expires after about five minutes and, for as long as the page stays open, the service renews it by itself, contacting Cloudflare again. Lastly, the service stores a code in your browser, distinct from the verification code, which has no set expiry and whose content and specific function Cloudflare does not publicly document: from our checks it differs for each browser and can therefore allow Cloudflare to recognise the same browser on later occasions and, depending on the browser and its settings, on other websites that use the service too. It is an online identifier (recital 30 of the GDPR), described in the Cookie Policy. This processing does not concern a visit during which neither a field of the contact form nor the checkbox is changed, whether by you or by the browser on your behalf, and the form is not submitted.

Once the check is passed, the service gives your browser a single-use code, which is sent to the Website's server together with the form data. To have the check confirmed the server sends the Turnstile service, of the data concerning you, only that code: it does not add your IP address or the data entered in the form to the confirmation request, and it delivers the message only if the confirmation is positive. The Data Controller does not keep the code on its own systems. According to the documentation of the service, the check does not access what you write in the form, does not store it and does not transmit it.

This processing is automatic and starts at the first change to a field of the form or to the checkbox, including a field filled in automatically by the browser, or, in the case described above, when the form is submitted: the form cannot be submitted without the check. If the check fails the message is not delivered, and the submission can be repeated. Anyone who prefers to avoid this processing can write directly to the email addresses published on the Website.

Navigation data

During normal browsing, the computer systems responsible for operating the Website automatically collect certain technical data. The Website is delivered through Cloudflare's network (section 4), which receives every request addressed to the Website and processes the technical data needed to answer it, including the IP address. For the requests that reach the Website's server — in particular the pages, including redirects and pages not found, the robots.txt and sitemap.xml files and the requests to submit the contact form; not static files such as style sheets, scripts and fonts — Cloudflare also records, in the logs it makes available to the Data Controller, one entry per request: the address of the page requested, the method and outcome of the request, date and time, browser type and version (User-Agent header) and network metadata, such as the country, the approximate location and the network operator the request comes from. According to the documentation of the service the entry includes the request headers, that is the technical information that accompanies every request — for example the preferred language and the referring page — among which is the IP address. To these entries are added the diagnostic messages written by the Website's server, which contain neither the data entered in the contact form nor the IP address. The Data Controller uses this data exclusively to ensure the proper functioning of the Website, to diagnose malfunctions and for cybersecurity purposes; as regards the processing the provider carries out for its own purposes, see section 4.

The collection of navigation data is automatic and inherent to the operation of internet communication protocols: it does not result from any voluntary act on your part and cannot be disabled while continuing to use the Website.

Cookies

The Website uses technical cookies only. As of the last update, no statistical analysis or marketing cookies are active; should any be introduced, they will be installed only with your prior consent and this privacy policy will be updated accordingly. For detailed information about the cookies used, their purposes, and how to remove or block them, please refer to our Cookie Policy. The Cookie Policy also describes whatever is stored in the browser's local storage without being a cookie, including what the anti-abuse check on the contact form stores there.

3. Purposes and Legal Basis for Processing

The personal data collected is processed for the following purposes, each associated with the relevant legal basis under Art. 6 of the GDPR and, where relevant, Art. 9:

PurposeLegal basisData processed
Responding to inquiries submitted through the contact form or written to the published email addresses, other than unsolicited job applications, and managing the resulting communicationLegitimate interest of the Data Controller (Art. 6(1)(f) GDPR) in responding to communications received and following up on contacts initiated by the data subject. You may object to this processing on the conditions set out in section 7 (Art. 21).For the form: name, email, organization, message, confirmation that the policy was reviewed. For emails: sender's address and content of the message
Assessing unsolicited job applications received and contacting candidatesTaking steps at the request of the data subject prior to entering into a contract (Art. 6(1)(b) GDPR); pursuant to Art. 111-bis of Italian Legislative Decree 196/2003, within the limits of that purpose consent is not required. For any special categories of data necessary in the field of employment law, Art. 9(2)(b) GDPRIdentification and contact details, curriculum vitae, education and professional experience, any other data included by the candidate
Technical operation and security of the WebsiteLegitimate interest of the Data Controller (Art. 6(1)(f) GDPR) — ensuring the availability, integrity, and security of the Website. You may object to this processing on the conditions set out in section 7 (Art. 21).Navigation data (IP address, browser, pages requested, request headers, network metadata); technical data of DNS queries for the domain; technical cookie recording that the cookie notice was dismissed
Preventing abusive or automated submissions of the contact form, by limiting the number of submissions per IP addressLegitimate interest of the Data Controller (Art. 6(1)(f) GDPR) in protecting the contact form from abuse and keeping it available. You may object to this processing on the conditions set out in section 7 (Art. 21).IP address (for IPv6 addresses, the network prefix) and number of recent form submissions
Protecting the contact form from automated submissions, by means of a service that checks that the form is being used by a person (Cloudflare Turnstile)Legitimate interest of the Data Controller (Art. 6(1)(f) GDPR) in protecting the contact form from abuse and keeping it available. You may object to this processing on the conditions set out in section 7 (Art. 21).Technical information (signals) collected by the service from your browser, including IP address, fingerprint of the encrypted connection, User-Agent, technical characteristics of the browser and signs of its being used by a person; code stored by the service in the browser; single-use verification code
Compliance with accounting, tax and document-retention obligations imposed by law, and responding to lawful requests from public authoritiesLegal obligation (Art. 6(1)(c) GDPR)The data contained in documentation subject to a statutory retention obligation
Establishment, exercise or defence of legal claimsLegitimate interest of the Data Controller (Art. 6(1)(f) GDPR) in protecting its rights; for any special categories of data, Art. 9(2)(f) GDPRThe data necessary in relation to the specific dispute

4. Third-Party Services and Data Recipients

Personal data may be made accessible or disclosed to the following:

  • Authorised persons: the persons acting under the authority of the Data Controller, authorised to process data under Art. 2-quaterdecies of Italian Legislative Decree 196/2003 and acting on the Data Controller's instructions under Art. 29 of the GDPR, who access the data to perform their tasks.
  • Professional advisors: lawyers, accountants, and auditors, to the extent necessary for the management of legal, tax, and accounting obligations.
  • Public authorities: bodies or institutions to which the Data Controller is required to disclose data in compliance with legal obligations.

The Data Controller also engages the following third-party providers, who, for the processing they carry out on the Data Controller's behalf, act as Data Processors pursuant to Art. 28 of the GDPR:

Brevo

Transactional email delivery service provided by Sendinblue SAS (France), which trades as Brevo. When you submit the contact form, the Website's server transmits the data entered — name, email, organization, message and the confirmation that this policy was reviewed — to Brevo so that it is delivered by email to the Data Controller's mailbox. The transmission is server-to-server: your browser does not contact Brevo. Brevo keeps in its sending log the data relating to the delivery, including recipient, sender, subject line (which carries your name and, if provided, your organization), reply-to address (your email address), and the date, time and outcome of the sending. The text of the message is not kept in the log. For this processing Brevo acts as a Data Processor, under the data processing agreement (DPA) that forms Appendix 3 of its Terms of Service. The same DPA provides that Brevo may process data as an independent controller, in accordance with its own privacy policy, in order to manage the customer's account, for billing, to produce statistics and to defend its rights. According to the list published in the DPA, Brevo's hosting infrastructure is located in France and Belgium; as regards the sub-processors Brevo engages, see section 5.

Cloudflare

Cloudflare, Inc. (USA) provides the Data Controller with four services. First, running and delivering the Website: the Website runs on Cloudflare's network (the Cloudflare Workers service), which receives every request from visitors, answers it and records the logs described in section 2; the data submitted through the contact form also passes through it, for the time needed to forward it to the delivery service, without the Website recording it on that infrastructure in persistent form. Second, the DNS service of the domain operalife.eu: Cloudflare answers the queries by which the names of the domain are translated into network addresses, queries which as a rule reach it from the DNS server used by the visitor or by the sender of an email and not directly from their device; the Data Controller's ordinary mailboxes are hosted by a different provider (Aruba, named below). Third, counting contact form submissions per IP address (section 2). Fourth, the Turnstile anti-abuse check, described in the next paragraph. For these services, and subject to what follows, Cloudflare acts as a Data Processor on the Data Controller's behalf, under the data processing agreement (Data Processing Addendum, published at www.cloudflare.com/cloudflare-customer-dpa) referred to in the contractual terms of the service (www.cloudflare.com/terms). According to those terms and to its own privacy policy (www.cloudflare.com/privacypolicy), Cloudflare also uses for its own purposes — including the security, maintenance and improvement of its network — the traffic data generated by providing the services. The Data Controller accesses the logs and the statistics through the management dashboard of its own account. The basis for the transfer to the United States and the information on the place of processing are set out in section 5.

As for the Turnstile anti-abuse check, which protects the contact form as described in section 2, Cloudflare collects the signals directly from your browser and, according to what it states in the Turnstile Privacy Addendum (www.cloudflare.com/turnstile-privacy-policy), processes them in two distinct capacities. When it uses them to protect the Website's form it acts as a Data Processor on the Data Controller's behalf, under the same Data Processing Addendum. When it uses the same signals to improve its own ability to detect automated programs it states instead that it acts as a data controller, on the basis of its own legitimate interest: that processing is governed by the Turnstile Privacy Addendum and by Cloudflare's privacy policy. The collection of the signals from your browser, which also makes this use possible, takes place because the Data Controller has chosen to protect the form with this service, for the purpose and on the legal basis set out in section 3; as of the last update, neither the Turnstile Privacy Addendum, nor the Data Processing Addendum, nor the documentation of the service indicates a way for the Data Controller to exclude that use. An objection to this use, and the other rights concerning it, may be exercised directly against Cloudflare, which in the Turnstile Privacy Addendum gives its data protection officer as the contact (dpo@cloudflare.com) and in its privacy policy, for objections, the address sar@cloudflare.com; you may in any case contact the Data Controller, at the addresses given in section 8, as regards the collection of the signals through the Website. According to the documentation of the service, Cloudflare also makes available to the Data Controller, in the management dashboard, statistics on the use of the check which include the IP addresses from which the largest number of requests originate.

Aruba

Email hosting service provided by Aruba S.p.A. (Italy). Emails addressed to the Data Controller's ordinary mailboxes, including those generated by the contact form and those sent to the addresses published on the Website, are received and stored on servers located within the European Union. Aruba acts as a Data Processor pursuant to Art. 28 of the GDPR, under the relevant data processing agreement. The foregoing does not concern certified email (PEC): messages sent to the Data Controller's PEC address are received and stored by the provider of that service, under the terms of that service.

5. International Data Transfers

Among the third-party providers listed above, Cloudflare, Inc. is based in the United States of America. Transfers are carried out in compliance with Chapter V of the GDPR, on the bases set out in the table and in the notes that follow it:

ServiceCountryTransfer basis
Cloudflare (running and delivering the Website, DNS, limiting form submissions, Turnstile anti-abuse check)United StatesEU-US Data Privacy Framework adequacy decision (Commission Implementing Decision (EU) 2023/1795; Art. 45 GDPR) — as of the last update Cloudflare, Inc. is listed as certified on the DPF register

Aruba S.p.A. is based in Italy and data remains within the European Union; no international transfer therefore occurs.

Cloudflare runs the Website and counts its form submissions at the data centre of its network that receives the request, as a rule the one nearest to the visitor: the Data Controller has not restricted execution to a given region, and the data of a request may therefore also be processed at a data centre located outside the European Economic Area; the locations in which Cloudflare has data centres are published at www.cloudflare.com/network. In its privacy policy Cloudflare states that it stores information primarily in the United States and in the European Economic Area. According to Cloudflare's Data Processing Addendum, the data processed on the Data Controller's behalf may be processed by Cloudflare and its sub-processors in other countries outside the European Economic Area as well: the list, published at www.cloudflare.com/gdpr/subprocessors, as of the last update names providers and Cloudflare group companies established, besides the European Economic Area and the United States, in Australia, Canada, India, Japan, Malaysia, Mexico, Singapore, South Korea, Switzerland, the United Arab Emirates and the United Kingdom. As of the last update, among these countries Australia, India, Malaysia, Mexico, Singapore and the United Arab Emirates are not covered by an adequacy decision of the European Commission; the same is true of many of the countries in which Cloudflare has data centres. Transfers to countries without an adequacy decision are governed by the provisions of the Data Processing Addendum set out below. For transfers from the Data Controller to Cloudflare that are not covered by an adequacy decision the agreement provides for the standard contractual clauses adopted by Commission Implementing Decision (EU) 2021/914 to apply; for onward transfers of that data it requires compliance with the applicable law and, where applicable, with the same clauses. The text of the agreement is published at the address given in section 4 of this policy; the Data Controller will provide a copy on a request sent to privacy@operalife.eu.

Sendinblue SAS (Brevo) is based in France and, according to the list of sub-processors annexed to its DPA, hosts data in France and Belgium. The same list states that, for activities ancillary to the service — including content delivery and traffic protection network, customer support and reporting tools, support and maintenance by group companies — Brevo engages sub-processors established in the United States and in India, which may involve processing, outside the European Economic Area, of the data of messages sent through the contact form and of the related sending log. For those cases the list indicates, depending on the sub-processor, the EU-US Data Privacy Framework, binding corporate rules or standard contractual clauses with supplementary measures; for India, for which there is no adequacy decision, standard contractual clauses with supplementary measures. The current list of sub-processors, with the location, place of processing and safeguards of each, is published in Annex 2 of the DPA at www.brevo.com/legal/termsofuse.

For Brevo's sub-processors, the safeguards applicable to each are set out in Annex 2 of Brevo's DPA; on a request from you sent to privacy@operalife.eu, the Data Controller will approach the provider to obtain a copy of those safeguards or any further information available, and will pass on to you what it obtains. The adequacy decision concerning the EU-US Data Privacy Framework (Implementing Decision (EU) 2023/1795) is published in the Official Journal of the European Union and is available at eur-lex.europa.eu; the current list of certified entities is available at www.dataprivacyframework.gov.

6. Data Retention Period

The Data Controller retains personal data only for the time strictly necessary to fulfil the purposes for which it was collected, in accordance with the principle of storage limitation (Art. 5(1)(e) GDPR); where a period depends on a provider that does not state it, the table says so:

Data typeRetention periodJustification
Contact form and email communication data, other than unsolicited job applications12 months from the last communication exchanged in connection with the inquiryTime necessary to handle the inquiry and a reasonable subsequent period for potential follow-up communications
Sending log of the email delivery provider (Brevo): recipient, sender, subject line, reply-to address, date, time and outcome of the sending1 month from sending, plus the provider's technical deletion time (up to 24 hours)Checking that delivery took place and diagnosing any failed deliveries
Unsolicited job applications and curricula12 months from receipt of the application, even where further messages are exchanged, unless you ask for earlier deletion. If the application leads to an employment or collaboration relationship, the data is processed in accordance with the privacy notice provided at that stageAn unsolicited application does not refer to a specific position: the period allows it to be assessed against staffing needs that arise in the following months
Logs of the requests to the Website's server (navigation data), the server's diagnostic messages and technical data of DNS queries3 days for the logs that Cloudflare makes available to the Data Controller, according to the documentation of the service and under the service plan in use as of the last update. For the other technical data it processes on the Data Controller's behalf, including that of DNS queries, Cloudflare states no period: the criterion of the Data Processing Addendum set out in the row on the anti-abuse check applies. Cloudflare may keep for longer the data it processes for its own purposes, in accordance with its own privacy policyCybersecurity and technical diagnostics
IP address used to limit contact form submissionsAs part of this limit the address is recorded in the counters kept by Cloudflare and, only when that service is unavailable, in the server's volatile memory; the submission request remains recorded in the logs described in the previous row. Only the submissions made in the last 60 seconds count towards the limit; Cloudflare's documentation does not state how long the counters are kept beyond that interval: the criterion of the Data Processing Addendum set out in the row on the anti-abuse check applies. When the count takes place in the server's volatile memory (section 2), the addresses that have been inactive for more than 60 seconds are deleted the next time the same server instance counts a submission in memory, or when that instance stopsThe data serves only to count recent submissions; how long the counters last depends on the provider, which does not state it
Signals collected by the anti-abuse check on the contact form (Cloudflare Turnstile), code stored by the service in the browser, and verification codeThe Data Controller keeps neither the signals nor the verification code on its own systems; the code is used once, at the moment of submission. The statistics Cloudflare makes available to the Data Controller cover, according to the documentation of the service, the last seven days at most under the plan in use as of the last update. For the signals it processes on the Data Controller's behalf Cloudflare states no period in days or months: its Data Processing Addendum provides that the data is kept for as long as the processing is necessary and that, when the contract ends, it is deleted or returned, unless the law requires it to be kept. To the processing it carries out for its own purposes Cloudflare applies the criteria set out in its own privacy policy. The code the service stores in your browser stays on your device with no set expiry, until it is deleted (Cookie Policy, sections 4 and 8); the Data Controller does not receive it and does not keep itThe check needs the signals at the moment you use the form. For the rest the criterion laid down in the agreement with the provider applies, which does not express it as a fixed term
Technical cookie recording that the cookie notice was dismissedUp to 365 days from the dismissal of the noticePreventing the cookie notice from being shown again on every page
Data retained under legal obligationsFor the period required by the specific applicable legislation: as a rule ten years for accounting and tax documentation (Art. 2220 of the Italian Civil Code)Compliance with accounting, tax or other obligations imposed by law
Data needed to defend legal claimsUntil the limitation period for the claim expiresEstablishment, exercise or defence of legal claims

Where more than one period applies to the same data, the longest prevails, limited to the purpose that justifies it; this is without prejudice to section 2 as regards special categories of data and data relating to criminal convictions and offences. At the end of the retention period, data is deleted or anonymised. Deletion may take additional technical time for copies held in backups, which are retained only for the duration of their rotation cycle and are not used for any other purpose.

7. Data Subject Rights

Under Articles 15–22 of the GDPR, and under Art. 7(3) as regards the withdrawal of consent, you have the right to:

  • Access (Art. 15): obtain confirmation as to whether your personal data is being processed, access its content and obtain a copy of it.
  • Rectification (Art. 16): obtain the correction of inaccurate personal data or the completion of incomplete data.
  • Erasure (Art. 17): obtain the deletion of your personal data, in the cases provided for by the GDPR.
  • Restriction of processing (Art. 18): obtain the restriction of the processing of your personal data in certain circumstances.
  • Data portability (Art. 20): receive the personal data you have provided in a structured, commonly used, and machine-readable format, and transmit it to another controller, where the processing is based on consent or a contract and is carried out by automated means. As of the last update none of the processing described in this privacy policy is based on consent; the only processing based on pre-contractual steps is that of unsolicited job applications, in respect of whose data this right may be exercised.
  • Objection (Art. 21): object at any time to the processing of your personal data based on legitimate interest, on grounds relating to your particular situation; the Data Controller will cease the processing unless it demonstrates compelling legitimate grounds which override your interests, rights and freedoms, or the need to establish, exercise or defend legal claims. Should personal data be processed for direct marketing purposes, you have the right to object at any time without providing any reason; upon such objection, the data will no longer be processed for these purposes.
  • Withdrawal of consent (Art. 7(3)): withdraw at any time any consent given, without affecting the lawfulness of processing based on consent given before its withdrawal. As of the last update none of the processing described in this privacy policy is based on consent; should non-essential cookies be introduced, that consent may be withdrawn at any time through the preference tool that will be made available on the Website.
  • Automated decisions (Art. 22): not be subject to a decision based solely on automated processing, including profiling, which produces legal effects concerning you or similarly significantly affects you. Within the processing described in this privacy policy, the Data Controller carries out no such processing. The limit on submissions and the anti-abuse check on the contact form are automated controls, but they produce no such effects: a refused submission can be repeated, and the email addresses published on the Website remain available.

Right to object. We specifically draw your attention to the fact that, where processing is based on the Data Controller's legitimate interest, you have the right to object at any time on grounds relating to your particular situation. Were data to be processed for direct marketing purposes, you may object at any time and without providing any reason (Art. 21 GDPR).

8. How to Exercise Your Rights

To exercise the rights listed above, you may send a written request to privacy@operalife.eu or to the certified email address (PEC) operalife@pecaruba.it, specifying the right you wish to exercise. The Data Controller will request additional information needed to confirm your identity only where it has reasonable doubts as to the identity of the person making the request (Art. 12(6) GDPR). The Data Controller will respond within one month of receiving the request, as provided by Art. 12(3) of the GDPR; that period may be extended by two further months taking into account the complexity and number of requests, in which case you will be informed of the extension and of the reasons for the delay within one month. Should the Data Controller not act on the request, it will inform you without delay and in any event within one month, stating the reasons and your right to lodge a complaint with the supervisory authority and to seek a judicial remedy (Art. 12(4) GDPR). Rectifications, erasures and restrictions are communicated to each recipient to whom the data has been disclosed, unless this proves impossible or involves disproportionate effort; on your request the Data Controller will inform you of the identity of those recipients (Art. 19 GDPR). For processing based on legitimate interest, you may ask the Data Controller to explain the reasons why it considers that this interest prevails over your interests, rights and freedoms. Exercising your rights is free of charge, except for manifestly unfounded or excessive requests, for which the Data Controller may charge a reasonable fee or refuse the request, providing reasons for the decision.

9. Complaint to the Supervisory Authority

If you believe that the processing of your personal data infringes the GDPR, you have the right to lodge a complaint with the competent supervisory authority pursuant to Art. 77 of the GDPR. For Italy, the competent authority is the Garante per la Protezione dei Dati Personali, Piazza Venezia 11, 00187 Roma — email: protocollo@gpdp.it — certified email (PEC): protocollo@pec.gpdp.it — website: www.garanteprivacy.it. Alternatively, the complaint may be lodged with the supervisory authority of the EU/EEA Member State where you habitually reside, where you work, or where the alleged infringement took place.

10. Updates to This Policy

The Data Controller reserves the right to modify or update this privacy policy at any time, for example following regulatory changes, the introduction of new services, or changes in data processing practices. The date of the last update is shown at the top of this page. In the event of substantial changes, the Data Controller will provide notice through a clearly visible announcement on the Website. We recommend that you periodically review this page to stay informed about how the personal data collected is protected. Should the Data Controller intend to process personal data for a purpose other than those described herein, the data subject will be informed of the new purpose and any other relevant information pursuant to Art. 13(3) of the GDPR prior to such further processing.