Privacy policy

What it reads

Everything the extension reads is public Codeforces data that you could open in a browser tab yourself.

• The handle shown in the Codeforces page header, to know whose profile to look at. Viewing someone else's profile does not change this.
• The public organization link on that profile, in automatic mode.
• Every page of that organization's public rating list, to build the member roster.
• The contest's public standings and published rating changes, from the Codeforces API.

It does not read your password, your API key, your submissions, your friend list, or your browsing history. It has no access to any site other than codeforces.com.

What it stores, and where

All of it lives in Chrome's local extension storage on your own machine, and persists across browser restarts:

• Your chosen organization and any extra handles you entered.
• The detected link between your signed-in handle and its organization, rechecked about every hour.
• The cached public member roster — handles, ratings, country flag and the time it was fetched — rechecked about every 24 hours.
• Filtered contest results, so a view you have already opened appears instantly next time. This cache is bounded to 40 views and roughly 3 MiB, evicting the oldest first.

Full contest responses are held in memory for about a minute and never written to storage. Nothing is synced to an account, and nothing is sent to me.

What leaves your browser

Requests go directly to codeforces.com and nowhere else. There is no server of mine anywhere in the path, so there is no point at which I could collect anything even if I wanted to.

Codeforces therefore receives what any web request gives it: your IP address, normal request headers, and which organization or contest was asked for. Requests to the Codeforces API are made anonymously, with cookies deliberately omitted. Requests for organization and profile pages are made with your browser's existing Codeforces cookies, because that is how those pages render while you are signed in — the extension never reads or stores the cookie values themselves.

Codeforces handles anything it receives under its own privacy policy, which is outside my control.

What it never does

• No advertising, analytics, telemetry or tracking of any kind.
• No selling, renting or sharing of data — there is none collected to sell.
• No developer-operated server, database or log.
• No third-party service receives anything from the extension.
• No remote code: every line of JavaScript ships inside the package, and network responses are treated as data, never executed.

Your control over it

• Change the organization, switch between automatic and manual, or edit extra handles at any time from the extension's settings.
• Refresh members discards the saved roster and reads it again.
• Removing the extension deletes everything it stored. There is no separate deletion request to make, because there is no copy anywhere else.

Changes to this policy

If the extension ever starts handling data differently, this page changes with it and the version and date at the top move forward. The same policy ships inside the extension and is linked from its settings page, so the two stay in step.

Contact

Questions about this policy, or about the extension, go to support@asilkhalifa.com.