INBOUNDONSTEROIDSResearch tool ↗

LinkedIn pattern research / Privacy

Privacy, in plain terms.

This notice covers the LinkedIn pattern research tools offered by InboundOnSteroids. It describes the data our service receives when you use those tools.

Publisher: Ivan Manfredi
Contact: im@ivanmanfredi.com

What reaches the service

Niche breakouts receives the requested market and a 7, 28 or 90-day window. Check draft receives category labels selected within ChatGPT. We do not request or store a full draft or your conversation in the application usage record.

The tools use these inputs to return historical rates, sample sizes and links to public LinkedIn posts. An unrecognized market is mapped to a labelled pooled fallback, with a nearest covered-market hint. The raw unrecognized text is not saved in our usage record.

A small record helps us run the tools.

To control abuse and understand usage, Cloudflare handles the caller network address briefly to derive a daily salted HMAC hash. The application does not store the raw IP address in its usage record. It stores the rotating hash, tool name, canonical market, whether that market was uncovered, request and completion times, response size, and an anonymous event identifier. Short-lived minute and day counts enforce service limits.

The hash changes daily. Recent-admission hashes used for the minute limit are pruned during later successful admissions; they may remain in local storage while the service is idle. The daily hash may still be personal data, and it may limit our ability to identify a particular row from an email request. We do not use the tool response to serve advertising. These information pages have no analytics script or cookies.

Where the records sit

The tool endpoint runs on Cloudflare Workers. Its SQLite Durable Object serves public research snapshots only while they are no more than five minutes fresh; an expired snapshot may remain stored until it is replaced or the service is retired. The object also durably holds anonymous usage events while they await import into our Supabase reporting table. After Supabase confirms an event, the pending copy is removed from the Durable Object. The central Supabase usage table currently has no automatic expiry; its rows remain until we delete them or retire the service.

Cloudflare and Supabase may separately retain operational logs or backups under their own controls and policies. Public example links open LinkedIn posts hosted by their publishers. If you open one, that site handles your visit under its own terms and privacy practices.

Email us directly.

For a question about this notice, or to request access, correction or deletion where applicable, email im@ivanmanfredi.com. Include the approximate time and tool used. Please avoid sending private drafts or sensitive identifiers. We will explain what we can locate and what action we can take, including limits caused by the rotating hash.