Privacy Policy

DOCIBLE is a microlearning product on the web at getdocible.com and in the iOS and Android apps. This policy applies to all of those surfaces. Questions: hello@getdocible.com.

When you create an account we store:

• The email address you use to sign in, and a password hash managed by our authentication provider — we do not store your password in plain text.
• A display name if you provide one during onboarding.
• Onboarding choices: topic interests, a daily learning-goal length, and any optional schedule or content preferences you set.
• Notification category preferences (for example daily reminder or achievements). We do not send push notifications unless that feature is enabled and you have allowed it.

If you later use Sign in with Apple or Google, we receive the identifiers those providers share for sign-in — typically an email or a provider user id. Those buttons stay hidden until the provider is configured.

To operate the library we store, on your account only:

• Lessons and insights you open, complete, save, or add to a collection, including resume position and time spent where the product records it.
• Quiz attempts and scores. Correctness is scored on the server; the client does not receive an answer key.
• Progression derived from that activity: XP events, level, streak, daily goals, quests, achievements, and Knowledge Score.
• Search queries you run in the product, stored only as needed to return results — we do not sell search history.
• If you use DOCIBLE AI, the prompt and generated reply for that request, tied to your account and the passage you asked about.

We store entitlement state for DOCIBLE Pro — plan, product identifier, platform, period end, and whether the subscription will renew. We do not store full payment-card numbers.

Web checkout is processed by Stripe. The iOS and Android apps use Apple or Google billing through RevenueCat. We keep a provider customer or app-user identifier so restore and webhook updates can attach Pro to the correct DOCIBLE account.

Product analytics (PostHog) and crash reporting (Sentry) are wired in the apps. They send data only when a project key or DSN is configured. If those keys are not set, the product does not call those services.

When they are on, events include things such as “lesson opened” or “quiz completed,” a content id, platform, and whether the account is Pro. The analytics layer strips emails, names, passwords, tokens, cookies, and AI prompt or output text. Sentry is configured not to send default personal information and strips authorization and cookie headers.

We do not use advertising SDKs, and we do not sell personal information.

• Supabase — authentication, the application database, and row-level security so you can only read and write your own private records.
• Vercel — hosts the website and admin.
• Stripe — web subscription checkout and the customer billing portal.
• RevenueCat, Apple, and Google — App Store and Play subscriptions and restore.
• OpenAI — only if you use DOCIBLE AI, via a server-side proxy. The model key is never shipped in the app.
• Resend — transactional email (for example account deleted) when that service is configured.
• PostHog and Sentry — only when their keys are configured, as described above.

Hosting and authentication providers may process ordinary technical logs (such as IP address, user agent, and timestamps) to keep the service running and secure. We do not use those logs to build advertising profiles.

The website uses session cookies so Supabase can keep you signed in. The apps may cache a local snapshot of your account so the library can load. Clearing the session signs you out. We do not set third-party advertising cookies.

We use it to authenticate you, deliver the library, remember progress, enforce free-plan limits, apply a Pro entitlement, send transactional mail you trigger, and — when configured — understand product usage and fix crashes. We do not use your lesson answers or AI prompts for advertising.

In the website, open Settings and choose Delete account. In the iOS or Android app, use the same control in Settings. That calls our server, which removes your private rows (progress, saves, collections, quiz attempts, subscription row, AI generations, and related account data cascade from your profile) and then deletes the authentication user.

You can also write to hello@getdocible.com from the email on the account. Store billing history remains with Apple, Google, or Stripe according to their policies. Cancel a subscription in the store or billing portal before or after deletion if you do not want it to renew.

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

If the product starts collecting a new category of personal data, we will update this page and the effective date. The current policy lives at getdocible.com/privacy.

DOCIBLE · hello@getdocible.com

Terms of Use · Support