Legal
Privacy Policy
Last updated: April 27, 2026
This Privacy Policy explains how Codex Switcher handles information when you use the macOS app, iPhone app, Apple Watch app, widgets, controls, complications, shortcuts, App Intents, account archives, and related documentation (collectively, the “App”).
Codex Switcher is an open-source project. Its source code is publicly available so users can inspect how the App stores and uses data.
1. Summary
Codex Switcher is designed to avoid developer-operated account storage.
- The App stores your account library and related app data locally on your devices and in your private Apple iCloud, CloudKit, Keychain, and iCloud Keychain areas.
- The developer does not operate a server that receives your saved Codex/OpenAI account snapshots.
- The developer does not have access to the data stored in your private iCloud, CloudKit, Keychain, or iCloud Keychain areas.
- The App does not sell personal information.
- The App does not include advertising or cross-app tracking features.
- The App may communicate directly with OpenAI/ChatGPT/Codex services for browser sign-in, token exchange, and rate-limit refresh features that you initiate or enable.
- Exported
.cxaaccount archives may contain secret authentication material and should be protected like credentials.
2. Who is responsible for this policy
Codex Switcher is maintained as an independent open-source project.
Contact: marcel2215@icloud.com
Website: https://codexswitcher.marcel2215.com
Source code: https://github.com/marcel2215/codex-switcher-app
This Policy applies only to Codex Switcher. It does not apply to OpenAI, ChatGPT, Codex, Apple, iCloud, CloudKit, iCloud Keychain, the App Store, TestFlight, GitHub, email providers, or any other third-party service.
3. Information the App stores or uses
The App stores different categories of information depending on which features you use.
| Category | Examples | Where it is stored or used |
|---|---|---|
| Account metadata | Account names, icons, identity keys, auth mode, email/account hints, ordering, pinned state, last-login dates, availability, cached rate-limit display fields | Locally on your device and in your private iCloud/CloudKit app container |
| Secret authentication snapshots | Full Codex auth.json-style snapshots, ChatGPT/OpenAI tokens, refresh tokens, ID tokens, API-key auth payloads, and related credential material |
Keychain on your device and, when available, synchronizable iCloud Keychain |
| Rate-limit credentials | Identity key, auth mode, optional ChatGPT account ID, access token, and export timestamp used for live rate-limit refresh | Keychain and, when available, synchronizable iCloud Keychain |
| Linked Codex folder information | Security-scoped bookmark or local path information needed for the macOS app and extensions to access the selected .codex folder |
Local device storage and App Group storage |
| Shared extension state | Current account display state, display-safe account records, local snapshot availability, pending commands, command results, and widget/control state | Local App Group storage on your device |
| Rate-limit and notification state | Cached 5-hour and 7-day remaining values, reset dates, data status, notification preferences, and scheduled local notifications | Local device storage, private iCloud/CloudKit metadata, Keychain where credentials are needed, and Apple notification systems |
| Session-log observations | Recent Codex session telemetry read from your linked Codex folder when remote refresh is unavailable | Read locally from the selected folder; not sent to the developer |
| Account archives | .cxa files that may contain metadata, cached rate limits, synced rate-limit credentials, and full auth snapshots |
Wherever you save, copy, paste, share, back up, or import them |
| Support communications | Email address, message content, logs, screenshots, or files you voluntarily send for support | The email, hosting, or support systems used to receive and respond to your message |
4. How the App uses information
The App uses the information above to provide its features, including:
- saving and displaying your Codex account library;
- switching the selected macOS Codex folder by replacing or deleting
auth.json; - syncing account metadata through your private iCloud/CloudKit container;
- syncing secret snapshots and rate-limit credentials through Keychain and iCloud Keychain where available;
- showing widgets, controls, complications, menu bar items, Dock items, Shortcuts, and App Intents;
- importing and exporting
.cxaaccount archives; - refreshing and displaying 5-hour and 7-day Codex rate-limit information;
- scheduling local notifications for account switches and rate-limit resets;
- preserving account order, pinned state, settings, and preferences; and
- troubleshooting issues when you voluntarily contact support.
5. iCloud, CloudKit, Keychain, and developer access
The App uses Apple storage systems so your data can remain under your Apple account rather than being stored on a developer-operated server.
Account metadata is stored with SwiftData and CloudKit in the private iCloud container associated with the App. Secret auth snapshots and selected rate-limit credentials are stored in Keychain and, when available, synchronizable iCloud Keychain. Widgets, controls, and intents also use local App Group files on your device.
The developer does not have access to your private iCloud database, iCloud Keychain, local Keychain, local App Group files, linked Codex folder, local auth.json, or .cxa files unless you intentionally send that information to the developer.
Apple may process and store this data as part of iCloud, CloudKit, Keychain, iCloud Keychain, App Store, TestFlight, operating-system, or device services. Apple’s handling of that data is governed by Apple’s own privacy policies and terms.
6. OpenAI, ChatGPT, Codex, and rate-limit refresh
When you use browser sign-in or live rate-limit refresh, the App may communicate directly with OpenAI, ChatGPT, Codex, or related OpenAI-operated endpoints.
Examples include:
- opening an OpenAI authentication page in your browser;
- receiving an OAuth callback on a local loopback server on your Mac;
- exchanging an authorization code for tokens with OpenAI;
- sending an access token and optional ChatGPT account ID to a ChatGPT usage endpoint to request rate-limit information; and
- reading local Codex files or session telemetry from the
.codexfolder you selected.
These requests are made from your device. They are not routed through a developer-operated Codex Switcher server. OpenAI’s handling of sign-in, account data, tokens, usage, and rate limits is governed by OpenAI’s own terms and policies.
OpenAI’s terms may restrict or prohibit sharing account credentials or making your account available to another person. Do not share .cxa archives, auth.json files, tokens, API keys, Apple/iCloud access, or saved account snapshots with other people unless you fully understand the legal, security, and account consequences and have the right to do so.
7. Information the developer does not intentionally collect through the App
The App does not intentionally collect the following through a developer-operated backend:
- your saved OpenAI/ChatGPT/Codex auth snapshots;
- your OpenAI passwords;
- your OpenAI API keys;
- your ChatGPT/OpenAI access tokens, refresh tokens, or ID tokens;
- your private iCloud account library;
- your local Keychain items;
- your Codex
auth.jsonfile; - your
.cxaarchives; - analytics events;
- advertising identifiers; or
- cross-app tracking data.
The developer may receive information only when you voluntarily provide it, such as by sending an email, opening a GitHub issue, submitting feedback, attaching logs, attaching screenshots, or sharing files for support. Do not send secrets or credential files in support requests.
8. Sharing and disclosure
The developer does not sell your personal information and does not share your app-stored account data with advertisers or data brokers.
Information may be processed or disclosed in the following limited situations:
- Apple services: Your app data may be stored or synced through Apple services such as iCloud, CloudKit, Keychain, iCloud Keychain, App Store, TestFlight, and Apple notification systems.
- OpenAI services: Browser sign-in, token exchange, and rate-limit refresh may send authentication or account-related requests directly from your device to OpenAI/ChatGPT/Codex services.
- Support: If you contact the developer, your message and contact details may be processed by email, hosting, GitHub, or other support-related providers.
- Legal or safety reasons: The developer may disclose information actually received from you if required by law, legal process, or a good-faith belief that disclosure is necessary to protect rights, security, users, or the public.
- Open-source collaboration: Information you post publicly, such as a GitHub issue or comment, may be visible to others according to the platform you use.
9. Legal bases where required
Where privacy law requires a legal basis for processing personal information, the relevant basis depends on the context:
- Providing requested functionality: processing needed to run the App features you choose to use, such as account management, iCloud sync, Keychain storage, widgets, notifications, import/export, and rate-limit refresh.
- Consent or user direction: processing based on actions you take, such as selecting a Codex folder, starting browser sign-in, enabling notifications, exporting an archive, importing an archive, enabling automation, or contacting support.
- Legitimate interests: maintaining, securing, debugging, documenting, and improving the App and open-source project, responding to support requests, and preventing misuse.
- Legal obligations: processing or disclosure where required to comply with applicable law, legal process, or enforceable government requests.
Most account data described in this Policy is stored under your control in local device storage, private iCloud/CloudKit storage, Keychain, or iCloud Keychain, and is not accessible to the developer.
10. Retention and deletion
Data stored by the App remains in your local device storage, private iCloud/CloudKit container, Keychain, iCloud Keychain, App Group storage, backups, exported archives, or linked Codex folder until you remove it or Apple’s systems remove it according to your settings.
You can usually delete or reduce app data by:
- removing accounts inside the App;
- using any reset or remove-all actions provided by the App;
- deleting exported
.cxaarchives you created or received; - deleting local copies, backups, clipboard contents, and shared files that contain credentials;
- deleting the App from your devices;
- removing Codex Switcher data from iCloud where Apple provides that option;
- disabling or clearing iCloud Keychain data where Apple provides that option; and
- rotating, revoking, or regenerating OpenAI tokens/API keys through OpenAI where applicable.
Because the developer does not have access to your private iCloud, CloudKit, Keychain, iCloud Keychain, local device data, or exported archives, the developer generally cannot delete that data for you.
Support emails and other information you voluntarily send may be retained as long as reasonably needed to respond, maintain records, prevent abuse, comply with legal obligations, or resolve disputes. You may request deletion of support communications by contacting the developer, subject to legal and practical limitations.
11. Security
The App is designed to use Apple platform security features such as sandboxing, security-scoped bookmarks, Keychain, iCloud Keychain, CloudKit private storage, file coordination, atomic file replacement, restrictive file permissions for restored auth.json files, and local App Group storage for extensions.
However, no software or storage method is perfectly secure. The App handles sensitive authentication material, and misuse can create serious risk. In particular:
.cxaarchives may contain secrets and are not a substitute for encrypted storage;- copied or shared archives may allow another person to access an account;
- compromised devices, Apple IDs, iCloud accounts, backups, malware, phishing, or weak device security may expose credentials;
- using Codex’s own logout flow or third-party account controls may invalidate saved snapshots; and
- OpenAI, Codex, Apple, or operating-system changes may affect security, compatibility, or account availability.
You are responsible for securing your devices, using strong device passwords, enabling two-factor authentication where available, protecting your Apple ID and OpenAI accounts, avoiding credential sharing, and deleting exported archives you no longer need.
12. Children
The App is a developer tool for managing Codex/OpenAI account snapshots. It is not directed to children and is not intended for users who are not allowed to manage the relevant Apple, OpenAI, ChatGPT, or Codex accounts under applicable law or third-party terms.
The developer does not knowingly collect personal information from children through the App. If you believe a child has provided personal information to the developer through support channels, contact the developer so it can be addressed.
13. International processing
The App may rely on third-party services, including Apple, OpenAI, GitHub, email providers, and website-hosting providers, that process information in different countries. Their processing is governed by their own privacy policies, terms, and applicable transfer mechanisms.
App-stored iCloud, CloudKit, Keychain, and iCloud Keychain data is handled by Apple under Apple’s systems and policies. OpenAI sign-in and rate-limit requests are handled by OpenAI under OpenAI’s systems and policies.
14. Your privacy rights and choices
Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or receive a copy of certain personal information.
For data stored locally, in private iCloud/CloudKit storage, in Keychain, in iCloud Keychain, or in exported archives, you generally exercise control directly through the App, your Apple devices, your Apple/iCloud settings, your filesystem, and your OpenAI account settings.
For support communications or other information you intentionally sent to the developer, you may contact the developer to request access, correction, deletion, or other available privacy rights. The developer may need to verify your request and may be unable to comply where an exception applies.
You may also have the right to complain to a data-protection authority or other regulator in your jurisdiction.
15. No sale, no advertising, no tracking
The App does not sell personal information. The App does not use advertising networks. The App does not intentionally track you across other companies’ apps or websites for advertising purposes.
16. Changes to this Policy
This Privacy Policy may be updated from time to time. The updated version will be posted through the App, website, repository, or another appropriate location. The “Last updated” date will indicate when this Policy was last revised.
17. Contact
For privacy questions or requests, contact:
Email: marcel2215@icloud.com