Skip to content

Privacy Policy — Browser Extension

Effective date: 21 November 2026  ·  Klupt Chrome extension 1.9.3

This policy explains what the Klupt Chrome extension (the "Extension", "we", "us") accesses, stores, and shares. It applies only to the browser extension, not to any other KLUPT product.

In short: the Extension shows the accounts an Instagram profile followed most recently, newest first. When you open or search a profile, the Extension sends its username to our server, which checks whether it's public; we log that lookup. For a public profile, the server returns its recent follows, so the Extension never uses your Instagram session for it. For a private profile you already follow, the Extension reads its lists in your own browser, using your own Instagram session, and keeps the full lists on your device. After each check it sends us a short result: the accounts it found newly followed, new followers or no longer there, plus how the check went. We use it to send you Telegram alerts if you turn them on, and to fix problems. We never receive your Instagram password or cookies. Our usage statistics never contain the usernames of the profiles you view. The sections below say exactly what reaches us, why, and for how long.

Every profile you open: checked by our server

When you open or search an Instagram profile, public or private, the Extension sends that profile's username, together with your random device ID, to the KLUPT API, which checks whether the profile is public. For a public profile, our server returns the accounts it followed most recently (username, display name, profile picture, verified/private flags) from publicly available Instagram data. For a private one, it only says so. Results for a username are cached on our server for a few hours and shared by everyone who looks that profile up, so the same lookup isn't repeated.

We also log every lookup: the username, your device ID, the result (for example found, private or not found), whether you're a subscriber, how long it took, and the IP address and country the request came from. We use these logs to keep a daily limit of lookups per device, prevent abuse, fix problems and improve the service. This means our records show which profiles were looked up from your device ID. The Extension also re-checks the profiles you track now and then, the same way. We never notify the profile.

Private profiles: read on your device, results sent to us

For a private profile you follow, the Extension calls Instagram's own web API from your browser, authenticated by your existing Instagram session. It reads that profile's following list, and its followers list where available (username, display name, profile picture, and verified/private flags), and keeps a snapshot on your device so later checks can spot changes.

After each check, the Extension sends our server a check result, with your device ID and the Extension version:

  • the private profile's username and Instagram ID, and whether the check was manual or automatic;
  • the accounts the check found newly followed or as new followers (username, display name, Instagram ID, verified/private flags, at most 100 per list), and the usernames of accounts that are no longer in the list;
  • how the check went: whether it finished, the reason if Instagram limited or blocked it, how many requests it made, how long it took, and the size of each list.

We use check results to send your Telegram alerts (below) and to find and fix problems with the Extension. We also record the IP address and country the result came from.

  • The full lists never leave your device: we receive only the accounts that changed since the last check.
  • The Extension can only see what your own Instagram account is permitted to see.
  • We never receive or store your Instagram password or session cookies.
  • We never notify the profile or the accounts in its lists.

Telegram alerts (optional)

With a plan, you can turn on Telegram alerts in Settings → Telegram alerts. "Connect Telegram" asks our server for a one-time link to our Telegram bot. When you press Start in Telegram, your Telegram account (its ID and username) is linked to the account behind your purchase, the same way linking Telegram works on klupt.io.

From then on, when a check result shows that a private profile you track followed someone new or got a new follower, our bot sends you a Telegram message naming those accounts. To avoid repeats, we remember which accounts we already alerted you about for 30 days. You can turn alerts off in the same place at any time; it's one switch for your account, so it also applies to klupt.io's alerts.

Stored on your device

  • Following-list snapshots and the new-follow feed for the private profiles you track.
  • The last results shown for recently opened public profiles, which of those accounts you had already seen (to mark new ones), and your recent searches.
  • A randomly generated device ID (not derived from your name, email or Instagram account).
  • Your unlock status and an access token for it; a checkout reference while you pay; your email only if you restore a purchase.
  • Your language choice, and the Instagram request counts the Extension uses to stay under Instagram's limits.

This data stays in your browser. Uninstalling the Extension removes it.

Sent to our servers

  • Username of a profile you open or track, public or private, with your device ID: to check whether it's public and, if it is, return its most recent follows. Each lookup is logged (see above).
  • Check results for private profiles you track, with your device ID: the accounts each check found new or gone, and how the check went (see "Private profiles" above).
  • Your device ID, to create a checkout, check and grant your unlock, open the billing portal, load the Extension's feature settings, and link or check your Telegram alerts.
  • Your email address, only if you use "Restore purchase" (so we can email you a secure link).
  • If you click "See it on klupt.io" on a public profile: your device ID, to get a one-time login link for klupt.io. The profile's username goes only to klupt.io, in the address of the page that opens.
  • Feedback: if you use "Send feedback", your rating (1–5), your message and, if you give it, your email, with your device ID, the Extension version and language.
  • Chat with us opens the support chat on klupt.io (run by Crisp) in a new tab. So we know who we're talking to, the Extension passes your device ID, its version and language, whether you have a plan, and your purchase email if it has one, in the part of the page address after "#", which your browser doesn't send to our server; the page hands them to the chat and removes them from the address. What you write in the chat is stored by Crisp so we can reply.

Our server also records the IP address it sees, the country that address maps to, and your browser's user agent with these requests. We use this to run the Extension and process payments, prevent abuse, find and fix bugs, and improve the product. We do not sell it, use it for advertising, or share it except with the processors below.

Usage analytics

So we can tell whether the Extension works for people and fix it when it doesn't, it sends us a small number of product events, each tagged with your random device ID, the Extension version and, once you have bought a plan, the email on your purchase. We collect:

  • When the Extension is installed, updated, or opened, which screen it showed (home, live list, tracker, private-profile notice) and, if it can't load, a coarse reason code (for example "not on Instagram").
  • When you search, start or stop tracking a profile, and when a check begins, finishes, or fails — with how many new follows it found and how many requests it took (numbers only) or a coarse failure reason.
  • When the unlock paywall is shown, when checkout starts, and when an unlock completes.
  • When the "rate us" prompt or the klupt.io button is shown or clicked, and when you send feedback.
  • When you open Telegram alerts, open the Telegram link, finish linking, or turn alerts on or off.

Events never contain the username of the profile you're viewing, nor any following list or anything about the accounts in it. (Check results for private profiles are separate, and are described above.)

Third-party services

  • Stripe — payment processing. When you buy a plan, Stripe handles your card details and billing email under Stripe's privacy policy. KLUPT never receives your full card number.
  • Instagram data providers — our server reads public Instagram profiles through a third-party data API.
  • Crisp — the support chat on klupt.io that "Chat with us" opens, under Crisp's privacy policy.
  • Telegram — if you turn on Telegram alerts, they are delivered by our Telegram bot, under Telegram's privacy policy.
  • Instagram / Meta — for private profiles you follow, the Extension uses your own Instagram session in your browser, under Instagram's terms.

Permissions we request & why

  • Access to instagram.com — to know which profile you're on, and to read the following list of private profiles you follow.
  • Access to Instagram's image CDNs — to display profile pictures.
  • Access to our API — profile lookups, private-profile check results, Telegram alerts, purchase and unlock, feature settings, usage events and feedback.
  • Storage / unlimited storage — the device-only data listed above.
  • Alarms — to check for your unlock shortly after payment, and to re-check tracked private profiles every few hours while Instagram is open.
  • Notifications — to tell you when your purchase has unlocked.
  • Tabs / activeTab / scripting — to detect Instagram profile pages and open the checkout, klupt.io, support chat and Telegram tabs.

What we don't do

  • No selling or renting of your data.
  • No advertising or ad tracking.
  • No collection of browsing history outside of detecting Instagram profile pages.
  • No storage of private profiles' full lists on our servers: only the accounts each check found new or gone.

Data retention & your choices

Device data stays until you uninstall the Extension or clear its storage. Public-profile results are kept on our server only as a short cache. Usage events and lookup logs are kept for up to 13 months, then deleted. Private-profile check results are kept for 90 days, and the record of which accounts a Telegram alert already named for 30 days. Your Telegram link stays until you disconnect it on klupt.io or ask us to remove it. Feedback is kept until you ask us to delete it; chat conversations are kept in Crisp until you ask us to delete them. Purchase records (device ID, email, transaction) are kept as needed to honor your access and meet legal and accounting obligations.

Uninstalling removes the device ID from your browser, but what was already sent to us stays for the periods above. To ask for a copy of your data or for its deletion, contact us below; if you bought a plan or gave us an email, include it so we can find your records.

Children

The Extension is not directed to children under 13 and we do not knowingly collect their data.

Changes

We may update this policy; material changes will be reflected by a new effective date on this page.

21 November 2026 (extension 1.9.3): after each check of a private profile you track, the Extension now sends our server the result (the accounts it found newly followed, new followers or no longer there, and how the check went), kept for 90 days; added optional Telegram alerts for those changes.

5 November 2026 (extension 1.7): the username of each profile you open or track is now sent to our server, which checks whether it's public and looks public profiles up instead of your Instagram session (each lookup is logged); added the feedback form and Chat with us (the klupt.io support chat); added how long we keep these records.

Contact

Questions or data requests: privacy@klupt.io

© 2026 KLUPT. This policy covers the Klupt Chrome extension.