Effective date: April 2, 2021
The CodeLinaro Service is provided to you by Linaro Limited, a UK registered company number 07180318. Any reference to CodeLinaro is also a reference to Linaro Limited.
CodeLinaro provides a great deal of transparency regarding how we use your data, how we collect your data, and with whom we share your data. To that end, we provide this page, which details our subprocessors, and how we use cookies.
When we share your information with third party subprocessors, such as our vendors and service providers, we remain responsible for it. We work very hard to maintain your trust when we bring on new vendors, and we require all vendors to enter into data protection agreements with us that restrict their processing of Users' Personal Information as defined in our Privacy Statement.
| Name of Subprocessor | Description of Processing | Location of Processing | Corporate Location |
| Atlassian | StatusPage incident management communications | United States | United States |
| AWS Amazon | Data hosting | United States | United States |
| Elavon | Credit card Proccessing | United States | United States |
| EventBridge | XMatters critical event management | United States | United States |
| ITMethods | Git hosting services | Singapore / United States | Canada |
| JFrog | Binary data hosting services | United States | Israel |
| Linaro | Support ticketing system, IRC services, wiki services | United States | United Kingdom |
| Okta | Auth0 authentication services | United States | United States |
| Zoho | Mail services | United States | United States |
When we bring on a new subprocessor who handles our Users' Personal Information, or remove a subprocessor, or we change how we use a subprocessor, we will update this page. If you have questions or concerns about a new subprocessor, we'd be happy to help. Please contact us via Privacy contact form.
CodeLinaro uses cookies to provide and secure our websites, as well as to analyze the usage of our websites, in order to offer you a great user experience. Please take a look at our Privacy Statement if you’d like more information about cookies, and on how and why we use them.
Since the number and names of cookies may change, the table below may be updated from time to time.
| Service Provider | Cookie Name | Description | Expiration* |
| CodeLinaro Website via Auth0 | auth0.is.authenticated | This cookie is used during a session as an indicator for the web application to know without having to continually call Auth0 service if a user has been previously authenticated | 24 hours or until session is terminated by user |
| Git | _gitlab_session | Though we integrate with Auth0 SSO, the GitLab service itself also handles an active user session using this cookie | Active until session terminated by user |
| Git | known_sign_in | For GitLab internal analytic purposes, this cookie is set to tell the service which IP and device is being used to access | 2 weeks |
| Git | experimentation_subject_id | This cookie is set by GitLab’s experimental framework within its core. It’s used to primarily perform A/B testing of the UI. CodeLinaro does not utilize this cookie nor does it contain any personally identifying information. | 5 hours |
| ServiceDesk | atlassian.xsrf.token | Helps prevent XSRF attacks. Ensures that during a user's session, browser requests sent to a Jira server originated from that Jira server. | Active until session terminated by user |
| mo.jira-sso.* | ServiceDesk SSO plugin which allows Auth0 integration uses this for session tracking purposes | Active until session terminated by user | |
| JSESSIONID | ServiceDesk uses this for session tracking purposes | Active until session terminated by user | |
| Artifacts | _ga | Google Analytics for JFrog | Active until session terminated by user |
| ACCESSTOKEN | Issued by JFrog for user requests made to the APIs that are used by the UI | 30 minutes | |
| REFRESHTOKEN | Issued by JFrog for user requests made to the APIs that are used by the UI | 30 minutes | |
| Wiki | jwt | Issued by Wiki for user requests made to the APIs that are used by the UI; contains scope/permissions as pertinent to said user | 30 minutes |
(!) Please note while we limit our use of third party cookies to those necessary to provide external functionality when rendering external content, certain pages on our website may set other third party cookies. For example, we may embed content, such as videos, from another site that sets a cookie. While we try to minimize these third party cookies, we can’t always control what cookies this third party content sets.