Render Third-Party Providers
Last Modified: June 7, 2024
This document lists the third-party vendors that assist in operating, protecting, and improving Render, along with details about the data shared with them and their respective services.
We understand the importance of transparency regarding data privacy. We are committed to working with trustworthy vendors and taking necessary measures to protect user information. We:
Contractually prohibit vendors from selling personal information.
Limit vendor access to only the required information for their services.
Implement privacy-protective measures to minimize data sharing.
Regularly review and update this list.
Please note that we have not added to this list the “IT” business services such as Gmail and Slack to operate our organization. These services may incidentally contain personal information (e.g., email address or contact handle). We apply the Service Provider restrictions described above but have not included a detailed list of these IT business services below.
We will update the list below from time to time. If you have any questions, please contact us at privacy@buildwithrender.org. You can also learn more in the Render Privacy Policy.
Technical Service Providers
Name of Service Provider with Link to Privacy Policy | Service | Details |
Hosts databases and servers that power and backup Render platform & applications | We use various AWS services to develop and serve the Render platform & applications. AWS services also power all storage and backup of Render content, traffic, and data. | |
Hosts the public website (www.buildwithrender.org) on the http://wpvip.com enterprise agile content platform. | Automattic will receive the IP address and traffic data of any visitors to the Render public website. | |
Help Center and Customer Support tickets | Authorized CZI support staff will use JIRA for customer support tickets. We will also host help resources and guide through the JIRA help center. | |
Provides software engineering, technical, and operational support for Render. | Authorized CZI staff have access to the full Render content and traffic data in the course of providing engineering, technical, and operational support. | |
Used for website analytics. | On the marketing (WWW) site, we use Crazy Egg to show user behavior on the site. This includes referral source information, clicks, scroll depth, and actions taken by the end-user while on the site. Site visitor data and behavior are anonymized and aggregated in the CrazyEgg platform. | |
Serves as data warehouse that powers Render | All data for the Render platform & applications is collected and stored in Databricks for offline analysis (data is always encrypted) | |
Used to obtain electronic signature from Participants for certain documents (i.e., consent form) | DocuSign receives a Participant’s email address in order to transmit and obtain an authenticated electronic signature | |
Used for websSite analytics | On the marketing (WWW) site only, we use Google Analytics to show user behavior on the site. This includes referral source information, clicks, scroll depth, and actions taken by the end user while on the site. Site visitor data and behavior are anonymized. | |
Provides single-sign-in (SSO) authentication | For SSO, Google sends Render, the authentication tokens, email addresses and name, but not account passwords. Render does not share any information back with Google for this service. | |
Used to dynamically trigger firing of tags without code changes | On the marketing site only, Google Tag Manager receives data in standard HTTP request logs, all of which is deleted within 14 days of being received. Google Tag Manager does not collect, retain, or share any information about visitors. | |
Email service for sending emails to teachers, school officials, and everyone who requests to receive information from us. | Hubspot receives names and email addresses of email recipients and the content of the emails, and provides analytics | |
Provides single-sign-in (SSO) authentication | For SSO, Microsoft sends Render, then authentication tokens, email addresses and name, but not account passwords. Render does not share any information back with Microsoft for this service | |
Used to manage cookie consent for the public website (www.buildwithrender.org) | OneTrust receives the IP address of the visitor to the website and stores the user’s preferences in a cookie on their local device. For known users who have previously logged into the Render application on the same device, OneTrust is not loaded and receives no information because all non-essential tracking is turned off and cannot be turned on. | |
Used for Generative AI services | User application data (excluding personnel information) is sent to OpenAI to power Render with intelligent GenAI components. | |
Used for managing incidents | Errors (de-identified) are sent to OpsGenie, which depending on severity may trigger the need for a coordinated response across multiple teams (incident), to ensure any disruption to the platform users is addressed asap. | |
Salesforce Sales Cloud | Houses and tracks partnership agreements, points of contact and other coordination information. | Salesforce receives the names, email addresses, physical addresses and phone numbers of school and district officials, as well as active and prospective Render users (teachers only, not students). |
Tool for standardizing data collection for analytics | Segment receives event data based on user actions taken on Render. | |
Used for reporting and tracking application errors | Error reports are de-identified and sent to Sentry for error tracking and continuous improvement of the Render platform & applications. | |
Create and send surveys for educators and students, with the intent of improving Along through teacher and student feedback. | SurveyMonkey receives the email addresses of educators and students submitting feedback, the content of the survey feedback requests (e.g. improvements, feature requests and suggestions etc.), and the responses provided. | |
ELT tool for ingesting data from third-party platforms into a warehouse. | We use Fivetran in conjunction with long-term storage of Google Analytics data. |