YAIkes — Privacy Policy
Last updated 2 August 2026. Applies to YAIkes version 0.2.0 and later.
Nothing about you is transmitted anywhere. There is no server, no account, no backend, no telemetry, and no analytics. YAIkes never makes a network request of its own — not when you install it, not on first run, not ever. Everything described below is stored on your own machine and is deleted when you remove the extension.
“Of its own” is precise rather than evasive. Two things you can do in the popup navigate your browser, and navigation is a network request in the ordinary sense: clicking the donation link, and pasting a post’s address into Teach from a link. In the second case the extension opens that address in a background tab — the page loads the way it would if you had opened it yourself — reads the post’s text there, turns it into the same kind of numeric representation everything else here uses, stores that with the label you chose, and closes the tab. It fetches nothing itself, and the address must belong to one of the three feeds the extension already works on. What the extension never does is make a request by itself — no fetch, no background call, nothing that happens without you acting.
This is not a promise that happens to be kept; it is a property of how the extension is built. The language model that does the matching is inside the downloaded package, and Manifest V3's content security policy would refuse to load code from anywhere else.
There is nothing to opt out of
Because nothing leaves your device, there is no data sharing to disable, no account to delete, and no third party involved. YAIkes does not sell data, does not transfer it for any purpose, and is not used to assess creditworthiness or for lending.
What is kept on your device
All of this lives in chrome.storage.local. YAIkes deliberately
does not use chrome.storage.sync — that area would
put a record of what you hide onto Google's servers, which is the opposite of
the point.
| What | Why it exists |
|---|---|
| Your icks — which built-in filters are on, and the text of any you wrote yourself. | It is the thing you configured. |
| Confirmed examples — up to 50 embeddings (384 numbers each) per filter, from posts you confirmed when asked. | A filter built from one sentence stays a sentence. This is how it learns what you actually meant. |
| Posts you hid by hand — up to 200 records, each an embedding, a timestamp, the site, and a content hash. | Spotting something in common across several hides is the only way to notice a filter you have not thought to write. |
| A sample of posts you scrolled past — embeddings of up to 400 recent posts you did not hide. No text, no hashes, no timestamps, no addresses. | To tell that you object to something, YAIkes has to know what an ordinary post on your feed looks like. Without this it mistakes "common on your feed" for "something you dislike". Not collected at all until you have hidden a post by hand at least once. |
| Recent scores — numbers between −1 and 1, per site and filter, up to 200 each. | The same wording reads as ordinary on one platform and remarkable on another, so some filters judge against how a site normally reads. |
| Posts you put back — up to 200 content hashes per filter. No text, no embeddings. | So a filter cannot hide the same post again after you have already told it no. The hashes are used for nothing else — they never affect how any other post is scored. |
| What being wrong looked like — up to 50 embeddings per filter, from posts that filter hid and you put back. | A filter otherwise only ever hears when it was right. This is how it hears when it was wrong, so it can move away from what you keep restoring. |
| Posts you taught it — up to 50 embeddings per label you can teach (three content categories plus “sincere”), each with a timestamp and the site it came from. No text, no addresses. | Examples you handed over deliberately — including “sincere — never hide things like this”, which actively protects posts resembling them from being hidden. |
| Patterns you have already answered — a rounded average of a group's embeddings, plus content hashes of groups noticed but not yet confirmed. | So you are never asked twice about something you already dismissed. |
Post text is never stored
Several of the items above hold embeddings. An embedding is 384 numbers derived from a post's text by the language model. It is not the text, and it is not practically reversible to the words — but it is honest to call it derived from a post rather than unrelated to one. Someone reading the storage area could tell that two hidden posts resembled each other. They could not read either post.
The post text itself is held in memory while the page is open and dies with the page. It is never written to disk.
Storage access is restricted to trusted contexts, which deliberately denies it to the part of the extension running inside linkedin.com, x.com and reddit.com.
Nothing here asks who you are
An earlier plan had a paid edition, and with it one more item on that list: a licence key holding the buyer's email in readable form. That edition was cancelled. YAIkes is free in full — nothing is gated, so nothing needs to know who you are.
There is no account, no identifier, and no field anywhere in this extension that is for a person — no name, no email, no device ID, nothing assigned to you or derived from your identity.
One honest qualification, because “we store no names” would be too neat. Your own icks are stored as the text you typed, and that text is arbitrary: if you write an ick naming somebody, that name sits in storage, because you put it there and the extension cannot filter on a phrase it is not allowed to keep. It stays on your machine like everything else here, and it goes nowhere.
The popup carries a link to a donation page. It is an ordinary outbound link that opens in a new tab. The extension does not contact it, cannot tell whether you followed it, and behaves identically either way.
Which sites it reads, and no others
YAIkes reads the feeds on linkedin.com, x.com
(including twitter.com, which X still serves) and
reddit.com. It reads them in order to compare each post against
your filters and hide the ones that match. It requests access to no other site,
and it has no permission to see your browsing history or your open tabs beyond
those three.
Getting rid of it
- Reset on any filter discards everything it learned — the examples you confirmed and the per-site baselines — and returns it to its original wording.
- Reset deliberately does not erase the posts you hid by hand or the patterns you have already answered. Those are a record of what you did, not of what a filter concluded.
- Removing the extension removes all of it, as with any extension's local storage.
Children
YAIkes is not directed at children and collects nothing from anyone. It has no account system and no way to know who is using it.
Changes to this policy
If a future version stores something new, this page changes before that version ships, and the date at the top changes with it. A change that would involve transmitting anything off your device would be a different product, and would be announced as one.
Contact
Questions about this policy, or about what the extension does: kamilandrzejrybacki@gmail.com.