All Legal Documents

Data Processing Agreement

Effective date: November 19, 2026

Get AI Explanation

Need help understanding this document? Get an AI-powered explanation from your favorite AI models.

Version 2.0. Section 8 says when it applies to a Customer that accepted the version dated August 25, 2026. Compared with that version, it adds UK and Swiss data protection law, restates the international transfer terms, replaces the list of security measures with the measures in place on the effective date, and corrects the sub-processor list.

1. Parties, Acceptance and Precedence

This Data Processing Agreement ("DPA") is entered into between:

Customer: the individual or organization that has agreed to the Signa Terms of Service (the "Agreement") and uses the Service in a way that involves the processing of Customer Personal Data.

and

Signa Technologies Ltd ("Signa"):
Registration No. HE 495212
Fellachoglou 35, Mouttallos
8016 Paphos, Cyprus
Email: legal@signa.so

1.1 Acceptance. This DPA forms part of the Agreement. By accepting the Agreement, Customer accepts this DPA. No separate signature is required.

1.2 When this DPA applies. This DPA applies where Signa processes Customer Personal Data on Customer's behalf and Data Protection Laws apply to that processing. If Customer's use of the Service does not involve Customer Personal Data, this DPA places no additional obligations on Customer.

1.3 Signed copies. Where the Signa dashboard offers it, an owner of Customer's Signa organization may accept this DPA there on Customer's behalf, naming Customer's legal entity. Signa offers this DPA for acceptance in the dashboard and is bound by it when Customer accepts. An acceptance recorded there is a writing signed by both parties, and the dashboard provides a copy that records the parties' details for Annex D. Any Customer may instead ask for a countersigned copy for its records by writing to legal@signa.so.

1.4 Precedence. For the processing of Customer Personal Data, if this DPA and the rest of the Agreement conflict, this DPA prevails. If this DPA and the Standard Contractual Clauses or the UK Addendum conflict, the Standard Contractual Clauses or the UK Addendum prevail.

2. Definitions

2.1 "Customer Personal Data" means personal data contained in the content and requests that Customer, or anyone using Customer's account or API keys, submits to the Service, and that Signa processes on Customer's behalf. Annex A describes it.

2.2 "Data Protection Laws" means, to the extent each applies to the processing of Customer Personal Data: (a) Regulation (EU) 2016/679 ("EU GDPR") and the laws of EU and EEA member states that supplement it, including Cyprus Law 125(I)/2018; (b) the EU GDPR as it forms part of the law of the United Kingdom ("UK GDPR") and the UK Data Protection Act 2018; and (c) the Swiss Federal Act on Data Protection ("FADP").

2.3 "GDPR" means the EU GDPR or the UK GDPR, whichever applies to the processing. A reference in this DPA to an Article of the GDPR includes the corresponding provision of the other Data Protection Laws that apply, where there is one.

2.4 "controller", "processor", "data subject", "personal data", "processing" and "supervisory authority" have the meanings given in the GDPR.

2.5 "Sub-processor" means a third party that Signa engages to process Customer Personal Data.

2.6 "Personal Data Breach" means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Customer Personal Data in Signa's or its Sub-processors' possession.

2.7 "Standard Contractual Clauses" or "SCCs" means the clauses annexed to Commission Implementing Decision (EU) 2021/914 of 4 June 2021.

2.8 "UK Addendum" means the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses, version B1.0, issued by the UK Information Commissioner under section 119A of the Data Protection Act 2018, as revised from time to time under its section 18.

2.9 "Restricted Transfer" means a transfer of Customer Personal Data that Data Protection Laws prohibit unless a safeguard such as an adequacy decision or regulation, the SCCs or the UK Addendum is in place.

2.10 Capitalized terms that this DPA does not define, including "Service", have the meanings given in the Agreement.

3. Roles and Scope

3.1 Customer as controller. For Customer Personal Data, Customer is the controller and Signa is the processor. Where Customer acts as a processor for its own customers, Signa is Customer's sub-processor, and Customer confirms that its instructions to Signa are authorized by the relevant controller.

3.2 Details of processing. Annex A sets out the subject matter, duration, nature and purpose of the processing, the types of Customer Personal Data and the categories of data subjects.

3.3 Signa as controller. Signa processes the following as an independent controller, under its Privacy Policy and not under this DPA:

(a) account, contact and billing information about Customer and its users;

(b) billing records, which for a paid watch include the query it monitored, and the organization, endpoint, time, status, response time and credits used of each request, which Signa needs for billing, capacity planning, security, and the prevention of fraud and abuse, and to meet its legal obligations. Otherwise the content of a request, the IP address and user agent of its caller, and search quality records that can identify an individual remain Customer Personal Data;

(c) statistics about use of the Service, including statistics drawn from search quality records, that do not identify Customer or any individual, which Signa uses to operate and improve the Service; and

(d) trademark registry data that Signa obtains from public registers and returns through the Service.

3.4 No other use. Signa does not sell Customer Personal Data, does not use it for advertising, and does not use it to train artificial intelligence models.

4. Customer's Obligations

4.1 Customer confirms that:

(a) it has a lawful basis under Data Protection Laws for each processing activity that involves Customer Personal Data;

(b) it has given data subjects the information that Data Protection Laws require, including that their data may be handled by processors;

(c) it is entitled to instruct Signa to process Customer Personal Data as described in this DPA; and

(d) it will comply with Data Protection Laws in its use of the Service.

4.2 The Service is not designed for special categories of personal data (Article 9 GDPR) or personal data relating to criminal convictions and offences (Article 10 GDPR). Customer will not knowingly submit such data to the Service, and will not design its use of the Service to collect it.

4.3 Customer is responsible for the security of its own systems, accounts and API keys, and for deciding whether the Service and the measures in Annex C are appropriate for its Customer Personal Data.

5. Signa's Obligations

5.1 Instructions

Signa will process Customer Personal Data only on Customer's documented instructions, including with regard to transfers of Customer Personal Data to a third country. Customer's instructions are the Agreement, this DPA, and Customer's use and configuration of the Service. Signa may process Customer Personal Data otherwise only where a law it is subject to requires it: for processing governed by the EU GDPR, the law of the European Union or an EEA member state; for processing governed by the UK GDPR, the law of the United Kingdom; for processing governed by the FADP, Swiss law. Signa will then tell Customer of the requirement before processing, unless that law prohibits it on important grounds of public interest.

Signa will tell Customer immediately if, in its opinion, an instruction infringes Data Protection Laws.

5.2 Confidentiality

Signa will ensure that everyone it authorizes to process Customer Personal Data is bound by a duty of confidentiality, and that access is limited to those who need it to provide the Service.

5.3 Security

Signa will implement and maintain appropriate technical and organizational measures to ensure a level of security appropriate to the risk, as Article 32 GDPR requires. They include the measures described in Annex C. Signa may update those measures as the Service and the threats to it change, provided the overall level of protection is not reduced.

5.4 Sub-processors

(a) Authorization. Customer gives Signa general written authorization to engage Sub-processors. The Sub-processors authorized on the effective date are listed in Annex B. The current list is published at https://signa.so/legal/sub-processors.

(b) Changes. Signa will notify Customer by email, at the addresses of its account owners, at least 30 days before a new or replacement Sub-processor starts processing Customer Personal Data, and will update the published list at the same time. The notice will name the Sub-processor and say what it will do and where.

(c) Objection. Customer may object to a new Sub-processor on reasonable data protection grounds within 30 days of the notice. The parties will work in good faith to resolve the objection. If they cannot do so within a further 30 days, Customer may terminate the Agreement without penalty by written notice.

(d) Sub-processor terms. Signa will have a written contract with each Sub-processor that imposes data protection obligations which, in substance, are the same as those in this DPA, and that requires the Sub-processor to impose them on any further processor it uses. Signa remains fully liable to Customer for each Sub-processor's performance of those obligations, as Article 28(4) GDPR provides. Section 7 applies to that liability.

5.5 Data Subject Requests

(a) If Signa receives a request from a data subject about Customer Personal Data, Signa will pass it to Customer without undue delay and will not respond to it itself, unless Customer instructs otherwise or the law requires it.

(b) Taking into account the nature of the processing, Signa will help Customer respond to requests from data subjects to exercise their rights. The Service lets Customer read its request logs for the period its plan provides and export them from the dashboard, read and change its watches and other configurations, and delete its organization and the data in it. Where Customer cannot fulfil a request with those tools, Signa will give reasonable assistance on request.

5.6 Personal Data Breach

(a) Signa will notify Customer of a Personal Data Breach without undue delay, and in any event within 48 hours of becoming aware of it.

(b) The notice will describe, to the extent known: 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 at Signa. Signa may provide this information in stages as it becomes available.

(c) Signa will take reasonable steps to contain and remedy the breach, will cooperate with Customer's investigation, and will give Customer the assistance it reasonably needs to meet its own obligations under Articles 33 and 34 GDPR.

(d) Signa will keep a record of each Personal Data Breach, its effects and the remedial action taken, and will make it available to Customer on request.

5.7 Assistance

Taking into account the nature of the processing and the information available to Signa, Signa will give Customer reasonable assistance with data protection impact assessments, prior consultation with supervisory authorities, and Customer's obligations under Article 32 GDPR, to the extent they relate to Signa's processing of Customer Personal Data.

5.8 Deletion and Return

(a) During the Agreement, Customer can retrieve the Customer Personal Data that the Service makes available through the API and the dashboard, within the retention periods in Annex A, and can ask Signa for help retrieving other Customer Personal Data that Signa still holds.

(b) When the Agreement ends, Customer may choose to have Customer Personal Data returned and then deleted, or deleted without return. Deleting the organization from the dashboard is an instruction to delete without return. Where the Agreement ends in another way, Signa will give Customer 30 days to ask for return before it deletes. If Customer gives no instruction in that time, Signa will delete the Customer Personal Data within 90 days after the Agreement ends.

(c) Deletion from the Service's live databases begins promptly after the instruction and is completed without undue delay. Copies that remain in backups, logs, search quality records, error reports and dashboard assistant workflow run storage are deleted on the schedules in Annex A, which can extend beyond the 90 days in (b). Until then they stay protected by this DPA, are not used to provide the Service, and are accessed only where needed for recovery, a security investigation or a legal requirement. If a backup is restored, Signa will apply Customer's deletion instruction again before the restored data is used.

(d) Signa may keep Customer Personal Data where a law it is subject to requires it (for processing governed by the EU GDPR, the law of the European Union or an EEA member state; for processing governed by the UK GDPR, the law of the United Kingdom; for processing governed by the FADP, Swiss law). Signa will keep that data confidential and will not process it for any other purpose.

(e) On request, Signa will confirm the deletion in writing.

5.9 Information and Audit

(a) Signa will make available to Customer the information needed to demonstrate compliance with Article 28 GDPR and this DPA. Signa will answer Customer's reasonable written questions, including one security questionnaire in any 12 months, and will share any independent audit reports or certifications it holds at the time.

(b) Where that information is not enough to demonstrate compliance, Signa will allow for and contribute to an audit, including an inspection, by Customer or an independent auditor that Customer appoints, on these terms:

  • Customer gives at least 30 days' written notice, or shorter notice where a supervisory authority requires it;
  • audits take place no more than once in any 12 months, unless a Personal Data Breach or a supervisory authority requires more;
  • audits take place during business hours, are conducted remotely where that is sufficient, and do not unreasonably disrupt the Service or put other customers' data at risk;
  • the auditor is bound by confidentiality obligations; and
  • Customer bears its own costs.

The limits on notice and frequency do not apply where Customer has credible evidence of a material breach of this DPA. The parties will then agree a proportionate scope without delay.

6. International Transfers

6.1 Where data is processed. Signa is established in Cyprus, a member state of the European Union. The Service is hosted in the United States, and Sub-processors process Customer Personal Data in the locations listed in Annex B. Customer authorizes those transfers on the terms of this Section 6.

6.2 Transfers from Customer to Signa. Signa is established in the European Economic Area. The laws of the United Kingdom and Switzerland permit a transfer of Customer Personal Data from a Customer in those countries to Signa without further safeguards, because each treats the European Economic Area as providing adequate protection. To the extent that a transfer of Customer Personal Data from Customer to Signa is a Restricted Transfer that is not covered in that way, for any reason, the SCCs apply to it as set out in Annex D from the moment it is not covered.

6.3 Onward transfers by Signa. Signa will not transfer Customer Personal Data to a Sub-processor in a country outside the European Economic Area, the United Kingdom and Switzerland unless one of the following covers the transfer:

(a) an adequacy decision or adequacy regulations under each Data Protection Law that applies to the Customer Personal Data concerned. For a recipient in the United States this means certification under the EU-U.S. Data Privacy Framework and, for Customer Personal Data subject to the UK GDPR or the FADP, under the UK Extension to that framework or the Swiss-U.S. Data Privacy Framework respectively; or

(b) the SCCs between Signa and the recipient (Module Three, processor to processor), together with, for Customer Personal Data subject to the UK GDPR, the UK Addendum or the UK International Data Transfer Agreement and, for Customer Personal Data subject to the FADP, the amendments needed to meet the FADP; or

(c) another transfer mechanism that each Data Protection Law applying to the Customer Personal Data concerned recognizes for the transfer, such as approved binding corporate rules.

For this Section 6.3, Customer Personal Data is subject to the UK GDPR or the FADP where that law applies to Customer's processing of it, whether or not it also applies to Signa directly.

Where Signa's contract is with a Sub-processor established in the European Economic Area, the United Kingdom or Switzerland that itself sends Customer Personal Data to another country, that contract will require the Sub-processor to make the transfer in compliance with the Data Protection Laws that apply.

Signa will have the contract that Section 5.4(d) requires, and a mechanism described in this Section 6.3, in place with each Sub-processor before it starts processing Customer Personal Data.

6.4 Transfers from Signa to Customer. Where Signa makes Customer Personal Data available to a Customer established in a country that does not benefit from an adequacy decision under the EU GDPR, and the EU GDPR requires a safeguard for that transfer, the SCCs apply as set out in Annex D: Module Four (processor to controller) where Customer is the controller, and Module Three (processor to processor) where Customer is a processor.

6.5 Assessment. Signa has assessed its transfers of Customer Personal Data to Sub-processors outside the European Economic Area, including, where a transfer relies on the SCCs, the laws and practices of the destination country that are relevant to it, as Clause 14 of the SCCs requires. Signa will give Customer a summary of that assessment on request. Signa applies the measures in Annex C to all Customer Personal Data in the systems it operates, whichever country the data comes from.

6.6 Requests from public authorities. If Signa receives a legally binding request from a public authority for Customer Personal Data, Signa will, unless the law prohibits it, notify Customer before disclosing anything, disclose only what the request lawfully requires, and challenge the request where, after careful assessment, it concludes that there are reasonable grounds to consider it unlawful.

7. Liability

7.1 Each party's liability under this DPA is subject to the limitations of liability in the Agreement, except that neither party's liability is limited for:

(a) fines or penalties imposed on one party by a supervisory authority that result from the other party's breach of this DPA;

(b) Signa's processing of Customer Personal Data outside Customer's documented instructions, unless the law required that processing; or

(c) willful misconduct or gross negligence in the processing of Customer Personal Data.

7.2 Compensation of data subjects, and contribution between the parties, are governed by Article 82 GDPR. Nothing in this DPA limits a data subject's rights, or any liability that cannot lawfully be limited, under Data Protection Laws, the SCCs or the UK Addendum.

8. Term

This DPA takes effect when Customer accepts the Agreement, or on the effective date above if later. For a Customer already bound by the Data Processing Agreement dated August 25, 2026, it takes effect on the date both parties have agreed to it in a signed writing, which includes an acceptance under Section 1.3, and it replaces that version from that date. Until then that version continues to apply. This DPA continues for as long as Signa processes Customer Personal Data. Section 5.8 applies when the Agreement ends.

9. Governing Law and Jurisdiction

This DPA is governed by the law that governs the Agreement, and disputes under it are subject to the courts named in the Agreement. The SCCs and the UK Addendum are governed by the law, and subject to the courts, that they or Annex D specify.

10. Changes to this DPA

This DPA is part of the Agreement and changes the way the Agreement does. Signa may update it, and gives at least 30 days' notice by email before a material change takes effect, as Section 17.1 of the Agreement provides. Signa may also update Annex B as Section 5.4 provides and Annex C as Section 5.3 provides. The SCCs and the UK Addendum change only as they themselves provide.

11. Contact

Signa Technologies Ltd
Registration No. HE 495212
Fellachoglou 35, Mouttallos
8016 Paphos, Cyprus
Data protection: privacy@signa.so
Legal and signed copies: legal@signa.so
Security and breach reports: security@signa.so


Annex A: Details of Processing

ElementDetails
Subject matterSigna's provision of its trademark data API, dashboard and related services to Customer
DurationThe term of the Agreement, and afterwards until Customer Personal Data is deleted under Section 5.8
Nature of processingReceiving, storing, searching, retrieving, transmitting and deleting Customer Personal Data submitted through the API, the dashboard and connected tools
PurposeProviding the Service to Customer: answering trademark searches and other API requests, running watches and delivering alerts, operating AI-assisted features that Customer uses, keeping request logs that Customer can read, keeping the Service secure, investigating errors, and checking and maintaining the quality of the results the Service returns
Types of personal dataNames and other identifiers that appear in search queries, watch and portfolio configurations, references, notes and other text Customer submits; text sent to AI-assisted features; IP addresses and user agents of the systems or end users that call the API with Customer's credentials; email addresses that Customer configures to receive alerts
Special categoriesNone intended. Section 4.2 applies
Data subjectsCustomer's end users, clients and customers; individuals whose names Customer searches for or monitors; Customer's own personnel who use the Service
Frequency of transferContinuous, for as long as Customer uses the Service
RetentionRequest logs: a daily job removes search text, IP address, user agent and error detail from records more than 90 days old, and the rest of each record (endpoint, status, timing, credits) is kept for up to 5 months. Search quality records: search text for 7 days, then a keyed hash of it with filters and result details for up to 5 months; these records are treated as personal data where an individual can still be identified. Network access logs at the edge of the Service, which record the caller's IP address and user agent and the method, host, status and timing of each request, but not its URL path or query string: 90 days. Edge logs written on or before 15 November 2026 also hold the full request address, with any search text in it, until they expire. Firewall logs of blocked or flagged requests, with the URL path, query string and request body redacted: 30 days. Database error logs, which can quote a value from a request that failed: 3 days. Application logs: 90 days. Watches, portfolios and other configurations: until Customer deletes them or its organization. The billing history of a paid watch includes the query it monitored. Signa keeps it as a billing record, as controller (Section 3.3(b)), for as long as the law requires Signa to keep billing records. Database backups: 7 days. Error reports held by Sentry: 30 days. Dashboard assistant workflow run data held by Vercel: readable for 7 days after each run ends and deleted within 96 days after that run ends
Zero data retentionThis row applies only where Signa has confirmed in writing that zero data retention is on for Customer's organization. For API and MCP requests that start at or after the time Signa confirmed, Signa keeps a billing-level record of each request and does not store what Customer searched for or looked up. The record, the requests covered and the exceptions are set out in the zero data retention section of Signa's documentation. Signa will give Customer at least 30 days' notice by email before a change that reduces what that section covers for Customer. The dashboard is not covered
Sub-processorsAnnex B, for the purposes and in the locations listed there, for the duration of the Agreement

Annex B: Authorized Sub-processors

These providers are authorized on the effective date. The current list is at https://signa.so/legal/sub-processors. A provider is a Sub-processor under this DPA only to the extent that it processes Customer Personal Data. Some of them mainly support Signa's own account administration, which the Privacy Policy covers.

Sub-processorPurposeData processedLocation
Amazon Web ServicesHosting of the API: compute, databases, search, storage, network and logsCustomer Personal Data submitted through the API, and the logs of those requestsUnited States (US East). Requests pass through Amazon CloudFront edge locations in North America and Europe
VercelHosting of the dashboard, including the dashboard assistant. Vercel's AI Gateway also carries requests for AI-assisted features to the model providerDashboard requests; classification and suggestion inputs; assistant prompts and tool results; text typed into AI-assisted filters; account information used in internal reportingUnited States and Vercel's global edge network
AnthropicModel provider for AI-assisted features (classification and goods and services suggestions, the dashboard assistant) and for internal reporting, reached through Vercel's AI GatewayClassification and suggestion inputs; assistant prompts and tool results; account information used in internal reportingUnited States
OpenAIModel provider for the dashboard's AI-assisted filters, reached through Vercel's AI GatewayText typed into AI-assisted filtersUnited States
Neon (Databricks)Database for sign-in and account recordsNames, email addresses, hashed passwords, sessions, sign-in tokens, invitationsUnited States (US East)
Sentry (Functional Software)Error trackingError events and stack traces. Structured request data (headers, cookies, bodies, query strings, IP addresses and email fields) is scrubbed first. Error messages and stack traces can still contain content from the failed requestUnited States
UpstashRate limiting and session state for the dashboardIP-derived rate-limit keys, session identifiersGlobal edge network
StripePayments and invoicingBilling name, address, payment method, transaction history. No API requests or search queries. Stripe also acts as a controller for parts of its serviceUnited States and Ireland
ResendSending transactional email, including alertsRecipient email address, name, email contentUnited States
SlackInternal operational notificationsAccount events, error details and feedback that Customer sends to SignaUnited States
Google (Workspace and Sign-In)Signa's email and documents; optional sign-in with GoogleCorrespondence with Customer; for Google sign-in, the name, email address and Google account identifierUnited States and European Union

A plain trademark search or lookup is processed only on Amazon Web Services, apart from the error reports and operational notifications described above when a request fails. Its text is not sent to an AI model provider.

Advertising platforms and website analytics providers do not process Customer Personal Data. The Privacy Policy describes them.

Annex C: Technical and Organizational Measures

Hosting and network

  • The API runs on Amazon Web Services in the US East region. Databases, search clusters and caches run in private subnets and cannot be reached from the internet.
  • Traffic to the API through Amazon CloudFront is filtered by a web application firewall with managed rule sets for common exploits, known bad inputs, SQL injection and IP reputation, and by rate limiting.

Encryption

  • Public connections to the API, the dashboard and the website use TLS 1.2 or higher. Plain HTTP is redirected to HTTPS.
  • Databases, search clusters, caches, object storage and backups are encrypted at rest with AES-256.
  • API keys are stored only as hashes. Webhook signing secrets are encrypted with a dedicated key in AWS Key Management Service.

Access control and tenant separation

  • Each record that belongs to a customer is scoped to that customer's organization, and every request is authorized against it. No other customer can see an organization's request logs.
  • Access to production systems is limited to the people who need it to run the Service.
  • Deployments run through an automated pipeline that uses short-lived credentials.

Logging and monitoring

  • API requests are logged per organization. Administrative changes to customer accounts are recorded in an audit log.
  • Management activity in the AWS account is recorded by AWS CloudTrail across regions, with log file integrity validation, and kept for 365 days.
  • Automated alarms cover error rates, service health and unusual traffic at the edge.

Vulnerability management

  • Third-party dependencies are scanned for known vulnerabilities when they change and every six hours against the main branch, from which production is deployed.
  • Target remediation times, counted from when a fix is available, are 24 hours for critical vulnerabilities, 7 days for high and 30 days for medium. These are targets, not guarantees.
  • Every change is made through a pull request and automated checks before it is deployed. Infrastructure is defined as code.

Backups and recovery

  • The database is backed up continuously with point-in-time recovery. Backups are encrypted and kept for 7 days.

Data minimization and deletion

  • A daily job removes search text, IP addresses, user agents and error details from request log records more than 90 days old.
  • Network access logs at the edge do not record the URL path or query string of a request. The firewall log redacts the URL path, query string and request body.
  • Zero data retention for API and MCP requests is available by agreement (Annex A).
  • Structured request data (headers, cookies, bodies, query strings, IP addresses and email fields) is scrubbed from error reports before they leave the Service.
  • Customer can delete its organization, and the data in it, at any time.

Incident response

  • Signa maintains a written incident response procedure that covers detection, containment, investigation, notification under Section 5.6, and review after the incident.

Independent assurance

  • Signa does not hold an independent penetration test report, a SOC 2 report or an ISO 27001 certificate on the effective date. Signa plans to obtain them but has set no date, and this DPA does not oblige it to. The current status is on the Security page.

Annex D: Transfer Terms

Part 1: Standard Contractual Clauses

Where Section 6.2 or 6.4 says the SCCs apply, they are incorporated into this DPA by reference and completed as follows. A party's acceptance of the Agreement, its acceptance under Section 1.3, or its signature of a signed copy of this DPA, counts as its signature of the SCCs and of the UK Addendum, including their annexes, on the date this DPA takes effect between the parties.

ItemTransfers from Customer to Signa (Section 6.2)Transfers from Signa to Customer (Section 6.4)
ModuleModule Two (controller to processor), or Module Three where Customer is a processorModule Four (processor to controller), or Module Three where Customer is a processor
Data exporterCustomerSigna
Data importerSignaCustomer
Clause 7 (docking)Not usedNot used
Clause 9(a) (sub-processors)Option 2, general written authorization, with the notice period in Section 5.4 of this DPADoes not apply to Module Four. For Module Three, Option 2 with 30 days' notice
Clause 11 (redress)The optional wording is not usedThe optional wording is not used
Clause 13 and Annex I.C (supervisory authority)The authority determined under Clause 13Does not apply to Module Four. For Module Three, the Office of the Commissioner for Personal Data Protection of the Republic of Cyprus, subject to Parts 2 and 3
Clause 17 (governing law)The law of IrelandThe law of Ireland
Clause 18 (forum)The courts of IrelandThe courts of Ireland
Annex I.A (parties)The parties and contact details in Section 1 and in an acceptance under Section 1.3 or on the signature page of a signed copy, or otherwise in Customer's accountThe same
Annex I.B (description of transfer)Annex A of this DPAAnnex A of this DPA
Annex II (security measures)Annex C of this DPADoes not apply to Module Four. For Module Three, Customer's measures as described in a schedule the parties agree before the transfer begins
Annex III (sub-processors)Annex B of this DPADoes not apply

Clauses 14 and 15 of the SCCs apply to Module Four, because the Service combines what Customer submits with trademark register data that Signa collects.

Part 2: United Kingdom

Where the SCCs apply under Part 1 to a transfer that is a Restricted Transfer under the UK GDPR, they apply as amended by the UK Addendum, which is incorporated into this DPA by reference. The tables in Part 1 of the UK Addendum are completed as follows.

UK Addendum tableContent
Table 1: PartiesThe exporter and importer, with their details and key contacts, are as set out in Part 1 of this Annex. The start date is the date this DPA takes effect between the parties
Table 2: Selected SCCs, Modules and Selected ClausesThe version of the Approved EU SCCs incorporated under Part 1 of this Annex, with the modules, clauses and optional provisions selected there
Table 3: Appendix InformationThe information that completes Annexes I.A, I.B, II and III under Part 1 of this Annex
Table 4: Ending this Addendum when the Approved Addendum changesNeither party

Part 2 of the UK Addendum is completed as follows: "Part 2: Mandatory Clauses of the Approved Addendum, being the template Addendum B.1.0 issued by the ICO and laid before Parliament in accordance with s119A of the Data Protection Act 2018 on 2 February 2022, as it is revised under Section 18 of those Mandatory Clauses."

Part 3: Switzerland

Where the SCCs apply under Part 1 to a transfer that is subject only to the FADP, references to the GDPR are read as references to the FADP, the Federal Data Protection and Information Commissioner is the competent supervisory authority, and Swiss law governs the SCCs. Where a transfer is subject to both the FADP and the EU GDPR, those changes apply only to the FADP aspect of the transfer, and the EU GDPR, the competent EU supervisory authority and the governing law chosen in Part 1 are unaffected. In both cases "member state" is not read in a way that prevents data subjects in Switzerland from suing for their rights in their place of habitual residence. Nothing in this Part reduces the protection that the EU GDPR or the UK Addendum requires.

This Data Processing Agreement was last updated on November 19, 2026. For a signed copy, see Section 1.3.