How we protect your data
This explains our approach to looking after your data internally and protecting it when it's on our servers. It is also the set of terms that all of our Testers agree to when they sign up to participate in tests with Engage.
Our Terms and Conditions have a section about confidentiality. In short: we keep your information confidential.
With PingPong being integrated into Hotjar as part of Hotjar Engage, Hotjar is a sub-processor of PingPong.
Why we won't sign custom contracts
Occasionally, customers will ask us to sign their own NDA, a custom contract, or to negotiate with their procurement department so that they can have us set up as a supplier to their business.
We're a small bootstrapped team building a SaaS product that's designed for many customers to use.
While we want as many customers as possible to be able to experience Engage, reviewing and signing custom legal agreements costs us a lot of time and money. On a strategic level, this simply doesn't make financial sense for us - we'd soon find ourselves drowning in paperwork and legal fees!
We appreciate that this might be a dealbreaker for some customers, and we'd like to change this in the future when we're a little bigger.
How you can obtain additional protection
It's worth keeping in mind that when running public user testing on Engage, you'll be sharing your IP with people outside of your core team.
While we track down the best testers we can find to participate in your research, these testers are not directly controlled or employed by Engage. We simply connect you to them so that you can hold a productive conversation and run effective research.
We recommend that you find ways to avoid sharing sensitive IP with your customers during your research. Engage is not a good fit for super secret stealth mode products and launches. Instead, think of PingPong research as a semi-public beta test of your designs and ideas.
If it's important for your company to have extra legal protection, we recommend creating a simple 1-page NDA and asking the tester to sign this before or at the beginning of the session. Don't forget to warn testers in advance of this, by including a reference to the NDA requirement in your research description and a screener question to make sure they will be happy to sign an NDA.