[prodtorok]

I'm not sure how to mitigate the data selling concern or what to show you there. But we're trying to upsell a paid service via nice free utility. We send your data to use AI to generate the resume, that is part of the deal. So if you wouldn't give your data to ChatGPT, don't give it to us (delete it from linkedin also - because your principles sound weak while you let it reside there). We store the data so that paid users can reference their linkedin profiles. Feel free to request a delete and we'll do so with adequate proof: support at cvgist dot com.

Google in fact allows minified code, not obfuscated.

Using LinkedIn is a highly desired feature in the resume builder business. Highly successful firms are using 3rd party services that scrape your profile (already have) without your consent.

So, no, you can parse the minified code all you like - the advantage we have with my implementation is competitors spend minutes scraping while we dont need to. - Which as you've inherently figured out, is not that insightful. - The extension codebase is small and doesnt communicate with any server

[bitbasher]

Your extension works on people's profiles that are not your own (if you paid for the enterprise ability, according to the extension's code). So is this not aiding with scraping peoples' data?