It's important to us that we keep your information safe and secure. In order to help Peergrade provide, maintain, protect and improve our services, Peergrade shares information with other partners, vendors and trusted organizations to process it on our behalf in accordance with our instructions, and any other appropriate confidentiality, security or other requirements we deem appropriate. These companies will only have access to the information they need to provide the Peergrade service.
You can find information on these partners and service providers we work with below, including what data we share with them or they provide to us, the service the provide for Peergrade and links to their respective privacy policies. 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 at firstname.lastname@example.org.
Intercom for delivering customer support on email and live chat to all users (teachers and students). Used to send out product updates to teachers and on-boarding emails to help teachers get started.
Google Analytics for general website analytics (see how many visitors we have, where they come from etc.).
Fullstory to help us understand how teachers and students use Peergrade.
Sendgrid for sending automatic email notifications to our users (eg. a
notification that submission closes soon for students).
Redis To Go for scheduling periodic jobs and for queing tasks related to the product.
Logentries for logging errors and exceptions to make it easier to debug.
Sentry for logging errors and exceptions to make it easier to debug.
Amazon Web Services for storing submission files / work by students and teachers and for hosting our database.
LocalizeJS for translation of our website and app.
Stripe for accepting payments from teachers and institution.
Hubspot for keeping track of institutions that use Peergrade.
Slack for internal team communication.
ProductBoard to help us store, manage and track user feedback on which features we should build and improve.
On the 3rd of April 2019 we updated this list to reflect that we stopped using mLab as our database provider and switched it to Amazon Web Services (which we were already using).