Training Lab · BetaAdaptive practice, explained
Training Lab · Privacy

Your practice data,
explained plainly.

Training Lab uses your account, linked Codeforces activity, practice preferences, and activity in the service to provide practice plans, save progress, maintain security, and improve the service.

Data lifecycle

What is kept and who handles it

Data used

Only what supports the service.

This includes account and consent records, your linked public Codeforces profile and activity, preferences, saved plans, reported outcomes, and security or support records.

Retention

Records are kept only as needed.

Short-lived verification and browser-session data expires automatically. Account and practice records remain while needed to provide the service or meet security, backup, and legal obligations, unless you use the applicable deletion control.

Service providers

Other services help operate Training Lab.

Google provides sign-in and Codeforces provides public activity. Hosting, database, logging, security, backup, and network providers process data to operate the service under their own applicable terms.

Choices and limits

Controls do different jobs

Export, unlink, and delete are different

Export gives you a copy. Unlink disconnects your Codeforces handle but does not delete server records. “Delete Training Lab data” removes account-linked Training Lab records while leaving your sign-in account available.

You can close the full account

Full account deletion removes this service’s account, sessions, provider link, and applicable Training Lab data. It does not delete your Google or Codeforces accounts.

Some retention limits apply

Backups expire on normal schedules. De-identified information and records required for security, fraud prevention, legal compliance, or dispute resolution may be retained where permitted.

Consent stays current

We record the privacy and terms version you accept. Material changes may require you to review and accept updated terms before continuing.