Privacy
early access · last updated October 16, 2026
This page explains what Taybit collects, why, and how long we keep it. Taybit LLC, a Wyoming, United States company, operates Taybit and is responsible for the personal information described here. Contact team@taybit.com for privacy requests.
What we collect
- Your GitHub account identifier, username, display name, avatar, and verified email when you authorize access. We also collect the first and last name you confirm and a phone number if you provide one.
- GitHub access tokens for your account, stored encrypted.
- Feedback you send, its page category, and a reply email if you provide one.
- The pull requests you submit and a private snapshot of the changed and surrounding files used to build your walkthrough.
- When you enable automatic PR walkthroughs for a selected GitHub installation, existing open PRs and subsequent PR events may be processed using the funding account's credits. GitHub can retain the walkthrough link posted on a PR after a board is deleted.
- The questions you ask, the answers, generated illustrations, saved source links, your walkthrough progress, and notes you draw on the board.
- Usage and cost records needed to enforce limits, and operational logs without source code.
- The version and time of Terms acceptance submitted through account onboarding or settings.
- Stripe customer, subscription, invoice, and billing-event identifiers; subscription status, paid-period dates, cancellation state, and refund or dispute status needed to manage paid access.
- First-party visit measurements: an opaque per-tab session identifier, page categories, selected button and form actions, active time, broad screen-size category, referring-site category, and supported loading and layout measurements. Browser error counts contain no error messages or stacks.
Voice questions are sent for transcription when you hold the microphone. We keep the text of the question, not the recording.
How we use it
To provide walkthroughs and answers to you, manage subscriptions, enforce limits, keep the service secure, and understand which parts of Taybit people use so we can improve them. We don't sell your data. Taybit does not use your content to train its own models.
Visit measurements
These measurements go directly to Taybit, without a third-party analytics service. We do not collect form values, question text, source code, repository names, walkthrough identifiers, or full URLs in visit events. We accept only the named campaign parameters utm_source, utm_medium, and utm_campaign. Sources and media use known categories, and only configured short campaign labels are retained. Other query parameters and referring-page paths are discarded.
Active time counts only while the page is visible and stops after 30 seconds without a click, key press, scroll, or navigation. A per-tab identifier is stored in your browser's session storage and rotates after 30 minutes without activity. If you sign in, we associate the visit with your Taybit account. We respect Global Privacy Control and Do Not Track by disabling browser visit measurements. Essential account, preparation, question, and cost records still support the service.
Who processes it
GitHub (identity and repository access), OpenAI (analysis, answers, optional web research and illustration generation, and transcription), ElevenLabs (narration text and audio), Stripe (payments and subscription management), Resend (feedback email delivery), and Railway (application hosting, database, and private file storage). These services may process data in the United States and other countries where they operate.
We set store: false on OpenAI Responses API requests. This disables response storage for that feature; it does not eliminate provider abuse-monitoring logs or every form of provider retention. OpenAI says API data is not used for model training unless the customer opts in. Its optional model-improvement sharing is separate from response storage and must be disabled for confidential customer data. See OpenAI's data controls.
For abuse monitoring, some OpenAI requests include a pseudonymous identifier derived from your internal Taybit account ID. That identifier contains no GitHub username, email address, or contact details.
On October 16, 2026, we disabled ElevenLabs' model-improvement data sharing for our workspace. ElevenLabs says this choice excludes new submissions from model training; it does not erase earlier submissions. See ElevenLabs' training controls.
ElevenLabs may keep generated narration in its request history under the account's settings. Taybit currently does not automatically delete that provider history when you delete a board. Provider history, security logs, and backups follow the provider's retention rules. Contact us for a provider deletion request; we will explain any limits that apply. See ElevenLabs' privacy policy.
If you enable web research, Taybit sends the public-topic query shown in the board controls to OpenAI's web search tool. Do not put private information in that query. Generated illustrations stay private to your learning board and are removed when you delete it.
Stripe collects the payment and billing information you enter in its hosted Checkout and customer portal. Taybit does not store your full payment-card number or security code. Our billing records link Stripe's payment and subscription status to your Taybit account. Your repository source, questions, and answers are not sent to Stripe by our billing integration.
We send your confirmed name, GitHub-verified email, and phone number if provided to Stripe to keep your customer and billing details up to date. Adding a phone number does not verify that number or subscribe you to messages.
Feedback is emailed to team@taybit.com. The form sends your message and optional reply address, without automatically attaching board contents or URL query parameters. Contact us at that address to request deletion of feedback you sent.
Retention and deletion
Unsubmitted drawings and board names can be saved in your browser's local storage so you can return to them. A question kept through sign-in is stored in that browser tab's session storage for up to 30 minutes and removed after it is restored to your signed-in workspace. URLs carry a random reference instead of that question or board name. Clearing Taybit's site data in your browser removes local drafts; a server-side account deletion cannot erase copies on your devices.
- Source snapshots used to prepare a walkthrough are deleted automatically 30 days after preparation.
- PR walkthroughs, learning boards, questions, answers, generated images/audio, and your progress stay until you delete the associated board or request account deletion.
- Visit measurements older than 90 days are removed during routine cleanup.
- Deleting a walkthrough does not remove subscription, billing, or allowance records used to manage payments, prevent duplicate credits, and resolve refunds or disputes.
- You can delete any walkthrough from your dashboard at any time.
- Deletion removes access immediately. If storage is temporarily unavailable, we keep a deletion request and retry until the stored files are removed.
- Feedback remains in our support inbox until the request is resolved and no longer needed for support, security, or legal purposes. Request its deletion by email.
- Account, payment, allowance, and security records may be retained where needed to manage existing payments, prevent duplicate grants or fraud, resolve disputes, or meet legal obligations. We review these records when handling a deletion request rather than promising the same deletion date for every category.
- Deleted data can remain in backups until those backups expire. We do not promise immediate erasure from every backup or provider system. We restrict its use to recovery, security, and legal obligations.
Your choices and requests
Open Account to correct your name, remove an optional phone number, or find billing and GitHub access controls. Your verified email comes from GitHub; change it there and sign in again. You can delete individual boards in My boards.
For access to or a copy of your data, account deletion, correction you cannot make yourself, or a privacy question, email team@taybit.com from your verified address with your GitHub username. We verify ownership before disclosing or deleting data and explain any records we must retain. If you have lost access to that email or GitHub account, contact us so we can arrange another proportionate verification method. Do not send secrets or identity documents unless we request a necessary, secure verification step.
Account deletion requests are handled by support. Revoking GitHub access or deleting a board does not cancel a paid subscription; use Manage subscription in Billing or contact us for cancellation help. Privacy rights and response deadlines depend on where you live. You may also complain to your local privacy regulator where applicable.
Adults and changes to this notice
Taybit is for people 18 and older. We do not knowingly provide accounts to children. Contact us if you believe a child has provided personal information so we can investigate and remove it as appropriate.
We update the date on this page when this notice changes. We will provide notice in the service or by email before a material change to how we use your information takes effect.
Access
Walkthroughs are shared with signed-in GitHub users who currently have access to the repository and whose repository is selected for the Taybit App. Questions, answer drawings, answer audio, and saved progress stay private to the reviewer who created them. Before showing source, Taybit rechecks with GitHub that you still have access to the repository.