Your Data is Yours
AetherCP was built on a simple premise: a developer companion should have access to your data, but its creators shouldn't.
No Tracking
We collect no analytics, send no telemetry, and use no third-party trackers.
No Backend
There is no database, cloud API, or sign-up backend. Data storage is 100% offline.
No Selling
We cannot sell your search or coding habits because we do not have them.
1. Data Storage and Control
Every record generated during your coding sessions — including problem names, contest IDs, duration metrics, streak lists, and weekly heatmaps — is stored in your Chrome sandbox using the chrome.storage.local API.
This storage is local to your machine and web browser. Uninstalling AetherCP instantly deletes all data stored by the extension. We have no way to recover or back up your data since we do not host a central cloud service.
2. Transparent Permissions
To provide automatic problem tracking and editor integrations, AetherCP requests specific browser permissions. Below is the full description of why each is required:
3. Web Request Safety
AetherCP makes only two types of network requests: (1) read-only API calls to codeforces.com/api to fetch public submission history for profile analytics, and (2) local loopback requests to localhost:27121 when sending a problem to the VS Code CPH extension. No other external network requests are ever made.
4. Fully Auditable & Open Source
Because AetherCP is fully open-source under the MIT license, you do not have to take our word for any of the statements in this policy. You can inspect the source code, check the manifest files, review network requests inside Chrome DevTools, or compile the extension manually from source.
5. Changes to This Policy
Since AetherCP has no servers and does not collect any database entries, we will never change this extension to collect user metrics silently. If sync functions are added in future versions, they will be strictly opt-in and end-to-end encrypted locally before sync.