1. Parties and how this agreement applies
This data processing agreement ("DPA") is between CVA TECH LTD, a company registered in Cyprus under number HE 479560, with its registered address at 4 Louki Akrita Street, Pediaios Building, Floor 4, Office 406, Ayios Andreas, 1100 Nicosia, Cyprus ("trackspot.ai", "we" or "us"), and the customer that has accepted our terms of service ("Customer" or "you").
This DPA forms part of the terms of service at /legal/terms (the "Terms"). It applies automatically when you accept the Terms. You do not need to sign it for it to apply. It applies whenever we process Customer Personal Data in providing the service.
This DPA replaces any earlier data processing terms between the parties for the service.
2. Definitions
Words not defined here have the meaning given in the Terms or in Data Protection Law.
- "Data Protection Law" means the General Data Protection Regulation (EU) 2016/679 ("GDPR"), the Cyprus law that implements it, and any other data protection law that applies to the processing under this DPA, including the UK GDPR and the Swiss Federal Act on Data Protection where they apply.
- "Customer Personal Data" means the personal data that we process on behalf of the Customer in providing the service.
- "Controller", "processor", "data subject", "personal data", "processing", "personal data breach" and "supervisory authority" have the meanings given in the GDPR.
- "Sub-processor" means a processor that we engage to process Customer Personal Data.
- "SCCs" means the standard contractual clauses for the transfer of personal data to third countries adopted by the European Commission in Decision (EU) 2021/914, as amended or replaced.
- "Service" means the trackspot.ai service as described in the Terms, including the tracking endpoints, the tracker, the API, the merchant dashboard and the partner portal.
3. Roles of the parties
For Customer Personal Data, the Customer is the controller and we are the processor. Where the Customer acts as a processor for a third party, such as an advertiser or a network client, we are a sub-processor, and the Customer is responsible for passing on the required terms and getting the required authorisations from its controller.
We are an independent controller for the personal data that we process to run our own business. This includes customer account and user data, billing data, support data and security logs. Our privacy policy at /legal/privacy covers that processing. This DPA does not apply to it.
Each party will comply with the Data Protection Law that applies to it.
4. Subject matter, duration, nature and purpose
- Subject matter: the provision of the Service to the Customer under the Terms.
- Duration: the term of the Terms, plus the period until we delete or return Customer Personal Data under section 15.
- Nature: collection, recording, storage, organisation, structuring, retrieval, consultation, analysis, combination, transmission, export, erasure and destruction of personal data, by automated means.
- Purpose: to track clicks, leads and sales that partners refer; to attribute conversions to partners; to detect fraud; to calculate and manage commissions; to prepare payouts; to run the partner portal; to send notifications, postbacks and webhooks that the Customer sets up; to produce reports; and to give support.
5. Data subjects and types of personal data
Categories of data subjects:
- The Customer's partners and affiliates, including influencers, publishers, referrers and sub-affiliates, and their staff.
- End visitors and buyers who click a partner link or use a partner coupon, and who visit or buy from the Customer.
- The Customer's users and staff, to the extent that their data appears in program data, such as approvals, notes and audit logs.
Types of personal data:
- Partner data: name, email, company, country, phone number, website or social profiles, login details for the partner portal, payout details (such as bank or wallet details), tax details and invoices, commission and payout history, and messages.
- Visitor and buyer data: IP address, user agent, referrer, country and region derived from the IP address, landing page, click ID, sub-IDs, coupon codes, cookie or local storage identifiers, and time of events.
- Conversion data: order ID, order amount and currency, product or plan details, customer or subscription identifiers, and, where the Customer chooses to send them, the buyer's email or name.
- Fraud signals: risk scores and flags derived from the data above.
- Any other personal data that the Customer chooses to send to the Service, for example in custom fields.
Special categories of data: none. The Customer will not send special category data or data about criminal convictions to the Service.
6. Customer instructions
We process Customer Personal Data only on the Customer's documented instructions, unless EU or Member State law requires otherwise. In that case, we will tell the Customer of that legal requirement before processing, unless the law forbids it.
The Customer's instructions are: the Terms and this DPA; the Customer's settings and use of the Service, including its dashboard settings, integrations, postbacks and API calls; and other written instructions that the Customer gives and we accept in writing. Instructions outside the scope of the Service may lead to extra fees, which we will agree with the Customer first.
We will tell the Customer promptly if we believe an instruction breaks Data Protection Law. We can then suspend that processing until the Customer confirms or changes the instruction.
The Customer is responsible for:
- Having a lawful basis for the processing, including any consent needed for cookies and similar technologies on its sites.
- Giving data subjects the notices that the law requires, including notice of the use of partner tracking.
- The accuracy and quality of the data it sends to us, and the lawfulness of its instructions.
- Its choices about where to send data, such as postbacks, webhooks and exports to partners or other tools.
7. Confidentiality of personnel
We give access to Customer Personal Data only to staff and contractors who need it to provide, support or secure the Service. Each of them is bound by a written duty of confidentiality or a statutory duty of confidentiality. We train them on their data protection duties.
8. Security measures
We implement technical and organisational measures that give a level of security appropriate to the risk, as Article 32 GDPR requires. We take into account the state of the art, the cost, and the nature, scope, context and purposes of the processing. Our measures include:
- Encryption in transit: all traffic to the Service, the API and the tracking endpoints uses TLS. Internal traffic between our systems is encrypted or runs on private networks.
- Access control: access to production systems and Customer Personal Data on a least-privilege, need-to-know basis. We remove access promptly when a person no longer needs it.
- Multi-factor authentication: required for all staff access to production systems and admin tools.
- Tenant isolation: each Customer's data carries a tenant identifier, and every application query filters on it, so that one Customer cannot see another Customer's data.
- Application security: password hashing, secure session cookies, rate limits, input validation, and edge protection against attacks and bots.
- Logging and monitoring: logs of access and security events, monitoring and alerts for unusual activity.
- Backups: regular backups, stored with restricted access, and tested restore procedures.
- Vulnerability management: regular updates of systems and dependencies, review of code changes, and a channel to report security issues at security@trackspot.ai.
- Incident response: a documented process to detect, investigate, contain and report incidents.
- Physical security: we use hosting providers whose data centres have physical access controls.
We may update these measures over time. An update will not reduce the overall level of security of the Service.
The Customer is responsible for the security of its own accounts, including the protection of passwords and API keys, the users it invites and the permissions it gives them.
9. Sub-processors
The Customer gives us a general authorisation to engage sub-processors. Our sub-processors fall into these categories: hosting and infrastructure, CDN and security (including Cloudflare), email delivery, and support tools. The current list of sub-processors by name, location and category is available on request at privacy@trackspot.ai.
Before a sub-processor processes Customer Personal Data, we sign a written contract with it. That contract imposes data protection duties that are no less protective than those in this DPA.
We will give the Customer at least 30 days' notice before we add or replace a sub-processor. We send notice by email to the account owner or in the dashboard.
The Customer can object to a new sub-processor on reasonable data protection grounds within those 30 days, by writing to privacy@trackspot.ai. If the Customer objects, we will discuss the concern in good faith and try to offer a reasonable alternative. If we cannot do this, the Customer can terminate the affected part of the Service before the new sub-processor starts, and we will refund any prepaid fees for the period after termination.
We remain liable to the Customer for the acts and omissions of our sub-processors as for our own, as the Terms set out.
10. International transfers
We may transfer Customer Personal Data outside the European Economic Area only in compliance with Chapter V of the GDPR.
Where a transfer is not covered by an adequacy decision or another valid mechanism, the SCCs apply and are incorporated into this DPA by reference, as follows:
- Module 2 (controller to processor) applies where the Customer is a controller.
- Module 3 (processor to processor) applies where the Customer is a processor.
- Clause 7 (docking clause) applies.
- Clause 9: option 2 (general written authorisation) applies, with the notice period in section 9 of this DPA.
- Clause 11: the optional language does not apply.
- Clause 17: the SCCs are governed by the law of Cyprus.
- Clause 18: disputes are resolved by the courts of Cyprus.
- Annex I is completed with the information in sections 1, 4 and 5 of this DPA. The competent supervisory authority is the Office of the Commissioner for Personal Data Protection in Cyprus, unless the SCCs require another.
- Annex II is completed with the measures in section 8 of this DPA.
- Annex III is the list of sub-processors available under section 9 of this DPA.
For transfers of personal data from the United Kingdom or Switzerland, the SCCs apply with the changes that the law of those countries requires, including the UK International Data Transfer Addendum where it applies.
We also apply the same safeguards to onward transfers to our sub-processors.
11. Help with data subject requests
Taking into account the nature of the processing, we will help the Customer, by appropriate technical and organisational measures, to respond to requests from data subjects to use their rights under Data Protection Law.
The Service lets the Customer find, export, correct and delete partner and conversion data. If the Customer cannot do what it needs through the Service, we will help on request.
If a data subject contacts us directly about Customer Personal Data, we will not respond to the request ourselves, except to tell the data subject to contact the Customer. We will pass the request to the Customer without undue delay.
12. Help with impact assessments and other duties
Taking into account the nature of the processing and the information available to us, we will give the Customer reasonable help with:
- Data protection impact assessments about the Customer's use of the Service.
- Prior consultations with a supervisory authority, where the law requires them.
- The Customer's security duties under Article 32 GDPR.
We can charge reasonable fees for help that goes beyond the documentation we make available and that is not required because of our own breach.
13. Personal data breaches
We will notify the Customer of a personal data breach that affects Customer Personal Data without undue delay, and in any case within 48 hours after we become aware of it.
The notice will include, as far as we know at the time:
- The nature of the breach, including the categories and approximate number of data subjects and records affected.
- The likely consequences of the breach.
- The measures we have taken or propose to take to address the breach and reduce its effects.
- A contact point for more information.
If we cannot give all the information at once, we will give it in phases without further undue delay. We will take reasonable steps to contain and investigate the breach, and we will cooperate with the Customer.
The Customer is responsible for notifying supervisory authorities and data subjects where the law requires. Our notice of a breach is not an admission of fault or liability.
14. Audits and information
We will make available to the Customer the information reasonably needed to show that we comply with Article 28 GDPR and this DPA.
Audits work in this order:
- Documentation first. On written request, we will answer reasonable security and data protection questionnaires and give relevant documentation, such as summaries of our policies and measures. The Customer will first try to use this documentation to meet its audit needs.
- On-site audit. If the documentation is not enough to show compliance, or a supervisory authority requires it, the Customer can audit us, itself or through an independent auditor bound by confidentiality. The Customer can do this once in any 12-month period, unless a personal data breach or a supervisory authority requires an extra audit.
- Notice and scope. The Customer must give at least 30 days' written notice and a proposed scope. The audit takes place during business hours, avoids disruption to our business, and does not give access to other customers' data or to information that would compromise our security.
- Cost. The Customer pays its own costs of an audit, and our reasonable costs if the audit takes more than one business day of our staff time.
The results of an audit are our confidential information.
15. Return and deletion of data
When the Terms end, the Customer has 60 days to export Customer Personal Data from the Service with the export tools and the API.
After the 60-day export window, we will delete Customer Personal Data from our live systems within 30 days, unless EU or Member State law requires us to keep it. Deleted data rolls off our backups as the backups expire on their normal cycle. Until then, backups stay protected under this DPA and we do not use them except to restore the Service.
During the term, Customer Personal Data is kept according to the retention settings of the Service. Raw click records are kept for 25 months, conversion request logs for 180 days and postback logs for 90 days, unless the Customer deletes them earlier.
On request, we will confirm the deletion in writing.
16. Liability
Each party's liability under or in connection with this DPA, including under the SCCs to the extent the law allows, is subject to the limits and exclusions of liability in the Terms. Nothing in this DPA limits a party's liability to data subjects that cannot be limited under Data Protection Law.
17. Governing law and jurisdiction
This DPA is governed by the law of the Republic of Cyprus. The courts of Cyprus have exclusive jurisdiction over any dispute about this DPA, unless the SCCs or Data Protection Law require otherwise.
18. Order of precedence
If there is a conflict between documents, this order applies:
- The SCCs, where they apply.
- This DPA.
- The Terms.
In all other respects the Terms continue to apply. If a part of this DPA is invalid, the rest stays in force.
19. Changes to this DPA
We may update this DPA when the law or the Service changes. We show the date of the last change at the top of this page. We will give at least 30 days' notice of a material change. A change will not reduce the overall level of protection of Customer Personal Data, unless the law requires it.
20. How to get a signed copy
This DPA applies without a signature. If you need a countersigned copy for your records, write to legal@trackspot.ai with your company's legal name, address, registration number and the name and email of the signatory. We will send you a copy for signature.
For questions about this DPA or the list of sub-processors, write to privacy@trackspot.ai.
21. Contact
Questions about this document: email legal@trackspot.ai or use the contact page.
CVA TECH LTD, registration number HE 479560, 4 Louki Akrita Street, Pediaios Building, Floor 4, Office 406, Ayios Andreas, 1100 Nicosia, Cyprus.