This document describes all measures and efforts taken by Sentiance to ensure the security and quality of the data it processes via its Sentiance Ambient Intelligence Platform, such as the type of device, operating system, type of mobile browser, use of a specific application, real-time location based on information provided by device operating system, accelerometer data, gyroscope data, and (for certain device makes and types and to the extent permission is granted) step detection and count, Bluetooth information and battery information (collectively the ‘Data’)
By applying the following measures, Sentiance prevents the entrance of non-authorized persons to data-processing installations in which Data are processed or used:
Data is collected and processed by Sentiance on two locations:
By applying the following measures, Sentiance prevents the utilization of data-processing systems by non-authorized persons:
Sentiance employs two types of data-processing systems:
By applying the following measures, Sentiance ensures that persons authorized to use a data-processing system will only have access to those data that they have been authorized for and that, neither during the processing nor after storage, Data can be read, copied, altered or removed without a respective authorization:
Sentiance employees, i.e. software developers, that are authorized to use data processing systems are provided with a personal AWS user account and tokens. Specific accounts are in place to restrict certain access to Data depending on the job content and contribution to the Sentiance Platform.
By applying the following measures, Sentiance ensures that Data cannot be read, copied, altered or removed during electronic data transmission without authorization and that it is possible to check and determine at which points a transmission of personal data by means of data transmission installations is intended:
Sentiance employs an SSL connection for all data transmission in and out of the Sentiance API on AWS. The connection uses TLS 1.2. The connection is encrypted and authenticated using AES_128_GCM and uses ECDHE_RSA as the key exchange mechanism.
By applying the following measures, Sentiance ensures that it is possible to check and determine subsequently whether and by whom Data have been entered into data-processing systems, altered or removed:
Sentiance employs the AWS CloudTrail service to monitor any modification to its AWS account.
By applying the following measures, Sentiance ensures that Data subject to job processing are processed in strict accordance with the instructions given by the principal:
Access to Data and servers is granted to AWS via an encrypted connection and all access is logged and can be traced by Sentiance’s technical team. Specific accounts are in place to restrict certain access to Data.
By applying the following measures, Sentiance ensures that Data are protected against accidental destruction or loss:
Personal data arriving at the Sentiance Platform is consolidated as-is into a Master Dataset which can be interpreted as an append-only log of events. This Master Dataset is stored on an Hadoop Distributed File System (HDFS) on Elastic Compute (EC2) nodes on the AWS cloud computing environment. Data is stored on this HDFS instance with a replication factor of 3 for resilience against catastrophic loss of two nodes simultaneously.
Furthermore, every couple of hours a backup of the Master Dataset is created on S3. Backups stay available on S3 for two weeks.
Additionally, all raw events (i.e. before consolidation into the Master Dataset) received by the Sentiance Platform are backed up to S3 indefinitely. From these raw events, the Master Dataset can be recreated at any time.
By applying the following measures, Sentiance ensures that data collected for different purposes can be processed separately:
Every integration of the Sentiance SDK into a mobile app, i.e. a specific purpose, is required to be provisioned with new app-specific credentials, i.e. app ID and key, even if it concerns different apps of the same client.
The Sentiance SDK automatically creates a new user account and id on first use within an app and associates the app-specific token to it.
Data is stored for processing in an append-only log partitioned by app.
During processing, data is only aggregated by user and by app.
All employees and consultants working for Sentiance are subject to individual confidentiality agreements.
Last updated: Friday, March 25 2016
Sentiance is the leader in motion insights. Our mission is to save lives every day and shape the future of road safety. Unlike telematics companies, we focus on the driver and not the vehicle because most accidents are caused by human error.
With our revolutionary on-device AI technology, companies use insights from The Edge Platform to produce scalable, cost-efficient, and privacy-centric solutions for their customers.
You may unsubscribe from these communications at any time.
© Sentiance NV. - a website by mimosa
Cookie | Duration | Description |
---|---|---|
_GRECAPTCHA | 6 months | Google Recaptcha service sets this cookie to identify bots to protect the website against malicious spam attacks. |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie records the user consent for the cookies in the "Advertisement" category. |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
cookielawinfo-checkbox-utility | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Utility". |
CookieLawInfoConsent | 1 year | CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie. |
rc::a | persistent | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
rc::b | session | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
rc::c | session | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
rc::f | session | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
__hssc | 30 minutes | HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
__hssrc | session | This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. |
vuid | 1 year 1 month 4 days | Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website. |
wpEmojiSettingsSupports | 1 year | WordPress sets this cookie when a user interacts with emojis on a WordPress site. It helps determine if the user's browser can display emojis properly. |
yt-player-headers-readable | session | The yt-player-headers-readable cookie is used by YouTube to store user preferences related to video playback and interface, enhancing the user's viewing experience. |
yt-remote-cast-installed | persistent | The yt-remote-cast-installed cookie is used to store the user's video player preferences using embedded YouTube video. |
yt-remote-connected-devices | 6 months | YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. |
yt-remote-device-id | persistent | YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. |
yt-remote-fast-check-period | persistent | The yt-remote-fast-check-period cookie is used by YouTube to store the user's video player preferences for embedded YouTube videos. |
yt-remote-session-app | session | The yt-remote-session-app cookie is used by YouTube to store user preferences and information about the interface of the embedded YouTube video player. |
yt-remote-session-name | session | The yt-remote-session-name cookie is used by YouTube to store the user's video player preferences using embedded YouTube video. |
ytidb::LAST_RESULT_ENTRY_KEY | persistent | The cookie ytidb::LAST_RESULT_ENTRY_KEY is used by YouTube to store the last search result entry that was clicked by the user. This information is used to improve the user experience by providing more relevant search results in the future. |
Cookie | Duration | Description |
---|---|---|
__cf_bm | 30 minutes | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
_cfuvid | 1 year | Calendly sets this cookie to track users across sessions to optimize user experience by maintaining session consistency and providing personalized services |
Cookie | Duration | Description |
---|---|---|
__hstc | 13 months | Hubspot set this main cookie for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). |
_gcl_au | Persistent | Google Tag Manager sets the cookie to experiment advertisement efficiency of websites using their services. |
hubspotutk | 13 months | HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. |
VISITOR_INFO1_LIVE | 6 months | YouTube sets this cookie to measure bandwidth, determining whether the user gets the new or old player interface. |
VISITOR_PRIVACY_METADATA | 6 months | YouTube sets this cookie to store the user's cookie consent state for the current domain. |
YSC | session | Youtube sets this cookie to track the views of embedded videos on Youtube pages. |
yt.innertube::nextId | Session | YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen. |
yt.innertube::requests | Session | YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen. |