Last updated: October 17, 2026
This update corrects our AI-provider and retention disclosures and explains first-party product analytics.
When you use KittyLog, we collect:
We use your information to:
KittyLog requests minimal GitHub permissions:
We do not sell your personal information. We may share data with:
The default generation and translation path currently uses OpenAI, with Groq and Anthropic as fallback providers. Availability depends on the model and provider.
Provider rules differ for model training, abuse monitoring, caching, retention and processing locations. For example, OpenAI and Anthropic describe default API retention periods of up to 30 days, with exceptions for legal or safety purposes and applicable agreements. Groq may retain request content for reliability or abuse investigations. Provider settings and the features used can change these periods.
Provider policies and service information:
Contact [email protected] for current details about a provider or model before submitting information with specific handling requirements.
We implement industry-standard security measures to protect your data, including encryption in transit (HTTPS) and at rest. GitHub access tokens are encrypted and stored securely. However, no method of transmission over the internet is 100% secure.
We retain your data for as long as your account is active. Generated changelogs are stored on our servers and remain accessible at your hosted changelog URL. You can delete your account at any time, which will remove your data from our systems within 30 days.
We retain usage and generation metadata, such as model names, token counts, timings and outcomes, to operate the service. Detailed AI debugging logs are restricted to specifically allowlisted operator accounts or repositories. Those logs may contain prompts, code excerpts, model output and reasoning. A scheduled cleanup clears this content once it is older than 24 hours; removal occurs when the cleanup runs. Usage metadata is retained separately. AI providers have their own retention practices, described above.
You have the right to:
For users in the European Economic Area (EEA), you have additional rights under GDPR including the right to data portability and the right to object to processing. Our lawful basis for processing is contract performance (providing the Service) and legitimate interests (improving the Service).
KittyLog uses hosting, delivery and AI services that may process data in the United States and other countries. Processing locations depend on the provider, service and applicable account configuration. Data protection laws may differ from those in your country. Contact us for information about the providers and transfer arrangements relevant to your use of KittyLog.
When you visit a valid referral link, we store an essential, first-touch referral cookie for up to 30 days. If GitHub OAuth creates a new KittyLog account in that browser, we record the referring account, program version, qualification state, and reward history. Referral dashboards show aggregate counts only and do not identify referred people.
Cash-pilot participants may provide their country, age attestation, terms acceptance, and preference for a business check. The referral system does not ask for or store a legal payee name or mailing address. An authorized administrator obtains those details directly from the participant outside KittyLog only when a check is ready. We do not put referred-person information in checks, referral analytics, tickets, or internal payout notes.
Your account export includes your referral attribution, reward ledger, terms acceptance, and payout history. Deleting your account removes the payout preference and anonymizes retained referral records. We may retain only the minimal paid payout records—including amount, status, dates, and payment reference (a check number, or a legacy Venmo transaction reference)—needed for accounting, tax, fraud, and legal obligations. To enforce one-time referral eligibility and the annual cash ceiling after deletion, we retain a keyed, one-way fingerprint of the numeric GitHub account ID; it is not displayed or used to recreate the deleted account profile.
We use essential cookies to maintain your session and authentication state. We do not use tracking cookies or third-party analytics that track you across websites.
We record first-party events such as plan selections, sign-in starts, account creation, repository connections, generations, publications and upgrades to understand use of KittyLog. A random journey identifier and selected plan may be stored in your browser tab and used for attribution during a 30-minute window. Expiry stops their use for attribution but does not delete the stored values; we clear that context after sign-in when browser storage is available. We can link those events to a new account when sign-up completes. These product events contain limited identifiers, counts and statuses, rather than prompts, source code, email addresses or payment details. IP addresses are used for transient rate limiting and are not stored in these product events.
We use Sentry only for error monitoring. We do not enable Sentry performance tracing or Session Replay. Error reports may include technical diagnostics and your internal KittyLog user ID so we can investigate failures. Sentry does not track you across other websites.
We may update this Privacy Policy from time to time. We will notify you of significant changes by email or through the Service.
For questions about this Privacy Policy or to exercise your data rights, please contact us at [email protected].