1Overview
WinQA (“we,” “our,” or “the platform”) is an AI testing playground for developers and QA professionals. This Privacy Policy explains how we collect, use, store, and protect your information when you use our platform at winqa.ai.
2Information We Collect
Account Information
We use Clerk for authentication. When you sign up, Clerk collects your email address and authentication credentials. We do not store passwords directly — Clerk handles all authentication securely.
API Keys
If you save API keys for AI providers (Cohere, Google Gemini, Groq, Mistral, or a custom provider): Keys you save are stored in our database encrypted with AES-256-GCM under a key held only in our server environment. They are decrypted only on our servers, at the moment a request goes to that provider. They are never sent back to your browser; Settings shows only the last four characters. Removing a key, or deleting your account, deletes it. If a built-in provider rejects your key as unauthorized, WinQA may retry the request once with its shared key; custom providers are not retried. Keys saved in this browser before October 2026 stay there, obfuscated, and are sent to our server over HTTPS with each request that needs them until you move them from Settings; browser storage is deprecated and will be removed in a later release.
User-Generated Content
Content you create on the platform — prompts, test cases, bug reports, insights, and battle results (including the code models write in Code Duel) — is stored in our MongoDB database and associated with your user account. Code you run in Code Testing is sent to the code runners and not stored.
Usage Analytics
We use Vercel Analytics to collect anonymous, aggregated usage data such as page views and performance metrics. This data does not personally identify you.
3How We Use Your Information
- •To provide and maintain the WinQA platform and its features
- •To authenticate your identity and secure your account
- •To make API calls to AI providers using the keys you save
- •To store and display your testing data (prompts, bugs, test cases, insights)
- •To improve platform performance and user experience
4Data Storage & Security
Your data is stored in MongoDB and secured with the following measures:
- •Keys you save are stored in our database encrypted with AES-256-GCM under a key held only in our server environment. They are decrypted only on our servers, at the moment a request goes to that provider. They are never sent back to your browser; Settings shows only the last four characters.
- •All connections use HTTPS/TLS encryption in transit
- •Authentication is handled by Clerk with industry-standard security practices
- •Access to data is restricted to authenticated users viewing their own content
5Data Sharing
We do not sell your data.
We do not sell, rent, or trade your personal information or content to third parties. Your data is shared only with the following service providers, each for the purpose and with the data listed:
- •Clerk — Account and authentication: your email address and sign-in credentials, and the account ID we use to key your content.
- •Cloudflare Turnstile — Bot check during sign-up (loaded by Clerk): browser signals from your device.
- •MongoDB Atlas — Database hosting: everything you create and store on WinQA (prompts, bug reports, test cases, insights, battles, usage counters).
- •Vercel — Hosting and request logs. Analytics is described under Usage Analytics above.
- •Cohere, Google Gemini API, Groq, Mistral — AI providers: your prompts and conversation, plus your own API key for that provider if you saved one.
- •Judge0 CE (ce.judge0.com) — Code execution: the code you run and its standard input.
- •Piston public API (emkc.org) — Code execution fallback when Judge0 CE fails: the code you run and its standard input.
- •Judge0 via RapidAPI (judge0-ce.p.rapidapi.com) — Code execution fallback, used when configured: the code you run and its standard input.
- •Custom providers you configure — They receive what you send to them, including your key for that provider, under your own account with that provider. Check their privacy policy.
- •CodeSandbox and CodePen — Only when you click Open in CodeSandbox or Open in CodePen: the code shown, sent from your browser.
6Cookies
WinQA uses essential cookies for authentication (managed by Clerk) and session management. We use Vercel Analytics which may set anonymous performance cookies. We do not use advertising or tracking cookies.
7Your Rights
You have the right to:
- •Access or update your account details through Manage account in your profile menu.
- •Delete your account. Deleting your account deletes your content, battles, usage counters and saved keys from our database within minutes. Public library items you contributed stay, re-attributed to WinQA. To delete, use Manage account in your profile menu, or email privacy@winqa.ai.
- •Remove saved API keys at any time in Settings.
- •Delete any content you have created (prompts, bugs, test cases, insights)
- •Export your bug reports, prompts, test cases and insights from Settings. Other data, such as battles and usage counters, is not part of that export; email privacy@winqa.ai to request it.
8Changes to This Policy
We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated “Last updated” date. Your continued use of WinQA after changes constitutes acceptance of the updated policy.
9Contact
For questions about this Privacy Policy, to request deletion or access to your data, or for bugs and feature requests, email privacy@winqa.ai.