We build one thing, and we build it properly.

Why this exists

Creators kept describing the same experience: a link in the bio works for weeks, then reach quietly drops, with no notification and nothing to appeal. The cause was usually mechanical — a platform crawler opening the page behind the bio link and evaluating every destination on it.

Every link-in-bio tool solves the page. Almost none of them touch what happens when the visitor is not a person. That gap is the whole reason this product exists.

What we actually do

A visit is classified before the page renders: the request is matched against known crawler signatures, the IP is checked against datacenter, VPN, proxy and Tor exit ranges, and anything still ambiguous gets an invisible verification the visitor never sees. A recognised platform crawler receives a clean, compliant version of the panel; a real visitor at the identical address receives everything.

Link destinations are never written into the page. Each one resolves through a single-use, short-lived token at the moment it is clicked, so scraping the HTML returns nothing useful either way.

That protection applies to every panel on every plan, including the free one. What price gates is convenience — a custom domain, a crawler view you design yourself, the stats API, geo filtering, team accounts — never the protection itself.

What we deliberately do not do

We do not promise you will never be banned. This removes one specific, very common cause; it does not touch anything else about how you use your account, and no tool can make that promise honestly.

We do not make prohibited content permitted. If a destination breaks a platform’s rules, that does not change because a crawler saw a different page.

We do not sell a storefront, an email list or a course. One product, one problem.

We do not publish invented testimonials, customer logos or usage numbers. If you do not see social proof on this site, it is because we have not earned any we can name yet.

How we handle data

Panels are excluded from search indexes by default, and so are the images uploaded to them. Analytics are aggregated: visit counts, clicks per link, country, device, referrer. Visitor IPs are processed for the security checks and for counting unique visitors as a one-way, per-panel salted hash — the original address cannot be recovered from it, and the same visitor cannot be correlated across different panels.

The full detail, including every subprocessor and the legal basis for each, is in the privacy policy. It is written to be read, not to be survived.

Where it runs

On our own server, not a managed platform we can be evicted from. Data lives in our own database and our own disk. That is a deliberate choice for a product whose entire premise is that platforms change their minds about you without warning.

Getting in touch

Questions about the product, or something broken? The support channel is linked from the footer of every page, and we read everything.