Privacy Policy
This Privacy Policy explains how Cynopta, Inc. ("Cynopta," "we," "us," or "our") handles personal information. We work with data in three different settings, so this policy has three main parts. Part A covers our website and business relationships. Part B covers the Cynopta SDK that our Customers build into their apps. Part C covers apps that Cynopta and its affiliates publish themselves, each of which also has its own privacy notice. Part D applies to all three.
| Part A: Website and business relationships | Part B: The SDK in our Customers' apps | Part C: Cynopta's own apps | |
|---|---|---|---|
| Who it covers | Website visitors, prospects, and our Customers' developers and team members | People who use a Customer's app that includes the Cynopta SDK ("End Users") | People who use an app that Cynopta or its affiliates publish for research |
| What reaches Cynopta | Browsing and device information, the details you give us, sign-in and setup page records, and visit records for Cynopta Insights pages | Always: a usage report with no user or device identifiers. Optional, on by default and controlled by the Customer: crash reports; dashboard reports with a random installation identifier and derived device and behavioral data; and, from debug builds and in the full report mode of dashboard reports, raw touch data for debugging and research. On Android, Google checks each usage report. The SDK's score itself is computed on the device. | Set out in each app's own privacy notice. Where an app includes the SDK, the reports in Part B |
| Cynopta's role | Controller | The app provider is the controller. Cynopta is its processor for its dashboard, and a controller for licensing, billing and SDK quality | Set out in each app's own privacy notice |
| Where to send requests | privacy@cynopta.com | The company that provides the app, or Cynopta for its own purposes | The contact in each app's own privacy notice, or privacy@cynopta.com |
Our Website and Business Relationships
This part covers personal information we collect through our website, our sales and marketing activities, developer onboarding, and the accounts our Customers hold with us. For this information, Cynopta is the controller.
A1. Who Part A Covers
- Website visitors: people who visit cynopta.com or any of its subdomains.
- Prospects: people who contact us, request a demo, or view Cynopta Insights demo pages and other materials we share with them.
- Developers and Customer team members: people who sign up through the SDK setup page at setup.cynopta.com, integrate the SDK, use the client dashboard, or act as a Customer's billing or support contact. A "Customer" is a company or person that uses the SDK in its apps.
Part A does not cover data processed by the SDK inside our Customers' apps (Part B), apps that Cynopta and its affiliates publish themselves (Part C), or our Customers' own apps and websites, which have their own privacy notices.
A2. Information We Collect
A2.1 When you visit our website
- IP address, and the approximate location (city or region) derived from it
- Browser type and version, language preference, operating system and device type
- Pages viewed, the time of your visit, and the website that referred you
- Information from cookies and similar technologies (see A3)
Our hosting and content delivery provider, Cloudflare, processes connection data such as IP addresses to deliver the website and protect it against attacks. Our website loads its fonts from Google Fonts, so Google receives your IP address when a page loads.
A2.2 Information you give us
When you use our contact form or email us, for example to request a demo, we collect your name, work email address, company, job title and the content of your message. When you send the contact form, we keep your message on our servers and our email provider delivers it to our team. If the form cannot reach our servers, it opens your own email app instead. Providing this information is voluntary, but we need it to respond to you.
A2.3 Cynopta Insights and other shared materials
Cynopta Insights demo pages, and other materials prepared for a specific prospect, are available only to approved email addresses. Cloudflare Access handles the sign-in. When you access them, we collect the email address you sign in with and a record of your access: which pages and sections you open, which sections you expand, how far you scroll, how long you spend on each section, and when. Each page tells you that it records which parts you read. We use these records to provide access, keep the materials secure, and follow up with you about your interest in our services. These records are linked to you. We do not record your IP address with them.
A2.4 Developer onboarding, the client dashboard and billing
- Sign-up and onboarding: your name, work email address, company and role, the package names and platforms of the apps you integrate, and any access request you send us with its note. You sign in with Google, or with a one-time code that we send by email. When you ask for a code, Cloudflare Turnstile checks that the request comes from a person. While you integrate the SDK, the usage reports from your debug and release builds show the integration status on the setup page, and crash reports from your builds help us support the integration (see B3).
- Setup page activity: which steps of the setup page you complete, how you reached the page (for example from Cynopta Insights, an email or GitHub), and whether you used an AI coding agent. We do not store your IP address with these records
- Private links: when a private link fetches a license file, we record the time, the country and the type of browser or tool
- Setup assistant: the questions you ask the assistant on the setup page, and its answers
- Acceptance records: which versions of our Terms of Use, this Privacy Policy and our Data Processing Agreement were accepted, by whom, for which company, and when
- Client dashboard: if you use it, your sign-in information, settings and the features you use
- Billing: billing contact and company details, license, plan, subscription and invoice records, and the daily counts of assessments reported by the SDK (see B3). Card payments are handled by Stripe; we do not receive full card numbers
- Communications: support requests and other correspondence about the account
Providing this information is voluntary, but we cannot open or run an account without it. Activity of a Customer's team on the setup page and in the dashboard is covered here. Data about End Users that appears in the dashboard is covered in Part B.
A3. Cookies and Similar Technologies
The SDK setup page and Cynopta Insights pages use cookies and similar technologies, such as browser storage, for the purposes below. Our main website sets no cookies of its own and uses no analytics tool. If Cloudflare's security checks ask your browser to pass a challenge, Cloudflare sets a strictly necessary cookie (cf_clearance) to remember the result. We do not use retargeting pixels, and we do not use cookies to show you ads on other websites. If we measure whether our own ads lead people to our website or setup page, for example with a Google Ads conversion tag, we will list the tag in the table below before we use it, and use it only with your consent where the law requires it.
- Strictly necessary: needed to deliver and secure the website, and to keep you signed in to the setup page and to shared materials. These do not require consent.
- Measurement: random identifiers that let us count which steps of the setup page people complete, and link your visits to Cynopta Insights pages (see A2.3).
Your choices
You can delete cookies and browser storage at any time in your browser settings. If you delete them, you stay signed out until you sign in again, and we count your next visit as a new one.
| Name | Provider | Purpose | Category | Duration |
|---|---|---|---|---|
| Sign-in session cookie | Cynopta | Keeps you signed in to the setup page | Strictly necessary | 7 days |
| cy_vid | Cynopta | Holds a random identifier, so that we can count which steps of the setup page people complete | Measurement | 180 days |
| CF_Authorization | Cloudflare Access | Keeps you signed in to Cynopta Insights pages and other shared materials | Strictly necessary | Until your sign-in session ends |
| mc_vid | Cynopta | Holds a random identifier in your browser's local storage, so that we can link your visits to Cynopta Insights pages | Measurement | Until you clear it |
| mc_sid | Cynopta | Holds a random identifier for one visit to Cynopta Insights pages in your browser's session storage | Measurement | Until you close the tab |
A4. How We Use Information and Our Legal Bases
Where the EU General Data Protection Regulation (GDPR) or the UK GDPR applies, we rely on the legal basis shown for each purpose. Where the contract is between Cynopta and your employer, we process your information as its representative on the basis of our legitimate interests in running that business relationship.
| Purpose | Information used | Legal basis |
|---|---|---|
| Deliver and secure the website, the setup page and Cynopta Insights pages | Connection data, server logs, strictly necessary cookies | Legitimate interests in running a secure, working website and services (Art. 6(1)(f)) |
| Respond to inquiries and demo requests | Contact details, message content | Legitimate interests in responding to business inquiries, or steps you ask us to take before a contract with you (Art. 6(1)(b)) |
| Provide Cynopta Insights and shared materials, and follow up | Sign-in email address, access records | Legitimate interests in sharing materials securely and following up on a prospect's interest in our services; consent where a page asks for it (Art. 6(1)(a)) |
| Onboard developers and support integration | Sign-up details, package names, build and crash information, integration status | Performance of a contract with you, or legitimate interests in providing the services your employer ordered |
| Run accounts, licenses, the setup page, the client dashboard and support | Account details, license records, dashboard activity, communications | As above |
| Answer setup questions | Setup assistant questions and answers | As above |
| Billing and plan limits | Billing information, license records, daily assessment counts | As above; legal obligations for tax and accounting records (Art. 6(1)(c)) |
| Improve the setup page | Setup page activity | Legitimate interests in making the setup page easier to use |
| Keep records of accepted terms | Acceptance records | Legitimate interests in documenting what was agreed; legal obligations |
| Sales and marketing emails about our products | Name, work email address, company | Consent, or legitimate interests in telling business contacts about our products where the law allows it. You can opt out at any time by replying or by writing to privacy@cynopta.com |
| Security, fraud prevention and protecting our rights | Any of the above, as needed | Legitimate interests in protecting our services, users and rights; legal obligations |
| Comply with law and respond to lawful requests | As needed | Legal obligations |
You can object to processing based on legitimate interests (see A7). We do not sell personal information or use it for behavioral advertising.
A5. Who We Share Information With
- Service providers: hosting and content delivery, the setup service and file storage (Cloudflare), cloud infrastructure (Amazon Web Services, and Neon for the setup service database, in North Virginia, United States), sign-in for shared materials and checks on sign-in requests (Cloudflare), sign-in with Google, company email and website fonts (Google), emails that carry sign-in codes and contact form messages (Amazon Web Services), error monitoring for the SDK (Sentry), answers from the setup assistant (OpenAI, which does not receive your email address and does not keep the questions) and payments (Stripe). Most act only on our instructions. Some, such as payment processors, also use data for their own legal and fraud-prevention purposes under their own privacy policies. We update this list when our providers change.
- Business transfers: if Cynopta is involved in a merger, acquisition, financing, reorganization or sale of assets, personal information may be transferred as part of that transaction.
- Legal requirements: where we believe in good faith that disclosure is necessary to comply with the law, protect our rights or property, prevent fraud or illegal activity, or protect anyone's safety.
- With your consent: in any other case where you have agreed.
A6. How Long We Keep Information
- Server and security logs: 30 days, or longer where needed to investigate a specific incident
- Inquiries and demo requests: 24 months after our last contact with you
- Cynopta Insights and shared-materials access records: 12 months
- Setup page sign-in sessions: 7 days
- Setup assistant questions: 12 months
- Account details, setup page activity and dashboard activity: for the term of the agreement and 12 months afterwards
- Billing and accounting records: seven (7) years, as tax and accounting law requires
- Contracts and acceptance records: for the term of the agreement and the period in which legal claims can be brought
- Support communications: 24 months after the request is closed
- Marketing preferences: until you opt out, plus a record of the opt-out so that we continue to respect it
We may keep information longer where a legal hold or ongoing dispute requires it.
A7. Your Rights
Depending on where you live, you may have the right to:
- access the personal information we hold about you and receive a copy
- correct inaccurate or incomplete information
- delete your information, subject to our legal obligations
- restrict our processing in certain circumstances
- receive your information in a portable, machine-readable format
- object to processing based on legitimate interests, and to direct marketing at any time
- withdraw consent at any time, without affecting processing that took place before
To exercise these rights, email privacy@cynopta.com. If you include the email address you used with us, we can locate and delete the information linked to it. We may need to verify your identity first. We respond within one (1) month under the GDPR and UK GDPR, which can be extended where the law allows, or within the period your local law requires. You can also complain to your local data protection authority or, in the United Kingdom, the Information Commissioner's Office (ICO).
If you use an app that includes the Cynopta SDK, see B8. If you use one of our own apps, see C4.
A8. California Residents
This section applies to California residents to the extent the California Consumer Privacy Act, as amended (the "CCPA"), applies to our processing. We collect the categories of personal information described in A2: identifiers (such as name, email address and IP address), professional information (company and job title), commercial information (plans and billing records), internet activity (such as pages viewed, setup page activity, visits to Cynopta Insights pages and dashboard activity), approximate location derived from IP address, and account sign-in information. We use them for the purposes in A4, disclose them to the service providers in A5, and keep them for the periods in A6. We do not sell personal information or share it for cross-context behavioral advertising, and we do not use sensitive personal information for purposes that would give you a right to limit its use.
You can ask to know, delete or correct the personal information we hold about you, and you will not be discriminated against for doing so. You or an authorized agent can make a request by emailing privacy@cynopta.com. We will verify the request and respond within forty-five (45) days. Where we hold data about you only as a service provider to a Customer, we will refer you to that Customer where we can. Where Cynopta uses SDK data for its own purposes (B5) or receives data from its own apps (Part C), the categories, sources and purposes described in those parts also apply.
The Cynopta SDK in Our Customers' Apps
This part explains how the Cynopta SDK handles data inside our Customers' apps. It is written for the people who use those apps ("End Users") and for our Customers' privacy and security teams. It describes the Cynopta SDK for Android. The SDK for iOS is in internal beta and not yet available to Customers, and we will update this policy before it is. Apps that Cynopta and its affiliates publish themselves are covered in Part C. Customers can link to this part directly at cynopta.com/privacy-policy.html#sdk. Our SDK data flow page shows in one diagram what the SDK sends and where each report goes.
B1. What the SDK Does and Who Is Responsible
The SDK runs inside the Customer's app on the End User's device. When the app asks, the SDK assesses on the device whether the current activity comes from a real person or from automation, and returns the result directly to the app. The result includes a trust score from 0 to 1, where 1 means human; a classification; a device realness score; a session bot risk score; reason codes; and a timestamp. It also includes a compact token that the Customer's app can pass to its own servers. The token goes only to the Customer's app, and to the Customer's servers if the app sends it there; the SDK does not send it to Cynopta. The result contains no identifiers, and computing it requires no network call.
Computed on the device. Computing the result does not require raw behavioral measurements to leave the device. This does not mean that nothing leaves the device: B3 lists exactly what the SDK sends, and which parts the Customer can turn off.
The result is a signal, not a decision. A result of "automated" does not mean the activity is malicious, and a result of "human" does not confirm who the person is or that they are authorized. The Customer's app decides what to do with the result.
- The Customer is the controller. The company that publishes the app decides whether to use the SDK, whether to leave the optional reports on, and how to act on the results. It is responsible for telling End Users about this in its own privacy notice and for obtaining any consent the law requires.
- Cynopta acts for the Customer when it uses dashboard reports to provide the Customer's dashboard and analytics. For this, Cynopta is the Customer's processor (and its service provider under the CCPA), under our Data Processing Agreement.
- Cynopta acts for its own purposes when it uses the usage report for licensing, plan limits and billing, and crash reports to keep the SDK working (B5). For these purposes, Cynopta is a controller.
- Research and model training. Cynopta uses data from a Customer's apps to train or test its detection only where that Customer has agreed to it in a written agreement. Cynopta does not combine one Customer's data with another Customer's data.
B2. What the SDK Processes on the Device
To produce its result, the SDK reads and analyzes the following on the device, where the Android version and the device allow it. This information is processed and stored on the device, and most of it stays there. What leaves the device, mostly as summaries, is described separately in B3.
- Touch and motion: the shape, timing and position of touch gestures inside the app, and motion sensors such as the accelerometer, gyroscope and gravity sensor. The SDK does not capture typing on the system keyboard, the content of text fields, or the identity of buttons and other screen elements; it notes only the name of the app screen.
- Device state: battery and charging state, thermal state, screen on and off and unlock events, ambient light, and audio volume and output routing. The SDK does not use the microphone.
- Usage rhythm: app sessions and time in the foreground.
- Network and connectivity: network type and changes, Wi-Fi signal strength and connection events, local network addresses, network traffic volumes, mobile carrier, network and country codes, the number of active SIM cards and SIM changes, and whether a proxy or VPN is in use.
- Bluetooth: connections to paired devices such as wearables and cars.
- Device settings and hardware: device model and manufacturer, operating system version, screen brightness, font size, auto-lock, keyboard languages and time zone, whether a passcode or biometrics is set up, region and app store country, whether location services are switched on (on or off only), and whether certain permissions have been granted.
- Apps: the installed apps that Android makes visible to the SDK, used to compute counts by category, install and uninstall counts and a one-way hash of the list, and checks for known emulator, cloner, auto-clicker and root tools. The SDK also reads which apps have an active accessibility service.
- Media: the number of photos and videos taken each day. The SDK only counts them. It never collects or analyzes the photos or videos, and it does not read their content or metadata.
- Device and app integrity: signs of emulators, rooting, hooking and code-injection tools, debuggers, automation through accessibility services, debug builds and repeated reinstalls.
- Local network devices: at most every 12 hours, and only while the device is on a Wi-Fi network that the SDK recognizes as home or work, the SDK listens on the local network for 3 minutes. It asks devices there, such as routers, TVs and printers, to describe themselves. On a work Wi-Fi network, it also tests the network route to the internet. The Customer can turn both checks off (see B9).
Learning the device's routine
Over time, the SDK learns the device's normal routine, on the device: regular places such as home and work, recognized from Wi-Fi sessions and local network addresses rather than GPS; car journeys, from connections to a car's Bluetooth; sleep and wake patterns; how much the device moves, measured from motion sensors and network changes; and travel between countries. This continues while the app is not in use, and the SDK can start again after the device restarts. When an app update adds the SDK to an app that is already installed, the SDK can start before the End User next opens the app. After a first installation, the SDK does not start until the End User opens the app.
Storage on the device
The SDK stores its data in the app's private storage, keeps its databases out of device backups, so they are not restored on a new device or when the app is reinstalled, and encrypts the data in its main database. It deletes data automatically on rolling schedules: 14 days for diagnostic logs, 30 days for Wi-Fi quality data, 60 days for network traffic volumes, 90 days for touch, sensor, battery, screen, audio, Bluetooth and session data, and 365 days for the history of countries visited.
B3. What the SDK Sends
| Report | What it contains | Why | Can the Customer turn it off? |
|---|---|---|---|
| Usage report | A one-time report ID and timestamp; app package name and version; SDK platform and version; debug-build and emulator flags; the Customer's license ID, which identifies the license for the app and not a device or a person, the license version and the license status; whether dashboard reports are enabled; daily counts of assessments, of scores in each of 20 score bands, and of score requests that the SDK did not answer because the license did not allow it; the first days, weeks and months in which the installation made an assessment; and a summary of each finished week, as score bands and a volume range. No installation, session or device identifiers. | License verification, plan limits and billing; the integration status on the setup page and usage statistics for the Customer | No. It is required for the service. |
| Crash reports | Errors that originate in the SDK's own code, including errors that the SDK handles, such as a report that failed to send, with the SDK's diagnostic notes, app and SDK versions, operating system version, and device model and manufacturer. Errors elsewhere in the Customer's app are ignored. Sent to Sentry. | Finding and fixing faults in the SDK | Yes. On by default. |
| Dashboard reports | An installation identifier and timestamp; app name, version and API key, and SDK version; device model, manufacturer and operating system version; and summaries computed on the device: derived behavioral and device metrics based on B2, plus a security summary covering the device environment, bot-farm, rooting, hooking, accessibility and debugger checks, a gesture summary and detection results. | The Customer's dashboard and analytics | Yes. On by default, in full report mode. The Customer can instead choose security-related data only (see B9). |
| Debugging and research data | Raw touch data, such as the position of touches on the screen, in a security report that the SDK compiles on the device. | Debugging the SDK and, where the Customer has agreed to it, research (see B5) | Yes. Sent from debug builds, and from release builds when dashboard reports are in full report mode, which is the default. Choosing security-related data only, or turning dashboard reports off, stops it in release builds. |
More detail on dashboard reports. Depending on the device, they can include the score, its parts and the detection results, and flags for emulators, rooting, hooking tools, app cloners, debuggers and automation; the number of touch gestures, how many of them looked simulated, and the signs that made them look simulated; daily patterns such as screen time, charging, sleep and wake times, and time spent at home and at work; the brand and model of a connected car, a partly masked version of the car's Bluetooth name and the manufacturer part of its Bluetooth address; generic model names of paired wearables; the mobile carrier name, network and country codes, the number of active SIM cards and the number of SIM changes; keyboard languages and time zone; counts of installed apps by category, the one-way hash of the app list, and the names of any known emulator, cloner, auto-clicker or root tools found; the names of apps that have an active accessibility service, other than the built-in accessibility tools of Google and some device makers; counts of phones, computers, TVs and printers on the home network, an estimated household size, and a one-way hash of the network route from work; and the number of score requests for each action name that the Customer's app uses. The security report in debugging and research data covers up to 100 recent gestures from the past two days. For each gesture it includes the screen name, the timing and duration, the start and end positions on the screen, the distance and straightness of its path, its speed, pressure and touch size, the number of fingers, the tool and input device used, and whether the gesture looked simulated.
Security-related data only. In this mode, dashboard reports carry only the score and its parts, the detection and tampering results, touch and motion summaries, the device model and the SDK's own health data. They leave out installed apps, daily patterns, network, carrier and Bluetooth data, and debugging and research data.
When reports are sent. The SDK sends the usage report shortly after the app's process starts, and then about once a day. This can happen before the End User opens the app (see B2). It sends dashboard reports about once a day, with a random delay of up to 12 hours. It sends a crash report when an error happens in the SDK.
The installation identifier is a one-way hash of a random value created when the app is installed. It changes when the app is uninstalled or its data is cleared. It is not derived from any hardware or advertising identifier, and Cynopta cannot link it to a named person. It is different in each app on the same device. It lets reports from the same installation be linked. The SDK keeps it out of device backups, so restoring the app from a backup does not bring it back.
Device integrity check. Before it sends a usage report, the SDK asks Google Play services for an integrity token. The SDK gives Google only a one-way hash of the report. It sends the token with the report, and our server asks Google to check it. We delete the token within two hours. Only assessments from verified reports count toward billing.
Never sent: names, contact details or phone numbers, Wi-Fi network names, full Bluetooth addresses, SIM or hardware identifiers (such as IMSI, ICCID, IMEI, serial number or Android ID), advertising identifiers, the position of touches on the screen except in debugging and research data, text entered in the app, and anything typed on the system keyboard.
IP addresses. Like any internet connection, the SDK's connections reveal the device's IP address to our servers, to Sentry and, for the integrity check, to Google. Our servers that receive reports do not store IP addresses, and Sentry is configured not to store them. If we switch on network diagnostics to investigate a fault, they keep IP addresses for up to 7 days.
How we describe this data. Reports contain no names, contact details, or hardware or advertising identifiers. We treat everything the SDK sends as potentially personal data. Because dashboard reports carry an installation identifier and device characteristics, we treat them as personal data and protect them accordingly.
Customers can check all of this. Reports can be inspected with standard network tools in a test build.
B4. What the SDK Does Not Access, and Permissions
The SDK does not access names, email addresses, phone numbers, contacts, the camera, the microphone, messages, calendars, health or step data, the content or metadata of photos and videos, location services or GPS, advertising identifiers (IDFA or GAID), text in the app, or input on the system keyboard. For some features it checks only an on or off state, such as whether location services are switched on or whether a permission has been granted.
- Android: the SDK requests no permissions that the End User has to approve. It declares only standard permissions that Android grants at installation: internet access, network state, Wi-Fi state, Wi-Fi multicast used only for local network discovery, Bluetooth, and starting after the device restarts.
These statements concern platform rules only. They do not mean that no notice or consent is needed under privacy law (see B9).
B5. How Cynopta Uses SDK Data
- Usage reports (as controller): to verify licenses, apply plan limits, bill the Customer and show the integration status on the setup page. The same counts give the Customer usage statistics for its apps. They contain no identifier of an End User or a device. Where the GDPR applies, our legal basis is our legitimate interests in licensing and billing our service.
- Crash reports (as controller): to find and fix faults in the SDK. Where the GDPR applies, our legal basis is our legitimate interests in keeping the SDK reliable.
- Debugging and research data (as controller): to find and fix faults in the SDK. We use it for research only under the conditions in the research item below.
- Dashboard reports for the Customer (as processor): to provide the Customer's dashboard and analytics about its app's users as a whole, and to check the quality of the data that its apps send.
- Research and model training: to develop, train and test our bot and automation detection, only with data from a Customer that has agreed to it in a written agreement. The agreement sets out each party's role. Where Cynopta acts as a controller for this use and the GDPR applies, our legal basis is our legitimate interests in improving bot detection. Data from different Customers' apps is not combined for this purpose.
We do not use SDK data to recognize particular devices across Customers. The installation identifier is different in each app on the same device. Before introducing any such feature, we will update this policy, notify Customers, and obtain any consent and contractual agreement it requires.
We do not sell SDK data, use it for advertising, or try to identify End Users.
B6. Sharing of SDK Data
- Service providers: Amazon Web Services for cloud hosting, Cloudflare and Neon for licenses and usage reports, all in North Virginia, United States, and Sentry for crash reports, in Germany.
- Google: the device integrity check described in B3.
- The Customer: dashboard results and analytics about its own app.
- Legal requirements: where the law requires disclosure. Where permitted, we will notify the Customer first.
We do not share one Customer's SDK data with another Customer.
B7. Retention of SDK Data
Data on the device is deleted on the schedules in B2. On our servers, we keep SDK data for up to 13 months, unless the Customer asks us to delete it sooner or to keep it longer:
- Usage reports: up to 13 months; the daily counts are also kept with the Customer's billing records (see A6)
- Integrity tokens: deleted within two hours
- Crash reports: up to 13 months
- Dashboard reports: up to 13 months
- Report queue and collector logs: 14 days. The collector logs contain no IP addresses and no report content
When a Customer's agreement ends, we delete or return the data we process on its behalf as set out in the Data Processing Agreement.
B8. Deleting Data and End Users' Rights
- On the device: clearing the app's data, or uninstalling the app, deletes the SDK's data on the device. The Customer's app can also delete it at any time through the SDK.
- On our servers: Cynopta does not know who End Users are, so it can find their data only through the installation identifier. End Users do not see their installation identifier, so Cynopta usually cannot find the reports of one End User. If you give us information that lets us find your data, we will act on your request. Usage reports contain no identifier, so they hold nothing to delete for a single End User. Reports are deleted after 13 months at the latest, and the Customer can ask us to delete all the data from its apps at any time.
For data processed on the Customer's behalf, please contact the company that provides the app. We will help it respond. For data Cynopta uses for its own purposes (B5), you can also contact us directly at privacy@cynopta.com, and the rights and complaint options described in A7 apply. We will not ask for more information than we need. You do not need to uninstall the app to exercise your rights.
B9. Information for Customers
- Controls: the usage report is always on. Crash reports are on by default, and can be turned off in the configuration file that comes with your license file (
enableCrashReports), during integration or later. Dashboard reports are on by default and have three modes:FULL, the full report and the default;BOT_ONLY, security-related data only; andDISABLED, off. We set the mode in the configuration file that comes with your license file. To change it, including to turn dashboard reports off, write to support@cynopta.com. - Signal switches: the Android SDK has switches that turn individual signals off, such as installed apps, Wi-Fi, Bluetooth and the home network scan. Turning a signal off also removes the parts of dashboard reports that depend on it. All signals, including the home network scan and the work network route test, are on by default. Access to the switches through the SDK's API is being added.
- Verification: reports can be inspected with standard network tools in a test build, and our data-flow documentation lists every field of every report.
- Notice and consent: you are responsible for telling End Users about the SDK in your privacy notice, for your legal basis, and for collecting any consent the law requires. EU and UK rules on accessing information stored on a device can apply when the SDK reads information on the device, not only when it sends data. Dashboard reports are on by default. If your End Users are in the European Economic Area or the United Kingdom, obtain any consent required before the SDK starts, or turn dashboard reports off. We are reviewing the defaults for apps with End Users in these regions, and we will update this policy if they change. Your app's notice and consent mechanisms should also cover the Cynopta processing described in this part, including the SDK's work in the background and its start after an app update (B2).
- Cynopta's responsibilities: Cynopta remains responsible for its own obligations as your processor, and as a controller for the purposes in B5.
- Sensitive screens: if your app uses its own on-screen PIN pad or similar custom input, tell us, or choose security-related data only, because touch positions in debugging and research data could reflect what was entered there.
- Action names: do not put personal data in the action names that your app passes to the SDK. Dashboard reports count score requests for each action name.
- App store disclosures: you are responsible for your Google Play Data safety answers, which depend on which reports you leave on. When dashboard reports are on, they include an installation identifier. We provide the information you need.
- Agreements: our Data Processing Agreement governs the data we process on your behalf and forms part of your agreement with us. You accept it, together with our Terms of Use and this Privacy Policy, on the setup page before you receive your license file.
- Use of results: the result is one signal among your controls. You decide how to act on it, and you are responsible for those decisions, including where the law restricts decisions based solely on automated processing.
- Children's apps: tell us before deploying the SDK in an app directed at children or likely to be used by them, and comply with laws such as the Children's Online Privacy Protection Act (COPPA).
Cynopta's Own Apps
This part covers apps that Cynopta and its affiliates publish themselves. Each of these apps also has its own privacy notice, which says who publishes the app and is responsible for your data in it. Where this part and an app's own notice differ, the app's notice applies to that app.
C1. Which Apps Part C Covers
Cynopta and its affiliates publish a small number of apps for research, which help us test the SDK and study how bots behave:
- My Finance Assistant and My Network Assistant: published under the name of Anagog, an Intent HQ group company, in Google Play and the Apple App Store.
Apps that we use only inside our own team for development and testing are not offered to the public and are not covered here.
C2. What Our Apps Collect
Each app's own privacy notice, available in the app and on its app store page, says whether the app includes the Cynopta SDK and what else the app collects. Where an app includes the SDK, the SDK works on your device as described in B2 and sends the reports described in B3.
C3. How We Use It and Our Legal Bases
Cynopta uses the reports that our apps send to test the SDK and to develop, train and test our bot and automation detection. Each app's own privacy notice sets out the legal basis for its processing. We keep the reports for the periods in B7.
C4. Your Choices and Deletion
- Choices in the app: each app's own privacy notice describes the choices the app offers.
- Delete data on your device by clearing the app's data or uninstalling it.
- Delete data on our servers by writing to the contact in the app's own privacy notice or to privacy@cynopta.com.
The rights and complaint options in A7 also apply.
Provisions for All Parts
D1. International Data Transfers
We host data on Amazon Web Services, Cloudflare and Neon, all in North Virginia, United States, Sentry processes crash reports in Germany, and our team works from countries including Israel, Spain and Ukraine. When personal information from the European Economic Area, the United Kingdom or Switzerland is transferred to a country without an adequacy decision, we use the European Commission's Standard Contractual Clauses, with the UK Addendum for transfers from the UK and the adjustments Swiss law requires for transfers from Switzerland. A transfer to a recipient in the United States can instead rely on that recipient's participation in the framework that matches the transfer: the EU-U.S. Data Privacy Framework for the EEA, its UK Extension for the UK, and the Swiss-U.S. Data Privacy Framework for Switzerland. Cynopta does not currently participate in these frameworks. Israel is recognized by the European Commission and the United Kingdom as providing adequate protection. Transfers from other countries, such as Thailand or India, are made with the safeguards their laws require. For data we process on a Customer's behalf, the Data Processing Agreement also applies. You can ask us at privacy@cynopta.com about the safeguards we use and, where appropriate, for a copy.
D2. Security
On the device, the SDK keeps its data in the app's private storage, encrypts the data in its main database with AES-256 using a key protected by the device's secure hardware where available, and relies on the operating system's storage encryption. All reports travel over encrypted connections (TLS). On our servers, personal information is encrypted at rest, and access is limited to staff who need it. No system is completely secure. If a breach affects personal information we control, we will notify you and the relevant authorities as the law requires. If it affects personal information we process for a Customer, we will notify the Customer without undue delay, as set out in the Data Processing Agreement.
D3. Children's Privacy
Our website, setup page and business accounts are not directed at children under sixteen (16), and we do not knowingly collect personal information from children through them. If you believe we have, contact us at privacy@cynopta.com and we will delete it. For our own apps, each app's own privacy notice sets out who may use it. For the SDK in Customers' apps, see B9. Customers' obligations do not remove any obligations Cynopta has under children's privacy laws.
D4. Third-Party Links
Our website may link to third-party websites and services. We are not responsible for their privacy practices, and a link does not mean we endorse them. Please review their privacy policies before giving them personal information.
D5. Changes to This Policy
We update this policy when our practices, our products or the law change. Each version carries a version number and effective date, and previous versions are available on request. If we make material changes, we will give notice in advance where the law requires, by email or through a prominent notice on our website. We notify Customers of changes to Part B as set out in the Data Processing Agreement.
D6. Contact Us
Cynopta, Inc., a Delaware corporation, 500 West 43rd St., Suite 31A, New York, NY 10036, USA
Email: privacy@cynopta.com