Privacy Policy

The short version

AccessPath doesn't collect, store, transmit, or sell any personal data — from this website, or from the widget once it's installed on someone else's site. There's no analytics, no cookies, no tracking pixels, and no third-party calls beyond the two exceptions listed below.

This website (accesspath.dev)

This is a static site. It doesn't run any server-side code, doesn't set cookies, and doesn't use any analytics or advertising service. We don't know who visits this page, how many times, or from where.

The AccessPath widget

When embedded on a host site, AccessPath stores a visitor's accessibility preferences (text size, contrast, profile selection, and similar settings) in that browser's own localStorage — on the visitor's device, under a key the host site controls. That data:

• Never leaves the visitor's browser.
• Is never sent to AccessPath, to us, or to any server we operate — the widget doesn't have a backend at all.
• Is only accessible to the site that set it, exactly like any other localStorage value.

The two exceptions

Two optional features make outbound network requests, and only when a visitor actively uses them:

• Dictionary lookups — double-clicking a word sends that single word to api.dictionaryapi.dev, a free, keyless public dictionary API, to fetch its definition. No other page content or visitor data is sent.
• Read Aloud — uses your browser's own built-in speechSynthesis API. This runs entirely on-device; nothing is sent anywhere.

Every other feature — text size, contrast, spacing, saturation, reading guide, page structure navigation, and the rest — runs entirely client-side with zero network activity.

Self-hosting

Because AccessPath is open source and self-hosted (see the MIT License), a site that installs it is running your own copy of the code from your own infrastructure. We have no visibility into, and no involvement with, how any individual site uses it.

Questions

AccessPath is a community project without a formal support channel yet. Once the repository is public, the best place to ask a privacy question will be a GitHub issue.