Who Are Seesaw's Subprocessors?
Seesaw uses a handful of third-party subprocessors – other companies that we share information with to help us do business. These companies help us do things like manage our data centers to make sure Seesaw is reliable and fast or provide software that powers our customer support. If you would like further information on the data collection and use practices of the subprocessors listed, please visit our Privacy Policy linked below or contact us at privacy@seesaw.me.
Our subprocessors have signed a Data Processing Agreement with us, which stipulates that any data we share with them will be used exclusively to provide services to us and not for any other purposes. We currently use the following subprocessors.
Subprocessors
Core Services: Vendors used to make the Seesaw service operate.
| Subprocessor Name + Link to Privacy Policy * indicates the subprocessor accesses student data |
Category of Subprocessor | How we use this subprocessor | What is shared with the subprocessor | Location | Security |
|---|---|---|---|---|---|
| Amazon Web Services* | Core Services | We use Amazon Web Services (AWS) to manage our data centers and the computers that we use to operate Seesaw. All information we collect is stored on computers and databases managed by AWS. | Everything in Seesaw. | USA | More |
| Amplitude | Core Services | We use Amplitude for analytics and reporting in the Seesaw app. | User device information and actions or interactions with the app. | USA | More |
| Datadog* | Core Services | We use Datadog for analytics and reporting in the Seesaw app. | User device information and actions or interactions with the app. | USA | More |
| Google* (Analytics, Firebase, Google Workspace) | Core Services | We use Google for analytics and reporting as well as for internal documentation. | For Analytics and Firebase: Device information, county-level location.For Google Workspace: Seesaw teammates collaborate via Google Workspace and may incidentally share limited user data like email address or user IDs of individuals submitting requests and the content of the requests itself (e.g., bug reports, any other help center requests, and data pull requests from teachers and schools). | USA | More |
| HighTouch | Core Services | We use HighTouch to sync data between two other systems. | Teacher and admin name and email address. | USA | More |
| Mailgun* | Core Services | We use Mailgun to send emails to Seesaw users to notify them about activity in their account. | Your name and email address. | USA | More |
| Maxio (SaaSOptics) | Core Services | We use Maxio for business tracking. | Admin name and contact information. | USA | More |
| Outreach | Core Services | We use Outreach to send emails to current and prospective customers. | Admin name and contact information. | USA | More |
| Quickbooks | Core Services | We use Quickbooks for financial tracking and for auditing purposes. | Admin emails related to Purchase Orders. | USA | More |
| SalesforceAnd native apps:-Sonar-Tableau-Vicasso | Core Services | We use Salesforce and its native apps for customer tracking. | Admin name and contact information. | USA | More |
| Sentry | Core Services | We use Sentry for analytics and reporting. | Your contact information, device information and actions or interactions with the app. | USA | More |
| Snowflake* | Core Services | We use Snowflake for Analytics and Reporting | Your name and email address. | USA | More |
| Stripe | Core Services | We use Stripe for payment processing. | Admin name and school payment information. | USA | More |
| Twilio | Core Services | We use Twilio to send text messages to Seesaw users about activity in their account. | User phone number (if you have provided it to us). Seesaw does not collect student phone numbers. | USA | More |
Internal Tools: Vendors used internally by Seesaw employees to operate the business.
| Subprocessor Name + Link to Privacy Policy * indicates the subprocessor accesses student data |
Category of Subprocessor | How we use this subprocessor | What is shared with the subprocessor | Location | Security |
|---|---|---|---|---|---|
| Calendly | Internal Tools | We use Calendly to schedule customer calls. | Admin name and contact information. | USA | More |
| Docusign | Internal Tools | We use Docusign to electronically sign contracts. | If you receive a Docusign contract, your name and email address. | USA | More |
| Form Assembly | Internal Tools | We use Form Assembly to electronically sign contracts. | If you receive a Form Assembly contract, your name and email address. | USA | More |
| Gong | Internal Tools | We use Gong to record calls, emails and demos with current and prospective customers. | Admin name, contact information, and call recording if the call recipient consents. | USA | More |
| LeanData | Internal Tools | We use LeanData to improve routing of opportunities for the Sales team. | Admin name and contact information. | USA | More |
| Marketo | Internal Tools | We use Marketo to manage email campaigns and marketing channels. | Marketo pulls data directly from Salesforce. | USA | More |
| Slack* | Internal Tools | We use Slack for internal employee communication. | Seesaw teammates collaborate via Slack and may incidentally share limited user data like email address or user IDs of individuals submitting requests and the content of the requests itself (e.g., bug reports, any other help center requests, and data pull requests from teachers and schools). | USA | More |
| Zapier | Internal Tools | We use Zapier to communicate between web applications. | Seesaw teammates use Zapier to efficiently manage multiple web applications and may incidentally share limited user data like email address or user IDs of individuals submitting requests and the content of the requests itself (e.g., bug reports, any other help center requests, and data pull requests from teachers and schools). | USA | More |
User Support and Research: Vendors used to provide support to current and prospective customers and conduct user experience research.
| Subprocessor Name + Link to Privacy Policy * indicates the subprocessor accesses student data |
Category of Subprocessor | How we use this subprocessor | What is shared with the subprocessor | Location | Security |
|---|---|---|---|---|---|
| Ada | User Support and Research | We use Ada to provide automated customer support to adults via a chat interface. | If you use our support chatbot, Ada will receive all of the information you input. If you submit a support ticket through Ada, Ada will receive your name and email address. | Canada | More |
| BigMarker | User Support and Research | We use BigMarker to host webinars with admins and teachers. | Admin and teacher name and contact information. | USA | More |
| Chameleon | User Support and Research | Seesaw uses Chameleon to give teachers and admins real-time updates on product updates and provide product tips to help them navigate and utilize the platform. | Limited user data such as role type (teacher or admin); email domain; district, user, and org IDs; and general account data (last seen, date created, etc.). | USA | More |
| Chili Piper | User Support and Research | We use Chili Piper to help prospective customers navigate the website, drive lead generation, and have live chat conversations to schedule meetings. | The information inputted in the request form- Admin name, email, title, school name and state or country | USA | More |
| Thinkific | User Support and Research | We use Thinkific to provide Seesaw trainings to teachers. | Teacher name and contact information. | USA | More |
| Typeform | User Support and Research | We use Typeform to conduct surveys and user research. | Your name and contact information if you are asked to complete a survey. Students do not participate in surveys. | USA | More |
| Zendesk | User Support and Research | We use Zendesk to operate our internal customer support tools, such as our help center and support ticketing system. | If you submit a support ticket, Zendesk will receive your name, contact information, and the content of your support request. Seesaw takes steps to prevent students from contacting Seesaw support and deletes any support requests and associated data students submit to Zendesk. | USA | More |
Website Services: Vendors used to operate the Seesaw marketing website.
| Subprocessor Name + Link to Privacy Policy * indicates the subprocessor accesses student data |
Category of Subprocessor | How we use this subprocessor | What is shared with the subprocessor | Location | Security |
|---|---|---|---|---|---|
| CookieYes | Website Services | We use CookieYes to obtain and honor cookie consent preferences on web.seesaw.me | If you visit Seesaw's website, your IP address. | USA | More |