Aviso de privacidad para GigScope: Gig Rank & SEO Keywords for Fiverr
GigScope: Gig Rank & SEO Keywords for Fiverr por exochard
Aviso de privacidad para GigScope: Gig Rank & SEO Keywords for Fiverr
Last updated: 2026-10-03
GigScope reads the content of Fiverr pages you open in your browser and shows extra information on those pages. It runs only on www.fiverr.com.
- Gigs you choose to track, the keywords you attach to them, and the rank history for those keywords.
- A journal of the edits GigScope saw on your tracked gigs, and the last Keyword Scout run for each gig (Pro).
- Your daily usage counters, your settings, and the start date of your trial.
- Your Pro license key and the pass end date, if you activate Pro.
This data lives in your browser's extension storage. Uninstalling the extension deletes it.
- License validation. When you activate Pro, and at most once a day after that, your license key is sent to the GigScope API, which checks it with Payhip (the seller of record for Pro passes). Nothing else is sent with it.
- Suggestions and problem reports. If you press Send in the suggestion form, the message you typed, the kind you chose (idea or problem), the extension version and the email address, if you typed one, are sent to the GigScope API. Nothing is sent before you press Send, and the email address is optional. Your browser may ask for permission to share this data before it is sent; if you decline, nothing is sent.
- Rank checks. The extension requests Fiverr search pages from your browser, the same way you would by searching. This happens when you press a check button or a Keyword Scout button. A Pro or trial user can also switch on one automatic check a day, which runs while the browser is open and is off until you switch it on. Those requests go to Fiverr only.
Apart from the items above, no browsing history and no page content leave your computer. Nothing is sold or shared with advertisers.
- Payhip (payments, license keys): https://payhip.com/privacy
- Cloudflare (hosting of the GigScope API)
Open an issue at https://github.com/exochard/gigscope-site/issues