1. Buigas, S.L. (“Buigas” or “we”)
    C/ Iradier, 19-21, 08017 Barcelona (Spain)
    NIF: B60716388+34


We will process the data you provide through “contact” and “work with us” forms. These data generally include name, surname, email, company, telephone, country, city and any other data you may provide in the free text section of the form. By providing us with your data, you guarantee and take responsibility for the truthfulness and accuracy of the data. On the other hand, we will also collect aggregate data through cookies with the sole purpose of analysing the browsing on our website.


Purpose of providing services and/or attending to your requests for information based on Art. 6.1.(b) RGPD (performance a contract or pre-contract).

The purpose of sending you commercial emails about our services based on Art. 6.1.(a) RGPD (consent).

Purpose of carrying out analysis of navigation on our website based on Art. 6.1.(a) RGPD (consent).


We will store your data for the duration of client-lawyer relationship in order to manage it correctly and send you commercial information of interest. However, if we observe a prolonged period of inactivity, we will also proceed to cancel your data to the extent that the processing is no longer appropriate, relevant and necessary for the purposes intended. This rule will apply unless you request us to delete your data.

As for the data provided by you through the “work with us” form, they will be stored until you either enter into an employment relationship with us or until you exercise your right to cancel them. Therefore, you have the right to access your personal data, rectify inaccurate data or request their deletion when they are no longer necessary. Notwithstanding the above, if you do not initiate an employment relationship with the owner of the data, your data will be deleted on 31st December of the third year following the date when you sent your data. The data will not be transferred to third parties.



As a general rule, we will not communicate your data to third parties. However, we will need to communicate your data in some events to:

Suppliers: Those suppliers who require such access to provide us with their services, such as managers, IT specialists, cloud or hosting providers, CRM providers, partners, consultants or collaborators, will have access to your personal data. These third parties will act as our (sub)managers and will have appropriate guarantees in place to protect your personal information including the corresponding contract of assignment of processing in accordance with Art. 28 RGPD.

Other: We will share your personal data with third parties if required to do so by a regulation, administrative or judicial authority or for the good purpose of public interest or public order, such as to comply with money laundering and anti-terrorism regulations, tax obligations or for social security purposes.


We do not conduct or intend to conduct international data transfers. However, some computer providers have their servers located outside the European Economic Area (EEA), in particular in the United States of America. In the event that one of our providers is located outside the EEA (for example, Google or Mailchimp), we will subscribe to as many documents as necessary to ensure that they provide adequate safeguards equivalent to those in the EU for such international transfers and you consent to the international transfer of your data.


What rights do you have?

As provided in the General Data Protection Regulations (RGPD) and the Organic Law 3/2018 on the Protection of Personal Data and the guarantee of digital rights, we inform you that you have the following rights.

Access: You have the right to access your data in order to know what personal data concerning you we are processing.

Rectification or suppression: In certain circumstances, you have the right to rectify inaccurate personal data concerning you that is processed by us, or even to ask us to suppress it.

Limitation: Under certain circumstances, you will have the right to ask us to limit the processing of your data, in which case we inform you that we will only keep them for the exercise or defence of claims.

Portability: Under certain circumstances, you will have the right to receive the personal data concerning you, which you have provided to us, in a structured, commonly used and machine-readable format, and to transfer it to another controller.

Opposition: In certain circumstances and for reasons related to your particular situation, you will have the right to oppose the processing of your data in which case, we will stop processing them except for compelling legitimate reasons or for the exercise or defence of any claims. You may at any time object to the receipt of commercial communications.

How can you exercise your rights?

You may exercise your rights at any time by contacting, stating “Privacy Rights” in the subject line. In order to verify your identity, we may require you to send us certain additional information or documentation, such as a copy of your ID card or similar document.

The exercise of these rights is free of charge.

Do you have the right to remove your consent?

Yes, at any time you can remove your consent to the processing of your data for one, several or all of the above purposes based on your consent to their processing. Please note that this may alter or even lead to the termination of the provision of services.

Are you entitled to make a claim?

Yes, at any time you can complain to the competent control authority according to your place of residence. In Spain: the Spanish Data Protection Agency (AEPD). In any case, before initiating any complaint, please contact us by e-mail ( in order to solve any discrepancy or dispute in a friendly way.

How soon will we reply?

We will respond to your requests as soon as possible and in any case within one month. If this is not the case, we apologise and ask you to contact us again so that we can assist you and rectify any possible technical mistakes that may have prevented us from replying to you in time.


What are Cookies and what are they for?

A cookie is a file download to your computer when you access certain websites. Cookies allow a website, among other things, to store and retrieve information about the user’s browsing behaviours and, depending on the information they contain and the way the computer is used, they can serve to recognise the user.

Cookies are used to capture information about user navigation and, by analysing it, to find out how the user interacts with our website, thus optimising their browsing experience.

What types of cookies are there?


They are essential for browsing a website and being able to use its functions.

This site uses technical cookies necessary to ensure safe and uninterrupted browsing of our website, to save user preferences regarding settings, to accept or reject site cookies and to share content on social networks such as Linkedin. As they are necessary for the performance of the site, these cookies are activated by default and cannot be refused.


They are analysis cookies, property of Google. Google Analytics is a web analysis tool from Google that mainly allows website owners to know how users interact with their website by tracking and analysing user behaviour in order to make improvements based on the user’s use of the website and services.

Google Analytics enables cookies in the domain of the site where you are located and uses a set of cookies to collect information anonymously and to report website trends without identifying individual users.

Together with our server log files, they allow to know the total number of users visiting our Website and those parts of the Website that are most popular.

Use of cookies: gtag.js and analytics.js

The JavaScript library analytics.js is part of Universal Analytics and uses its own cookies for:

  • Distinguishing unique users.
  • Limit the percentage of applications.

When the recommended JavaScript fragment is used, the cookies are assigned to the highest possible level domain. For example, if your website address is, analytics.js will set as the cookie domain. Assigning cookies to the highest possible level domain allow to track users in various sub-domains without having to make any additional settings.

Note: With gtag.js and analytics.js it is not necessary to set cookies to transmit data to Google Analytics.

The following cookies are set by the gtag.js and analytics.js libraries:

Name Duration Description
_ga 2 years It is used to distinguish users.
_gid 24 hours It is used to distinguish users.
_gat 1 minute It is used to limit the percentage of requests. If Google Analytics has been implemented using Google Tag Manager, this cookie will be called _dc_gtm_<property-id>.
AMP_TOKEN From 30 seconds to 1 year Includes a token that can be used to retrieve a customer ID from the AMP Customer ID service. Other possible values indicate disqualifications, ongoing requests, or errors obtained when retrieving an AMP Client ID service ID.
_gac_<property-id> 90 days It includes campaign information about the user. If you have linked your Google Analytics and Google Ads accounts, the Google Ads website conversion tags will read this cookie unless you disable it. More information about Google Ads

Use of cookies: ga.js

The ga.js JavaScript library uses its own cookies for:

  • Determine the domain to be monitored.
  • Distinguishing unique users.
  • Limit the percentage of applications.
  • Remember the number and duration of previous visits.
  • Remember the information from the traffic sources.
  • Determine the start and end of a session.
  • Remembering the value of personalized variables at the visitor level.

By default, this library sets cookies to the domain specified in the browser’s property and assigns the cookie path to the root level (/).

This library sets the following cookies:

Name  Duration Description
__utma 2 years from configuration or upgrade It is used to distinguish users and sessions. The cookie is created when the JavaScript library is run and there is no __utma cookie. The cookie is updated each time data is sent to Google Analytics.
__utmt 10 minutes It is used to limit the percentage of requests.
__utmb 30 minutes from setup or update It is used to determine new sessions or visits. The cookie is created when the JavaScript library is run and there is no __utmb cookie. The cookie is updated each time data is sent to Google Analytics.
__utmc End of browser session Not used in ga.js. It is configured to interact with urchin.js. Previously, this cookie acted together with the __utmb cookie to determine if the user was in a new session or visit.
__utmz 6 months from the configuration or update It stores the source of traffic or the campaign that explains how the user got to the website. The cookie is created when the JavaScript library is run and is updated each time data is sent to Google Analytics.
__utmv 2 years from configuration or upgrade It is used to store custom variable data at the visitor level. This cookie is created when a programmer uses the _setCustomVar method with a custom variable at the visitor level. It was also used for the _setVar method, which is no longer available. The cookie is updated each time data is sent to Google Analytics.

Use of cookies: urchin.js

Previously, Google Analytics provided a JavaScript measurement library called “urchin.js”. When the latest ga.js library was launched, programmers were advised to migrate their content to the new library. For the websites that have not finished the migration, urchin.js sets the cookies just as they are set in ga.js. See the previous section on the use of ga.js cookies for more information.


These cookies store information on the behaviour of users obtained through continuous observation of their browsing habits. This allows a specific profile to be developed to display advertising based on this.

We use the Google Analytics functions for advertisers in the Display Network, such as remarketing, using a third-party DoubleClick cookie in addition to the other cookies described in this document only for these functions. For more information about this cookie, see the Google advertising privacy FAQ.

Use of cookies: Optimize

Name Duration Description
ggaexp It depends on the duration of the experiment, but it is usually 90 days It is used to determine the inclusion of a user in an experiment and the expiration of the experiments in which he participates.
_opt_awcid 24 hours It is used for campaigns associated with Google Ads client IDs.
opt_awmid 24 hours It is used for campaigns associated with Google Ads campaign IDs.
opt_awgid 24 hours It is used for campaigns associated with Google Ads Group IDs.
opt_awkid 24 hours It is used for campaigns associated with Google Ads criteria IDs.
opt_utmc 24 hours Stores the last query parameter utm_campaign.

How do I disable cookies?

You can block or disable cookies by activating the setting on your browser which allows you to refuse the installation of all or some cookies. Most browsers allow you to be alerted to the presence of cookies or to refuse them automatically. If you reject them, you will still be able to use our Website, although the use of some of its services may be limited and therefore your experience on our Website less satisfactory.

For more information on disabling cookies visit