Privacy policy for GigScope: Gig Rank & SEO Keywords for Fiverr
GigScope: Gig Rank & SEO Keywords for Fiverr by exochard
Last updated: 2026-11-16
GigScope for Fiverr ("GigScope") is a browser extension published by Giuseppe Castelluccio as Exochard, the publisher named on its store listings. Giuseppe Castelluccio decides what data GigScope handles and is responsible for it. Contact: support@exotools.dev
This policy covers the extension, the GigScope API it talks to (hosted on Cloudflare at api.exotools.dev; older versions call it at exotools-api.exochard.workers.dev, or at gigscope-api.exochard.workers.dev, which forwards to it) and the website https://gigscope.exotools.dev. It describes every kind of data GigScope collects, how it is used, where it is stored, how long it is kept and who it is shared with. GigScope collects no data that is not listed here.
GigScope helps Fiverr sellers see their market. It reads the Fiverr pages you open (it also requests public gig pages, see Gig pages below) and shows extra information on them: statistics on search results and gig pages, a rank checker for gigs you choose to track, and Keyword Scout, which checks related keywords (more of them with Pro). A press on Read top reads the first five gig pages of a search in your browser. It runs only on www.fiverr.com.
- Authentication information: your Pro licence key, sent to the GigScope API to check it and, when you remove or replace it, to free its seat.
- Your gigs, history and research, only if you turn on Drive sync, in builds that include it: encrypted in your browser under a passphrase you choose, then stored in the hidden app folder of your own Google Drive. We receive nothing.
- Technical data, if you press Send in the diagnostics panel, and the trial marker: the diagnostics report is a short report about your install, shown on screen before it is sent (see Technical report below); the trial marker described under Licence check is read when the extension starts and when you press Try Pro, and written when a trial starts.
GigScope does not collect your browsing history, health, financial or payment information, location, or the content of pages other than the Fiverr pages described here. It does not sell data, does not use it for advertising, and does not use it to decide creditworthiness or for any purpose unrelated to helping you with your Fiverr gigs.
The extension asks for room beyond the usual storage limit, so rank history, journal and notes are not capped by the browser's 10 MB limit. Rank history keeps checks for up to 97 days on every plan, at most 400 per keyword; Free shows the last 30 days and Pro shows 90. All of it stays on your computer.
These stay in your browser's extension storage and are never sent to us:
- Gigs you choose to track, the keywords you attach to them, and the rank history for those keywords.
- Rank history you import from a CSV file: GigScope reads the file you pick in your browser and keeps its readings with the rank history, marked as imported. The file is not sent anywhere.
- A journal of the edits GigScope saw on your tracked gigs, with the text of a title, tags or description before and after, and the last Keyword Scout run for each gig (Pro).
- Your drafts and recorded edits for tracked gigs: the text you typed or pasted, the gig text it replaced, and the date of the edit.
- Competitor gigs you choose to watch: the gig's title, seller name and url, its place, price and review history for the keyword, and, when you open the gig page, a snapshot of its tags, packages, description (up to 2,000 characters) and FAQ with a log of what changed.
- The seed and results of your Gig ideas runs: the latest one for free, up to 5 for Pro.
- Edit tests you mark, the gig ids on the last Fiverr search page you opened, the page-one medians kept with rank samples, and the title words page one used at the last check of each keyword.
- A dated audit trail of facts read from each tracked gig's page (title length, tags, description length, packages, FAQ, gallery), the pages-deep readings from Look deeper, and the sort and filters you left on each keyword's results, including the currency of a price range.
- For each tracked gig, once a day, when you open its page or when an automatic check reads it: its review count, orders in queue and lowest package price, and the seller's completed orders and reviews, kept up to 120 days, for the estimated orders.
- Dated notes you write on a gig's timeline.
- The review counts GigScope saw for each gig on search pages, kept 180 days, for Reviews since.
- Your daily usage counters, your settings and the start date of your trial.
- The state of the gig panel (open, pinned, position, role per gig), whether the search summary is open, the rating prompt state, the daily-check schedule and progress of a running job, a count of Fiverr pages GigScope could not read with the date of the last one.
Your licence record stays in the same storage:
- Your Pro licence key and the pass end date, if you activate Pro.
- The random id for this browser.
- Any key whose seat release is still waiting, with the signed pass kept for it.
The licence keys and the random id go to the GigScope API only with the licence check and the seat release described below.
Uninstalling the extension deletes all of it.
In your browser's sync storage, the extension also keeps the start and end dates of your free trial, the latest clock time it has seen and the trial outputs you have used. We never receive the clock time or the trial outputs. The trial dates reach our API only in the trial cookie described under Licence check.
- What is sent: your licence key, the product name, the random id for this browser, and the licence features this version understands. Each check adds a one-time random code and its time. For a key already active in this browser, the check adds the seat code our server gave this browser and the signed pass it holds.
- The random id: the extension makes it when the licence first needs it. If the server sees the same id in a copied browser profile, the extension replaces it with a new one.
- Seat release: when you remove a key or enter another one in its place, the extension sends that key, the product name, the random id for this browser, the licence features this version understands and the seat code it holds for that key, to free its seat. When you remove a key, it also sends the signed pass it holds for that key. If the server does not confirm the release, the extension sends it again later until the server confirms it. It keeps at most the last 10 keys waiting. A new key entered over an active pass with an end date also sends the old key, so the new pass starts where the old one ends.
- Firefox: the browser asks your permission before the key is first sent. Without it, the key and the random id for this browser are not sent.
- When: when you activate Pro or press Check now, then about once a day. After a check that fails or gets no clear answer, the extension tries again about 15 minutes later. The free trial starts and ends on your device. Starting a Pro trial stores a small cookie from api.exotools.dev in this browser, holding only the trial's start and end, to the hour, and whether it is an offer trial, for up to 400 days, so a reinstall continues the same trial. A trial that already runs is stored the same way the first time the extension reads it after an update. Firefox sets it only if you allow technical data; one set earlier is moved to its new address after the update either way. With no trial on this device, the extension asks api.exotools.dev for that cookie when it starts and when you press Try Pro, so a reinstall shows the trial this browser already had. The request names only the product, in its address, and the browser sends this product's trial cookie with it. Versions before 2.0.1 kept the trial cookies of all exoTools products under one address, so each request carried the others' cookies too. Once after updating to 2.0.1, the extension asks api.exotools.dev to move this product's older cookie to its own address, and the old one is deleted. Until another exoTools extension you use also updates, its older cookie still goes along with this request; the API reads only this product's. Once it has an answer it stops asking at start; with no answer, it asks again at the next start. On Firefox this read asks no permission; pressing Try Pro asks for the technical data permission first, because starting a trial writes the marker. It holds no identity, and we keep no copy. Clearing cookies or site data for api.exotools.dev deletes it; uninstalling does not.
- Why: to confirm the key is valid with Payhip, the seller of record for Pro passes, and to count each browser once, so entering the key again in the same browser never takes a second of its 3 seats.
- Where it is kept: the GigScope API files a seat record under a one-way hash of the product name and key. It holds the random id of each browser that uses the key, and when each was last seen. It also holds one-way hashes of each browser's current seat code, with its issue time, and of the last code that browser presented, and whether each seat was reported to Payhip. The key and the seat codes themselves are not stored. All of it except a marker that the record once existed is deleted at most 400 days after the key was last checked.
- Pass record: the GigScope API also notes which pass the key belongs to, under another one-way hash of the product name and key. It is deleted at most 400 days after the key was last checked or bought.
- Refunded-key marker: When a full refund withdraws a known licence, the API stores a one-way hash of the product and key to keep it disabled. The marker has no automatic expiry; backups can contain it.
- Seat moves: when a key's seat moves to a new browser, the GigScope API notes the time under the seat record's hash and deletes it after 7 days.
- Early-user offer count: While the plan is Free or a trial, each screen that shows the Pro passes (the popup, the Upgrade screen, and the options page or side panel where the product has one) asks api.exotools.dev how many of the discounted orders for each early-user code are left, and asks again every 2 minutes while it stays open. The request names only the product, in its address; it sends no key, id or cookie, and nothing is stored.
- Regional price: the extension reads your browser's time zone on your device and never sends it. Only when the time zone is in India, Pakistan, Bangladesh or Nigeria does it ask api.exotools.dev for the regional code, sending no key, id or cookie. To answer, the API reads which country the connection comes from, as Cloudflare reports it, and keeps nothing.
- What happens: to check where a tracked gig ranks, the extension requests Fiverr search pages from your browser, the same way you would by searching.
- When: when you press a check button, a Keyword Scout button, Look deeper (which reads up to 25 search pages one after another) or a request to read pages 4 to 5. Free can switch on a weekly check of the first gig; a Pro or trial user can switch on one automatic check a day. Both run while the browser is open and are off until you switch them on. If you allow notifications, an automatic check may show a notification on your device when keywords drop.
- Gig pages: the extension requests the public page of a gig when you press Peek or a review CSV button, and, while an automatic check is on, once a day for each tracked gig that has no estimate reading yet that day. It sends nothing to us.
- Where it goes: to Fiverr only, with your normal Fiverr session and nothing added by GigScope. The results stay in your browser.
- What is sent: your tracked gigs and keywords, rank history, the journal, your roles, saved scouts and Gig ideas runs, encrypted in your browser with a key made from your passphrase, to the hidden app folder of your own Google Drive, and the Google sign-in token the browser holds for that folder. The passphrase is never stored on disk or sent.
- When: only after you turn Drive sync on, about every 15 minutes while it is on, and when you press Sync now.
- Why: to keep your gigs, history and research on every browser you sign in to. GigScope's servers are not involved; the traffic goes between your browser and Google.
- Where it is kept: in your Google Drive app folder, which only exoTools extensions can reach and which you can delete from the Drive section in GigScope. Google handles that data under its own privacy policy.
- Permissions: identity and access to www.googleapis.com, to sign in to Google and reach your Drive app folder. In Chrome and Edge both are optional and asked for only when you turn on Drive sync; in Firefox identity comes with the install, is used only for Drive sync and shows no prompt. Also alarms, for the daily and weekly automatic checks.
At most once a day, the extension checks gigscope.exotools.dev/rules.json for a signed settings file and keeps its built-in defaults when none is published. The request sends no cookies and no data from the extension.
- What is sent: product and version, browser name and major version, operating system family, language, plan (free, trial, pass or lifetime), the failure classes for Fiverr pages GigScope could not read, and two settings: the daily check on or off, and reading paused or not.
- Never in it: Fiverr page addresses, gig, seller or search text, your account, licence key or email.
- When: only when you open Send diagnostics and press Send, after the report is shown on screen in full. Copy sends nothing. GigScope sends no report in the background or on a schedule.
- Firefox: the browser asks for its technical data permission at the first Send and when you press Try Pro free.
- Where it is kept: the GigScope API keeps the report for 30 days, then deletes it. Backups do not include reports. The API does not store your network address with the report.
- Deleting: the panel shows a reference after sending. A report is found only by that reference. To delete one earlier, write to support@exotools.dev with the reference.
When you remove the extension, the browser opens https://gigscope.exotools.dev/bye. The uninstall page sends nothing. It offers a link to leave a review and an email address.
The roadmap page at https://gigscope.exotools.dev/roadmap shows planned and shipped changes. Loading it asks the API for the list of items and sends only the product name. The website sets no cookies. The theme you pick with the theme button stays in this browser (localStorage) and is never sent. It counts page views, except on the uninstall page, with Cloudflare Web Analytics, which sets no cookies and keeps nothing that identifies you.
If you buy Pro, Payhip handles the payment, your name, your email address and the licence key under its own privacy policy. Payhip then sends the GigScope API a notice about the order. The API keeps the order number, the product code of the pass and the price in a log for 30 days. It keeps the order record (order number, product code, a one-way hash of each licence key and any refund amount) and a daily count of sales for 400 days. When a pass renews an earlier one, it also keeps a one-way hash of each of the two licence keys with the pass start and purchase dates and the length of the earlier pass. This link is deleted about two years (766 days) after the renewal starts. The API keeps a pass record under a one-way hash of the product and licence key. It expires 400 days after it is written; its expiry is periodically refreshed when the key is used. Nightly cloud backups may include order records, renewal links and pass records. These backups are normally kept for 30 days. They can be kept longer when newer complete backups are not available. Your name, email address, network address and licence key are not stored by GigScope, except when you withdraw (below).
If you withdraw from a purchase on the withdrawal page, GigScope keeps the name, email address, order number and order date you type, a reference and the time, for 24 months, then deletes them. They are used only to handle that withdrawal. Withdrawal backup copies are scheduled for deletion after 30 days, even when other backup records are kept longer. The withdrawal page loads Cloudflare Turnstile to block bots; Cloudflare sees your network address and browser signals. No other page loads it.
We share data only with the services that run GigScope, and only for the purposes above:
- Fiverr, for rank checks and Keyword Scout: https://www.fiverr.com/privacy
- Payhip, to check licence keys and handle Pro payments: https://payhip.com/privacy
- Cloudflare, which hosts the GigScope API and the website: https://www.cloudflare.com/privacypolicy/
We do not sell or rent data, do not share it with advertisers or data brokers, and do not transfer it for any other purpose. We would disclose data only if the law requires it.
All traffic between the extension, the GigScope API and the services above uses HTTPS. The GigScope API keeps licence keys and network addresses only as one-way hashes.
- See or delete your local data: uninstall the extension, or clear its data in your browser's extension settings.
- Ask a question or free a licence seat: write to us at support@exotools.dev. We answer within 30 days.
- Delete a technical report: write to support@exotools.dev with the reference shown after sending.
- Delete a withdrawal record: write to support@exotools.dev with the reference shown after sending.
- If you live in the EU or the UK, you also have the rights the GDPR gives you, including the right to complain to your data protection authority.
GigScope is a tool for Fiverr sellers and is not directed at children under 16. We do not knowingly collect data from them.
When this policy changes, we update this page and the date at the top. A change that adds a new kind of data ships only with an extension update whose store listing describes it.
Exochard, at support@exotools.dev