ADHD Reading extension permissions
ADHD Reading extension permissions must be understandable before installation, because users deserve to know why a reading tool can interact with web pages.
A reading extension needs permission to inspect and adjust page text in the browser. Without access to the visible page, ADHD Reading cannot apply bionic reading, semantic highlighting, focus overlays, typography changes, or site memory.
The important distinction is local access versus server upload. Page formatting can happen locally without turning reading content into a remote dataset.
The identity and identity.email permissions read the email and account identifier of the signed-in Chrome browser profile. A website login alone is insufficient. The email is verified by a code before a browser can use trial or paid access. Your account email, device public key and authorization session are sent to the access service; page text and browsing URLs are not included.
Permissions should be kept as narrow as practical. If broader permissions are required for compatibility, the permissions page must explain why, what changes, and how users can control the feature.
ADHD Reading stays privacy-first by treating page content as sensitive reading material. Routine formatting should happen locally in the browser, and any future cloud or AI feature must be clearly explained before users decide whether to send content outside the device. For support, contact support@adhd-reading.com.
Users should have a panic-off control, site-level disable, reset settings, and delete local data option. Permission trust is created by clear controls, not by vague promises.
Frequently asked questions
It needs page access to format visible text and apply focus tools locally in the browser.
No. Permissions allow browser-side operation; uploads should require a separate explicit cloud feature.
Site-level disable and reset controls are part of the product requirements.