Privacy policy

What the extension sends to codex-resets.com

Codex Resets (codex-resets.com) is an independent site, not run by this extension's developer, that tracks Codex usage limit resets and sends the alerts. The extension contacts it in these cases:

• When you turn alerts on. Chrome creates a push subscription for the extension, and the extension sends it to codex-resets.com: the endpoint (a unique address for this subscription at your browser's push service), the two keys that let Codex Resets encrypt each alert for this browser (the p256dh public key and the auth secret), and the subscription's expiration time, if it has one. While alerts stay on, the extension registers a new subscription the same way when Chrome replaces the old one, and when its missed-alert check finds a reset that push did not deliver. When it registers again, it first asks codex-resets.com to remove the previous subscription if this browser still has it.
• When you turn alerts off. The extension removes the subscription from Chrome and sends its endpoint to codex-resets.com, asking the site to remove its record.
• When it reads public reset data. When you open the popup, or press Retry in it, the extension reads the public status and the five most recent resets from the Codex Resets public API. While alerts are on, it also reads the public status about 5 minutes after Chrome starts and every 3 hours, to notice a reset whose alert did not arrive (the missed-alert check). These reads carry no personal data. The missed-alert check sends back the version tag (ETag) that the site attached to its previous answer, so unchanged data is not downloaded again.

The extension never sends your name, email address, details of your OpenAI or Google account, browsing history, or the content of web pages. It cannot read them: it has no access to web pages and asks for access to no site other than codex-resets.com.

How alerts reach your browser

Codex Resets sends each alert to the push endpoint, and your browser's push service delivers it. For Chrome, the push service is Firebase Cloud Messaging, operated by Google. Chrome, not the extension, keeps the connection to that service. The alerts are encrypted with the keys described above, so the push service cannot read their content. The extension then shows each alert as a notification.

Your IP address

As with any web request, the requests to codex-resets.com reveal your IP address and standard browser information, such as the user agent, to codex-resets.com and its hosting provider. The push service also sees the IP address of the connection that Chrome keeps with it. The extension itself does not read or store your IP address. Codex Resets describes its own handling in its privacy notice, and Google describes its handling in the Google Privacy Policy.

What stays on your device

The extension keeps its state in Chrome's local extension storage (chrome.storage.local). It does not use sync storage, so none of it is copied to your Google account. It stores:

• whether alerts are on, and when they were turned on;
• the push endpoint, while alerts are on;
• the last alert received (its time, kind, title and link), and the time and link of the last confirmed reset alert;
• the result of the last missed-alert check, the last error, and the ID of the last missed reset it reported;
• a copy of the last public status with its ETag and, after the site asks the extension to slow down, the time when it may ask again.

Chrome itself keeps the push subscription, with its keys, while alerts are on. Removing the extension deletes the extension's stored data from your device.

Turning alerts off, and deletion

Turning alerts off does three things: it removes the push subscription from Chrome, so alerts sent to that address no longer reach you; it asks codex-resets.com to remove its record of the subscription; and it clears the endpoint that the extension stored. If the request to codex-resets.com fails, alerts are still off and the popup tells you that the request failed.

The extension can only ask. Codex Resets is a separate service, and the extension cannot confirm or guarantee that it deletes the record, or what it keeps in its logs. Its privacy notice says that turning browser notifications off requests removal of its server record, and lists its contact for questions and deletion requests.

If you remove the extension while alerts are on, the extension cannot send that request, so codex-resets.com may keep its record. Turn alerts off first.

The rest of the local data (the last alert, the last check and the cached status) stays on your device until it is replaced or the extension is removed.

Notifications and links

Notifications appear only after you turn alerts on: a possible reset, a confirmed reset, or a notice that push missed a reset. Clicking a notification opens its link in a new tab, or codex-resets.com when the link is missing or does not use https. Links in the popup open only when you click them. The sites they open, such as the post that announced a reset, have their own privacy practices.

No analytics, no sale, no other use

The extension contains no analytics, tracking or advertising code, and it runs no code from outside its package. The developer does not receive your data, and it is never sold or rented. It goes only to the services described above, and it is used only to deliver the alerts you turned on and to show reset data in the popup. It is never used for advertising, to determine creditworthiness, or for lending.

Limited Use

The use of information received by Reset Alerts for Codex adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. The data is used only for the extension's single purpose, alerts about Codex usage limit resets, and is transferred only as needed for it: to codex-resets.com, which sends the alerts, and through Chrome to its push service, which delivers them.

How to stop

• Turn alerts off: open the extension's popup from the Chrome toolbar and press the bell button.
• Remove the extension: open chrome://extensions and choose Remove. Turn alerts off first, so the extension can ask codex-resets.com to remove its record.

Changes to this policy

If the extension starts handling data differently, this page will be updated, with a new effective date, before that version is published.

Contact

For questions or requests about this policy, open an issue at github.com/camarigor/codex-reset/issues. Issues are public, so do not include personal data or your push subscription. The source code is public at github.com/camarigor/codex-reset, so you can check what the extension does.