Privacy Policy - BuildWithGit

1. Scope

This Privacy Policy applies to the BuildWithGit website, application, support pages, checkout flow, challenge and learning surfaces, and related subdomains and infrastructure we operate, including challenge submission and account services.

2. Information We Collect

Depending on how you use the service, we may collect the following categories of information:

Account information: username, email address, password hash, email verification state, account creation timestamps, and avatar URL.
OAuth login data: if you sign in with Google, GitHub, or Facebook, we may receive your provider user ID, verified email address, access token, and profile photo or avatar made available by that provider.
Profile information you choose to add: optional hobby and social links such as GitHub, Facebook, Instagram, or X from your dashboard profile.
Learning and challenge activity: progress records, completed lessons, quizzes, projects, challenge progress, submission-related identifiers, and metadata needed to provision or map your submission repositories.
Support and communications: messages you send us and records required to send verification emails, password reset emails, or support replies.
Payment and plan metadata: selected plan, market, currency, order ID, payment ID, payment status, and related checkout metadata. Payment card details are processed by Razorpay and are not stored by BuildWithGit.
Technical data: session cookie data, timestamps, IP address, browser type, operating system, referring information, request logs, and security-related metadata generated when you use the service.

3. How We Use Information

To create and manage your account.
To authenticate you and maintain secure sessions.
To deliver lessons, challenges, progress tracking, and repository provisioning.
To process purchases, confirm payment status, and grant paid access.
To send account verification, password reset, transactional, and support emails.
To keep the platform secure, detect abuse, debug failures, and enforce our Terms.
To improve reliability, performance, and product operations.

4. How We Share Information

We do not sell your personal information. We may share data only as needed with:

Infrastructure and database providers that host the application and store account or progress data on our behalf.
Email providers used to send verification, reset, or support emails.
Authentication providers when you choose OAuth sign-in through Google, GitHub, or Facebook.
Payment providers such as Razorpay for checkout, payment verification, and fraud prevention.
Submission and challenge infrastructure when we provision or associate challenge repositories or submission endpoints with your account.
Legal or safety recipients when required to comply with law, enforce our terms, or protect users, the service, or BuildWithGit.

5. Cookies and Similar Technologies

BuildWithGit uses essential cookies and similar storage mechanisms for authentication and security. For example, we use session cookies to keep you signed in, and short-lived state or verifier cookies during OAuth sign-in flows. If you disable these features in your browser, login and other account features may not work correctly.

6. Do Not Track and Cross-Site Tracking

Our site does not currently respond differently to browser “Do Not Track” signals. We do not run third-party advertising networks on the site, and we do not intentionally allow third-party ad technology to track you across unrelated websites through the service.

7. Data Retention

Account and progress data are kept while your account remains active and as needed to operate the service.
Session records may remain active for up to 30 days unless you log out or they are invalidated sooner.
Email verification tokens expire after 24 hours.
Password reset tokens expire after 1 hour.
Payment and transactional records may be kept longer for security, audit, accounting, or legal reasons.

8. Your Choices and Rights

You can update some profile fields directly from your dashboard.
You can log out at any time and may request account deletion or data access by emailing us.
You may choose not to use OAuth sign-in and instead use email/password login where available.
You may control cookies through your browser settings, subject to the limitations described above.

9. Security

We use reasonable technical and organizational measures to protect account and service data, including hashed passwords, signed or validated session flows, payment signature verification, and server-side access controls. No system is perfectly secure, so we cannot guarantee absolute security.

10. Contact

For privacy questions, data requests, or account-related concerns, contact support@buildwithgit.com.