CoderX Privacy Policy
We believe in total transparency. CoderX is designed with a privacy-first architecture where your code runs locally in your browser using WebContainers. We never sell your personal information, never inject third-party ad trackers, and respect your right to erasure.
Client-Side Execution
Coding challenges run in your browser via StackBlitz WebContainers. Your drafts are never sent to a remote sandbox server.
OAuth Security
We never collect or store your passwords. Authentication is handled exclusively through verified Google and GitHub OAuth.
Self-Service Erasure
You maintain 100% control over your data. Delete your account and all associated submissions anytime with a single click.
01.Information We Collect
When you use CoderX, we collect only the minimum personal data strictly necessary to provide our educational developer services:
- OAuth Profile Data: When you sign in using Google or GitHub, we receive your email address, full name, avatar URL, and provider account ID. We do not receive or store your third-party account passwords.
- Developer Profile & Handle: Your chosen CoderX username (
@handle) and any bio details you choose to publish. - Code Submissions & Solutions: When you explicitly click "Submit Solution", we store your submitted source code, test execution outcomes (passed/failed tests, execution duration), and timestamp to power your progress tracking and public profile.
- Community Interactions: Questions, solutions, or comments you post in problem discussions, along with upvotes and reactions.
- Technical & Telemetry Data: IP addresses and browser user-agent strings are processed strictly for DDoS mitigation, rate limiting, and security compliance via Upstash Redis and Vercel Edge security.
02.How Code Execution Works (Browser Isolation)
Unlike traditional coding platforms that transmit your code to remote Docker containers on server farms, CoderX utilizes StackBlitz WebContainers.
Browser-Side Execution Guarantee:
• Code written in the Monaco Editor executes inside an isolated WebWorker in your local browser tab.
• Intermediate typing, terminal output, and local test runs remain entirely on your device.
• Code is transmitted to our database ONLY when you explicitly trigger a verified submission.
03.Third-Party Sub-Processors
We partner with industry-leading infrastructure providers to host and secure CoderX. All sub-processors adhere to strict data security standards:
| Partner / Provider | Purpose | Data Processed |
|---|---|---|
| Supabase Inc. | PostgreSQL Database & Auth | User profiles, submissions, discussion comments, consent audit log. |
| Google LLC & GitHub Inc. | OAuth Identity Providers | Authentication tokens, verified email, name, avatar. |
| Vercel Inc. | Application Hosting & Edge Network | Serverless execution, CDN caching, security WAF logs. |
| Upstash Inc. | Serverless Redis Cache | Rate limiting counters and temporary IP hash keys. |
| StackBlitz Inc. | WebContainer In-Browser Runtime | Browser client runtime libraries (no user code sent to StackBlitz). |
04.Cookies & Local Storage
We prioritize user privacy. CoderX does not use third-party advertising cookies, marketing pixels, or behavioral cross-site trackers.
1. Strictly Necessary Cookies
Required to authenticate sessions (sb-*-auth-token) and satisfy Cross-Origin Isolation headers (COOP/COEP) required by browsers for WebContainer threading.
2. Functional Local Storage
Stored directly on your device: your active theme preference (dark/light), challenge pagination limit, and custom smart-list filter tabs.
05.Your Rights (GDPR & CCPA Compliance)
Regardless of where you reside, CoderX respects your global data protection rights:
- Right to Access: You can view all your stored submissions and profile data directly in your CoderX profile dashboard.
- Right to Rectification: You can update your developer handle and profile details at any time.
- Right to Erasure (Right to Be Forgotten): We provide automated, self-service account deletion under your user menu. Triggering deletion permanently purges your profile, code submissions, progress, and authentication identity from our database.
- Proof of Consent: Your acceptance of our policies is recorded with a timestamp and policy version in our database (
user_consents) to fulfill GDPR Article 7(1) compliance.
06.Data Security Standards
All traffic between your browser and CoderX is encrypted using Transport Layer Security (TLS 1.3). Database records are guarded by PostgreSQL Row Level Security (RLS) policies, ensuring users can only read and write their own authorized data records.
07.Contact Us
If you have any questions, concerns, or requests regarding this Privacy Policy or your personal data, please reach out directly: