Service Providers Processing Information on Behalf of Code.org


1	Service Provider	Reason for Sharing Information	What Information is Shared?

2	Airtable	To track internal facing documents, which may include contact information for Code.org outreach and education teams.	Code.org collects facilitator name, email address, phone number, and other contact information, which may be processed by Airtable. No Student Records.
3	Amazon Web Services (AWS)	To host databases and servers that power and back up the Code.org platform. We also use various AWS underlying services to support functionality.	All user personal data is stored in AWS; passwords and student email addresses are stored as one-way hashes. All personal information written to disk is encrypted (see https://docs.aws.amazon.com/AmazonS3/latest/dev/serv-side-encryption.html).
4	Amplitude	To analyze website event data and trends to allow for website development and improvement.	Code.org uses the Amplitude cloud platform for analytics. Amplitude receives user event data (e.g., click info, pages visited, etc.) and data such as IP address, browser type, language, etc. No Student Records.
5	Asana	To manage internal processes for workflows across various teams.	Workflows may includes, names, email addresses, phone numbers, and other contact information (e.g., for Code.org regional partners, facilitators, certain teachers, donors, marketing contacts, etc.). No Student Records.
6	Atlassian	To provide the JIRA project management tool that allows issue tracking and internal task management.	Code.org stores issues and product ideas, and tracks work delivery in JIRA. In the course of responding to an issue, Code.org may include user data in the work tickets.
7	Bill.com	To process payments.	Names, addresses, banking information for teachers, facilitators and others. No Student Records.
8	Civilized Discourse Constructions Kit, Inc.	To provide a teacher communication forum.	Teachers can access the Code.org professional development community forum by signing into their Code.org account, which passes Discourse teacher information such as email address, username, and workshops run. No Student Records.
9	Classy	To collect and process donations to Code.org.	Name, email address, contact info and payment information is provided to Classy when a user chooses to enter the information to make a donation. Code.org receives contact and donation information, but payment card information is never sent to or accessible by Code.org. No Student Records.
10	Cvent, Inc.	To facilitate registration and attendance for Code.org educator conferences and events	Code.org uses the platform to collect contact information (e.g., name, title, company, email address, mailing address, phone number) and related information for the event. No Student Records.
11	Cube Planning, Inc.	To assist with internal management of finance and donor data	Code.org uses the service to automate integration of systems, including CRM donor data. No Student Records
12	DocuSign	To manage documents requiring signature and to collect digital signatures.	Code.org inputs name and email addresses of whoever we need to sign a document with DocuSign. No Student Records.
13	Dropbox	To store files and internal resources.	Code.org employees use Dropbox to store internal documents, which may incidentally contain personal information. For example, internal documents may contain photos of students from a photo shoot (done with permission given by the students' parent/guardian) to use on our website.
14	Egencia	To faciliate travel reservations.	When Code.org provides travel for teachers or faciliators, we share information required to facilitate the travel including names, email addresses, phone numbers, other contact information, etc. No Student Records.
15	Firebase	To store user-generated data within one of our programming tools.	Our App Lab and Game Lab programming tools allow users to make apps that can collect and store data (e.g. high score data, data on what people's favorite pizza is, etc.).
16	Google Inc. (Charts)	To display data charts in Code.org App Lab.	A student can import or create a data set into App Lab and use this service to turn that into a chart visualization, which could potentially include personal data.
17	Google Inc. (Analytics)	To track site performance data (both server and browser performance) for Code.org (e.g., what pages on our site people visit, visit duration, where they click).	Google directly collects data about the way our site is used, which allows us to create various analyses.
18	Google Inc. (G Suite)	To manage Code.org internal emails, docs, slides, spreadsheets, etc.	Code.org uses G Suite and Google Drive to store its own emails and other files. Code.org's data may include personal data. For example, if a user emails us on ZenDesk for support, their email address will be sent to our email. Memos, contracts, and other documents may also include personal data.
19	Google Inc. (Tag Manager)	To track the number of clicks on links in order to observe the traffic flow on various pages of our website.	The service uses information collected through Google Analytics. No Student Records.
20	Google Inc. (YouTube)	To embed videos for users to watch with captioning and translations.	The service collects and shares video views information. Code.org uses YouTube's no-cookie service to limit tracking. No Student Records.
21	Hivebrite	To host a communications platform for the Code.org CS Amabassador program (amabassador students may join the program only with parental consent).	The service collects contact information (e.g., name, email address) and limited other data (such as school, grade level). Other optional information (such as a photo) may be added to profile. User communications with Code.org and other ambassadors.
22	Honeybadger	To monitor our site performance and log errors.	Code.org passes information to Honeybadger regarding site errors, along with the associated IP address and relevant cookie information. In some cases, Code.org may need to share relevant information like school, user name, locale data, etc.
23	Hubspot	Used to manage school district/administrator email lists.	Code.org stores email information in HubSpot for certain non-student users (e.g., district and school administrators) and uses the service to send emails and to track school recruitment leads, adoption, and contact activity. No Student Records.
24	Intuit (Quickbooks)	To faciliate interaction between accounting software and bill payment software.	No information directly shared, but linked to bill.com. No Student Records
25	JotForm	To collect survey responses.	Code.org uses the platform to collect name, addresss, email address, answers to survey questions, and other personal data relevant to survey questions for teachers, facilitators, regional partners, etc.. Participation is optional, and information is entered directly by the individual. No Student Records.
26	Lead Pages	To host subdomain informational webpages and collect contact information for teachers and administrators seeking additional information (e.g., about events)	Code.org uses Leadpages to create and host subdomain webpages that are generally of a temporary nature. In some instances, Lead Pages may be used by Code.org to collect contact information provided by a visitor (e.g., teacher or administrator) seeking further information. No Student Records
27	Mailgun Technologoes, Inc.	To manage teacher email communications.	Code.org stores mailing list information for teachers using our platform in Mailgun's Mailjet system, such as name, email addresses, date of sign-up, and, where known, info like country and state, preferred language, grades taught, and subjects of interest. No Student Records.
28	Mapbox	To display info in a table and a map that users have agreed to share publicly.	Users that sign up to host one of Code.org's Hour of Code events provide their school/organization name, school/organization city, and a description of their event, which is passed to Mapbox to display on Hour of Code event maps. No Student Records.
29	Microsoft (Azure Content Moderator)	To provide content moderation of images in projects.	Code.org shares thumbnails and images from students' projects to the Azure Content Moderator to check for inappropriate content. No Student Records.
30	Mimeo	To allow partners and teachers to order workshop supplies (US only) and for school mailings	Code.org shares order details, such as name, email address, contact info, and shipping address that user inputs when placing an order or when Code.org sends a mailing. No Student Records.
31	New Relic	To track site and server performance.	Code.org shares user's IP address, locale information, browser info, which URL the user is on, the project URL they are working on, device type, etc. Some of this information is supplied directly by Code.org and some may be collected directly by New Relic. No Student Records.
32	New Visions for Public Schools	To automate data transfers between spreadsheets and Google Docs or PDFs (though the Autocrat add on).	Code.org employees may transfer data between internal documents, including names, addresses, email address and similar contact information related to teachers, facilitators, and regional partners. No Student Records.
33	Open AI API Platform	To receive input and provide output in connection with AI use in Code.org curricula.	Code.org uses the OpenAI API service, which does not use input or output to further train the model. All input and output are processed by OpenAI only as a data processor and not as a controller. We do not intentionally prompt for entry of any personal data, but such entry is possible. No Student Records.
34	Pusher	To report Internet Simulator state invalidations to connected clients, minimizing update lag.	Code.org shares with Pusher opaque identifiers that represent various messages or status changes (e.g., when a user connects to the Internet Simulator, they can request to connect with another user. That request is “pushed” to the receiving user, and the response is “pushed” back to the initiating user). Pusher will receive users' IP addresses in the course of providing the service. No Student Records.
35	Salesforce	To manage our email lists, send emails, and to act as CRM system.	Code.org stores mailing list information in Salesforce Pardot for non-student users, including information like email addresses, whether the user has opted-in or not, whether they have unsubscribed, what kind of user they are (e.g. teacher, volunteer, etc.), how Code.org obtained their email address (e.g. which form they filled out), location (city + zip code), etc. Code.org also uses the Salesforce CRM platform for donor relationship management, leads for new teacher training candidates, leads for new districts to adopt Code.org's curriculum, etc. No Student Records.
36	Slack	To provide internal communications between Code.org employees.	Code.org employees use Slack for internal communications, which may incidentally contain personal information about users.
37	Statsig, Inc.	To analyze website event data and trends to allow for website development and improvement.	Statsig receives user event data (e.g., click info, pages visited, etc.) and data such as IP address, browser type, OS type and version, etc. No Student Records.
38	Tableau	To publish data dashboards used internally and by Code.org Regional Partners.	Code.org creates visualizations analyzing the data in aggregate. However, the raw data shared with Tableau may contain personal information like usernames, emails, age, gender, etc.
39	Trello	To track internal workflows at Code.org	Code.org employees use Trello for workflow management, which may incidentally contain personal information about individuals. No Student Records
40	Trevor	To help manage and provide database access	Code.org uses the tool to manage employee and select partner access to Code.org databases. Although Trevor does not copy or store such data, the tool provides access to databases that may contain personal information like usernames, student names (entered by teachers); teacher email addresses, user age, user gender, school addresses, etc.
41	Twilio	To allow users to send a text message link to their project. Use of this feature is completely optional at the user's discretion.	Code.org shares the phone number entered by the user sharing their project, as well as a link to their project. Code.org does not store the user's phone number when using this service.
42	VoterVoice	To facilitate contacts with elected officials.	If a user chooses to send a message to an elected official, VoterVoice facilitates the communication. Use is optional and information is provided directly by the user. No Student Records.
43	WebPurify	To help identify inappropriate / offensive text in user-generated projects.	Code.org shares user-generated text from user-created projects with WebPurify to attempt to identify inappropriate content. No Student Records.
44	Yet Another Mail Merge (YAMM)	To send emails to teachers and partners.	Code.org shares names and email addresses of teachers and Regional Partners and the content of emails with YAMM. No Student Records.
45	ZenDesk	To respond to user requests and collect bug reports.	In the course of responding to a support ticket, Code.org passes information about the user's email address and their context (e.g. which level they were on) to ZenDesk. Users may also provide information directly to ZenDesk in the course of a responding to a support ticket.