FollowerOwl

[00] ABOUT

We build web apps in Ankara. This is one of our own.

FollowerOwl exists because the alternatives all began by asking for an Instagram password, and none of them needed one. Below is what we believe about handling other people’s data, and — more usefully — the decision behind each belief and the page where you can go and check it.

[01] WHO WE ARE

A web app development company, and a small product of our own. The company details, in full, because a trust claim needs a name attached.

We are a web app development company based in Ankara, Türkiye. Most of what we do is building software for other people. Some of it is building our own, and FollowerOwl is one of those — which is why it can afford to answer one question properly and refuse the rest, rather than growing features to justify a valuation.

Working on other people’s products is also where the opinions on this page came from. You see what happens when an app collects more than it needs, and how much easier the security conversation becomes when there is simply less to lose. FollowerOwl is that principle taken to its end: for the free check, your data never reaches us at all.

We are an independent project and are not affiliated with, sponsored by, or endorsed by Meta. It reads only the data export Instagram provides to you.

[ REGISTERED DETAILS ]

Company
Next Yazılım Teknoloji Anonim Şirketi
Address
Üniversiteler Mahallesi, 1606. Cadde, 4A Blok No: 304, Ankara, Türkiye
General enquiries
hello@followerowl.com
Anything about your data
privacy@followerowl.com

[02] WHAT WE BELIEVE

Five things, each with the decision that proves it. A belief with no evidence behind it is a slogan, so every one here links to its own proof.

  1. [01]

    A product should not need your password.

    There is no password field anywhere on this site, and we never ask for your Instagram credentials. Signing in is a link sent to your email that works once. Every competitor in this category starts by asking for the keys to your account; we decided the product had to work without them, and then built it that way.

    How the sign-in works
  2. [02]

    Read what the job needs. Nothing else.

    Your export holds your photos, your messages and years of viewing history. We open three files out of it and never touch the rest — not skipped after reading, never read at all. When you save a snapshot we keep three lists of usernames and their dates, and drop every other field at the point of reading.

    Which three files, and why
  3. [03]

    A claim you cannot check is just marketing.

    We say your archive is never uploaded, so we wrote the instructions for catching us out: open your network panel before you drop the file. The browser also enforces it independently of us, through a policy header you can read yourself. Nobody has to take the sentence on trust, which is the only reason it is worth writing.

    Check it yourself
  4. [04]

    Say what you have not built.

    Our trust page lists the gaps as well as the controls: there is no deletion endpoint yet, no bot challenge on profile creation, and no external audit of any kind. A page of unbroken green ticks would be easier to write and worth far less.

    The gaps, in full
  5. [05]

    A number should say what was measured.

    Results are ordered by how long a follow has lasted, because that is the fact people act on. Where an export carries no dates we say so rather than implying an order. And the headline number is rendered in the same colour as every other number on the page — a red one would be telling you how to feel instead of what happened.

    The arithmetic

[03] READ THE REST

Everything above is checkable. These are the pages where you would go and do it.