How ReadFit handles your information

1. Overview

ReadFit is a reading comfort prototype that helps you generate and adjust a reading profile based on your preferences. This privacy policy explains what information the current ReadFit release handles, how it is used, and what choices you have.

This policy reflects the product as it exists today. The current version includes member accounts through Supabase Auth, optional Google sign-in, local browser profile storage, anonymous product analytics, anonymous feedback submission, and an optional admin-only contact list for members who explicitly opt in with their email.

2. Information ReadFit handles

When you use the guided setup, ReadFit processes the choices you make in order to generate a recommended reading profile. Those answers are used in the app session to calculate your result.

If you create an account or sign in with Google, ReadFit uses Supabase Auth to handle your member account, session, and sign-in state. This includes account identifiers and session-related technical data needed to keep you signed in.

If you save a profile, ReadFit stores that saved profile in your browser's local storage on the device and browser you are currently using. This saved profile can include reading settings such as font preferences, spacing, width, contrast, and emphasis choices.

If you paste text into the reader, that text is used to render the preview inside the app. In the current version, that reader text is not saved to browser local storage by ReadFit and is not sent to a ReadFit server.

ReadFit also creates or reuses an anonymous session identifier in your browser local storage so it can group anonymous usage events and feedback submissions without requiring an account.

If the Supabase server connection is configured, ReadFit may send anonymous page views, test and profile events, feedback ratings, selected feedback tags, optional notes, page paths, and technical request details such as a user agent string to ReadFit's backend.

If you explicitly opt in when signing up or later in your account area, ReadFit stores your email address in a private admin contact list so the team can reach out about ReadFit updates or follow-up. If you do not opt in, your email is not added to that list.

3. How your information is used

ReadFit uses your quiz answers to generate a custom reading profile and uses your saved profile to power the dashboard and reader experience on later visits in the same browser.

ReadFit uses your account session to let you sign back in and, where applicable, determine whether your account has admin access.

Anonymous usage events and feedback submissions are used to understand which product flows are being used, how useful the current results feel, and what improvements should be prioritized next.

If you opt into the contact list, ReadFit uses your email address only for that private admin follow-up purpose.

The current version does not use your information for advertising, personal identity matching, or sale to third parties.

4. Where data is stored

In the current version of ReadFit, saved profile data is stored locally in your browser using local storage. It is not currently synced across devices through a ReadFit cloud profile system.

Because local storage is browser-based, clearing your browser storage, using private browsing tools, or switching devices or browsers may remove access to your saved profile.

If anonymous analytics or feedback submission is enabled through the server configuration, those records are stored in ReadFit's connected Supabase project rather than in your browser only.

Member authentication records and any optional email-list opt-ins are also stored in ReadFit's connected Supabase project.

5. Sharing and disclosure

ReadFit does not intentionally share your saved profile data with third parties through the current experience because the app does not currently sync saved profiles to a ReadFit backend.

Anonymous analytics and feedback records, account auth data, and optional email-list records may be processed through ReadFit's infrastructure providers in order to store and review them for product operations.

ReadFit may include links to third-party sites or services. If you follow those links, their own privacy policies and terms will apply.

6. Cookies and tracking

The current ReadFit release does not use marketing trackers.

ReadFit does use local browser storage for saved profiles and an anonymous session identifier. It also uses authentication/session cookies or equivalent session mechanisms through Supabase Auth to keep members signed in.

ReadFit may send anonymous product analytics and feedback data when the server-side Supabase connection is configured.

Your browser or hosting environment may still apply standard technical behavior outside the app itself.

7. Your choices

You can stop using ReadFit at any time. You can also remove locally saved profile data by clearing your browser storage for the site.

If you opt into the email contact list, you can remove your email later from the Account area. Once removed, it will no longer appear in the private admin contact list.

The current release does not yet include a self-serve export or full account deletion flow in the product UI.

8. Children's privacy

ReadFit is not currently designed as a service directed specifically to children. If the product scope changes in the future, this policy should be updated to reflect any new obligations.

9. Changes to this policy

ReadFit may update this privacy policy as the product evolves, especially if features such as accounts, richer analytics, cloud storage, or third-party integrations are introduced.

When this policy changes, the updated version should be posted here with a revised effective date.

10. Contact

If you have questions about this privacy policy, you can contact ReadFit at hello@readfit.app.