Privacy architecture
Your screen.
Your control.
Kinder is designed as a local perception layer. The current alpha contains no analytics, accounts, remote inference, or intentional transmission of page text.
Data map
What the alpha touches.
| Data | Purpose | Location | Retention |
|---|---|---|---|
| Visible page text | Match optional tone and reasoning rules. | Processed in the page’s extension content script. | Not intentionally transmitted. Original matched text may be stored temporarily in the element dataset so a future restore control can work. |
| Enabled mode and strength | Remember user choices. | Browser extension local storage. | Until reset or extension removal. |
| Disabled site hostnames | Respect per-site opt-out. | Browser extension local storage. | Until removed by the user. |
| Processed-item counter | Show local usage feedback. | Browser extension local storage. | Until reset or extension removal. |
Permissions explained
Read and change site content
The alpha needs page access to inspect visible comment-like elements and, when enabled, replace specific matched phrases or add a reasoning badge. This is powerful permission. The source is included so it can be inspected before installation.
Storage
Storage keeps the on/off state, rewrite mode, sensitivity, per-site exclusions, reasoning-badge preference, and local counter.
Active tab and scripting
These permissions support user-invoked interaction with the current page and leave room for a controlled rescan action. They are not used to send page text elsewhere.
Boundary: this statement describes version 2.0.0-alpha.1 in this package. Future versions must publish a new privacy record if architecture changes.