Account controls

Data & Account Rights

Review what you can change now, clear this browser’s account-scoped data, and understand which account rights still need backend support.

Last reviewed 17 November 2026

Clear this account’s data from this browser

Removes Connect2Code drafts, cached progress, and theme preference for the active account on this device. It does not delete your account, bookmarks, submissions, profile, or other server records.

Sign in to target an account-specific browser scope. Guest browser storage can be removed through your browser’s site-data controls.

Controls available now

  • Profile: authenticated users can review and update the profile and academic fields supported by the current API.
  • Bookmarks: authenticated users can add and remove saved problems.
  • Theme: users can change the current appearance preference.
  • Local data: the control below can remove the active account’s Connect2Code drafts, progress cache, and theme preference from this browser. It does not delete server records.
  • Logout: clears the in-memory session and the account’s local cache except the theme preference, then asks the backend to end the refresh session.

Server-side rights and requests

The current frontend/API contract has no verified endpoint for deleting an account, exporting a complete copy, restricting processing, recording an objection, withdrawing optional consent, or tracking a privacy request.

Those requests require a verified contact channel and backend workflow that authenticates the requester, finds primary and derived records, handles legal exceptions, propagates deletion or correction, and records completion without exposing another user’s data.

Backend dependency: implement authenticated account deletion and export/request workflows, retention rules, backup handling, and auditable completion before claiming these rights are self-service.

Request safety

  • Use only the verified contact published on the official website once configured.
  • Expect identity verification proportionate to the request; never send a password, OTP, cookie, or access token.
  • A response period cannot be promised until the owner confirms the applicable laws, process, and service level.
  • If a request is denied or limited, the final process should explain the reason and available grievance or appeal path where required.