This is a translation provided for convenience. The Spanish version of this document is the only binding one; any acceptance or contract refers to the Spanish version. If this translation and the Spanish version differ, the Spanish version prevails. Figures follow Spanish notation: a full stop separates thousands and a comma separates decimals, and numeric dates are written day-month-year. Read the Spanish version
PERSONAL DATA PROCESSING AGREEMENT
(Article 28 of Regulation (EU) 2016/679 (GDPR))
Version 1.5 — 23 October 2026
Data processing agreement under which Socialite Agency acts as PROCESSOR and the Client as CONTROLLER, in relation to the Chatbot IA service. It is accepted together with the Terms, which incorporate it, or signed separately by route 2 of the “Parties” section.
Parties
DATA CONTROLLER (the “Client” or “Controller”): the natural or legal person who accepts this agreement, identified by the details that the Client itself provides when contracting:
- Company name: the one entered in the field “Empresa o razón social” (company or registered business name) in the contracting process (or, if the Client is a sole trader, their first name and surname).
- Tax ID (NIF/CIF): the one entered as “NIF / CIF” in the contracting process.
- Address: the one entered as the registered tax address in the contracting process.
- Contact person: the one entered in the field “Nombre y apellidos” (full name) in the contracting process.
- Contact e-mail (privacy): the e-mail address entered in the contracting process, which will be used for all communications arising from this agreement, including those under clause 5 (sub-processors) and clause 7 (notification of personal data breaches).
These details appear in the order and in the invoice that the Processor issues for each period, and the Processor keeps them linked to the internal client identifier referred to in clause 13, making them available to the Controller on simple request. The Controller may consult or rectify them by writing to info@socialiteagency.com.
Two routes of acceptance, both valid.
- Online: by completing the purchase process on the website
socialiteagency.comand its subdomains (the “Website”) and ticking the acceptance boxes that the Website presents before the order is confirmed, including the specific box for this agreement. The Terms also incorporate this agreement in accordance with their section 2. - In writing: where online contracting is not available to the Client —today, Clients who do not have a Spanish tax identification number or whose registered tax address is not on the Spanish mainland or in the Balearic Islands, in accordance with section 3 of the Terms—, by signing this same document and returning it by e-mail to info@socialiteagency.com. In this case there is no online contracting process from which to take the above details, so the Controller will enter them here:
| Company name | [CAMPO POR RELLENAR] |
| Tax ID (NIF/CIF) | [CAMPO POR RELLENAR] |
| Address | [CAMPO POR RELLENAR] |
| Contact person | [CAMPO POR RELLENAR] |
| Contact e-mail (privacy) | [CAMPO POR RELLENAR] |
| Date of signature | [CAMPO POR RELLENAR] |
(This table is completed only under route 2. Under route 1 it is left blank and the details are those that appear in the order.)
All communications from the Processor provided for in this agreement are sent from info@socialiteagency.com.
DATA PROCESSOR (the “Processor”):
- Holder: Georgina Palma Castillo (self-employed) — trade name “Socialite Agency”
- NIF: 46981988A
- Address: Carrer Països Catalans 10, 08980 Sant Feliu de Llobregat (Barcelona), Spain
- Contact e-mail (privacy): info@socialiteagency.com
Both parties acknowledge that they have sufficient capacity and agree to this agreement, which governs the processing of personal data that the Processor carries out on behalf of the Controller in connection with the provision of the Chatbot IA service (hereinafter, the “Service”), in accordance with Art. 28 GDPR and the LOPDGDD.
1. Purpose and scope
The purpose of this agreement is to authorise the Processor to process, on behalf of the Controller, the personal data necessary to provide the contracted Service, on the terms and to the extent described in Annex I. The Processor will process such data solely on the documented instructions of the Controller, including this agreement, and not for its own purposes.
If the Processor considers that an instruction infringes data protection legislation, it will inform the Controller immediately.
2. Duration
This agreement will remain in force for as long as the Service is provided (the main contractual relationship). Once that has ended, the Processor will proceed in accordance with clause 9 (return or deletion).
3. Instructions and no use for own purposes
The Processor will process the personal data only on the documented instructions of the Controller. In particular, it will not process the data for its own purposes, nor disclose them to third parties except by legal obligation or with the Controller’s authorisation. The Processor may process aggregated and anonymised data —in such a way that they do not allow persons or the Controller to be identified— for statistical purposes and to improve the Service; such anonymised data cease to be subject to this agreement.
Processing required by Union or Member State law (Art. 28.3.a GDPR). Where the Processor is required to process or disclose personal data under Union or Member State law to which it is subject, it will inform the Controller of that legal requirement before processing, unless that law prohibits it on important grounds of public interest.
4. Obligations of the Processor
The Processor undertakes to:
a) Process the data in accordance with the Controller’s documented instructions. b) Ensure that the persons authorised to process the data have committed themselves to confidentiality or are under a statutory obligation of confidentiality. c) Apply the appropriate technical and organisational measures under Art. 32 GDPR (Annex II). d) Assist the Controller, insofar as possible and taking into account the nature of the processing, so that the Controller can respond to data subjects’ requests to exercise their rights (Arts. 15 to 22 GDPR). If a data subject sends a request directly to the Processor, the Processor will forward it to the Controller without undue delay. e) Assist the Controller in complying with its obligations regarding security, breach notification, data protection impact assessments (DPIAs) and prior consultations (Arts. 32 to 36 GDPR), taking into account the information available. f) Make available to the Controller the information necessary to demonstrate compliance with the obligations of Art. 28 and allow for and contribute to audits, on the terms of clause 8. g) Not disclose the data to third parties except on the Controller’s instruction or by legal obligation; where disclosure is imposed by a legal obligation, inform the Controller beforehand of that requirement on the terms of clause 3, unless prohibited by law on important grounds of public interest.
5. Sub-processors (general written authorisation)
The Controller gives general authorisation to the Processor to engage the sub-processors necessary to provide the Service. At the time of acceptance, the sub-processors are those listed in Annex III. The Processor will impose on each sub-processor, by contract, the same data protection obligations as those in this agreement (Art. 28.4 GDPR), and will be liable to the Controller for any failure by its sub-processors to comply.
The Processor will inform the Controller of any addition or replacement of sub-processors with reasonable advance notice (minimum 15 days), giving the Controller the opportunity to object on reasonable and well-founded grounds relating to data protection. If the Controller objects and the objection is well founded, the parties will seek a solution in good faith; failing that, the Controller may terminate the affected part of the Service, without further liability for the Processor.
Updating Annex III. Once the notice period has elapsed without the Controller having raised a well-founded objection, the notified addition or replacement will be incorporated into Annex III and will amend it automatically, without the need for a new signature, the rest of the agreement remaining unchanged. The Processor will at all times keep the current and up-to-date list of sub-processors and will provide it to the Controller on simple request. This mechanism does not impair the right to object regulated in the preceding paragraph.
6. International transfers
Certain sub-processors process data outside the European Economic Area (see Annex III). The Processor guarantees that such transfers have the appropriate safeguards of Chapter V GDPR (adequacy decision of the European Commission, where one exists; Standard Contractual Clauses of the European Commission and/or adherence of the importer to the EU-U.S. Data Privacy Framework, depending on the provider). The Processor will not carry out international transfers other than those arising from the use of such sub-processors without instruction or authorisation from the Controller.
Requests for access from third-country authorities. If the Processor or any of its sub-processors receives from a public authority of a third country a legally binding request for access to the personal data processed on behalf of the Controller, the Processor will: (i) notify the Controller without undue delay, unless the applicable law prohibits it —in which case it will use its best efforts to obtain a waiver of that prohibition and will document the steps taken—; (ii) challenge the request where there are reasonable grounds to consider it unlawful under the law of the requesting country or contrary to Union law, including, where appropriate, the interim remedies available; (iii) limit the disclosure to the minimum strictly necessary, based on a reasonable interpretation of the request; and (iv) keep a record of the requests received and of the response given, and make it available to the Controller and, where appropriate, to the competent supervisory authority. This clause reflects the obligations of clause 15 of the Standard Contractual Clauses and applies irrespective of the provisions of clause 3, which refers to the law of the Union or of its Member States.
7. Notification of personal data breaches
The Processor will notify the Controller without undue delay and, in any event, within 48 calendar hours of the moment at which the Processor becomes aware of a personal data breach. For the purposes of this clause, the period is computed in calendar hours (including weekends and public holidays) and starts at the moment of actual awareness by the Processor, not at the moment the breach occurred. The notification will provide the information available (nature of the breach, categories and approximate number of data subjects and records concerned, likely consequences and measures taken or proposed). This notification allows the Controller to comply, where applicable, with Arts. 33 and 34 GDPR. The obligation to notify the supervisory authority and/or the data subjects lies with the Controller.
8. Audits
The Processor will make available to the Controller the information reasonably necessary to demonstrate compliance with its obligations, including current certifications of its providers (e.g. ISO/IEC 27001, SOC 2, PCI-DSS) where available. The Controller may carry out audits or inspections, itself or through an independent third party bound by confidentiality, on the following reasonable conditions: (i) minimum notice of 30 days; (ii) at most once a year, except at the request of a supervisory authority or following a breach affecting the Controller; (iii) during working hours, without disproportionately disrupting the Processor’s activity; and (iv) with the Controller bearing the reasonable costs of the audit, unless it reveals a serious failure by the Processor to comply with its obligations.
9. Return or deletion of the data on termination
Once the provision of the Service has ended, the Processor will, at the Controller’s choice, return or delete the personal data processed on its behalf, as well as any existing copies, unless retention is required by Union or Member State law. The Controller will have a period of 30 days from termination to request return in a commonly used format; once that period has elapsed without instruction to the contrary, the Processor will securely delete the data.
Real scope of the return (important). The return covers the data that are being retained at that time in accordance with the periods declared in Annex II, and not a complete history of the Service. In particular:
- Conversations: only those of the last 30 days, because they are deleted automatically when that period expires by means of a periodic process. Earlier ones no longer exist and cannot be returned.
- Leads and bookings: they are retained for as long as the Service is provided, and are therefore returned in full.
- Billing data: they are subject to the statutory commercial and tax retention periods and are not deleted on request.
If the Controller needs to keep a longer history of conversations, it must export it during the term of the agreement or agree in writing a different retention period. Actual deletion by the sub-processors will be carried out in accordance with the periods of their respective policies.
10. Obligations of the Controller
The Controller undertakes to: (i) determine the purposes and means of the processing and have a valid legal basis for the processing of the data it manages through the Service; (ii) provide its data subjects with the information required by Arts. 13 and 14 GDPR and, where appropriate, obtain their consent; (iii) give lawful instructions to the Processor; (iv) comply with the regime on special categories of data (Art. 9 GDPR) and children’s data set out below; and (v) not include personal data in the files it uploads to its knowledge base (FAQ documents, catalogues or similar), in its logo or other brand assets, or in the image it uses as the assistant’s avatar, which must be limited to business information. In particular, the avatar will not be a photograph of an identifiable natural person. The Controller acknowledges that such files are stored with a provider declared in the Processor’s Privacy Policy and not listed in Annex III, precisely because they are not expected to contain personal data. If the Controller needs to include personal data in those files, it must notify the Processor in writing beforehand so that the relevant provider is added to Annex III with its location and transfer safeguards before the upload.
10 bis. Special categories of data (Art. 9 GDPR)
The Service is not designed to process special categories of data. This does not prevent the Controller from operating in sectors in which that type of information may appear. The applicable regime is as follows:
(a) Configuration — obligation of the Controller. The Controller will not configure the assistant to request, induce or collect special categories of data (Art. 9 GDPR): in particular, it will not include questions, forms, capture fields or instructions aimed at obtaining information on state of health, diagnoses, treatments, medication, disability, sex life or sexual orientation, racial or ethnic origin, religious or philosophical beliefs, trade union membership, genetic or biometric data. The legitimate purpose of an appointment or consultation may be collected in neutral terms (for example, “reason for the visit” as optional free text), without requiring clinical detail.
(b) Sectors in which such data is inherent — prior notification. If, because of its activity (for example, healthcare, social-healthcare or care), the Controller expects the Service to process special categories of data on a regular or foreseeable basis, it must notify the Processor in writing beforehand. The Controller must have a valid legal basis under Art. 9.2 GDPR (and, where applicable, the LOPDGDD) and be able to demonstrate it. Once the notification is received, the parties will assess before that processing begins whether additional measures are necessary —impact assessment (Art. 35 GDPR), reinforced safeguards, review of the suitability of the sub-processors concerned, or functional limitations— and will document them as a written instruction annexed to this agreement. Until that assessment is completed, the Controller will refrain from configuring the Service for that processing.
(c) Spontaneous disclosure by the end user — realistic acknowledgement. The parties expressly acknowledge that, owing to the conversational nature of the Service, an end user may provide on their own initiative information that constitutes a special category of data (for example, mentioning an ailment when requesting an appointment), without it having been requested by the Controller or by the Processor and without either of them being able to prevent it technically. With regard to that information, the Processor: (i) does not request or induce it; (ii) does not use it for any purpose other than generating the response and providing the Service, and in no case to build profiles, segment, train models or for commercial purposes; (iii) processes it with the measures in Annex II; and (iv) deletes it within the retention period declared for conversations (30 days; deletion is carried out by a daily process, so effective retention may reach up to 31 days). This 30-day period refers to the conversation record; if the Controller configures additional capture fields in accordance with Annex I, the information stored in them will follow the retention period for leads and bookings, and not that for conversations — a further reason not to configure fields that may collect special categories of data. Such spontaneous disclosure does not constitute a breach of paragraph (a) by the Controller.
Children’s data. The Controller will not direct the Service at children nor configure the capture of their data without having a legal basis and the safeguards required by Art. 8 GDPR and Art. 7 LOPDGDD.
11. Liability
Each party will be liable for the damage it causes by failing to comply with its obligations in accordance with Art. 82 GDPR and applicable law. The Controller will hold the Processor harmless against claims, penalties or damage arising from: (i) unlawful instructions from the Controller; (ii) the lack of a legal basis or of information to data subjects; or (iii) the Controller’s failure to comply with its obligations as data controller.
Limit of liability (also applicable where this agreement is signed separately by route 2 of the “Parties” section). To the fullest extent permitted by law, the Processor’s total aggregate liability to the Controller for any reason arising from this agreement is limited to the greater of these two amounts: (a) the amount actually paid by the Controller for the specific product or module to which the claim relates during the twelve (12) months preceding the event giving rise to the liability; or (b) five hundred euros (500 €).
The two foregoing clarifications are expressly agreed: (i) the amount is measured per product, so that liability arising from one module is calculated on what has been paid for that module and not on the Controller’s total billing with the Processor, which could include services unrelated to the matter claimed; and (ii) a minimum amount is set so that the limitation retains real economic content even when the amount paid is zero, which occurs during the installation period provided for in section 3 of the General Terms and Conditions of Contract, in which no charge is made. The greater of the two amounts always applies, never the lesser. The Processor will not be liable for indirect damage, loss of profit, loss of business, of opportunities, of revenue or of goodwill.
These limitations do not exclude or limit liability for wilful misconduct (Art. 1102 of the Civil Code) or for gross negligence, for personal injury caused by negligence, or liability towards data subjects or towards supervisory authorities that data protection legislation mandatorily attributes to each party (Art. 82 GDPR), or any other case that by law cannot be limited.
Relationship with the General Terms and Conditions of Contract and order of precedence. If the parties have also signed the Processor’s General Terms and Conditions of Contract, both documents will be interpreted jointly and consistently; the foregoing limit and that of those Terms are not cumulative, but constitute a single overall limit for the same facts. If the two limits yield different amounts for the same event, the greater of them will apply, so that the limitation never operates below the minimum agreed in this clause. In everything relating to the protection of personal data, this agreement will prevail; in all other respects, the General Terms and Conditions of Contract will prevail. If this agreement is signed separately by route 2 of the “Parties” section, the limit of liability set out in this clause applies fully in its own right, without any need to refer to any other document.
12. Governing law and jurisdiction
This agreement is governed by the data protection legislation of the EU and Spain and, in a supplementary manner, by Spanish law. For any dispute, the parties submit to the Courts and Tribunals of Barcelona, unless mandatory law provides otherwise.
13. Electronic record of acceptance
This agreement is entered into in electronic form, in accordance with Article 28.9 GDPR and Articles 23 and 24 of Law 34/2002, on information society services and electronic commerce.
As proof of acceptance, the Processor keeps an electronic record that records, for each document accepted: the identification of the document and its version, the date and time of acceptance, the e-mail address provided by the Client, an internal client identifier, a technical identifier of the purchase process, and the IP address and the user agent (browser) from which it was accepted.
This record does not contain the Client’s name or company name, NIF/CIF or address: those details appear in the order and in the invoice, and the Processor keeps them linked to the internal client identifier in accordance with the “Parties” section.
The record is generated when the payment process starts and, in any event, upon acceptance. It cannot be modified, and it is not deleted selectively, precisely so that it retains evidentiary value; it is destroyed in its entirety when the period declared in the Processor’s Privacy Policy expires, which also declares the legal basis for this processing.
The Client may request a copy of the record that corresponds to it by writing to info@socialiteagency.com, unless the record is blocked in accordance with the Privacy Policy.
In the processing regulated in this clause the Processor acts as controller, and not on behalf of the Controller: its purpose is to prove the conclusion of this agreement to third parties and before the supervisory authorities.
ANNEX I — Description of the processing
-
Subject matter of the processing: provision of the Chatbot IA Service (conversational assistant integrated as a widget on the Controller’s website).
-
Nature and purpose: receipt and processing of the Controller’s end users’ conversations in order to generate automated responses and, in the plans that include it, capture of contacts and management of bookings.
-
Duration: that of the provision of the Service.
-
Type of personal data:
- Identification and contact data that the end user voluntarily provides in the conversation: name, e-mail and telephone number.
- Content of the messages exchanged with the assistant.
- In plans with bookings: name, e-mail, telephone number and appointment time of the person making the booking.
- Technical session identifier of the visitor, generated only when the visitor sends their first message.
- Technical connection data processed inherently in the provision and security of the Service: IP address, user agent and timestamps, used for routing, protection against abuse and incident traceability.
If the Controller configures the capture of additional fields, these will likewise be subject to this agreement without the need to amend it.
Special categories of data (Art. 9 GDPR). The Service is not designed to process them and the Controller will not configure the assistant to request them. However, the parties acknowledge that an end user may disclose them spontaneously in the conversation; in that case the regime of clause 10 bis applies in full, including their deletion within the retention period declared for conversations. If, because of its activity, the Controller expects regular processing of these categories, the prior notification of clause 10 bis (b) applies.
-
Categories of data subjects:
- End users/visitors of the Controller’s website (the Controller’s potential or existing customers) — main category of the engagement.
- Authorised personnel of the Controller who access the client portal (account and session data), to the extent strictly necessary to give access to the Service and invoice it.
ANNEX II — Security measures (Art. 32 GDPR)
The Processor applies technical and organisational measures appropriate to the risk, relying on providers with recognised certifications, including:
- Encryption of data in transit (TLS/HTTPS) and at rest where the provider supports it.
- Role-based access control and individual credentials; strong authentication where available.
- Hosting of the database (Supabase — Ireland) and of the backend (Render — Frankfurt) in the European Union whenever possible.
- Activity logging and backups in accordance with the providers’ capabilities.
- Providers with ISO/IEC 27001 and/or SOC 2 certifications, and PCI-DSS Level 1 for the payment gateway.
- Incident management and breach notification procedure (clause 7).
- Minimisation in error monitoring: the error detection tool removes the request body and the query string, the IP and credential headers, and redacts e-mails and telephone numbers before sending.
- Scheduled deletion: conversations are deleted automatically in accordance with the retention periods indicated below, by means of a daily process.
- Encryption of the access credentials of portal users and session control with expiry.
Retention periods applied by the Processor (unless otherwise instructed and documented by the Controller, and without prejudice to the statutory retention periods for billing):
| Data | Period |
|---|---|
| Chatbot conversations | 30 days (daily process; up to 31 days) |
| Leads and bookings | For as long as the Service is provided; return or deletion in accordance with clause 9 |
| Technical error logs | Must not contain personal data of end users (see the following note). As regards retention at the provider, Sentry’s official documentation sets 30 days for error events on the Developer plan, which is the one contracted (docs.sentry.io — Data Retention Periods, consulted on 31 July 2026) |
| Billing data | The periods legally required in commercial and tax matters |
Note on error monitoring. The relevant measure is not the provider’s retention period, but that error logs do not contain personal data of end users. The Processor applies a pre-sending filter that removes the request body, the query string, cookies and the IP and credential headers, discards navigation breadcrumbs and redacts the e-mail addresses and telephone numbers that might appear in exception messages. Consequently, the provider’s retention period operates on technical data, not on personal data of the Controller’s data subjects.
If the Controller requires additional measures or different periods, they will be recorded in writing as a documented instruction and annexed to this agreement.
ANNEX III — List of authorised sub-processors
| Sub-processor (entity) | Service | Location of processing | Transfer safeguard (if outside the EEA) |
|---|---|---|---|
| Supabase, Inc. | Database (PostgreSQL): clients, conversations, leads and bookings | EU — Ireland (AWS eu-west-1) | Data in the EU; access/support from the US covered by SCC (Modules 2 and 3) |
| Render Services, Inc. | Backend hosting and computing | EU — Frankfurt (Germany) | Data in the EU (Frankfurt); its DPA provides for transfers outside the EEA where necessary to provide the service, in particular to the US, where it has its main operations; covered by an adequacy decision, where one exists —including the EU-U.S. DPF for adhering US entities—, or, failing that, by SCC (Modules 2 and 3) of its DPA |
| Redis (“Redis Cloud”) | Access sessions and background job queues (technical identifiers and task data; it is not a profile store) | EU — Paris (France), eu-west-3 | Database in the EU (Paris); possible support and operations access from Redis group entities or their sub-processors outside the EEA is covered by an adequacy decision, where one exists, or, failing that, by SCC (Modules 2 and 3) of its DPA |
| Functional Software, Inc. (“Sentry”) | Application error monitoring | EU — Germany (de.sentry.io) | Data in the EU (Germany); the region chosen determines storage only: the provider may process data in the US and in other countries where it or its sub-processors operate, and retains in the US the data provided in support requests; covered by an adequacy decision, where one exists —including the EU-U.S. DPF for adhering US entities—, or, failing that, by SCC (Modules 2 and 3) of its DPA |
| Cloudflare, Inc. | Delivery and security network: CDN, DNS, WAF and anti-abuse protection (Turnstile) of the service; processes data in transit. | Global; its DPA provides that the provider and its sub-processors may process data outside the EEA | SCC + EU-U.S. Data Privacy Framework |
| Cloudflare, Inc. (“Cloudflare R2”) | Object storage (a service distinct from the foregoing): screenshots and generated resources. No copies of conversations are stored. | EU — Western Europe (WEUR); bucket jurisdiction: European Union | Objects stored in the EU (jurisdictional restriction of the bucket, which does not extend to metadata, staff access or request processing); possible access from Cloudflare group entities or their sub-processors outside the EEA is covered by an adequacy decision, where one exists —including the EU-U.S. DPF for adhering US entities—, or, failing that, by SCC (Modules 2 and 3) of its DPA |
| Anthropic, PBC | AI models (API) that generate the chatbot’s responses | United States | SCC (data are not used for training; retention ≤ 30 days) |
| Plus Five Five, Inc. (“Resend”) | Transactional e-mail (sole e-mail provider) | United States | SCC (main basis) + EU-U.S. DPF (“Active — Re-certification under Review”) |
| Google LLC | Speech synthesis (Text-to-Speech) for the assistant — receives only the text of the response | Global | SCC + EU-U.S. Data Privacy Framework |
| Calendly, LLC | Bookings and appointments through the Client’s public link (Pro plan) — processes the name, e-mail, telephone number and time of the person making the booking | United States | SCC + EU-U.S. Data Privacy Framework (active participant, with the status “Active — Re-certification under Review”; certification verified on 14-10-2026, next re-certification 06-10-2027) |
| Stripe Payments Europe, Ltd. / Stripe, LLC | Subscription payments (relationship between the Processor and the Client; does not process data of the Controller’s end users) | EU (Irish entity) + US | SCC + EU-U.S. Data Privacy Framework (Stripe, LLC) |
Note on the scope of this list. Annex III lists the sub-processors that process personal data on behalf of the Controller, in either of the two categories of data subjects declared in Annex I (the Controller’s end users and the Controller’s authorised personnel). It does not include providers that merely store the Controller’s own business assets —for example the image provider where its logo and the documents it itself uploads to its knowledge base are kept—, because under clause 10(v) those files must not contain personal data. Such providers are declared, for transparency, in the Processor’s Privacy Policy.
Note on analytics. The Processor does not use Google Analytics or Google Tag Manager in providing the Service: the assistant does not load analytics tools on the Controller’s website. The analytics that the Processor uses on its own corporate website fall outside the scope of this agreement, since in that processing the Processor acts as controller and not on behalf of the Controller.
The sub-processor lists of each provider and their respective data processing agreements (DPAs) are published on each provider’s official website; the Processor will provide them to the Controller on its request and will periodically reconfirm them.
Acceptance
The parties accept Version 1.5, dated 23 October 2026, made up of fourteen clauses (clauses 1 to 13 and clause 10 bis) and Annexes I, II and III, which form an inseparable part of this agreement.
For the Controller: accepted by the Client on completing the purchase process on the Website and ticking the acceptance boxes that the Website presents before the order is confirmed, including the specific box for this agreement. The date and time of that acceptance, and the version accepted, appear in the electronic record regulated in clause 13. Where acceptance takes place by route 2 of the “Parties” section, the date will be that of the Client’s signature appearing in the table of that section.
For the Processor: Georgina Palma Castillo (Socialite Agency), who offers this agreement on the terms published on the Website and is bound by it from the moment the Client accepts it, without the need for any further act.
Last updated: 23 October 2026.