Ostrich collects nothing about you. It runs entirely in your browser. No data leaves your machine. This summary contains everything of substance in this document. The rest is the same thing, said again, in more words, for legal reasons that do not apply to you because you are not reading this.
What Ostrich does
Ostrich is a Chrome extension that reads your LinkedIn feed, checks whether posts contain certain keywords, and hides the ones that do. It replaces them with a small placeholder so your feed continues to look like a feed, only quieter. That is the entire product.
It runs entirely as local code in your browser. There are no servers. No backend. No analytics. No infrastructure of any kind, which is worth noting because this is the sort of document — a privacy policy — that normally exists in proportion to the amount of infrastructure there is. This one is longer than the infrastructure warrants. The infrastructure warrants nothing. And yet here we are.
What we collect
Nothing. Below is a complete and exhaustive list of the personal data Ostrich collects, stores, processes, or transmits to any party, including but not limited to Org Fwd, its employees, its contractors, or anyone else who might conceivably be interested, which is no one, because the list is as follows:
- — Your name
- — Your LinkedIn activity
- — The content of posts you see or hide
- — Your browsing history
- — Your location
- — Any identifying information whatsoever
The dashes represent the data. There is no data. The dashes are the point. If you have reached the dashes and are still reading, you are doing something statistically extraordinary, and we are grateful, in the abstract sense that one can be grateful to someone who will never know they were appreciated, which is the only sense available here, since we do not know who you are, because we collect nothing.
What gets stored locally
Ostrich uses Chrome's built-in storage to remember two things between sessions: whether the extension is enabled or paused, and how many posts it has hidden in total. Both live in your browser. Neither leaves it. You can clear both at any time by removing the extension, though we would prefer you didn't, not for data reasons — there are no data reasons — but because then the extension would be gone.
Third parties
There are none. Ostrich does not use analytics tools, crash reporting services, advertising networks, or any external services of any kind. It does not make network requests. It is, from a data perspective, entirely inert. Writing a third-party section for a product with no third parties is itself a kind of performance — a formal gesture toward a concern that does not exist — and we are aware of that, and we are doing it anyway, because this is a privacy policy and that is what they contain.
Ostrich reads the text of posts on your LinkedIn feed locally, in your browser, in order to check for keywords. It does not interact with LinkedIn's API. It does not transmit post content anywhere. It reads and immediately forgets, which is, on reflection, a reasonable way to approach most of LinkedIn.
Changes to this policy
If we ever change what Ostrich collects, we will update this page. The current version collects nothing. Should we ever collect something, we will tell you here, in a document you will not read, which is perhaps the most honest possible arrangement.
Contact
Questions about this policy can be sent to hello@orgfwd.com. Ostrich was built by Org Fwd, an organisational development consultancy based in Stockholm. We help organisations change. We built a Chrome extension that hides LinkedIn posts. These two things are consistent.
Last updated: 17 April 2026