Privacy Policy

1. Who this covers

This policy describes how Fabling, at fabling.app, handles information when you visit the site, join the waitlist, or use the app. Questions: fablingapp@gmail.com.

2. Information we collect

Depending on how you use Fabling, we may store:

• Google account name, email address, and profile image, used to sign you in
• learning profile: language (Spanish or French), placement level, and onboarding answers
• stories written for you, including title, text, ratings, and narration audio
• vocabulary: saved words, review history, lookups, and related progress
• reading and listening time, words consumed, and grammar-practice state
• legacy waitlist details and requests for podcast or AI tutor beta access
• AI tutor text transcripts, session times, interruptions, and the learner context and instructions used for each session
• your saved timezone and story-generation allowance
• first-party account milestones, such as onboarding, lesson completion, and return visits
• session cookies needed to keep you signed in

We do not run advertising pixels or third-party analytics on the site today.

3. How we use it

We use this information to:

• create and keep your account
• write stories at your level and play audio
• show definitions and in-sentence explanations
• schedule vocabulary reviews
• operate subscription access, billing, and learning features
• fix bugs and keep the service running

4. Language models and audio

During a speaking session, audio is sent to Google to provide the live tutor. Fabling saves text transcripts and session details for learning support, troubleshooting, and improving tutor behavior. Authorized administrators can review these records. Fabling does not store recordings of your tutor audio.

Story text, word lookups, and in-context explanations are produced by Google language models on the server. Narration is produced by Google text-to-speech. The story text and the word you look up are sent to those services so they can return a story, a gloss, an explanation, or audio. We do not use those requests to advertise to you.

5. Processors

We rely on:

• Google, for sign-in, story generation, AI speaking tutor sessions, explanations, and audio
• Supabase, for the database and media assets
• Vercel, to host the application
• Stripe, for secure subscription billing, trials, and payment processing
• PostHog, for product usage and onboarding funnel analytics (we do not use advertising trackers)
• Resend, for transactional notifications and trial lifecycle emails

Each of those providers processes data securely according to its own terms and privacy policy.

6. Cookies

Fabling uses cookies and similar storage to keep you signed in after Google authentication. We do not use cookies for advertising.

7. Retention

We keep account and learning data while your account exists. Waitlist entries are kept until you are invited or removed. From Profile you can reset your learning data or delete your account. Reset clears stories, vocabulary, and progress and keeps you signed in. Delete removes your account and associated learning data. You can also email fablingapp@gmail.com to ask for deletion, including removal from the invite list. We may keep limited records if we are required to, or if they are needed to prevent abuse.

8. Sharing

We do not sell your personal information. We share it with the processors above to run Fabling, or if the law requires it.

If you connect an assistant, Fabling shares the learning information requested through that connection and within the permissions you grant. This can include vocabulary, grammar evidence, practice focus, brief practice records, and progress totals. You can separately allow word corrections and saved practice. These tools do not share your email, billing information, private tutor transcripts, or full content library.

We store the connected app’s supplied name and callback addresses, your permissions, connection and last-use times, and a history of its learning updates. Authentication credentials are stored as hashes. We retain your learning records and connection history while your account exists. A learning reset clears connector practice records and focus and revokes connections; deleting your account removes its associated connector records.

Daily cleanup removes authorization codes, access-token records, and request-limit records more than one day after expiry. Refresh-token hashes remain while a connection can still refresh, so reused tokens can be detected. They are removed after the connection has been revoked for 30 days or all its tokens have been expired for 30 days. Client registrations that never acquired a connection are removed after 90 days. These operations do not remove saved learning progress.

Manage and disconnect assistants at Connected apps. Disconnecting stops future access; it does not remove information already received by another service. That service handles the information under its own privacy policy. Connector and consent pages are excluded from product analytics, including sign-in links carrying connection parameters.

9. Children

Fabling is not directed at children under 13, and we do not knowingly collect personal information from them.

10. Changes

We may update this policy. The date at the top will change when we do.

11. Terms

Use of Fabling is also governed by the Terms of Service.