ADHD Reading AI transparency means users should know when reading help is local, when AI is optional, and what must happen before any text leaves the browser.
Why AI transparency matters
ADHD Reading AI transparency matters because reading tools can interact with sensitive text. A user may open school notes, internal work documents, personal emails, health information, financial content, legal pages, or private writing. If a future AI feature summarizes, extracts, translates, or analyzes text, users deserve a plain-language explanation before that text leaves the browser.
The ADHD Reading AI transparency standard begins with a distinction: routine formatting is not the same as AI processing. Bionic cues, semantic keyword rules, typography controls, focus overlays, local timers, reading themes, and local stats can happen in the browser. AI summaries or advanced language analysis may require sending selected text to a service. ADHD Reading AI transparency should make that boundary visible.
A transparent product does not hide upload behavior behind vague words like smart, magic, or enhanced. ADHD Reading AI transparency should tell the user what happens, why it happens, and how to avoid it. The goal of ADHD Reading AI transparency is not to reject AI forever. The goal is to make AI understandable, optional, and respectful of private reading contexts.
Sensitive text
Local vs AI processing
Plain-language disclosure
Optional use
Local-first remains the default
ADHD Reading AI transparency starts with the local-first default. The product should use browser-side processing whenever a feature does not need a server. Visual emphasis, focus overlays, reader mode de-emphasis, reading themes, timers, keyboard shortcuts, and local text-to-speech can support many reading needs without uploading full page content.
This local-first baseline matters because ADHD readers need fast help in the moment. They should not have to evaluate a privacy tradeoff just to increase line height or start a focus loop. ADHD Reading AI transparency means ordinary reading assistance should remain available without requiring cloud analysis. ADHD Reading AI transparency means optional AI should be an extra layer, not a hidden dependency.
If a future feature can run locally with acceptable quality, ADHD Reading should prefer the local path. If a future feature truly needs cloud AI, ADHD Reading AI transparency requires that the user see the difference before using it. The ADHD Reading AI transparency default promise is simple: local support first, AI only with clear user understanding.
Local support first
No hidden AI dependency
Cloud only when needed
Clear user understanding
Consent before text upload
The strongest ADHD Reading AI transparency rule is consent before upload. If a feature needs selected text, a paragraph, or a page segment to leave the browser, the product should explain that moment before it happens. ADHD Reading AI transparency requires consent to be specific to the action, not buried in a general settings page. Users should understand whether they are summarizing, translating, extracting actions, or asking a question about text.
Consent should also include scope. ADHD Reading AI transparency should show whether the feature sends selected text, the current paragraph, the article body, metadata, or settings. Sending a selected sentence is different from sending an entire page. The product should not ask users to trust a vague black box when the scope can be explained clearly, and ADHD Reading AI transparency keeps that scope visible.
Users should be able to cancel. ADHD Reading AI transparency is weaker if the user cannot back out after seeing the upload explanation. A respectful ADHD Reading AI transparency flow gives users a clear continue action, a cancel action, and a local alternative when possible. This makes privacy part of the workflow instead of a surprise.
Specific consent
Visible scope
Cancel path
Local alternatives
Data minimization and retention
ADHD Reading AI transparency should follow data minimization. If a feature only needs a selected paragraph, it should not send the whole page. If it only needs a question and excerpt, it should not send browser history. If it can work without account identity, it should avoid attaching account identity. Less data means less risk and less anxiety for users, which is why ADHD Reading AI transparency includes minimization.
Retention should also be understandable. ADHD Reading AI transparency should explain whether AI requests are stored, for how long, for what reason, and how users can delete related account data if cloud features are introduced. For many assistive reading use cases, ADHD Reading AI transparency should make the best default clear: do not retain page content longer than required to complete the request.
Data minimization also supports schools and workplaces. IT reviewers need to know what content moves, where it moves, and whether it can be controlled. ADHD Reading AI transparency should make that review easier by documenting boundaries in plain language rather than forcing reviewers to infer behavior from marketing copy.
Send less text
Avoid unnecessary identity
Explain retention
Support reviewers
User controls and auditability
ADHD Reading AI transparency needs user controls. Users should be able to keep AI features off, use local-only workflows, clear local settings, export preferences, reset site memory, and understand which features are local. If account or Pro features are added, the product should make AI-related controls visible and easy to find.
Auditability can be simple at first. ADHD Reading AI transparency can include clear labels, permission pages, changelog entries, privacy whitepaper updates, and support documentation. If an AI feature changes how data flows, the changelog should say so. If a feature remains local, the UI should say that too. ADHD Reading AI transparency labels reduce guesswork.
Questions about ADHD Reading AI transparency can go to support@adhd-reading.com. Users should avoid sending confidential page content in support emails unless absolutely necessary. A useful AI transparency support request can describe the feature, browser, page type, and concern without pasting private text.
AI off switch
Local-only workflows
Changelog updates
Support without private text
What this means for the roadmap
ADHD Reading AI transparency shapes the roadmap. Future summaries, action extraction, terminology help, question answering, or translation should be designed as optional workflows. They should not replace local bionic cues, focus overlays, typography controls, reader modes, themes, timers, checklists, and browser speech. Local reading help remains the base layer.
The ADHD Reading AI transparency roadmap should also separate free local features from paid AI features. ADHD Reading AI transparency helps users understand whether a feature costs money because it uses a cloud service, stores account settings, or requires additional infrastructure. With ADHD Reading AI transparency, clear pricing and clear data flow should move together.
ADHD Reading is not medical treatment and does not diagnose ADHD. ADHD Reading AI transparency should keep that boundary visible too. AI may help summarize text or extract actions, but it should not present itself as clinical advice. The ADHD Reading AI transparency product promise is practical reading support: calmer pages, clearer next steps, better restarts, and privacy-aware optional AI.
Optional roadmap
Local base layer
Clear pricing
No medical claims
Frequently asked questions
AI Transparency FAQ
What does ADHD Reading AI transparency mean?
It means users should know when a feature is local, when AI is optional, what text may be sent, why it is needed, and how to avoid uploading content.
Will ADHD Reading require AI for routine formatting?
No. Routine formatting such as bionic cues, focus overlays, themes, timers, and local stats should remain browser-side whenever possible.
Can future AI features upload page text?
Only if the user chooses an AI workflow that clearly explains the upload scope, purpose, and alternatives before text leaves the browser.
Is AI in ADHD Reading medical advice?
No. ADHD Reading is an assistive reading and productivity product, not diagnosis, treatment, therapy, or medical advice.
