Data Processing Agreement
This Data Processing Agreement sets the terms on which Cynopta, Inc. ("Cynopta," "we," "us," or "our") processes personal data in Dashboard Reports for Customers who use the Cynopta SDK. It forms part of our Terms of Use, and you accept it on the setup page before you receive your license file. Part B of our Privacy Policy describes each report that the SDK sends.
| In short | |
|---|---|
| What it covers | Personal Data in Dashboard Reports from your Licensed Apps (clause 3) |
| Roles | You are the Controller. Cynopta is your Processor, and your service provider under the CCPA |
| Not covered | Usage Reports, Crash Reports, the Google Play Integrity token and your staff's accounts. The Privacy Policy describes them |
| Where the data is | United States: Amazon Web Services and Cloudflare, in North Virginia (Annex 3) |
| Transfers | Standard Contractual Clauses, with the UK Addendum and the Swiss adjustments (clause 8) |
| Retention | 13 months, unless you ask for a shorter or longer period (clause 11) |
| Breach notice | Without undue delay, and within 72 hours (clause 10) |
Terms of the Processing
These clauses set out what Cynopta does with the Personal Data in Dashboard Reports, and what each party is responsible for.
1. Parties and status of this DPA
This Data Processing Agreement (the "DPA") is between Cynopta, Inc., a Delaware corporation ("Cynopta"), and the person or entity that accepted the Cynopta Terms of Use ("you"). If you signed another agreement with Cynopta that covers the SDK, that agreement takes the place of the Terms of Use here. In both cases it is the "Agreement".
1.1 Part of the Agreement. This DPA forms part of the Agreement. It applies from the day you accept the Agreement, for as long as Cynopta processes Dashboard Reports for you.
1.2 What it does. Section 7 of the Terms of Use says that Cynopta processes personal data for you under this DPA. This DPA sets the terms of that processing.
1.3 Order of precedence. If this DPA and the Agreement disagree about the processing of Personal Data, this DPA prevails. If the Standard Contractual Clauses apply and disagree with this DPA, the Standard Contractual Clauses prevail.
1.4 Signed data processing terms. If you and Cynopta signed a separate data processing agreement that covers the SDK, it replaces this DPA.
2. Definitions
Terms that the Agreement defines, such as "SDK" and "Licensed App", have the same meaning here.
| Term | Meaning |
|---|---|
| Dashboard Report | The report that the SDK in a Licensed App sends to Cynopta while dashboard reporting is on. It holds values that the SDK calculated on the phone, under a Report User ID. Annex 1 describes it |
| Report User ID | A random identifier that the SDK creates for one installation of a Licensed App. It stays the same until the End User uninstalls the app or clears its data. It is a pseudonymized identifier. The Privacy Policy calls it the installation identifier |
| Usage Report | The report that the SDK sends for licensing and billing. It carries your license ID and counts of assessments, and no user or phone identifier. It cannot be switched off |
| Crash Report | A report on an error in the SDK's own code |
| End User | A person who uses a Licensed App |
| Personal Data | Any information in a Dashboard Report that relates to an identified or identifiable person, or that Data Protection Laws treat as personal data or personal information. Cynopta treats everything in a Dashboard Report as Personal Data |
| Data Protection Laws | The privacy and data protection laws that apply to a party's processing of Personal Data under this DPA. Examples are the EU General Data Protection Regulation 2016/679 ("GDPR"), the UK GDPR, the Swiss Federal Act on Data Protection, the California Consumer Privacy Act ("CCPA"), Thailand's Personal Data Protection Act B.E. 2562, and India's Digital Personal Data Protection Act 2023 |
| Controller, Processor, Data Subject, Processing | The meanings that the GDPR gives them. They include the matching terms of other Data Protection Laws, such as "business" and "service provider", or "data fiduciary" and "data processor" |
| Sub-processor | A third party that Cynopta engages to process Personal Data for you |
| Personal Data Breach | A breach of security that leads to the accidental or unlawful destruction, loss, alteration or unauthorized disclosure of Personal Data, or to unauthorized access to it, on systems that Cynopta or its Sub-processors manage |
| Standard Contractual Clauses | The clauses annexed to European Commission Implementing Decision (EU) 2021/914 |
3. Scope and roles
3.1 What this DPA covers. This DPA covers the Personal Data in Dashboard Reports. For that data you are the Controller and Cynopta is your Processor. If you act as a Processor for another company, Cynopta is your Sub-processor, and you confirm that the Controller authorized your instructions to Cynopta.
3.2 What this DPA does not cover. The SDK and Cynopta's services handle other data that is outside this DPA. The table names each kind separately.
| Data | Who decides how it is used | Where it is described |
|---|---|---|
| The signals that the SDK reads on the phone, its local store and the score it calculates there | You, inside your app. Cynopta receives this data only when a report in this table carries it | The SDK documentation |
| Usage Reports. They cannot be switched off | Cynopta, as a Controller, for licensing, metering and billing | Part B of the Cynopta Privacy Policy |
| Crash Reports. They are on by default, and you can switch them off | Cynopta, as a Controller, to support and fix the SDK | Part B of the Cynopta Privacy Policy |
| The Google Play Integrity token, on Android only | Google, under its own terms, for the request that the SDK sends to it. Cynopta, as a Controller, for the token that it receives with a Usage Report | Part B of the Cynopta Privacy Policy |
| The accounts of your staff on the setup page and the dashboard, and your business contact details | Cynopta, as a Controller | Part A of the Cynopta Privacy Policy |
3.3 Your choice of mode. Dashboard reporting has three modes:
- Off. The SDK sends no Dashboard Reports.
- Security-related data only. The SDK sends the score, the security findings and the values that Annex 1 lists for this mode.
- Everything. The SDK sends every value that it calculated, and the debugging and research data that Annex 1 describes.
Dashboard reporting is on unless you ask Cynopta to switch it off. The configuration file that Cynopta issues with your license file sets the mode. To change the mode, including to switch dashboard reporting off, write to support@cynopta.com. The mode you choose is part of your instructions to Cynopta.
3.4 When reporting is off. While dashboard reporting is off, Cynopta receives no Dashboard Reports from your Licensed Apps and processes no Personal Data for you under this DPA. Usage Reports continue.
3.5 Details of the processing. Annex 1 describes the subject, duration, nature and purpose of the processing, the types of Personal Data and the categories of Data Subjects.
4. Your instructions and each party's obligations
4.1 Instructions. Cynopta processes Personal Data only on your documented instructions. Your instructions are the Agreement, this DPA, the reporting mode you choose, the settings you choose on the setup page and the dashboard, and any later written instruction that Cynopta accepts.
4.2 Purposes. Cynopta processes Personal Data only for these purposes:
- to give you your dashboard
- to provide, license, meter, support and fix the SDK for you
- to keep its systems secure
- to comply with a law that applies to Cynopta
4.3 What Cynopta will not do. Cynopta will not:
- sell Personal Data, or share it for cross-context behavioral advertising
- combine your Personal Data with data from other customers
- use your Personal Data for research or to train models, unless you and Cynopta signed a separate written agreement that allows it
- try to identify an End User from a Dashboard Report
- keep, use or disclose Personal Data outside its direct business relationship with you
4.4 Processing that a law requires. If a law requires Cynopta to process Personal Data in another way, Cynopta tells you before it does so, unless that law forbids the notice.
4.5 Instructions that may break the law. Cynopta tells you without undue delay if it believes that an instruction breaks Data Protection Laws. Cynopta may pause the work on that instruction until you confirm or change it.
4.6 Your obligations. You are responsible for the following:
- a legal basis for the SDK in your Licensed Apps, and the notices and consents that End Users must get, including for the SDK's operation while the app is not active and for the reports you leave on
- your app store privacy disclosures
- the lawfulness of your instructions to Cynopta
- keeping personal data out of the values you pass to the SDK, such as action names. The action names you choose appear in Dashboard Reports
- telling Cynopta before you use the SDK in an app directed at children
5. Confidentiality and personnel
5.1 Cynopta gives access to Personal Data only to the people who need it for the purposes in clause 4.2.
5.2 Each of those people is bound by a written duty of confidentiality, or by a legal one, that continues after their work for Cynopta ends.
5.3 Cynopta's team does not analyze Personal Data on local machines.
6. Security
6.1 Cynopta's measures. Cynopta applies the technical and organizational measures in Annex 2. Cynopta may change them as its systems develop, and no change may materially lower the protection of Personal Data.
6.2 Certifications. At the date of this DPA, Cynopta holds no SOC 2 report and no ISO 27001 certificate. Annex 2 states which measures are in place and which are planned.
6.3 Your part. You are responsible for the security of your Licensed Apps, your license file and API key, and the accounts of your staff on the setup page and the dashboard.
7. Sub-processors
7.1 Authorization. You give Cynopta a general authorization to engage Sub-processors. Annex 3 lists the Sub-processors at the date of this DPA.
7.2 Changes. Cynopta tells you at least 30 days before it adds or replaces a Sub-processor. It sends the notice to the e-mail address of your account owner on the setup page.
7.3 Objection. You may object in writing within 14 days of the notice, on reasonable data protection grounds. Cynopta and you then work in good faith on a solution. If none is found within 30 days, you may ask Cynopta to switch dashboard reporting off, or end the Agreement without a penalty.
7.4 Terms and liability. Cynopta binds each Sub-processor by a written contract that protects Personal Data to at least the standard of this DPA. Cynopta stays liable to you for what its Sub-processors do with Personal Data.
8. International transfers
8.1 Where the data is. Cynopta stores and processes Dashboard Reports in the United States, at the locations in Annex 3. Cynopta offers no other region at the date of this DPA. Sending a Dashboard Report to Cynopta is therefore a transfer of Personal Data to the United States.
8.2 Transfers from the EEA, the United Kingdom and Switzerland. Where the GDPR, the UK GDPR or Swiss law applies to your Personal Data, the Standard Contractual Clauses form part of this DPA, as follows:
- Module Two (Controller to Processor) applies. Module Three (Processor to Processor) applies instead where you act as a Processor.
- You are the data exporter and Cynopta is the data importer.
- Clause 7 (docking) does not apply. In Clause 9, Option 2 (general written authorization) applies, with the notice period in clause 7.2 of this DPA. In Clause 11, the optional wording does not apply.
- In Clause 17, Option 2 applies: the Standard Contractual Clauses are governed by the law of the EU Member State in which you are established or, where that law does not allow for third-party beneficiary rights, by the law of Ireland. In Clause 18, the courts of that same Member State have jurisdiction.
- Annex 1 of this DPA completes Annex I, Annex 2 completes Annex II, and Annex 3 completes Annex III.
- For the United Kingdom, the International Data Transfer Addendum issued by the UK Information Commissioner applies, and Annexes 1 to 3 of this DPA complete its tables.
- For Switzerland, references to the GDPR read as references to the Swiss Federal Act on Data Protection, and the Swiss Federal Data Protection and Information Commissioner is the supervisory authority.
8.3 Transfers from other countries. Where the law of another country, such as Thailand or India, sets conditions for sending Personal Data abroad, you decide whether the transfer may take place. Cynopta gives you reasonable help, including signing transfer terms that the law requires. If that law does not allow a transfer to the United States, keep dashboard reporting off.
8.4 Requests from authorities. If a public authority asks Cynopta to disclose Personal Data, Cynopta tells you before it answers, unless a law forbids the notice. Cynopta discloses only what the law requires, and it challenges a request that it believes is unlawful.
9. Help with requests, assessments and regulators
9.1 Requests from End Users. A Dashboard Report identifies an installation of your app by its Report User ID. Cynopta cannot link that ID to a named person, and the SDK does not give your app the Report User ID. So Cynopta cannot find the reports of one End User from a name, an account or a phone number. Cynopta helps you answer End Users' requests in these ways:
- On your written request, Cynopta deletes all Dashboard Reports of a Licensed App, or those of a period you name.
- If you give Cynopta a Report User ID, Cynopta exports or deletes the Dashboard Reports under that ID.
- If an End User writes to Cynopta about a Licensed App, Cynopta forwards the request to you and does not answer it for you.
9.2 Impact assessments. Cynopta gives you the information that you reasonably need for a data protection impact assessment, or for a consultation with a regulator, about the Dashboard Reports. That information includes this DPA, its Annexes and the SDK's data documentation.
9.3 Regulators. Cynopta cooperates with a regulator that asks about the processing under this DPA, and tells you about the request unless a law forbids it.
9.4 Cost. Cynopta gives this help at no charge within reason.
10. Personal Data Breach
10.1 Notice. Cynopta tells you about a Personal Data Breach without undue delay, and no later than 72 hours after it becomes aware of the breach. It sends the notice to the e-mail address of your account owner on the setup page.
10.2 Content. The notice describes, as far as Cynopta knows them:
- what happened, and when
- the Licensed Apps concerned, and the approximate number of installations and Dashboard Reports
- the likely consequences
- what Cynopta did, and what it advises you to do
Cynopta sends what it knows first and adds the rest as it learns more.
10.3 Response. Cynopta acts without delay to contain the breach, to investigate it and to stop it from happening again.
10.4 Your notifications. You decide whether to notify a regulator or End Users, and you send those notifications. Cynopta does not contact End Users. A notice under this clause is not an admission of fault or liability by Cynopta.
11. Retention, deletion and return
11.1 Retention. Cynopta keeps each Dashboard Report for 13 months after it receives the report, and then deletes it. You may ask Cynopta in writing to delete your Dashboard Reports sooner or to keep them longer.
11.2 Deletion on request. Cynopta completes a deletion that you request within 30 days.
11.3 End of the Agreement. When the Agreement ends, Cynopta deletes your Dashboard Reports within 30 days. If you ask before the end, Cynopta first gives you an export in a machine-readable format. Cynopta may keep Personal Data longer only where a law requires it, and then only for that purpose.
11.4 Copies of your app that are already installed. Copies of a Licensed App on End Users' phones keep sending Dashboard Reports until the End User updates or uninstalls the app. Before the Agreement ends, release a version of each Licensed App that has dashboard reporting off or does not include the SDK. Cynopta handles a Dashboard Report that arrives after the Agreement ends under this DPA. Cynopta does not use that report, and deletes it within 30 days of receiving it.
11.5 Data on the phone. On Android, the SDK keeps its local store inside your app's storage and out of device backups, and the phone removes the store when the End User uninstalls the app. Your Android app can also delete the store with Cynopta.stop(context, true). On the iPhone, a list of up to 10 install dates and a random encryption key stay in the Keychain after an uninstall.
11.6 Confirmation. On your request, Cynopta confirms in writing that it deleted your Dashboard Reports.
12. Audit and records
12.1 Records. Cynopta keeps a record of the processing that it carries out for you, and gives you the information you need to show that this DPA is followed.
12.2 Written questions first. You may send Cynopta written questions about its compliance with this DPA once every 12 months. You may also do so after a Personal Data Breach, or when a regulator requires it. Cynopta answers within 30 days.
12.3 Audit. If the answers do not give you what Data Protection Laws require, you may audit Cynopta, or appoint an independent auditor who is bound by confidentiality. You give 30 days' notice, the audit takes place in business hours, and you pay for it. The audit gives no access to other customers' data.
12.4 Cloud providers. Cynopta's systems run at the cloud providers in Annex 3. An audit of their data centers takes place through the audit reports that those providers publish.
12.5 Future reports. If Cynopta obtains an independent audit report or a certification, Cynopta gives you a copy on request. You then use that report first, before you ask for an audit.
13. Liability, term and general terms
13.1 Liability. The limits and exclusions of liability in the Agreement apply to this DPA. Nothing in this DPA limits a party's liability to a Data Subject under the Standard Contractual Clauses, or any liability that the law does not allow a party to limit.
13.2 Term. This DPA ends when Cynopta has deleted all Personal Data that it processed for you.
13.3 Changes. Cynopta may update this DPA in the way that the Agreement allows for its own updates. Cynopta gives you 30 days' notice of a change that materially affects the protection of Personal Data.
13.4 California. Where the CCPA applies, Cynopta acts as your service provider. Cynopta confirms that it understands the restrictions in clause 4.3 and will follow them. Cynopta tells you if it can no longer meet its obligations under the CCPA.
13.5 Governing law. The laws of the State of Delaware, United States, and the courts that the Agreement names govern this DPA. The Standard Contractual Clauses follow the law and the courts in clause 8.2.
13.6 Contact. Write to Cynopta about this DPA at privacy@cynopta.com. Cynopta writes to the e-mail address of your account owner on the setup page.
Details of the Processing
The Annexes describe the processing, the security measures and the Sub-processors. They complete the Annexes of the Standard Contractual Clauses.
Annex 1: Description of the processing
A. The parties and the processing
| Item | Description |
|---|---|
| Controller and data exporter | You. Your contact is the account owner on the setup page |
| Processor and data importer | Cynopta, Inc. Contact: privacy@cynopta.com |
| Subject of the processing | Dashboard Reports from your Licensed Apps |
| Nature of the processing | Cynopta receives the reports, stores them, calculates daily figures for each Licensed App, shows them on your dashboard and deletes them |
| Purpose | The purposes in clause 4.2 |
| Data Subjects | End Users of your Licensed Apps |
| Frequency | About one Dashboard Report every 24 hours from each installation, while dashboard reporting is on |
| Duration | The term of the Agreement, and the retention period in clause 11 |
| Special categories of data | The SDK is not designed to collect special categories of Personal Data |
| Platforms | Android. Cynopta updates this Annex when the iOS SDK sends Dashboard Reports |
B. Personal Data in a Dashboard Report, by mode
| Data | Security-related data only | Everything |
|---|---|---|
| The Report User ID | Yes | Yes |
| The time of the report, the SDK version, your API key, and the package name and version of your app | Yes | Yes |
| The phone's manufacturer, model and operating system version | Yes | Yes |
| The daily score, its classification and the partial scores behind it | Yes | Yes |
| Security findings about the phone: a rooted phone, an emulator, an app cloner, a hooking tool, an attached debugger, USB or wireless debugging, an accessibility permission in use, and signs of a phone farm | Yes | Yes |
| Summaries of touch and motion: the share and count of simulated touches, and whether the phone lies still | Yes | Yes |
| The number of assessments for each action name that you chose | Yes | Yes |
| The state of the license, and figures on the SDK's own operation, such as its storage size and processor time | Yes | Yes |
| Calculated values about how the phone is used: screen and charging patterns, sleep and wake times, counts of installed apps by category, network provider and country, Wi-Fi and cellular quality, and time on home and work Wi-Fi | No | Yes |
| The names of installed apps that hold the accessibility permission, and a hashed fingerprint of the installed apps | No | Yes |
| Debugging and research data: up to 100 gesture summaries from the last 2 days. Each one holds the name of the screen in your app, the timing and duration, the start and end coordinates of the touch, its path, speed, pressure and touch size, and the tool and input device used | No | Yes |
Cynopta's servers also see the IP address that sends a Dashboard Report, as every internet server does. Cynopta does not store it with the report. If Cynopta switches on network diagnostics to investigate a fault, they keep IP addresses for up to 7 days.
Annex 2: Technical and organizational measures
The "Status" column says whether a measure is in place today. A measure marked "Planned" is not yet a commitment.
| Area | Measure | Status |
|---|---|---|
| Encryption in transit | The SDK sends Dashboard Reports to Cynopta over HTTPS (TLS) | In place on Android |
| Pseudonymization | A Dashboard Report carries the Report User ID. The SDK builds it from random values that it creates on the phone | In place on Android |
| Data minimization | Three reporting modes: off, security-related data only, and everything. You choose the mode | In place on Android |
| Storage on the phone | The Android SDK encrypts the names and text values in its local store with AES-256-GCM. It keeps the store in a folder that Android does not include in a device backup | In place on Android |
| Encryption at rest on servers | Data in Cloudflare is under Cloudflare's encryption. Dashboard Reports in AWS are encrypted at rest | In place |
| Hosting | The collection pipeline runs in Cynopta's own AWS account. Development, staging and production are separate environments | In place |
| Separation of customers | Cynopta does not combine one customer's data with another's. It stores Dashboard Reports by customer and by app | In place |
| Access control | Staff and customers sign in with Google, or with a one-time code sent by e-mail. Restricted pages admit only listed addresses or domains | In place |
| Administrator access | Named administrators, least privilege and regular access reviews | Planned |
| Monitoring and logging | Monitoring and audit logging are built into Cynopta's cloud services | In place |
| Personnel | Staff are bound by confidentiality. The team does not analyze Personal Data on local machines | In place |
| Secure development | Static code analysis of the SDK | In place for the Android SDK |
| Security testing | A penetration test of the systems that hold Dashboard Reports | Not done yet |
| Policies | Information security policies aligned with ISO 27001, reviewed and signed by the team | In progress |
| Retention and deletion | Deletion after 13 months, and on your request | Committed in clause 11 |
| Incident response | A written procedure for detecting, handling and reporting a Personal Data Breach | Planned |
| Backup and recovery | Backup and recovery of Dashboard Reports | Planned |
| Certifications | None. Cynopta holds no SOC 2 report and no ISO 27001 certificate | Not held |
Annex 3: Sub-processors
Sub-processors for Dashboard Reports
| Sub-processor | What it does | Location |
|---|---|---|
| Amazon Web Services, Inc. | Hosts the collection pipeline that receives and stores Dashboard Reports, in Cynopta's own account | United States (North Virginia) |
| Cloudflare, Inc. | Hosts the license service, the setup page and the client dashboard pages, which show you figures calculated from Dashboard Reports | United States (North Virginia) |
Other recipients, outside this DPA
These companies receive the data that clause 3.2 places outside this DPA. They are listed so that you have the whole picture. They are not Sub-processors under this DPA.
| Recipient | What it receives | Location |
|---|---|---|
| Sentry (Functional Software, Inc.) | Crash Reports from the SDK's own code. Sentry does not store IP addresses | Germany |
| Google LLC | On Android, a hash of the Usage Report. Google returns a Google Play Integrity token that the SDK sends to Cynopta | Decided by Google |
| Cloudflare, Inc. | Usage Reports, in the license service and its usage log | United States (North Virginia) |
| Amazon Web Services, Inc. | The one-time sign-in codes sent to your staff by e-mail | United States (North Virginia) |
Privacy Contact
For questions about this DPA, or to send an instruction, a request or an objection under it, please contact us at:
Cynopta, Inc., a Delaware corporation, 500 West 43rd St., Suite 31A, New York, NY 10036, USA. See also our Privacy Policy and Terms of Use.