Privacy and trust

Privacy Policy

This notice describes the personal data the current Connect2Code website and API flows use, why it is used, and which controls are available.

Last reviewed 17 November 2026

Scope and operator details

This notice applies to the Connect2Code placement-preparation website, its account features, coding workspace, learning tools, and administration interface.

The repository does not identify the legal entity operating the service, its registered address, or a verified privacy or grievance contact. Those details must be approved and published by the service owner before production launch. Until then, do not send personal data to an address that is not published on the official Connect2Code website.

Owner action required: add the operator’s legal name, address, verified privacy contact, grievance contact, and—if applicable—data protection officer or EU representative.

Data used by current features

  • Account and authentication data: email address, name, password submitted to the API, account identifier, role, and authentication state.
  • Optional profile and academic data: registration number, joining and passing years, college name and identifier, biography, gender reference, and date of birth when supplied.
  • Learning and assessment activity: bookmarks, attempted and solved problem identifiers, code, selected language, custom input, submissions, answers, and results.
  • Preferences and device-local data: theme preference, per-account progress cache, code drafts, sign-in return path, and short-lived cross-tab session events.
  • Google sign-in data: identity information returned through the backend’s Google OAuth flow. The exact Google scopes and provider configuration require backend-owner confirmation.
  • Technical and operational data may be recorded by the API or hosting providers, such as IP address, request metadata, diagnostics, and security logs. This frontend repository cannot verify those server-side records.

Why the data is used

  • Create and authenticate accounts, restore sessions, secure protected requests, and support password recovery.
  • Provide coding practice, code execution, submissions, bookmarks, progress, learning sheets, aptitude practice, and profile features.
  • Keep account-specific preferences and drafts separated on the same browser.
  • Operate and protect the service, diagnose failures, enforce roles, and prevent misuse where the backend provides those controls.
  • Meet legal obligations and respond to valid rights or security requests where applicable.

Cookies and browser storage

The access token and signed-in identity are held in page memory rather than local storage. The backend is designed to use an HttpOnly refresh cookie for session restoration. The frontend cannot read that cookie.

Local storage is used for account-scoped theme preferences, progress cache, and code drafts. Session storage is used for a post-sign-in return path and a one-time logout notice. No analytics, advertising, tag-manager, or tracking SDK is present in the reviewed frontend source.

Services and recipients

  • The Connect2Code Spring Boot API receives account, profile, learning, and code-execution requests.
  • Google is involved only when a user chooses Google sign-in; the backend owns the provider exchange.
  • The static hosting provider serves the website. Google Fonts and cdnjs currently receive browser requests for fonts and icon styles when a page loads.
  • The backend mediates code execution through Judge0; the browser does not contact Judge0 directly.
  • Some company or problem links and images may load from the external destination selected by the user or supplied by the API.

Owner action required: confirm all processors, hosting regions, contracts, international transfers, server logs, analytics, and subprocessors before legal approval.

Retention and deletion

Browser-held drafts, progress cache, and preferences remain until cleared by the user, removed by the application, or erased by browser controls. Logout clears the departing account’s local cache except its theme preference.

The backend’s retention periods for accounts, profiles, submissions, security logs, backups, and deleted records are not defined in this frontend repository. Connect2Code must not promise a deletion deadline until the backend owner has documented and tested it.

Your privacy rights

Depending on applicable law and your location, you may have rights to information, access, correction, erasure, restriction or objection, portability, consent withdrawal, grievance redressal, or nomination. Some rights are subject to legal exceptions.

The current API has profile editing but no verified account deletion, complete data export, or privacy-request endpoint. See Data & Account Rights for the currently available device controls and the backend work still required.

Children and age assurance

Connect2Code is described as a placement-preparation service for college students and job seekers. The current product has no verified age-assurance or parental-consent flow. The owner must decide the permitted age range and implement any required child-data controls before knowingly serving children.

Security and changes

The frontend uses HTTPS production endpoints, memory-only access tokens, account-scoped browser storage, credential stripping, and route-level role presentation. Client-side guards are not a substitute for backend authorization.

This notice should be updated when data practices, providers, purposes, or legal obligations change. Material changes should be communicated through an appropriate in-product or account channel once one is configured.