FocusFlow Account

Privacy

Reading help should not mean sending your reading to us.

FocusFlow is designed around local page transformation. The extension needs access to normal webpages so it can change how text appears in your browser, but the reading content itself should stay on your device.

Extension data

Settings such as text size, focus band, presets, support pack, and motion preferences are stored locally or in Chrome sync.

  • No page content is required on a server
  • No analytics are needed for the reading effect
  • No remote scripts in the extension

Website checkout

Purchases should happen on the FocusFlow website through a payment provider such as Square. The extension receives only unlock status.

  • Payment data stays with the payment provider
  • License restore needs an email or account
  • Google Pay can be offered on the website where supported

Referral data

Referral codes need basic account records so partners can see earnings, pending status, and payout readiness.

  • Referral code
  • Email for dashboard access
  • Purchase attribution, not page content

Why the extension asks for page access.

A reading extension cannot improve text it cannot see. FocusFlow uses page access to wrap visible words, apply styling, draw overlays, and update focus aids while you scroll.

Chrome internal pages, the Chrome Web Store, PDF viewer pages, and some browser-controlled documents cannot be modified by content scripts. Some highly dynamic sites may need a refresh after an update.