4 ms·

Thanks necovek! TBH, LinkedIn probably won't be our biggest fan but there still remains a big gap between sales nav and CRMs that we're trying to fill. Our use

Thanks necovek! TBH, LinkedIn probably won't be our biggest fan but there still remains a big gap between sales nav and CRMs that we're trying to fill. Our users need to make sure they use our tool responsibly. It's doing what they can already do manually and making it easier for them. We think we should be outside the bounds of GDPR as we don't do business in the EU, though as more and more jurisdictions setup similar legislation it's something we will need to keep in mind and probably need to have a good think about as we move forward. A simple fix may be to ask our users to acknowledge that they have permission to gather this data in certain cases or something of that nature? With LinkedIn data itself, public profiles are considered in the public domain though I'm not sure of the legal nuances of that and how that works with GDPR or how it may impact us in future. Being super fresh, we don't have a way for you to count yourself out. I'm wondering though, how do you presently deal with your data that has already been, or may be, collected by the myriad existing lead and data aggregation services?

necovek 6y ago
Thanks for an honest reply. California has either already, or is in the process to introduce similar legislation, so you might need to worry about sooner than you might think. I personally don't make my profile public on any service (LinkedIn in particular), but with your product being a browser extension, it sounds as if it's not limited to public profiles, but profiles visible to the current user. In general, it is the responsibility of whoever might use your service to acquire permission from whomever they want to include in their databases, and to explicitely state what external data processors they use. You'd only be a data processor in that case, and you'd need to have a suitable contract with every customer, but IANAL, so take all this with a bucket of salt. There is no simple way to chase after anyone who might be keeping my personal data, so I ain't doing that, but if you end up popular, you may get some good will if you make it easy for people to directly opt out.
- JimNamii 6y ago
  Yeah great points. I think I heard that NY state might be on track for similar legislation soon too? Anyhow, we'll see - we certainly don't want to do anything super dodgy or put people in a bad position. Got any pointers to affordable datasets/lists? At this stage our first tool is a way for us to build datasets and a user base though yeah, it could turn out this is for a limited time only. Buying datasets can be expensive and we're trying to bootstrap.

necovek 6y ago

Thanks for an honest reply. California has either already, or is in the process to introduce similar legislation, so you might need to worry about sooner than you might think. I personally don't make my profile public on any service (LinkedIn in particular), but with your product being a browser extension, it sounds as if it's not limited to public profiles, but profiles visible to the current user. In general, it is the responsibility of whoever might use your service to acquire permission from whomever they want to include in their databases, and to explicitely state what external data processors they use. You'd only be a data processor in that case, and you'd need to have a suitable contract with every customer, but IANAL, so take all this with a bucket of salt. There is no simple way to chase after anyone who might be keeping my personal data, so I ain't doing that, but if you end up popular, you may get some good will if you make it easy for people to directly opt out.

JimNamii 6y ago
Yeah great points. I think I heard that NY state might be on track for similar legislation soon too? Anyhow, we'll see - we certainly don't want to do anything super dodgy or put people in a bad position. Got any pointers to affordable datasets/lists? At this stage our first tool is a way for us to build datasets and a user base though yeah, it could turn out this is for a limited time only. Buying datasets can be expensive and we're trying to bootstrap.