Privacy Policy

This Privacy Policy explains how ProzzleLabs collects, uses, shares, and protects information when you use the website, daily prozzles, AI-assisted coding workspace, profiles, leaderboards, subscriptions, and related services.

ProzzleLabs is a coding competition product. That means some activity, such as display names, ranks, solved counts, plan badges, and token-efficient passing submissions, may be used to operate public competition features.

We collect information you provide directly, information created when you use the Service, and information received from service providers that help us run ProzzleLabs.

• Account information: GitHub/Supabase Auth identifiers, username or display name, avatar URL, email address if provided by the auth provider, authentication session data, internal user id, discriminator, plan, and admin status.
• Profile information: display name, public tag, linked GitHub username, plan badge, and profile or leaderboard statistics.
• Session information: selected prozzle, problem language, prompts, chat messages, AI responses, tool calls, code buffer, model selection, token counts, router traces, edits, timestamps, and session status.
• Submission information: submitted code, hidden test results, pass/fail status, runtime errors, final token counts, ranks, and locked session metadata.
• Billing information: Stripe customer id, subscription id, price id, plan, subscription status, current period end, checkout and billing portal events, and limited payment metadata. Full payment card details are handled by Stripe and are not stored by ProzzleLabs.
• Usage and technical information: request metadata, logs, error reports, device or browser information, IP-derived security signals, cookie data, local storage preferences, and similar diagnostic information.
• Communications: messages you send through support channels, GitHub issues, or other contact methods.

We use information to provide, maintain, protect, and improve ProzzleLabs.

• Authenticate users, create accounts, keep sessions active, and secure access to private routes.
• Run AI chat and editing sessions, build model prompts, apply edits, track token usage, and enforce plan limits.
• Execute submissions against hidden tests, calculate pass/fail status, lock successful sessions, and compute leaderboard ranks.
• Display public profiles, leaderboards, plan badges, solved counts, rankings, and other competition statistics.
• Process subscriptions, route users to Stripe checkout or the billing portal, sync plan status, and respond to billing events.
• Detect abuse, investigate security issues, prevent cheating, enforce Terms of Service, and protect infrastructure.
• Debug errors, monitor performance, analyze product usage, prioritize improvements, and provide support.
• Comply with legal obligations and enforce our agreements.

When you use the AI workspace, ProzzleLabs may send your prompt, chat history, problem statement, current code buffer, tool-call context, model selection, and related session data to model providers such as OpenAI or Google so they can generate responses.

When you submit code, ProzzleLabs sends the code and hidden test harness data to grading infrastructure so the submission can be executed and evaluated. Do not include secrets, production credentials, private customer data, or confidential code in prompts, files, or submissions.

Model providers, grading infrastructure, and other processors handle data under their own terms, privacy policies, and data processing commitments. Where product settings allow you to bring your own API key, the model provider may associate usage with your provider account.

We do not sell your personal information. We share information only as needed to operate ProzzleLabs, comply with law, protect users, or support features you choose to use.

• Supabase provides authentication, database, server-side session handling, and related infrastructure.
• Stripe processes checkout, subscriptions, customer records, billing portal sessions, payment status, tax and payment-related metadata, and webhooks.
• OpenAI and Google may process AI session context when their models are selected or used by routing logic.
• Code execution or grading infrastructure processes submissions and hidden tests to evaluate correctness.
• Hosting, observability, analytics, security, or infrastructure providers may process technical logs and operational data.
• Public features may show leaderboard and profile data such as display name, rank, token count, solved count, plan badge, and average placement.
• We may disclose information if required by law, to enforce our Terms, to prevent fraud or abuse, to protect rights and safety, or as part of a merger, acquisition, financing, or sale of assets.

ProzzleLabs is built around public competition. If you complete or submit sessions, some information may become visible to other users or visitors.

Public data may include your display name, profile tag, plan badge, rank, final token count, problems solved, average placement, and other competition statistics. We may hide, blur, aggregate, or remove public data where needed for privacy, fairness, abuse prevention, or product changes.

ProzzleLabs uses cookies and similar technologies to keep you signed in, protect sessions, remember preferences, support security, and operate the website. The app may also use local storage for preferences such as theme.

GitHub, Supabase, Stripe, model providers, hosting providers, and other third-party services may use cookies or similar technologies according to their own policies when you interact with their services.

We keep information for as long as reasonably needed to provide the Service, maintain competition history, comply with legal and billing obligations, resolve disputes, enforce agreements, secure the platform, and improve ProzzleLabs.

Session records, messages, code buffers, submissions, test results, token counts, and leaderboard data may be retained to preserve competition integrity and product history. Billing records may be retained as required by Stripe, tax rules, accounting obligations, and fraud prevention needs.

You can update your display name in account settings. You can manage or cancel paid subscriptions through the billing portal when available. You can stop using ProzzleLabs at any time.

Depending on where you live, you may have rights to request access, correction, deletion, portability, restriction, or objection related to personal information. We may need to verify your identity before fulfilling a request, and some information may be retained where required for legal, security, billing, or competition integrity reasons.

We use technical and organizational measures designed to protect information, including authenticated access controls, server-side service keys, provider-managed authentication, and limited access to operational systems.

No online service is perfectly secure. You are responsible for protecting your GitHub account, API keys, and devices, and for avoiding secrets in prompts, code buffers, or submissions.

ProzzleLabs is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child under 13 has provided personal information, please contact us so we can take appropriate action.

ProzzleLabs and its service providers may process information in the United States and other countries. These locations may have privacy laws that differ from those where you live.

We may update this Privacy Policy from time to time. If changes are material, we will take reasonable steps to notify users, such as updating this page, changing the date above, or providing in-product notice.

Questions or privacy requests can be raised through the ProzzleLabs GitHub repository linked below.