Third Party Service Providers
It's important to us that we keep your information safe and secure. In order to help Schoolhouse.world (“Schoolhouse”) provide, maintain, protect and improve our services (the “Schoolhouse Services”), Schoolhouse shares information with a few other partners, vendors and trusted organizations (“Service Providers”) to process it on our behalf in accordance with our instructions, Privacy Policy and any other appropriate confidentiality, security or other requirements. These Service Providers will only have access to the information they need to provide the Schoolhouse Services.
You can find information on these Service Providers we work with below, including what data we share with them, or they provide to us, the service they provide for Schoolhouse and links to their respective privacy policies or other documents that govern how they handle the information they process on our behalf.
Like any other organization, we also use “IT” business services or internal tools such as Google Drive and Slack to operate our organization (“Internal Tools”). These Internal Tool services may incidentally contain personal information (e.g., email address or contact handle) and we apply the Service Provider restrictions described above and have included these in a separate chart below.
This list may change over time, and we’ll work hard to keep it up-to-date. If you have any questions, please get in touch with us at privacy@schoolhouse.world.
Schoolhouse Services Privacy Policy
Technical Service Providers
Name of Service Provider | How Schoolhouse uses the Service Provider | What user information is shared or collected by this Service Provider and/or passed back to us from the Service Provider? |
Authentication provider used for Schoolhouse authentication | Schoolhouse receives authentication token and user info (email, name, picture), but not account passwords. | |
Cloud software used for core infrastructure, servers, and databases | We store Schoolhouse content and traffic data on AWS servers. All personal information written to disk is encrypted in transit using 256-bit SSL encryption, and encrypted in storage (server-side encryption) with Amazon S3-managed keys (SSE-S3). | |
Customer feedback tool where users can publicly submit bug reports and feature ideas, and comment on each others’ | No data is explicitly shared as the Schoolhouse feedback page is served by Canny and so all the feedback-related data is stored by Canny. Single sign on allows for a seamless experience. When a user submits feedback, Canny collects data from the user such as user name, title of feedback post, and the feedback itself. | |
Authentication provider used for Schoolhouse authentication (via Auth0) | Schoolhouse receives authentication token and user info (email, name, picture), but not account passwords. | |
Cloud infrastructure software | Schoolhouse shares data with Cloudflare for caching purposes where caching occurs near the end user (around the world). | |
Chat support software used for answering users’ questions on the website or over support email (operated by volunteers out of Slack integration) | Schoolhouse shares certain user data (display name, email) to identify individuals requesting user support. This is needed for safety purposes (e.g. banning certain users who continue to spam user support). Crisp.chat collects data from the user, including the support request and cookies that are needed to save the support chat history. | |
Engineering monitoring and logging software | Schoolhouse shares server logs and other system events (including at a user level) in order to debug engineering issues that may arise. | |
Facebook / LinkedIn / Reddit / Twitter / Whatsapp | Tutoring session and series pages include "Share" buttons that direct you to these external websites (Facebook, LinkedIn, Reddit, Twitter, WhatsApp) if users want to optionally share them on social media | No user data is shared, and no trackers are put on the Schoolhouse website associated with these buttons. Instead, the buttons simply lead users to URLs on the social media websites where they can choose to log in and share (in which case those websites will collect user data, but nothing is shared back with Schoolhouse). |
Analytics platform used to improve the product and understand overall usage | Schoolhouse shares system events (including at a user level). | |
Cloud software used for core infrastructure and databases, particularly real-time data associated with notifications and messaging on the platform | We store Schoolhouse content and traffic data (particularly real-time data associated with notifications and messaging on the platform) on Google servers (all personal information written to disk is encrypted). | |
Authentication provider used for Schoolhouse authentication (via Auth0) | Schoolhouse receives authentication token and user info (email, name, picture), but not account passwords. | |
Analytics platform used to improve the product and understand overall usage | Schoolhouse shares system events (including at a user level). | |
Donation platform used for receiving donations to Schoolhouse.world 501c3 non-profit | No data is explicitly shared as the Schoolhouse donation page is served by Network for Good. When a user makes a donation, Network for Good collects data from the user such as full name, address, payment details, and donation amount. | |
Analytics platform used to improve the product and understand overall usage | Schoolhouse shares system events (including at a user level). | |
Email API service for sending emails to users (e.g. digests, notifications, etc.) | Schoolhouse shares user data needed to send personalized emails (e.g. email address, user's name to include in email, country to segment emails by country, content of the email). | |
In-platform and email surveys for assessing user needs and product feedback | Schoolhouse shares the user id and user email with Sprig to allow us to reach the user for the survey and keep track of users we've already surveyed before. Sprig collects and stores the user's responses to the surveys. | |
Community platform (forums, Q&A, groups, etc.) for both learners and tutors. | No data is explicitly shared as the forum is served by Tribe and so all the forum-related data is stored by Tribe. Single sign on allows for a seamless experience. When a user submits something to the forum, Tribe collects data from the user such as user name, email address, post title, and post content. | |
Platform for sending text messages to users who opt in to receive text notifications about tutoring sessions | This only applies if a user optionally decides to provide Schoolhouse with their phone number to receive notifications. In this case, Schoolhouse shares the user's phone number (along with the content of the SMS messages) with Twilio so that Twilio can send text notification reminders about tutoring sessions they are signed up for or that are about to start. | |
Form and survey software used for occasional surveys and also tutor training modules | When linking a user to a Typeform url from the website, Schoolhouse may include a unique identifier associated with the user in the url query parameters so as to match the Typeform responses with the user. We sometimes use Typeform webhooks as well to track once the user has completed the form and store some of the responses (e.g. "selected choice A for question 1") in Schoolhouse's databases. This allows us to create a seamless experience with these external forms. Typeform itself also collects and stores all the responses to Typeform surveys (e.g. our tutor training modules and product surveys). | |
Video platform for embedding occasional video content on the Schoolhouse platform. | Schoolhouse receives the analytics data about these YouTube (e.g. # of views). Schoolhouse uses YouTube's Privacy Enhanced Mode to limit tracking of viewing behavior and Schoolhouse is marked for Child-Directed treatment. If the user clicks or taps out of an embedded video, and is redirected to another website, that website may track the viewer’s behavior as per that website’s policies and terms. | |
Video conferencing software used for live tutoring sessions | Schoolhouse shares user registration details needed for the Zoom meetings (e.g. name, preferred pronouns). From Zoom's API, Schoolhouse receives metadata on the session (e.g. attendance data and how long participants stayed in the Zoom), as well as recordings that are saved for up to 60 days for safety & quality purposes before being deleted. |
Internal Tools
Name of Service Provider | How Schoolhouse uses the Service Provider | What user information is shared or collected by this Service Provider and/or passed back to us from the Service Provider? |
Utilized for Schoolhouse internal emails, docs, slides, spreadsheets, etc. | Schoolhouse stores its own emails and files using Google services. Schoolhouse may share personal information with Google in the course of utilizing Google services, for example if a user emails employees for support. | |
Team communication platform used by internal team as well as the tutor & volunteer community | Schoolhouse may incidentally share personal information with Slack, in the course of communications between team members, including engineers and support teams (e.g., debugging an issue for a user). User Support volunteers also manage user support tickets in Slack (see details on Crisp.chat.). |