Privacy Policy

1. Information we handle

• Preferences: selected adjustments, their strengths, interface settings, and website-specific choices. Some choices describe reading difficulties or accessibility needs and may reveal sensitive information about you. They are not a medical diagnosis.
• Account information: optional Auth0 sign-in provides an account identifier, name, and email. The extension stores account display information, an access token, and its expiry locally. Our sync database stores your account identifier, preferences, and the time they were updated; it does not separately store your name or email.
• Webpage information: the extension processes webpage elements, text, and site addresses to apply adjustments and website-specific settings. Selected text is processed for reading aloud or word lookup. Full webpage content is not uploaded to our preference-sync server.
• Interactions: features may process pointer movement, keyboard focus, and text selections locally to position reading aids or activate tools. Our application does not upload interaction recordings or keystroke histories to the sync database.
• Service connection information: online requests expose information such as IP addresses and request metadata to the services receiving them. Those providers may maintain operational or security logs under their own policies. We do not request GPS access or use precise location for adjustments.

2. How information is used

We use information to remember and apply your choices, authenticate optional accounts, save and retrieve account preferences, provide reading tools, and operate and troubleshoot these services. We do not sell user data, use it for advertising, or use it to determine creditworthiness or lending eligibility.

Site addresses support features such as permitted-tab adjustments and per-site preferences. The sync database is not designed as a browsing-history log, but website-specific settings may include site origins when saved or synced.

3. External services

• Auth0: handles sign-in and account credentials. The extension does not store your account password. See Okta/Auth0's privacy policy.
• Render and Neon: Render hosts our sync API and Neon stores account-linked preferences. The API verifies your Auth0 access token before reading or updating your settings. See Render's privacy policy and Neon's privacy policy.
• Google word lookup: when the enabled lookup feature is triggered, the selected word or short phrase is included in a Google search URL. Google receives the search text and normal connection information. See Google's privacy policy.
• Read aloud: selected text is passed to browser or operating-system speech tools. Voice availability and processing depend on the browser and voice provider; local-voice features are intended to use voices reported as local.

These services may process data in countries other than your own. We do not send your Auth0 access token to Google word lookup.

4. Your choices and deletion

• Use webpage adjustments without signing in to avoid account sync.
• Disable or reset adjustments through the extension, and manage site access through your browser.
• Turn off word lookup to stop that feature from sending selected words to Google.
• Sign out to remove the extension's saved account token and account display information. Your local settings remain, and signing out does not delete server-side preferences or your Auth0 account.
• Resetting choices changes preferences; it is not an account-deletion feature. Removing the extension does not delete previously synced server data.
• To request deletion of synced preferences or your project account, email ton53576nam@gmail.com. We may need to verify account ownership. Do not send passwords, access tokens, or database credentials.

5. Retention and security

Local preferences remain until cleared, replaced, or removed through browser controls. Account-linked preferences remain until replaced or deleted; the current sync service does not automatically expire them. Account tokens have an expiry time. Providers manage their own logs and backups under their policies.

Deployed login and sync requests use HTTPS. The sync API uses verified account identifiers to scope access to preferences. No system can guarantee absolute security.

6. Changes and contact

We will update this page and its date when our data practices change. Questions or privacy requests can be sent to ton53576nam@gmail.com.

Project: Accessify on GitHub.