Privacy Policy
This policy explains what ChatKit processes when you use the extension. ChatKit is provided by an individual business under the UUJX Studio brand. Contact: uujx.work@gmail.com.
Where chat content is processed
ChatKit reads ChatGPT or Gemini page content and history returned by the current conversation APIs locally in your browser to generate navigation, support search, selection and copy, and create a download when you choose file export. Conversation data is cached while the page is running. We do not send chat text to ChatKit account, payment, or analytics services.
When you choose Notion export
After you connect Notion, destination searches send the page or database name you enter to Notion and retrieve destination details within the granted permissions. When you actively export, the extension sends selected chat content, document titles, and any source information you choose to include to the Notion API to create pages or database records. A Supabase-hosted Notion OAuth Bridge verifies your identity using your ChatKit sign-in session and processes authorization data for connection, refresh, or revocation; chat text is not forwarded through this Bridge.
Local Notion data and retention
To complete, recover, or retry a Notion export, the extension stores connection state, export-job metadata, and pending requests in browser IndexedDB. Serialized export requests are cleared when an item succeeds, stops, or has an unknown result. Failed or retryable jobs retain the request data needed to retry until they are retried, cancelled, or cleaned up. Terminal job records become eligible for cleanup at least 24 hours after completion; no fixed maximum retention is promised before that cleanup runs.
Settings, sign-in, and authorization storage
The extension uses Chrome storage for settings, the analytics identifier, sign-in sessions, and cached access status. Some settings and the analytics identifier use Chrome sync storage, with a possible localStorage fallback when storage is unavailable. Notion access tokens are stored in browser-session storage; connection records and encrypted refresh credential handles are stored in local IndexedDB. Disconnecting Notion does not delete exported Notion pages and is not the same as deleting a ChatKit account or analytics records.
Runtime logs and retention boundaries
The OAuth Bridge logs request identifiers, operations, a hashed account-identifier summary, upstream status, and error categories, but not chat text or authorization credentials. Ordinary browser development logs are enabled only in development builds; limited redacted diagnostic warnings may appear in production. Retention of account, payment, service-access, and analytics records depends on service settings, fulfillment, and applicable legal requirements. This policy does not promise automatic deletion across all services within a fixed number of days.
Limits on data use
ChatKit uses user data in accordance with the Chrome Web Store User Data Policy, including its Limited Use requirements. Data is used only for the disclosed features and related operations, reliability, and improvement, not for personalized advertising or credit assessment.
Account and payment data
Sign-in and export access use Supabase. Relevant data includes authentication data, account identifier, export-access status, trial end time, and Stripe customer identifier. Stripe processes payments; ChatKit does not store full card numbers in the extension. We use this data to verify the account, trial, and purchased export access.
Product analytics
Production builds send product analytics events to PostHog. Events use a persistent extension identifier, so they are not anonymous. Current events include feature use, platform/page type or origin, export counts and settings, extension version, user agent, installation and first-use information, sign-in or access status, and time; analytics filters exclude chat text, OAuth tokens, passwords, and full page URLs. We use this information to understand feature use, diagnose issues, and improve the product.
Services that receive data
Data is processed for the purposes above by Supabase (authentication, account data, and OAuth Bridge), Stripe (payments), Notion (content you choose to export), and PostHog (product analytics). When Chrome sync is enabled, the extension identifier used for analytics and some settings may also be processed through the browser sync service. Vercel hosts the website and Vercel Blob serves the demo video; these services process ordinary network request data, such as IP addresses, when you visit a page or play the video. We do not sell personal data.
Security, retention, and choices
Network requests use HTTPS. You can choose not to connect Notion and can disconnect it from the extension. To delete an account or request access, correction, or deletion of personal data, email us; transaction or tax records required by applicable law may be retained.
Updates and rights
We update the policy version and effective date on this page. This policy does not limit privacy or consumer rights granted by applicable law.
Contact
For privacy questions or data-rights requests, contact: uujx.work@gmail.com