Skip to main content

Customer Intelligence Layer for E-commerce

SocialScore.io - Header Nav

SocialScore · Legal

Data Processing Agreement

Article 28 GDPR terms between DSNTech LTD (SocialScore), as processor, and the customer, as controller. Accepted online at sign-up together with the Terms of Service.

Version 2.0 · Last updated: October 20, 2026

Please read these terms and conditions carefully before using Our Service.

1. OBJECTIVE AND APPLICATION#

1.1 SocialScore (DSNTech LTD company reg. no.: 207337125; registered seat: Mladost 2 Sofia, Bulgaria, EU; with service product "SocialScore") has entered into an agreement for the Services, being either the SocialScore Terms of Service accepted by Customer online or a separately signed services agreement (the "Agreement"), with its customer ("Customer" or "Controller") that governs the provision of the Services by website SocialScore to Customer. Within the scope of the Agreement, SocialScore will process Customer Data for which Customer is the data controller and SocialScore is the data processor of Customer in accordance with the applicable Data Protection Legislation.

1.2 This DPA forms part of, and complements the provisions of the Agreement and regulates the processing and transferring of Customer Data in the scope specified in Appendix 1 to this DPA. Any issues not regulated by this DPA shall be governed by the provisions of the Agreement. By signing this Agreement or clicking through the click-through mechanism implemented by SocialScore at socialscore.io or by expressing its agreement otherwise, Customer agrees to this DPA and this DPA becomes a binding commitment between Customer and SocialScore. SocialScore records each acceptance together with the version of this DPA, the date and time of acceptance and the user account that accepted it, and makes the accepted version available to Customer in its account and by email. SocialScore does not process Customer Data before this DPA has been accepted.

1.2A SCOPE AND LIMITATIONS - DATA SIGNALS ARE NOT CREDIT ASSESSMENTS

(a) Explicit Disclaimer of Credit Assessment Activities

Notwithstanding any other provision herein, SocialScore explicitly clarifies and represents that:

(i) SocialScore does NOT conduct, provide, or facilitate credit assessments, credit scoring, creditworthiness evaluations, or credit risk determinations as defined in:

  • Regulation (EU) 2016/679 Article 22 (automated individual decision-making)
  • Regulation (EU) 2024/1689 (the AI Act), Articles 6-7
  • Directive (EU) 2023/2225 (Consumer Credit Directive), as transposed into national law
  • Any national consumer credit, lending, or financial services regulations

(ii) Data Signals provided by SocialScore are informational indicators only - fraud risk assessments, a breach exposure flag from a lawful third-party service used only for fraud prevention, Customer's own historical query data, marketing segmentation, and behavioral clustering - and are explicitly NOT:

  • Credit scores or ratings
  • Credit decisions or recommendations
  • Creditworthiness or credit risk opinions
  • Suitability determinations for lending or credit products
  • Legal conclusions regarding financial capacity
  • Binding or deterministic risk assessments

(iii) SocialScore shall NOT transfer Customer Data or Data Signals to:

  • Credit bureaus or credit reference agencies
  • Credit intermediaries or credit brokers
  • Financial services providers for credit or lending purposes
  • Other entities for credit decision-making

This restriction applies irrespective of any instruction of the Controller.

(b) Permitted Use of Data

The Services are limited to fraud prevention, marketing intelligence, and risk signal generation. Any other use of Customer Data by SocialScore requires prior written Controller consent.

(c) AI Act Compliance

To the extent SocialScore operates any High-Risk AI System under Regulation (EU) 2024/1689, this compliance is declared in Section 3.1 below. Controller acknowledges that its own use of Data Signals may trigger AI Act obligations for Controller, which are not the responsibility of SocialScore except as expressly stated herein.

(d) Controller's Corresponding Obligations

The uses of the Services and of Data Signals that are prohibited for Controller are set out in Section 8.7.

1.3 The objective of this DPA is to comply with the requirements in the Data Protection Legislation for a written agreement between data controllers and data processors.

1.4 Parties state that the Standard Contractual Clauses specified in Appendix 3 shall apply to the transfer from SocialScore to Customer of any Customer Data (including the processing thereof) if Customer is outside the EEA and its processing does not fall within the scope of the Data Protection Legislation, whereas Clause 14 and 15 of the Standard Contractual Clauses specified in Appendix 3 shall apply to such transfer provided additionally that SocialScore combines Customer Data received from Customer with Customer Data collected by SocialScore in the EEA. Parties agree that when Standard Contractual Clauses specified in Appendix 3 apply to the processing and transfer of Customer Data, the other provisions of this DPA complement the provisions of Standard Contractual Clauses specified in Appendix 3 to the fullest extent permitted by law and by the provisions of the Standard Contractual Clauses specified in Appendix 3. Where the other provisions of the DPA contradicts the provisions of the Standard Contractual Clauses specified in Appendix 3, the Standard Contractual Clauses specified in Appendix 3 shall prevail.

1.5 No Independent Controller Processing and No Pooling. SocialScore processes Customer Data solely as processor on behalf of Customer. SocialScore does not combine Customer Data with personal data processed for other customers, does not maintain a database of identifiers, query history or fraud flags shared across customers, and does not use Customer Data to provide services to any other customer, except in the form of anonymised statistics under Section 3.3. The Data Sharing Addendum for the History, Flag and Marketing Persona functionalities previously published together with this DPA is discontinued as of the effective date of version 2.0 of this DPA and no longer applies. Personal data processed by SocialScore under that addendum before that date shall be deleted or irreversibly anonymised within 30 days of that date.

2. DEFINITIONS#

2.1 The terms used in the DPA shall have the same meaning as assigned to them below and in the Data Protection Legislation, which inter alia imply that:

(a) The term "Controller's Email Address" means any email address provided for Controller's user accounts with "administrator" role created at socialscore.io pursuant to the Agreement. If Controller accesses the Services without having created an account, Controller's Email Address means any email address that SocialScore has on file of Controller;

(b) The term "Documentation" means the documentation of the Services as amended from time to time and available at: User Docs (socialscore.io);

(c) The term "DPA" means this data processing agreement together with its Appendices, and other documents explicitly referenced herein;

(d) The term "data controller" means anyone who alone or jointly with others determines the purposes and means of the processing of personal data;

(e) The term "data processor" means anyone who processes personal data on behalf of the data controller;

(f) The term "Data Protection Legislation" means the applicable data protection legislation. As from 25 May 2018, Regulation (EU) 2016/679 of the European Parliament of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation; the "GDPR") and such national legislation implementing the GDPR is the applicable data protection legislation;

(g) The term "data subject" means identified or identifiable natural person;

(h) The terms "European Economic Area" or "EEA" means the economic area consisting of the territory of the EU Member States and the member states of the European Free Trade Association (Iceland, Liechtenstein and Norway), excluding Switzerland.

(i) The terms "EU Member States" means then-current member states of the European Union.

(j) The term "personal data" means any information that, directly or indirectly, can identify a living natural person;

(k) The term "Customer Data" means personal data that is processed by SocialScore on behalf of Customer;

(l) The term "Personal Data Breach" means breach of data security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data transmitted, stored or otherwise processed, as defined by GDPR;

(m) The term "processing" means any operation or set of operations performed with regard to personal data, whether or not performed by automated means, for example collection, recording, organisation, storage, adaptation or alteration, retrieval, gathering, use, disclosure by transmission, dissemination or otherwise making information available, alignment or combination, restriction, erasure or destruction;

(n) The term "Services" mean SocialScore's marketing insight & fraud prevention services as provided from time to time;

(o) The term Standard Contractual Clauses means the standard agreement for Customer Data transfers (as defined in Data Protection Legislation) concluded between a data exporter and a data importer that fulfils the requirements of Article 46 GDPR, in particular the standard agreement as adopted by the European Commission by

Commission Implementing Decision (EU) 2021/914 of 4 June 2021 on standard contractual clauses for the transfer of personal data to third countries pursuant to Regulation (EU) 2016/679 of the European Parliament and of the Council ("Commission Implementing Decision (EU) 2021/914") as applicable to the situation at hand, provided that the referenced standard agreement may be deemed to provide appropriate safeguards within the meaning of Article 46(1) of GDPR pursuant to Article 4 of Commission Implementing Decision (EU) 2021/914.

(p) The term "sub-processor" means a processor that is engaged by SocialScore. The sub-processor processes Customer Data on behalf of Controller in accordance with the sub-processor's obligation to provide its services to SocialScore;

(q) Data Signals: The term "Data Signals" means all informational outputs provided by SocialScore to Controller, including risk indicators, fraud flags, a breach exposure flag from a lawful third-party service used only for fraud prevention, Controller's own historical query data (Storage Mode only), marketing segmentation classifications, and behavioral insights. Data Signals are explicitly NOT credit assessments, credit scores, or creditworthiness evaluations, and carry no binding or deterministic status.

(r) AI Act: The term "AI Act" means Regulation (EU) 2024/1689 of the European Parliament and of the Council of 13 June 2024 on artificial intelligence, as amended or supplemented, applicable to both parties' processing activities and use of personal data through artificial intelligence and automated systems.

(s) High-Risk AI System: The term "High-Risk AI System" means an AI system classified as high-risk under Article 6 of the AI Act, including the use cases listed in its Annex III. For clarity, AI systems used for the purpose of detecting financial fraud are excluded from Annex III, point 5(b), of the AI Act.

(t) Credit Assessment: The term "Credit Assessment" means any systematic evaluation, analysis, or determination of an individual's creditworthiness, repayment capacity, credit risk, credit rating, or suitability for credit products, as defined in consumer credit and financial services regulations. This term explicitly excludes Data Signals and non-binding risk indicators provided by SocialScore, and excludes fraud risk assessments provided for fraud prevention purposes.

(u) Pass-Through Mode: the configuration of the Services that applies by default, in which Customer Data is processed only transiently in order to return a query result and is not stored by SocialScore after delivery of that result, except in the Check Log under Section 3.4.

(v) Storage Mode: the optional configuration of the Services, activated by Controller, in which query results and enriched profiles are stored in Controller's account.

(w) Pixel: the SocialScore JavaScript tag that Controller may install on its own websites to measure visits and interactions.

(x) Account-Presence Check: a check described in Section 6.3.

(y) Check Log: the log of checks described in Section 3.4.

3. UNDERTAKING AND INSTRUCTION#

3.1 COMPLIANCE WITH AI ACT AND DATA CLASSIFICATION

(a) AI System Compliance by SocialScore. SocialScore's Services are limited to fraud prevention, marketing intelligence and the generation of non-binding risk signals. The provision of Data Signals does not constitute, and SocialScore does not operate, a High-Risk AI System for credit assessment or credit scoring purposes. To the extent any component of the Services were to constitute a High-Risk AI System under the AI Act, SocialScore shall comply with the obligations applicable to it as provider under the AI Act and shall, on a commercially reasonable basis, maintain documented risk-management, data-governance, technical-documentation, human-oversight and bias-monitoring measures appropriate to such system. SocialScore shall provide Controller with reasonable cooperation and documentation to support Controller's own compliance.

(b) AI Act Compliance by Controller

Controller acknowledges that:

(i) Controller's use of Data Signals or SocialScore outputs in automated decision-making may itself trigger AI Act or GDPR Article 22 obligations for Controller, which are not the responsibility of SocialScore.

(ii) If Controller uses Data Signals in any High-Risk AI System under the AI Act, Controller shall implement its own risk management systems; conduct Data Protection Impact Assessments (DPIA); implement human oversight and override mechanisms; register the system in EU AI Register if required; and maintain compliance documentation.

(iii) SocialScore's provision of Data Signals does not relieve Controller of these obligations, and Controller remains fully liable for downstream use and compliance.

(c) Transparency and Information Exchange

SocialScore shall:

(i) Provide Controller with reasonable transparency regarding the nature of AI processing applied to Customer Data; the categories of Data Signals and what they indicate; the categories of sources used; and known limitations. SocialScore is not required to disclose its trade secrets, source code or model parameters.

(ii) Notify Controller within 10 business days of significant changes to AI algorithms or processing methods; discovery of bias or discrimination concerns; regulatory investigations or enforcement actions; and material accuracy issues identified through testing.

(iii) Provide documentation upon reasonable request to support Controller's DPIAs, AI Act assessments, and regulatory compliance.

(d) Data Minimization in AI Training

SocialScore warrants and undertakes:

(i) NOT to use Customer Data to train, test, validate, or improve any AI models intended for credit assessment, lending, insurance underwriting, or any purpose other than those explicitly authorized in this Agreement.

(ii) If SocialScore uses Customer Data to train AI models for authorized purposes (fraud detection, marketing segmentation), to apply data minimization techniques; remove or anonymize Customer-identifying information before training; restrict model use to authorized purposes only; document all training data sources and usage; and periodically audit for unintended uses or downstream applications.

(iii) NOT to sell Customer Data and NOT to use Customer Data to build or improve products or services for any other customer, except in anonymised form in accordance with (ii) and Section 3.3.

3.2 SocialScore undertakes:

(a) to process and transfer Customer Data in accordance with the Data Protection Legislation, the Agreement and as further documented in any other written instructions given by Controller and acknowledged by SocialScore as constituting instructions for purposes of this DPA; Controller's documented instructions also include the configuration choices Controller makes in the Services, in particular the selection of Pass-Through Mode or Storage Mode, the retention settings and the Pixel settings;

(b) to inform Controller prior to processing that SocialScore is required by laws of the European Union or EU Member States, to which SocialScore is subject, to process Customer Data, provided that SocialScore is not prohibited to give such information on important grounds of public interest;

(c) to immediately inform Controller if, in its opinion, an instruction of Controller infringes applicable Data Protection Legislation. SocialScore will be under no obligation to follow such instruction, until the matter is resolved in good-faith between the parties;

(d) to keep Customer Data confidential and ensure that persons authorised to process Customer Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality;

(e) to implement all appropriate technical and organisational measures necessary in order to ensure a level of security, as required pursuant to the Data Protection Legislation, and necessary in order for SocialScore to comply with the security requirements set out in Appendix 1 of the DPA. SocialScore shall notify Controller about changes in the applied technical and organizational security measures that significantly affect the security of the processing of Customer Data;

(f) to assist Controller in the fulfilment of Controller's obligation to respond to and to fulfil requests from data subjects exercising their rights laid down in the Data Protection Legislation taking into account the nature of the processing, by implementing appropriate technical and organisational measures, insofar as this is possible. SocialScore shall notify Controller in case of receiving a request to exercise the data subjects' rights under the Data Protection Legislation without undue delay after receiving such request, and SocialScore should reasonably cooperate with Controller in addressing such request. Unless Controller otherwise instructs SocialScore, the notification of such request shall be sent to Controller's Email Address. If Controller provided more than one Controller's Email Address, notification sent to at least one of Controller's Email Address shall be sufficient to comply with this section. SocialScore is not responsible or liable for responding to the data subject;

(g) to assist Controller in the implementation of appropriate technical and organisational measures, the notification of a Personal Data Breach to data protection supervisory authorities and affected data subjects, preparation of data protection impact assessments and prior consultation with data protection supervisory authorities. SocialScore shall make available to Controller all information necessary to demonstrate compliance with applicable Data Protection Legislation, to the extent Controller does not otherwise have access to the relevant information, and that such information is available to SocialScore. Except for negligible costs, SocialScore reserves the right to claim the reimbursement of costs and expenses incurred by SocialScore in connection with the provision of assistance to Controller under this DPA;

(h) to inform and consult with Controller without undue delay in the event that a data protection supervisory authority initiates or takes any action in relation to SocialScore with regard to the processing of Customer Data;

(i) to process Customer Data only until the purposes of the processing for which the data was collected have been fulfilled. In Pass-Through Mode, which applies by default, SocialScore does not store Customer Data after the query result has been delivered, except in the Check Log under Section 3.4. In Storage Mode, SocialScore stores Customer Data at the latest until 1 year starting from the completion of the query to which Customer Data relate, or for such shorter period as Controller configures. Pixel data is kept for 30 days by default, or for such other period as Controller configures within the limits offered by the Services. Upon the expiration of the applicable period, SocialScore shall delete or anonymize Customer Data, unless it follows from the requirements of European Union law or EU Member State law that SocialScore is required to store Customer Data for a longer period;

(j) to maintain a record of all categories of processing activities carried out on behalf of Controller in accordance with Article 30(2) GDPR; and

(k) to make available to Controller the contact point for data protection matters at SocialScore: dpo@socialscore.io.

3.3 Anonymised Statistics

Controller instructs and authorises SocialScore to create anonymised statistics from Customer Data, such as the share of identifiers present on a given online platform, or the distribution of interest and lifestyle categories by country or sector. To create them, SocialScore removes all identifiers, including names, email addresses, phone numbers, IP addresses, postal addresses and any hash or other key that could link a record back to an individual, so that no individual can be identified by anyone, in line with Recital 26 GDPR. Anonymised statistics are not personal data and are not Customer Data. SocialScore may use them to provide market analyses and benchmarks to its customers and to improve the Services, only in aggregated form that identifies neither an individual nor Controller. SocialScore shall not attempt to re-identify any individual from anonymised statistics.

3.4 Check Log

In all modes, SocialScore keeps a log of the checks performed for Controller. In the Check Log, identifiers are stored only in hashed (pseudonymised) form, together with the time of the check and the result returned. SocialScore uses the Check Log solely to document the Services provided to Controller, to handle Controller's support requests and disputes, to verify billing, and to protect the Services against abuse and security incidents. The Check Log is kept separately for each Controller, is not shared with or used for any other customer, and is deleted 30 days after the check. Hashing is a security measure: the Check Log remains personal data and is processed in accordance with this DPA.

4. AUDIT#

4.1 SocialScore shall facilitate and participate in audits, including inspections, carried out by Controller or by a third party authorised by Controller. If Controller uses a third party to carry out the audit that third party shall be a well-regarded international service provider that is not a competitor of SocialScore. Controller and third party authorised by Controller shall undertake confidentiality in relation to SocialScore's confidential information prior to the audit. The details of the audits are subject to the prior approval of SocialScore, which shall not be unreasonably withheld. Controller shall carry out the audits at its own costs. Audits shall take place no more than once in any 12-month period, except where required by a supervisory authority or following a Personal Data Breach affecting Customer Data, on at least 30 days' prior written notice, during normal business hours and without unreasonable disruption to SocialScore's operations.

4.2 SocialScore may satisfy the audit obligation under this section by providing Customer with written answers to a reasonable security questionnaire, the description of measures in Appendix 1, and, where available, certifications or audit reports of SocialScore or of its sub-processors (such as the ISO/IEC 27001 certifications of Google Cloud). An audit under Section 4.1 takes place where this information is not reasonably sufficient to demonstrate compliance with this DPA.

5. ENGAGING SUB-PROCESSORS#

5.1 Controller provides a general authorization to SocialScore to engage or replace a sub-processor for the performance of its duties and responsibilities under this DPA in accordance with the provisions of this section.

5.2 The list of current sub-processors is attached as Appendix 2 to this DPA. Controller hereby provides written authorization to use sub-processors listed in Appendix 2.

5.3 SocialScore shall inform Controller of any intended addition or replacement of a sub-processor by email to Controller's Email Address and by updating Appendix 2, at least 14 days before the change takes effect. Controller may object to any new sub-processors within 14 days starting from the date of that notice. Any objection made by Controller regarding the use of any sub-processors has to be reasonable. SocialScore will within its discretion make all reasonable efforts necessary to accommodate the requests of Controller. If it is commercially reasonable SocialScore will review the possibility of finding another, equivalent sub-processor. If the Parties cannot resolve a reasonable objection, Controller may terminate the affected Services with effect from the date of the change, without penalty.

5.4 SocialScore and the sub-processor shall enter into a written data processing agreement that imposes substantively equivalent obligations on the sub-processor as those specified in this DPA and SocialScore shall ensure that the sub-processor provide appropriate level of protection for Customer Data as required by the Data Protection Legislation.

5.5 Controller authorizes SocialScore to engage sub-processors which process Customer Data in a country outside the European Economic Area. Provided that the European Commission has not determined, in accordance with the Data Protection Legislation, that such country ensures an adequate level of protection to the processing of Customer Data, SocialScore undertakes to provide appropriate safeguards when transferring Customer Data to such sub-processors, in particular, to conclude Standard Contractual Clauses and to take all necessary steps to ensure that the transfer is lawful under the Data Protection Legislation.

6. PUBLIC DATABASES AND PUBLICLY AVAILABLE PERSONAL DATA#

6.1 Controller acknowledges that carrying out real-time queries from public databases and collecting publicly available information from social media providers constitutes an inherent part of certain functionalities of the Services. Controller acknowledges and authorizes SocialScore to use public database providers (in particular, DNSBL providers, lawful security and compromise disclosure registries, sanction lists, etc.), and social media providers established within or outside the EEA to carry out queries on the basis of Customer Data and collect publicly available personal data to be able to provide the Services to Controller. Parties agree that in their assessment public database providers and social media providers shall be considered data controllers or third parties under the Data Protection Legislation.

6.2 Lawful Justification and Parameters for Breach Exposure Flags

Where the Services process indicators regarding whether an identifier has appeared in historical security incidents, the Parties expressly agree and document that:

(a) Specific Nature: Such data constitutes exclusively a breach exposure flag from a lawful third-party service, used only for fraud prevention.

(b) Legal Ground: Pursuant to Article 6(1)(f) and Recital 47 of the GDPR, processing strictly necessary for preventing fraud, combating unauthorized account creation, and ensuring network and information security constitutes an acknowledged legitimate interest.

(c) Prohibition of Illicit Repositories: SocialScore does not collect, crawl, trade, purchase, or maintain raw hacker dumps, stolen databases, or plaintext credentials. Queries are executed strictly against reputable, lawful third-party security verification services solely to ascertain whether a contact point has been exposed in public disclosures.

(d) Data Minimization: Output provided to Controller is limited to a non-sensitive informational security indicator (such as binary exposure presence or compromise date), excluding compromised credentials or personal contents, in strict compliance with Article 5(1)(c) GDPR.

(e) Strict Purpose Limitation: Controller warrants that breach exposure flags shall be utilized solely for defensive pre-KYC verification, account protection, and fraud defense, and shall never be utilized for credit assessment, creditworthiness scoring, or automated contract refusals.

6.3 Account-Presence and Public Profile Checks

Certain Data Signals indicate whether an identifier submitted by Controller is associated with a publicly visible profile on an online platform, and summarise the information that such profile publicly shares. SocialScore performs these checks only on information that the platform makes publicly available. SocialScore does not log in to accounts, does not use or store credentials of data subjects, does not access private content or private messages, and does not circumvent the access controls of any platform.

7. REPORTING PERSONAL DATA BREACH#

7.1 If SocialScore becomes aware of any Personal Data Breach, SocialScore shall notify Controller without undue delay after becoming aware and, in any event, within seventy-two (72) hours, and shall fully cooperate in order to reasonably remedy the issue. The notification shall include all available significant information on the circumstances of the Personal Data Breach, including, to the extent available, the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, the measures taken or proposed, and a contact point. Where not all information is available at once, SocialScore may provide it in phases without undue further delay.

7.2 The notification on Personal Data Breach shall be sent to Controller's Email Address. If Controller provided more than one Controller's Email Address, notification sent to at least one of Controller's Email Address shall be sufficient to comply with this section.

7.3 SocialScore is not responsible or liable for notifying to any data protection supervisory authorities or inform data subjects about Personal Data Breach.

8. RESPONSIBILITIES OF CONTROLLER#

8.1 Controller shall have sole responsibility for the accuracy, quality, and legality of Customer Data, the means by which Controller acquired Customer Data and for all other obligations imposed on Controller by Data Protection Legislation.

8.2 Taking into account the nature, scope, context and purposes of processing as well as the risks of varying likelihood and severity for the rights and freedoms of natural persons, Controller shall implement appropriate technical and organisational measures to ensure and to be able to demonstrate that processing is performed in accordance with the Data Protection Legislation. Those measures shall be reviewed and updated where necessary. Where proportionate in relation to the processing, the above measures shall include the implementation of appropriate data protection policies by Controller.

8.3 Controller shall inform the data subjects in accordance with Article 13-14 of the GDPR.

8.4 Controller shall secure all necessary permissions, authorizations and consents for processing Customer Data and ensure that the processing of Customer Data is based on a valid legal basis provided in the Data Protection Legislation.

8.5 Controller shall comply with the above Section 8.1-8.4 only if Controller falls within the scope of the Data Protection Legislation.

8.6 Pass-Through / Gateway Configuration: The Customer acknowledges that the Services operate by default in "Pass-Through Mode", whereby SocialScore processes Customer Data solely on a transient basis in order to return a query result and does not store or retain Customer Data after delivery of that result. The selection of any configuration that enables storage, retention, history or look-back functionality (Storage Mode), is a configuration choice made and controlled by the Customer. Where the Services operate in Pass-Through Mode: (a) SocialScore does not retain Customer Data, other than in the Check Log under Section 3.4, and is neither controller nor processor of any copy of Customer Data or query results stored by the Customer; (b) the Customer is solely responsible, as controller, for the storage, retention, security, accuracy, legal basis and downstream use of query results and any Customer Data retained on the Customer's own systems; and (c) SocialScore shall have no liability for any claim, loss or breach to the extent arising from the storage, retention or downstream processing of Customer Data or query results on the Customer's systems or under the Customer's control. SocialScore remains responsible for its own processing of Customer Data during the transient handling of a query in accordance with this DPA and applicable law.

8.7 Prohibited Uses. Controller shall not use the Services or any Data Signal, directly or indirectly: (a) to assess the creditworthiness of natural persons, to establish or support a credit score, or to predict affordability, repayment or default, including for buy-now-pay-later, instalment, leasing, overdraft or credit-limit products, or as an input to any credit model or credit decision rule; (b) to decide on, price or limit insurance, employment, housing, education or access to public services; (c) as the sole or determining factor in a decision producing legal effects or similarly significantly affecting a natural person, without meaningful human review; (d) to infer special categories of personal data or to target natural persons on the basis of a vulnerability; (e) to locate, monitor or profile natural persons for third parties, for background checks or employee screening, or in relation to persons with whom Controller has no actual or prospective customer relationship; (f) in relation to identifiers that Controller knows or should know belong to persons under 18 years of age; (g) to resell or redistribute Data Signals or to build a competing database or product; or (h) without a valid legal basis and the notices required under Section 8.8, or otherwise in breach of applicable law.

Breach of this Section 8.7 entitles SocialScore to suspend the Services immediately and to terminate the Agreement and this DPA with immediate effect. Controller shall indemnify SocialScore against all claims of third parties, including data subjects and authorities, and against all reasonable costs arising from such breach, to the extent permitted by law. The limitation in Section 9.1(b) does not apply to Controller's obligations under this Section 8.7.

8.8 Transparency, Consent and Pixel. Before submitting identifiers to the Services or installing the Pixel, Controller shall ensure that: (a) data subjects are informed in accordance with Articles 13 and 14 GDPR, including of the categories of personal data obtained through the Services and the categories of sources; (b) consent is obtained where Controller's use requires it, in particular where Controller uses the Services to enrich customer profiles for marketing purposes without another valid legal basis; and (c) the Pixel is activated on a visitor's device only after the visitor's consent has been obtained where required under Article 5(3) of Directive 2002/58/EC and its national implementation. SocialScore makes template notices available on its website; their adaptation and use remain Controller's responsibility.

8.9 Declared Use Case. Controller confirms the use case it declared when registering for the Services (fraud prevention, marketing insight, or both) and shall update that declaration in its account before using the Services for another permitted purpose.

9. LIMITATION OF LIABILITY#

9.1 Subject to the Section 9.2, neither party shall be responsible or liable under this DPA to the other party:

(a) for any indirect, exemplary, incidental, punitive, special or consequential damages; or

(b) for any amounts that exceed the fees actually paid or payable by Controller to SocialScore under the Agreement in the twelve (12) months prior to the act that gave rise to the relevant claim.

9.2 The limitation of liability provisions of the Agreement shall prevail over Section 9.1, and shall be applied mutatis mutandis in the context of this DPA.

9.3 Subject to Sections 1.4 and 9.2, the responsibility and the liability of the parties shall be regulated by the applicable laws, in particular the Data Protection Legislation and the applicable civil law provisions.

9.4 Nothing in this DPA limits or excludes liability that cannot be limited or excluded under applicable law, including liability for intent or gross negligence under Article 94 of the Bulgarian Obligations and Contracts Act, or the rights of data subjects under Article 82 GDPR.

10. TERM, TERMINATION#

10.1 The DPA is effective from the date SocialScore starts processing Customer Data and for as long as SocialScore processes Customer Data.

10.2 Parties may terminate this DPA anytime for any reason by providing thirty (30) days' notice to the other party. Controller acknowledges that SocialScore will be under no obligation to provide the Services, until a Data Protection Legislation compliant data processing agreement is concluded between the parties.

10.3 Within thirty (30) days from the expiration of the Agreement or the receipt of the notice of termination, SocialScore shall delete (or anonymize) or, based on Controller's instruction, return to Controller all Customer Data, and delete (or anonymize) existing copies unless the storage of Customer Data is required pursuant to European Union law or EU Member State's law.

10.4 All provisions of this DPA that are expressly or consequently intended to be fulfilled or remain in force following the termination of this DPA shall fully remain in force following the termination of this DPA, in particular, Section 2 (Definitions), Section 8 (Responsibilities of Controller), Section 9 (Limitation of Liability), Section 10 (Term, Termination), Section 11 (Miscellaneous).

11. MISCELLANEOUS#

11.1 Governing Law and Dispute Resolution. This DPA shall be governed by and construed in accordance with the laws of Bulgaria and the courts of Bulgaria shall have jurisdiction over any dispute, or claim arising out of, or in connection with this DPA, including its formation. Disputes regarding interpretation and application of this DPA shall be settled in accordance with the provisions in the Agreement regarding dispute resolution.

11.2 Amendments. This DPA shall be amended in accordance with the Agreement's provisions on amendments.

11.3 Severability. Should any provision of this DPA be invalid or unenforceable, then the remainder of this DPA shall remain valid and in force. The invalid or unenforceable provision shall be either: (i) amended as necessary to ensure its validity and enforceability, while preserving the parties' intentions as closely as possible or, if this is not possible; (ii) construed in a manner as if the invalid or unenforceable part had never been contained therein.

11.4 Entire Agreement. This DPA, together with its Appendixes supersedes and repeals all current or prior oral or written undertakings, covenants, agreements or communications, in particular all current or prior data processing agreements and data sharing addenda between Controller and SocialScore with respect to the subject matter of this DPA.

11.5 Order of Precedence. In the event of a conflict, the Standard Contractual Clauses prevail over this DPA, and this DPA prevails over the Agreement on matters of data protection, save as provided in Section 9.2.

APPENDIX 1 - DETAILS OF THE PROCESSING OF PERSONAL DATA#

1. THE SUBJECT MATTER OF THE PROCESSING

Providing the Services of SocialScore, including Marketing Intelligence and Fraud Prevention.

2. THE NATURE AND PURPOSE OF THE PROCESSING

Fraud prevention by carrying out the processing as described in the Documentation, Fraud Risk Assessment, Marketing Segmentation, website analytics through the Pixel where installed by Controller, and IT support, debugging the Services.

2.1 Primary Processing Purposes

SocialScore shall process Customer Data exclusively for the following purposes:

(a) Fraud Prevention: Real-time analysis to identify and flag fraudulent or high-risk transactions, account applications, or interactions, including the provision of a breach exposure flag from a lawful third-party service, used only for fraud prevention;

(b) Marketing Segmentation: Clustering and behavioral analysis to support Customer's marketing targeting and audience profiling;

(c) Risk Signal Generation: Provision of informational risk indicators to support Customer's independent decision-making;

(d) Service Optimization: IT support, system debugging, and platform performance improvement;

(e) Data Subject Rights Fulfillment: Processing necessary to respond to data subject requests under GDPR Articles 15-22 and AI Act requirements;

(f) Website Analytics: where Controller installs the Pixel, measurement of visits and interactions on Controller's websites for analytics and audience segmentation;

(g) Anonymised Statistics: anonymisation and aggregation of Customer Data in accordance with Section 3.3 of the DPA;

(h) Check Log: documentation of the checks performed for Controller in accordance with Section 3.4 of the DPA.

2.2 Processing Methods and Technologies

SocialScore processes Customer Data through:

(a) Real-time queries against publicly available databases and social media sources (with appropriate terms of service compliance);

(b) Matching against rules, reference lists and models maintained by SocialScore, which do not contain Customer Data of other customers;

(c) Statistical analysis, rule-based decision trees, and anomaly detection;

(d) Machine learning-based clustering, classification, and behavioral prediction (where applicable);

(e) Automated flagging and scoring systems for fraud prevention and marketing segmentation only, maintained within SocialScore's secure infrastructure;

(f) Data minimization and pseudonymization where technically feasible;

(g) Account-Presence Checks as described in Section 6.3 of the DPA.

2.3 CRITICAL LIMITATION: Data Signals Are NOT Credit Assessments

SocialScore explicitly does NOT:

  • Calculate, assign, or modify credit scores
  • Conduct creditworthiness or credit risk assessments regulated under consumer credit laws
  • Make or recommend credit decisions
  • Return approve or decline outcomes, credit amounts, repayment terms or probabilities of default
  • Provide binding or deterministic legal conclusions regarding risk or suitability
  • Perform assessment activities regulated under Article 22 GDPR or AI Act Articles 6-7
  • Maintain a database of personal data shared across customers

SocialScore DOES provide:

  • Data Signals - informational indicators designed exclusively to assist Customer's independent decision-making in fraud prevention and marketing
  • Risk assessments for fraud prevention purposes only
  • Historical and behavioral data to support Customer intelligence
  • Marketing insights and segmentation data

These outputs carry no binding force, carry no guarantee of accuracy, and do not constitute financial, credit, or legal determinations.

2.4 AI Processing

To the extent any AI systems used in Service delivery were to fall within the scope of the AI Act, SocialScore shall comply with the obligations applicable to it and shall maintain, on a commercially reasonable basis, appropriate risk-management, data-governance and quality, technical-documentation, record-keeping, human-oversight and bias-monitoring measures. Where material bias is identified through such monitoring, SocialScore shall document and pursue remediation within a reasonable period. SocialScore does not operate AI systems for credit assessment or credit scoring purposes.

3. CATEGORIES OF DATA SUBJECTS

The users of the services of Controller, Controller's prospective customers whose identifiers Controller submits, and visitors of Controller's websites where the Pixel is installed.

4. CATEGORIES OF PERSONAL DATA

As described in the Documentation, including identifiers (email, phone, IP), public digital footprint indicators, verification flags, and a breach exposure flag from a lawful third-party service used only for fraud prevention.

Pixel data: IP address truncated at ingestion (last octet removed), hashed device identifier (the raw value is deleted immediately), pages visited and interaction events. No names, email addresses or phone numbers are collected through the Pixel.

Special Categories of Personal Data: Processing of special categories of personal data pursuant to Article 9 GDPR (revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data for unique identification, health, or sex life/sexual orientation) is strictly excluded. Consumer interest categories are limited to general behavioral and lifestyle classifications (e.g. Lifestyle). National identification numbers, payment card data and bank account data of data subjects are not processed.

5. DURATION OF PROCESSING

Pass-Through Mode (default): transient processing only; no storage after the query result is delivered, other than in the Check Log. Check Log: 30 days from the check, identifiers in hashed form only. Storage Mode (optional): until deleted by Controller, and at the latest 1 year from the completion of the query, after which the data is deleted. Pixel data: 30 days by default, configurable by Controller. End of the Agreement: deletion or return under Section 10.3 of the DPA. Anonymised statistics under Section 3.3 of the DPA are not personal data and are not subject to these periods.

6. TECHNICAL AND ORGANISATIONAL SECURITY MEASURES

SocialScore implements the measures below, which are aligned with the principles of ISO/IEC 27001:2022. SocialScore is not certified under ISO/IEC 27001. SocialScore regularly tests, assesses and evaluates the effectiveness of these measures, at least once a year, in accordance with Article 32(1)(d) GDPR.

6.1 Baseline Security Measures

(a) Hosting and Encryption: Customer Data is hosted on Google Cloud and Firebase infrastructure in the EU. Data at rest is encrypted by default (AES-256) by the hosting provider. Data in transit is protected with TLS 1.2 or higher.

(b) Access Control: access to production systems is limited to named, authorised personnel on a least-privilege basis, through individual accounts with multi-factor authentication, and is removed when no longer needed.

(c) Logging: administrative access to production systems is logged through the audit logging of the hosting provider.

(d) Incident Response: security incidents are handled under an incident response procedure covering detection, containment, assessment, notification to Controller under Section 7 of the DPA, documentation and corrective action.

(e) Vulnerability Management: timely application of security updates to systems and software dependencies; infrastructure patching managed by the hosting provider.

(f) Personnel: confidentiality undertakings from all persons with access to Customer Data, and data protection awareness for personnel.

(g) Sub-Processor Oversight: Data Processing Agreements with all sub-processors, selection of sub-processors that hold recognised security certifications where available.

(h) Availability and Recovery: regular backups of stored data through the managed services of the hosting provider and the ability to restore access to data in a timely manner.

(i) Data Minimisation by Design: Pass-Through Mode by default; Storage Mode only when activated by Controller; identifiers in the Check Log stored only in hashed form; automatic deletion at the end of each retention period.

6.2 Data Minimization and Retention Practices

SocialScore shall:

(a) Collect only the minimum Customer Data necessary to deliver Services;

(b) Implement automated data deletion procedures upon expiration of retention periods;

(d) NOT create or maintain persistent individual profiles extending beyond authorized purposes;

(e) Apply pseudonymization or anonymization where technically feasible without compromising Service delivery.

6.3 AI System Security and Explainability

Where AI systems are used:

(a) AI systems shall be subject to reasonable measures to protect them against unauthorised access and manipulation;

(b) Training and testing environments shall be segregated from production systems to prevent data leakage;

(c) the Documentation describes each category of Data Signal, its meaning, the categories of sources used and its known limitations;

(d) SocialScore shall maintain documentation of the logic of the Data Signals at a level sufficient to support Controller's transparency obligations, without disclosure of trade secrets.

APPENDIX 2 - LIST OF SUB-PROCESSORS#

Sub-Processor Compliance Notice

All sub-processors listed below have been assessed and contractually required to comply with:

  • GDPR obligations and obligations substantively equivalent to the terms of this DPA
  • Data security requirements appropriate to the risk, as set out in their data processing terms
  • Prohibition on cross-purpose data use
  • Data deletion and retention obligations
  • Restrictions on onward transfers of Customer Data

SocialScore maintains documented agreements with all sub-processors imposing substantively equivalent obligations to those in this DPA. On request, SocialScore provides Controller with the certifications and audit reports that its sub-processors make available.

Service providerDescription of the serviceServer locationSafeguards
Google Cloud (Google Ireland Limited, Dublin)Hosting, storage and computing for the SocialScore applicationEUGoogle Cloud Data Processing Addendum, ISO 27001
Firebase (Google Ireland Limited)Hosting of the SocialScore web applicationEUGoogle Cloud Data Processing Addendum, ISO 27001; Standard Contractual Clauses for any transfer within the Google group outside the EEA
SEON Technologies Kft.Email, phone and IP signal data, including breach exposure flagsHungary (EU)Data processing agreement, ISO 27001
Hetzner Online GmbHBare-metal server hostingGermany / Finland (EU)Data processing agreement, ISO 27001

Other service providers (not sub-processors of Customer Data)

The following providers do not process Customer Data. They process data of Customer's own representatives and are described in SocialScore's Privacy Policy: Paypercut (processing of payments for SocialScore's invoices to Customer) and HubSpot (SocialScore's customer relationship management for Customer's business contacts).

APPENDIX 3 - PROCESSOR TO CONTROLLER STANDARD CONTRACTUAL CLAUSES#

SECTION I

Clause 1 - Purpose and scope

(a) The purpose of these standard contractual clauses is to ensure compliance with the requirements of Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data (General Data Protection Regulation) for the transfer of personal data to a third country.

(b) The Parties:

(i) the natural or legal person(s), public authority/ies, agency/ies or other body/ies (hereinafter 'entity/ies') transferring the personal data, as listed in ANNEX I.A (hereinafter each 'data exporter'), and

(ii) the entity/ies in a third country receiving the personal data from the data exporter, directly or indirectly via another entity also Party to these Clauses, as listed in ANNEX I.A. (hereinafter each 'data importer')

have agreed to these standard contractual clauses (hereinafter: 'Clauses').

(c) These Clauses apply with respect to the transfer of personal data as specified in ANNEX I.B.

(d) The Appendix to these Clauses containing the Annexes referred to therein forms an integral part of these Clauses.

Clause 2 - Effect and invariability of the Clauses

(a) These Clauses set out appropriate safeguards, including enforceable data subject rights and effective legal remedies, pursuant to Article 46(1) and Article 46(2)(c) of Regulation (EU) 2016/679 and, with respect to data transfers from controllers to processors and/or processors to processors, standard contractual clauses pursuant to Article 28(7) of Regulation (EU) 2016/679, provided they are not modified, except to select the appropriate Module(s) or to add or update information in the Appendix. This does not prevent the Parties from including the standard contractual clauses laid down in these Clauses in a wider contract and/or to add other clauses or additional safeguards, provided that they do not contradict, directly or indirectly, these Clauses or prejudice the fundamental rights or freedoms of data subjects.

(b) These Clauses are without prejudice to obligations to which the data exporter is subject by virtue of Regulation (EU) 2016/679.

Clause 3 - Third-party beneficiaries

(a) Data subjects may invoke and enforce these Clauses, as third-party beneficiaries, against the data exporter and/or data importer, with the following exceptions:

(i) Clause 1, Clause 2, Clause 3, Clause 6, Clause 7;

(ii) Clause 8 - Clause 8.1 (b) and Clause 8.3(b);

(iii) [Not applicable in case of processor to controller relationships];

(iv) [Not applicable in case of processor to controller relationships];

(v) [Not applicable in case of processor to controller relationships];

(vi) Clause 15.1(c), (d) and (e);

(vii) Clause 16(e);

(viii) Clause 18.

(b) Paragraph (a) is without prejudice to rights of data subjects under Regulation (EU) 2016/679.

Clause 4 - Interpretation

(a) Where these Clauses use terms that are defined in Regulation (EU) 2016/679, those terms shall have the same meaning as in that Regulation.

(b) These Clauses shall be read and interpreted in the light of the provisions of Regulation (EU) 2016/679.

(c) These Clauses shall not be interpreted in a way that conflicts with rights and obligations provided for in Regulation (EU) 2016/679.

Clause 5 - Hierarchy

In the event of a contradiction between these Clauses and the provisions of related agreements between the Parties, existing at the time these Clauses are agreed or entered into thereafter, these Clauses shall prevail.

Clause 6 - Description of the transfer(s)

The details of the transfer(s), and in particular the categories of personal data that are transferred and the purpose(s) for which they are transferred, are specified in ANNEX I.B.

Clause 7 - Docking clause [optional clause omitted]

SECTION II - OBLIGATIONS OF THE PARTIES

Clause 8 - Data protection safeguards

The data exporter warrants that it has used reasonable efforts to determine that the data importer is able, through the implementation of appropriate technical and organisational measures, to satisfy its obligations under these Clauses.

8.1 Instructions

(a) The data exporter shall process the personal data only on documented instructions from the data importer acting as its controller.

(b) The data exporter shall immediately inform the data importer if it is unable to follow those instructions, including if such instructions infringe Regulation (EU) 2016/679 or other Union or Member State data protection law.

(c) The data importer shall refrain from any action that would prevent the data exporter from fulfilling its obligations under Regulation (EU) 2016/679, including in the context of sub-processing or as regards cooperation with competent supervisory authorities.

(d) After the end of the provision of the processing services, the data exporter shall, at the choice of the data importer, delete all personal data processed on behalf of the data importer and certify to the data importer that it has done so, or return to the data importer all personal data processed on its behalf and delete existing copies.

8.2 Security of processing

(a) The Parties shall implement appropriate technical and organisational measures to ensure the security of the data, including during transmission, and protection against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access (hereinafter 'personal data breach'). In assessing the appropriate level of security, they shall take due account of the state of the art, the costs of implementation, the nature of the personal data, the nature, scope, context and purpose(s) of processing and the risks involved in the processing for the data subjects, and in particular consider having recourse to encryption or pseudonymisation, including during transmission, where the purpose of processing can be fulfilled in that manner.

(b) The data exporter shall assist the data importer in ensuring appropriate security of the data in accordance with paragraph (a). In case of a personal data breach concerning the personal data processed by the data exporter under these Clauses, the data exporter shall notify the data importer without undue delay after becoming aware of it and assist the data importer in addressing the breach.

(c) The data exporter shall ensure that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.

8.3 Documentation and compliance

(a) The Parties shall be able to demonstrate compliance with these Clauses.

(b) The data exporter shall make available to the data importer all information necessary to demonstrate compliance with its obligations under these Clauses and allow for and contribute to audits.

Clause 9

[Not applicable in case of processor to controller relationships.]

Clause 10 - Data subject rights

The Parties shall assist each other in responding to enquiries and requests made by data subjects under the local law applicable to the data importer or, for data processing by the data exporter in the EU, under Regulation (EU) 2016/679.

Clause 11 - Redress

(a) The data importer shall inform data subjects in a transparent and easily accessible format, through individual notice or on its website, of a contact point authorised to handle complaints. It shall deal promptly with any complaints it receives from a data subject.

Clause 12 - Liability

(a) Each Party shall be liable to the other Party/ies for any damages it causes the other Party/ies by any breach of these Clauses.

(b) Each Party shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages that the Party causes the data subject by breaching the third-party beneficiary rights under these Clauses. This is without prejudice to the liability of the data exporter under Regulation (EU) 2016/679.

(c) Where more than one Party is responsible for any damage caused to the data subject as a result of a breach of these Clauses, all responsible Parties shall be jointly and severally liable and the data subject is entitled to bring an action in court against any of these Parties.

(d) The Parties agree that if one Party is held liable under paragraph (c), it shall be entitled to claim back from the other Party/ies that part of the compensation corresponding to its/their responsibility for the damage.

(e) The data importer may not invoke the conduct of a processor or sub-processor to avoid its own liability.

Clause 13 - Supervision

[Not applicable in case of processor to controller relationships.]

SECTION III - LOCAL LAWS AND OBLIGATIONS IN CASE OF ACCESS BY PUBLIC AUTHORITIES

Clause 14 - Local laws and practices affecting compliance with the Clauses

(a) The Parties warrant that they have no reason to believe that the laws and practices in the third country of destination applicable to the processing of the personal data by the data importer, including any requirements to disclose personal data or measures authorising access by public authorities, prevent the data importer from fulfilling its obligations under these Clauses. This is based on the understanding that laws and practices that respect the essence of the fundamental rights and freedoms and do not exceed what is necessary and proportionate in a democratic society to safeguard one of the objectives listed in Article 23(1) of Regulation (EU) 2016/679, are not in contradiction with these Clauses.

(b) The Parties declare that in providing the warranty in paragraph (a), they have taken due account in particular of the following elements:

(i) the specific circumstances of the transfer, including the length of the processing chain, the number of actors involved and the transmission channels used; intended onward transfers; the type of recipient; the purpose of processing; the categories and format of the transferred personal data; the economic sector in which the transfer occurs; the storage location of the data transferred;

(ii) the laws and practices of the third country of destination- including those requiring the disclosure of data to public authorities or authorising access by such authorities - relevant in light of the specific circumstances of the transfer, and the applicable limitations and safeguards;

(iii) any relevant contractual, technical or organisational safeguards put in place to supplement the safeguards under these Clauses, including measures applied during transmission and to the processing of the personal data in the country of destination.

(c) The data importer warrants that, in carrying out the assessment under paragraph (b), it has made its best efforts to provide the data exporter with relevant information and agrees that it will continue to cooperate with the data exporter in ensuring compliance with these Clauses.

(d) The Parties agree to document the assessment under paragraph (b) and make it available to the competent supervisory authority on request.

(e) The data importer agrees to notify the data exporter promptly if, after having agreed to these Clauses and for the duration of the contract, it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under paragraph (a), including following a change in the laws of the third country or a measure (such as a disclosure request) indicating an application of such laws in practice that is not in line with the requirements in paragraph (a).

(f) Following a notification pursuant to paragraph (e), or if the data exporter otherwise has reason to believe that the data importer can no longer fulfil its obligations under these Clauses, the data exporter shall promptly identify appropriate measures (e.g. technical or organisational measures to ensure security and confidentiality) to be adopted by the data exporter and/or data importer to address the situation. The data exporter shall suspend the data transfer if it considers that no appropriate safeguards for such transfer can be ensured, or if instructed by the competent supervisory authority to do so. In this case, the data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses. If the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise. Where the contract is terminated pursuant to this Clause, Clause 16(d) and (e) shall apply.

Clause 15 - Obligations of the data importer in case of access by public authorities

15.1 Notification

(a) The data importer agrees to notify the data exporter and, where possible, the data subject promptly (if necessary, with the help of the data exporter) if it:

(i) receives a legally binding request from a public authority, including judicial authorities, under the laws of the country of destination for the disclosure of personal data transferred pursuant to these Clauses; such notification shall include information about the personal data requested, the requesting authority, the legal basis for the request and the response provided; or

(ii) becomes aware of any direct access by public authorities to personal data transferred pursuant to these Clauses in accordance with the laws of the country of destination; such notification shall include all information available to the importer.

(b) If the data importer is prohibited from notifying the data exporter and/or the data subject under the laws of the country of destination, the data importer agrees to use its best efforts to obtain a waiver of the prohibition, with a view to communicating as much information as possible, as soon as possible. The data importer agrees to document its best efforts in order to be able to demonstrate them on request of the data exporter.

(c) Where permissible under the laws of the country of destination, the data importer agrees to provide the data exporter, at regular intervals for the duration of the contract, with as much relevant information as possible on the requests received (in particular, number of requests, type of data requested, requesting authority/ies, whether requests have been challenged and the outcome of such challenges, etc.).

(d) The data importer agrees to preserve the information pursuant to paragraphs (a) to (c) for the duration of the contract and make it available to the competent supervisory authority on request.

(e) Paragraphs (a) to (c) are without prejudice to the obligation of the data importer pursuant to Clause 14(e) and Clause 16 to inform the data exporter promptly where it is unable to comply with these Clauses.

15.2 Review of legality and data minimisation

(a) The data importer agrees to review the legality of the request for disclosure, in particular whether it remains within the powers granted to the requesting public authority, and to challenge the request if, after careful assessment, it concludes that there are reasonable grounds to consider that the request is unlawful under the laws of the country of destination, applicable obligations under international law and principles of international comity. The data importer shall, under the same conditions, pursue possibilities of appeal. When challenging a request, the data importer shall seek interim measures with a view to suspending the effects of the request until the competent judicial authority has decided on its merits. It shall not disclose the personal data requested until required to do so under the applicable procedural rules. These requirements are without prejudice to the obligations of the data importer under Clause 14(e).

(b) The data importer agrees to document its legal assessment and any challenge to the request for disclosure and, to the extent permissible under the laws of the country of destination, make the documentation available to the data exporter. It shall also make it available to the competent supervisory authority on request.

(c) The data importer agrees to provide the minimum amount of information permissible when responding to a request for disclosure, based on a reasonable interpretation of the request.

SECTION IV - FINAL PROVISIONS

Clause 16 - Non-compliance with the Clauses and termination

(a) The data importer shall promptly inform the data exporter if it is unable to comply with these Clauses, for whatever reason.

(b) In the event that the data importer is in breach of these Clauses or unable to comply with these Clauses, the data exporter shall suspend the transfer of personal data to the data importer until compliance is again ensured or the contract is terminated. This is without prejudice to Clause 14(f).

(c) The data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses, where:

(i) the data exporter has suspended the transfer of personal data to the data importer pursuant to paragraph (b) and compliance with these Clauses is not restored within a reasonable time and in any event within one month of suspension;

(ii) the data importer is in substantial or persistent breach of these Clauses; or

(iii) the data importer fails to comply with a binding decision of a competent court or supervisory authority regarding its obligations under these Clauses.

In these cases, it shall inform the competent supervisory authority of such non-compliance. Where the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise.

(d) Personal data collected by the data exporter in the EU that has been transferred prior to the termination of the contract pursuant to paragraph (c) shall immediately be deleted in its entirety, including any copy thereof. The data importer shall certify the deletion of the data to the data exporter. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit the return or deletion of the transferred personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process the data to the extent and for as long as required under that local law.

(e) Either Party may revoke its agreement to be bound by these Clauses where (i) the European Commission adopts a decision pursuant to Article 45(3) of Regulation (EU) 2016/679 that covers the transfer of personal data to which these Clauses apply; or (ii) Regulation (EU) 2016/679 becomes part of the legal framework of the country to which the personal data is transferred. This is without prejudice to other obligations applying to the processing in question under Regulation (EU) 2016/679.

Clause 17 - Governing law

These Clauses shall be governed by the law of a country allowing for third-party beneficiary rights. The Parties agree that this shall be the law of Bulgaria.

Clause 18 - Choice of forum and jurisdiction

Any dispute arising from these Clauses shall be resolved by the courts of Bulgaria.

ANNEX I

A. LIST OF PARTIES

Data exporter(s):

Name: SocialScore (DSNTech LTD)

Address: Mladost 2, Sofia, Bulgaria

Contact person's name, position and contact details: Data protection contact, dpo@socialscore.io

Activities relevant to the data transferred under these Clauses: As defined by Appendix 1 of the DPA.

Signature and date: Pursuant to Section 1.2 of the DPA.

Role (controller/processor): Processor.

Data importer(s):

Controller, as defined by the DPA.

Contact person's name, position and contact details: Controller's Email Address as defined by the DPA.

Activities relevant to the data transferred under these Clauses: As defined by Appendix 1 of the DPA.

Signature and date: Pursuant to Section 1.2 of the DPA.

Role (controller/processor): Controller.

B. DESCRIPTION OF TRANSFER

Categories of data subjects whose personal data is transferred: As specified under Section 3 of Appendix 1 of the DPA.

Categories of personal data transferred: As specified under Section 4 of Appendix 1 of the DPA.

Sensitive data transferred (if applicable): Not applicable.

The frequency of the transfer: Data is transferred on a continuous basis.

Nature of the processing: As specified under Section 2 of Appendix 1 of the DPA.

Purpose(s) of the data transfer and further processing: As specified under Section 2 of Appendix 1 of the DPA.

The period for which the personal data will be retained: As specified under Section 5 of Appendix 1 of the DPA.

For transfers to (sub-) processors: N/A.

DSNTech LTD

Contact Us:

If you have any questions, You can contact us:

By email: office@socialscore.io

By visiting this page on our website: https://socialscore.io