How MyStalk.io treats your data
Revised
Our side of the ledger
Close to empty. Registration does not exist here, so we have no file with your name on it. The
site is a bundle of prebuilt pages, and nobody here keeps a list of the handles you type. The
catch: every lookup opens a page with the handle in its address, as /?u=name. That address
gets noted in the routine request logs our host and network shield keep for every visit, and our
edge keeps a per-IP tally of requests for a few minutes so that one visitor cannot flood the viewer.
Our own measuring is limited to one counter of where visitors come from, explained next. Ads are a separate story, told in the Advertising part
further down; any change to that gets written here first and the date up top moves.
In practice, the origin counter does this: some seconds into a visit the page sends the name of the referring host (never the whole link), the landing page, the country and, if there is one, a campaign label. The day’s total increments. No cookies, no IDs, no IPs. A browser that announces DNT or GPC stays silent, and day totals disappear after roughly three months. MyStalk.io also wants to know if anyone returns. Your browser holds a lone day number for that, written shortly after the page has loaded, and only a gap class (brand new, the same day, tomorrow, later that week, much later) is sent. It carries no identity, DNT or GPC visitors get none, and wiping what the site stored in your browser takes it away.
Your side of the ledger
Your recent-peeks row is saved by your browser (local storage, to be exact) and stays put on that machine. A service worker also tucks the site’s own pages into your browser’s offline cache so they open with no signal; no handles or profiles go into it. Hit Clear and it is gone; wiping MyStalk.io from your browser settings does the same, offline copy included. A second device or browser sees none of it, and incognito tabs forget it the moment you close them.
Anatomy of a lookup
You press View. First comes an invisible check, Cloudflare Turnstile, to confirm that a human
rather than a script is asking. It runs on every lookup, normally without a puzzle, judging a few traits of your browser
along the way. Then the page opens at /?u=name, MyStalk.io receives the handle, and our server
puts the question to an external data vendor, which reads that public account at Instagram. All that
vendor learns is the requested handle, sent from our own machine. Neither your IP nor your
browser headers nor our domain go any further than us. Its log retention is set by the vendor; we have no say in it.
The answer comes back through our server, and after that every picture and clip is loaded by your browser directly off Instagram’s photo and video servers; those servers log your IP but cannot tell which site sent you. The profile picture, the highlight covers and your downloads are routed via our server, so Instagram does not see you for those. Want to give everyone less? A VPN or a browser built for privacy narrows what each server you visit can pick up.
Advertising
MyStalk.io lives on ad income. Which ads show up is decided by an outside network, not by us, and the network keeps whatever data its own rulebook allows. Nothing asks for your consent beforehand, whichever country you are in. Expect the network, with those who buy space through it, to leave cookies, look-alike identifiers or tiny tracking images on your device while ads load.
- Tabs hiding underneath: tapping nearly anywhere on a page, whether the spot is an ad or plain text, can pop a sponsor’s site open in a tab that ducks behind this one.
- Little overlay cards: miniature promos float over the text, and a cross dismisses each.
- Screen-filling ads: when a lookup ends or a blog page is open, one can take over the whole window until closed.
- Alert permission: the browser may put up a question after you search: should mystalk.io be allowed to ping you? A yes means promos reach you while all our tabs are closed. You can retract it under the site’s settings in the browser at any point.
- Paid suggestions: “Dig deeper” tacked onto the last line of a bio, “Sponsored: next up” boxes and tiles dotted around results and articles, a ribbon stuck along the bottom, and “Hot picks” links under the recent-peeks row, within the photo-and-video viewer and at the page’s foot.
- Saving: a tap on a download button can bring up one sponsor tab too, though never twice inside sixty seconds. The thing you saved is delivered unaltered.
- Data on the network’s side: IP, browser and its language, viewport size, which site this is, and whether an ad was seen or tapped. All of it goes to picking ads, damping repeats, tallying views plus taps and spotting fraud. Ads can be tuned to what you did on unrelated sites.
- Blocker test: before every lookup a request goes out toward the network. A blocker that kills it cancels the lookup and a message asks for ads to be switched on for this site. We tally cancellations and nothing more: no handle, no IP.
We never pass a handle you typed to the network. But the result page’s address includes it
(/?u=name), so every script on that page, the ad ones among them, can read it.
Who else is involved
- Web host: stores the pages and sends them out.
- Network shield in front of the site, Cloudflare: keeps abusive traffic out and runs the invisible Turnstile check before each lookup, briefly handling IP addresses as it does.
- Data service: retrieves each public profile our server requests (see the lookup anatomy above).
- Instagram’s photo and video servers: send every picture and clip you view, seeing your IP address as they do.
- Advertiser-side network: the third party that runs each of the placements above.
Nobody else is on the list. We sell to no one, since we hold nothing worth selling.
Rights you have
Ask what we have on file about you and we will correct or delete it; honestly, the answer will be “nothing linked to you”, and we will say so by email. The team behind MyStalk.io handles these requests itself, all through contact@mystalk.io. Your national privacy regulator will also hear complaints.