Privacy Policy
Last updated: November 9, 2026
This notice explains how CP Visualizer handles information when you browse problems, use the playground, or request AI assistance.
Optional analytics and your choice
We use Google Analytics for Firebase only after you choose Allow analytics. Choose No thanks to use the site without optional analytics. Neither choice restricts the visualizers. You can change or withdraw consent at any time through Settings → Analytics preferences or open analytics preferences.
With consent, Google receives page views, selected problem identifiers, visualization starts and completions, playground run language, panel visibility changes, successful sign-ins (method only), and generic application failure categories. If checkout is enabled, we also record checkout starts and server-verified purchases: plan, currency, amount, and payment transaction identifier. Payment analytics helps measure revenue; it is separate from the payment records necessary to fulfil your purchase.
Google also processes browser/device information, session and engagement signals, referring site, approximate location derived from network information, and a pseudonymous browser identifier to report active users, acquisition, engagement, and return visits. This information is not anonymous. We do not attach your account name, email, or Firebase account ID to analytics. Our custom events do not send source code, chat messages, test inputs, search text, raw error messages, or URL query strings. We do not enable Google Signals or advertising personalization.
Analytics uses first-party _ga and _ga_* cookies. We request a lifetime of 180 days; visits may refresh their expiry and browser policies may shorten it. Your choice is stored in cpviz.analytics-consent.v1 in local storage for 180 days, after which we ask again. If browser storage is blocked, the choice may only last in the current tab.
Withdrawal stops future analytics collection and removes accessible Google Analytics cookies for this site. It does not erase information already received by Google. Analytics retention is governed by the site's Google Analytics property settings and Google's processing policies; cookie expiry does not determine deletion of aggregated reports. Google may process data outside your country. See Google's privacy policy and Google Analytics retention information.
We use one analytics provider; Vercel Web Analytics is not loaded by the app. Hosting and operational logs described below remain separate from optional analytics.
Essential preferences
The analytics choice itself is saved to respect your decision. When you choose "Don't show this again" in the Visualizer Pro panel, a first-party cookie named cpviz_plans_hidden remembers that preference for one year. Clearing site data removes these choices. Authentication and locally saved learning work operate independently of analytics consent.
Accounts, usage, and Pro payments
Free beta: Pro problem visualizers are free after Google sign-in. Free problem visualizers and the playground remain available without sign-in. No payment is required. The app uses Firebase Authentication’s sign-in state in the browser to unlock beta Pro problems. The current beta app skips account-status, trial, playground-access and checkout Cloud Function calls. The paid-access practices below describe the retained account/payment system; existing records are not deleted by free beta.
If you choose Google sign-in, Firebase Authentication processes your Google account identity, including your account identifier, name, email, and profile image. The app displays your name and email and stores your sign-in session in this browser. Free problem visualizers and the tutorial do not require an account.
When account access is enabled, our backend stores your account identifier, Pro expiry, and trial eligibility. The app caches your account access status in browser local storage for up to six hours to avoid repeated server calls. Pro and active trials include full playground access without daily usage metering or single-device restrictions. Signing out clears the current account’s access cache. Historical usage records from the previous metering system may remain on the backend; no new usage reservations are created by this version. Clearing browser data does not delete an account.
Razorpay processes Pro payments. We store order and payment identifiers, plan, amount, payment status, and access dates to provide and reconcile Pro access. Payment credentials are entered in Razorpay checkout; they are not stored by this app. Signing out does not delete billing records or cancel an already purchased access period.
Browser storage
The app uses local storage to remember preferences, AI provider settings, chat history, and playground code and inputs. This data remains in your browser until you delete it or clear this site's data. API keys entered in the playground's provider controls are stored in session storage, which normally lasts for the browser tab's session.
You can remove saved data using your browser's site-data settings. This also resets preferences and removes locally saved work. Close other open tabs of this site first so they do not save their current state again. These storage features support the app; they are not advertising cookies.
Optional AI features
When you request AI assistance, your messages and relevant context, which may include conversation history, problem details, visualization state, source code, inputs, or errors, are sent to the selected provider. Hosted Ollama and Google Gemini requests pass through the site's API. A key you supply for that request also passes through the API to authenticate with the provider. Local Ollama requests go directly to the configured Ollama server.
Provider processing and retention depend on the provider and account settings. See Ollama's privacy policy and Google's privacy policy. Avoid including sensitive personal information or secrets in prompts or code submitted for AI assistance. Clearing browser history does not delete information already sent to a provider.
Hosting and external resources
Hosting and API infrastructure process network requests to deliver and protect the service. Those requests include technical information such as IP addresses and request metadata and may appear in operational logs. Some editor and Python runtime resources are loaded from external content delivery networks, which also receive the network information needed to serve them. Their retention practices are separate from locally saved app data.
Your choices and questions
You can use the visualizers without requesting AI assistance and clear locally saved data through your browser. Browser privacy tools may also block analytics requests.
For privacy questions or requests, contact the maintainer through the project's GitHub repository. Do not include private information in a public issue. Depending on your location and the information involved, you may have rights to access, correct, or delete personal information or object to its processing.
We will update this page when the site's data practices change.