SDK Data Flow
This page shows what the Cynopta SDK sends from an End User's device, where each report goes, and how long we keep it. It supports Part B of our Privacy Policy.
1. About This Page
This page describes the Cynopta SDK for Android. It also describes the two Cynopta services that receive its reports: the license service and the data collection service. The SDK for iOS is not yet available to Customers, and we will update this page before it is.
This page is a technical description. Our commitments are in the Privacy Policy and, for Customers, in the Data Processing Agreement. "Customer" and "End User" mean the same here as in the Privacy Policy.
Data that developers give us on the setup page, such as sign-in and billing details, is covered in section A2 of the Privacy Policy.
Calculated on the device. The SDK calculates the result on the device and returns it to the Customer's app without a network call. The reports on this page serve other purposes: licensing and billing, the Customer's dashboard, and the reliability of the SDK.
2. Data Flow Diagram
The diagram shows the device on the left and the recipients on the right. A solid line is a flow that is always on. A dashed line is a flow that the Customer can switch off.
End User's device
Customer's app
Cynopta SDK
- Reads signals on the device
- Stores them in an encrypted database
- Calculates the result
The Cynopta SDK returns the result to the Customer's app. No network call
Result
From the Customer's app to the Customer's servers: Result, if the app sends it
Customer's servers
-
From the Cynopta SDK to the Cynopta license service.
From the Cynopta license service back to the Cynopta SDK: Signed license status
Cynopta license service
license.cynopta.comCloudflare and Neon, United StatesKept up to 13 months -
From the Cynopta SDK to Google Play services: A one-way hash of the report
From Google Play services back to the Cynopta SDK: An integrity token
The token travels with the usage report.
Google Play services
From the Cynopta license service to Google Play services: Token checkToken deleted within two hours
-
From the Cynopta SDK to Cynopta data collection.
Cynopta data collection
gateway.cynopta.comAmazon Web Services, North Virginia, United StatesKept up to 13 monthsFrom Cynopta data collection to the Customer: Dashboard and analytics
Customer
-
From the Cynopta SDK to Sentry.
SentryGermany
- Always on
- The Customer can switch it off
- Customer's own flow. Not sent to Cynopta.
All reports travel over HTTPS. Sections 4 to 6 describe each report.
3. What Stays on the Device
- Signals: the SDK reads signals such as touch gestures, motion sensors, screen and battery state, and network state. Section B2 of the Privacy Policy has the full list.
- Storage: the SDK stores this data in the app's private storage and encrypts its main database. It deletes the data on the schedules in B2.
- Result: the SDK calculates the result on the device and returns it to the Customer's app. The app can pass the result to the Customer's own servers. The SDK does not send the result token to Cynopta. Dashboard reports include the latest scores (section 5).
4. Usage Report
The SDK sends the usage report to the Cynopta license service at license.cynopta.com. It sends the first report shortly after the app's process starts, and then about once a day. The Customer cannot switch this report off.
| Part | What it contains |
|---|---|
| Report | A report ID that is new for each report, and the time |
| App | The package name and version, and whether the build is a debug build or runs on an emulator |
| SDK | The platform and version, and whether dashboard reports are on |
| License | The Customer's license ID and version, and the license status |
| Counts | Daily counts of assessments and of scores in each of 20 score bands. Daily counts of score requests that the SDK did not answer because the license did not allow it. |
| Activity | The first days, weeks and months in which the installation made an assessment. A summary of each finished week as score bands and a volume range. |
| Sent with it | The API key of the app and, when Google Play services provides one, an integrity token |
The report contains no installation, user or device identifier.
How the report is handled
- The SDK builds the report and asks Google Play services for an integrity token. It gives Google a one-way hash of the report.
- The SDK sends the report and the token to the license service.
- The license service checks the API key, writes one record of the report to its usage log, and answers with a signed license status. The status tells the SDK whether it can continue to score.
- The license service asks Google to check the token. It keeps the outcome and deletes the token within two hours.
Only assessments from verified reports count toward billing. The license service uses the IP address of the connection to limit requests that carry an invalid key. It does not write the IP address to the usage log.
5. Dashboard Reports
The SDK sends dashboard reports to the Cynopta data collection service at gateway.cynopta.com, about once a day. Dashboard reports are on by default, and the Customer can switch them off.
Each report contains:
- an installation identifier and the time
- the app's name, version and API key, and the SDK version
- the device model, manufacturer and operating system version
- summaries that the SDK calculates on the device, which section B3 of the Privacy Policy lists
The installation identifier is a one-way hash of a random value that the SDK creates in the app. It is different in each app on the same device, and it changes when the app is uninstalled or its data is cleared.
How the report is handled
- The SDK compresses the report and sends it to the data collection service.
- The service checks the API key and the app name against its registry before it reads the report.
- The service stores the report as it arrived, with the Customer, the app, the platform, a receipt ID and the time of receipt. It does not store the IP address with the report.
- Cynopta uses the stored reports to provide the Customer's dashboard and analytics.
6. Crash Reports
When an error starts in the SDK's own code, the SDK sends a crash report to Sentry in Germany. Crash reports are on by default, and the Customer can switch them off.
Each report contains:
- the error and the SDK's diagnostic notes
- the app name and version, and the SDK version
- the operating system version, and the device model and manufacturer
The SDK ignores errors elsewhere in the Customer's app.
7. Storage and Retention
| Data | Where it is stored | How long we keep it |
|---|---|---|
| Usage reports | Cloudflare and Neon, in the United States | Up to 13 months. The daily counts are also kept with the Customer's billing records. |
| Integrity tokens | Cloudflare, in the United States. Google checks each token. | Deleted within two hours |
| Dashboard reports | Amazon Web Services in North Virginia, United States, in private encrypted storage | Up to 13 months |
| Dashboard reports that wait to be stored | A queue at Amazon Web Services in North Virginia | Up to 14 days |
| Crash reports | Sentry, in Germany | See B7 of the Privacy Policy |
A Customer can ask us to delete the data from its apps sooner, or to keep it longer. Sections B7 and B8 of the Privacy Policy set out retention and deletion. If we switch on network diagnostics to investigate a fault, they keep IP addresses for up to 7 days.
8. Controls for Customers
- Usage report: always on. The service needs it for licensing and billing.
- Dashboard reports: on by default. Cynopta sets the mode in the configuration file that comes with your license file. To turn them off, or to send security-related data only, write to support@cynopta.com.
- Crash reports: on by default. Set
enableCrashReportstofalsein the same file. - Checking the flows: you can inspect every report with standard network tools in a test build.
Section B9 of the Privacy Policy explains notice, consent and app store disclosures.
Contact Us
Cynopta, Inc., a Delaware corporation
500 West 43rd St., Suite 31A, New York, NY 10036, USA
Email: privacy@cynopta.com
For our commitments on personal information, see the Privacy Policy.