In accordance with Law 34/2002 of July 11 on Information Society Services and Electronic Commerce (LSSI), Regulation (EU) 2016/679 of the European Parliament and of the Council of April 27, 2016 (GDPR), and Organic Law 3/2018 of December 5 on Data Protection and Guarantee of Digital Rights (LOPDGDD), it is mandatory to obtain the express consent of the user for the use of non-essential cookies on websites.
Cookies and similar technologies such as local shared objects, flash cookies, or pixels are tools used by web servers to store and retrieve information about visitors, as well as to ensure proper operation of the website.
These technologies allow the web server to remember certain data concerning the user, such as display preferences, username and password, or preferred products.
Under EU regulations, cookies that require the user’s informed consent are analytical, advertising, and affiliate cookies. Technical cookies and those necessary for the operation of the website or for services expressly requested by the user are exempt.
By purpose:
By ownership:
By retention period:
PaynoPain Solutions SL is the Data Controller and informs that personal data will be processed in accordance with GDPR, with the following details:
Data subject rights:
Contact to exercise rights:
PaynoPain Solutions SL
Paseo Universidad, 23 Bajo 5 5 – 12006 Castellón de la Plana (Castelló)
Email: compliance@paynopain.com
Data Protection Officer:
RS SERVICIOS JURÍDICOS S.L. – dpo@rsprivacidad.es
Technical and Functional Cookies
|
Provider |
Cookie Name |
Purpose |
Duration |
|
google.com |
__Secure-1PAPISID |
Necessary for using the website’s features and services |
1 year |
|
google.com |
__Secure-1PSID |
Necessary for using the website’s features and services |
1 year |
|
google.com |
__Secure-1PSIDCC |
Necessary for using the website’s features and services |
1 year |
|
google.com |
__Secure-1PSIDTS |
Necessary for using the website’s features and services |
1 year |
|
google.com |
__Secure-3PSIDCC |
Necessary for using the website’s features and services |
1 year |
|
google.com |
__Secure-3PSIDTS |
Necessary for using the website’s features and services |
1 year |
|
google.com |
__Secure-ENID |
Necessary for using the website’s features and services |
6 months |
|
google.com |
AEC |
Necessary for using the website’s features and services |
5 months |
|
google.com |
OGPC |
Necessary for using the website’s features and services |
17 days |
|
google.com |
SOCS |
Necessary for using the website’s features and services |
6 months |
|
paynopain.com |
moove_gdpr_popup |
Necessary for using the website’s features and services |
10 months |
|
paynopain.com |
wpml_current_language |
Necessary for using the website’s features and services |
Session |
Analytical Cookies
| Owner | Cookie | Purpose | Duration |
| __Secure-3PAPISID | These cookies are used to deliver ads more relevant to you and your interests. | 1 year | |
| __Secure-3PSID | These cookies are used to deliver ads more relevant to you and your interests. | 1 year | |
| clarity.ms | _clck | Analytical cookie that stores a unique identifier to record how users interact with the website through heat maps and session recordings | 1 year |
| clarity.ms | _clsk | Analytical cookie that connects multiple page views into a single recording session | 1 day |
| clarity.ms | CLID | Analytical cookie that identifies the first time a user visits the site | 1 year |
| clarity.ms | ANONCHK | Analytical cookie that indicates whether the Clarity user ID is being anonymized | 10 minutes |
| clarity.ms | MR | Analytical cookie that indicates whether a cookie should be refreshed | 7 days |
| clarity.ms | MUID | Microsoft analytical cookie that uniquely identifies web browsers visiting Microsoft sites | 1 year |
| clarity.ms | SM | Synchronization cookie used to synchronize the unique identifier assigned to the user | Session |
Advertising Cookies
|
Provider |
Cookie Name |
Purpose |
Duration |
|
|
APISID |
Downloads tools and stores preferences (e.g., number of search results per page, SafeSearch filter). |
1 year |
|
|
HSID |
Same as above. |
1 year |
|
|
NID |
Collects website statistics and tracks conversion and ad personalization. |
7 months |
|
|
SAPISID |
Same as above. |
1 year |
|
|
SID |
Same as above. |
1 year |
|
|
SIDCC |
Same as above. |
1 year |
|
|
SSID |
Same as above. |
1 year |
Third-party services are beyond the editor’s control. Providers may modify their conditions, purposes, and use of cookies at any time.
External providers for this website:
|
Provider |
Privacy Policy Link |
|
|
|
|
|
https://safety.google/settings/privacy-settings/ |
|
Microsoft Clarity |
https://www.microsoft.com/en-us/privacy/privacystatement |
COOKIES SETTINGS PANEL
From this panel, you can configure which cookies may be installed in your browser—excluding technical or functional cookies, which are essential for navigating and using the services offered.
You can delete cookies already stored on your device by clearing your browser history. This will remove cookies from all websites visited. Some saved information may also be lost (e.g., login credentials or site preferences).
For more precise control over site-specific cookies, users can adjust their privacy and cookie settings directly in the browser.
Most modern browsers can be configured to prevent cookies from being installed on your device. However, this may require you to manually adjust certain preferences every time you visit a site or page. Additionally, some services and features may not function properly (e.g., profile-based logins).
“PD Cookie Consent” is a JavaScript library designed to facilitate the blocking of DOM elements that may embed cookies. It allows the website technician to implement a pop-up window (banner) that notifies visitors about the use of cookies and provides tools to manage and block such elements until the user provides consent.
STEP 1:
Insert the following library and styles within the <head>…</head> tags of your website. The library script must be placed before any other <script> or <link> tags:
<link rel=”stylesheet” href=”https://pdcc.gdpr.es/pdcc.min.css”>
<script charset=”utf-8″ src=”https://pdcc.gdpr.es/pdcc.min.js”></script>
<script type=”text/javascript”>
PDCookieConsent.config({
“brand”: {
“dev”: true,
“name”: “RS SERVICIOS JURÍDICOS S.L.”,
“url”: “https://rsprivacidad.es”,
“websiteOwner”: “”
},
“showRejectButton”: true,
“cookiePolicyLink”: “https://paynopain.com/politica-de-cookies/”,
“hideModalIn”: [“https://paynopain.com/politica-de-cookies/”],
“styles”: {
“primaryButton”: {
“bgColor”: “#EEEEEE”,
“txtColor”: “#333333”
},
“secondaryButton”: {
“bgColor”: “#469AFF”,
“txtColor”: “#333333”
},
“rejectButton”: {
“bgColor”: “#EEEEEE”,
“txtColor”: “#333333”
}
}
});
</script>
If this step is not followed exactly as described, “PD Cookie Consent” will not function properly.
STEP 2:
If not already present, insert the URL of the Cookies Policy into the quotation marks of the following tags to ensure proper display of the link with all cookie-related information:
“cookiePolicyLink”: “http://……………”,
“hideModalIn”: [“http://……………”]
If this step is skipped or misconfigured, the consent banner will not be valid under applicable regulations.
NOTE: If the website has been developed using a CMS like WordPress, Ghost, Shopify, Magento, Prestashop, Joomla, Drupal, or similar, it is important to ensure that STEP 1 is also complied with.
If using a CMS, the best and most reliable option is to modify the theme or templates of the website. For example, in the case of WordPress, by creating a child theme.
Refer to the developer documentation provided by each of these platforms.
STEP 3:
The library provides a CSS property to access the banner once it has been closed. Any element containing this class will act as a button to reopen the panel.
You simply need to select any DOM element, such as a link, and insert the class property:
<a href=”#” class=”pdcc-open-modal”>Cookies Panel</a>
Once the visitor clicks the element, the PD Cookie Consent configuration panel will reopen.
When a visitor accesses the website, the PD Cookie Consent library observes each element present on the visited page. If any of these elements meet the criteria for being blocked, they are blocked.
Once all elements on the page have been scanned, the library displays the PD Cookie Consent panel and generates a session cookie named pd_cc, necessary for the correct functioning of the site.
NOTE: The “panel” will not appear automatically if only technical and functional cookies are present. In order for the panel to be displayed, either the library must have blocked at least one element that could insert cookies, or the method PDCookieConsent.blockList() must be used (as detailed in section 3 of the Technical Documentation).
In the initial panel view, visitors can:
– Read the notice informing about the use of cookies.
– Click on the link to the Cookies Policy.
– Accept all website cookies by clicking “Accept”.
– Reject all website cookies by clicking “Reject”.
– Go to the configuration view by clicking “Configure”.
In the configuration panel view, visitors can:
– Return to the previous view by clicking the “← Go back” link.
– View the list of all unpermitted domains and:
– Accept all domains at once by clicking “Accept all”.
– Reject all domains at once by clicking “Reject all”.
– Save changes by clicking “Save settings”.
In addition to the PD Cookie Consent panel, the library also provides a message at the top of the website that informs visitors about blocked visual elements that are not being displayed.
Visitors can:
IMPORTANT
This message primarily refers to blocked iframes.
To include scripts in the message, it is necessary to define the report property with the value true in PDCookieConsent.blockList(). For more details, consult section “3. Blocking DOM elements to prevent them from generating cookies” of the Technical Information document.
NOTE: The message will only appear on pages containing elements that have been blocked and affect the visual layout or interactivity of the site.
To understand how the PD Cookie Consent library works, it is important to note that it does not block or capture any type of cookie directly. PD Cookie Consent does not manage cookies; it manages the elements responsible for inserting cookies into the website (iframes, scripts, and noscripts), as described in the technical documentation.
When a website loads in the browser, various elements are generated to provide functionality, display images, videos, etc. It is through these elements that a wide variety of cookies are generated and installed.
During the website loading process, the library scans each element. When it identifies an iframe, script, or noscript, it analyzes it. If the element contains a forbidden string, it is blocked to prevent loading.
The purpose of this blocking is to prevent cookies from being inserted on the website without the user’s prior consent. For example, if the library blocks a YouTube video, it will not be displayed until the visitor gives permission to activate that blocked iframe.
The library includes a set of predefined strings to enable automatic blocking of elements. Additionally, developers may define their own strings through a method provided in the documentation—ideal for blocking undetected elements or unblocking unnecessarily restricted ones.
At PaynoPain, we collaborate with companies that share our vision of innovation, quality, and technological excellence. If you offer complementary solutions or want to distribute our products, together we can go further. We offer you support, training, and real opportunities for joint growth, with global impact.