Last Updated: July 24, 2026
CodX Editor does not sell personal information or build advertising profiles from the code you write. Standard project drafts stay in your browser, while optional features such as collaboration, publishing, GitHub, and translation use the limited data needed to provide those features.
The standard editor can be used without an account. Connected and sharing features have different data paths, so this summary separates them instead of suggesting that every action is local.
Unsaved recovery data, preferences, tutorial state (including whether the one-time Manage Session tip was shown), device identifiers used for collaboration safety, and locally saved projects can be stored in your browser. The project library keeps up to 24 entries, and an autosaved recovery draft remains eligible for restoration for up to seven days. Clearing site data may remove them.
A session temporarily carries display names, chosen colors, cursor styles, chat, pair tasks and suggestions, shared project updates, permissions, and connection identifiers through the collaboration server. Optional pair voice is direct browser-to-browser audio and is not recorded by CodX Editor.
OAuth authorization is handled through GitHub. The connection is protected in an encrypted, HTTP-only cookie that browser scripts cannot read and that is sent only to CodX Editor's GitHub API routes. It expires after seven days, or is removed from the current browser when you disconnect. You are never asked to paste a personal token.
Files included in a published project are sent to the service and stored so the public link keeps working. Publishing also creates a verification key. That key is needed to update the link, and anyone who has it can open the project's full source code and load every file into the editor, so treat it like a password and never post it publicly. Do not publish secrets, private messages, credentials, or material you do not have permission to share.
Runtime project files and packages can run in an isolated browser container supplied by the runtime provider. A temporary preview URL bridges the selected localhost port to the browser tab.
Country headers, a public IP lookup when necessary, or browser language may be used to choose an interface language. Visible interface phrases can be sent to a translation provider and cached.
At CodX Editor, we are committed to being transparent about how we handle data. This privacy policy explains what we do and do not collect, including how collaboration mode is powered by Socket.IO for temporary real-time communication.
Key Points:
CodX Editor may use Google AdSense, a third-party advertising service provided by Google LLC. When advertising is enabled, ads can help support the cost of providing the public website and editor.
Google AdSense uses cookies, web beacons, and similar tracking technologies to collect information about your browsing activity. This information is used to:
Google AdSense may collect the following types of information:
Google uses the DoubleClick cookie to enable personalized advertising. This cookie allows Google and its partners to serve ads based on your visits to CodX Editor and other websites across the internet.
Important: While we don't directly collect this data, Google does collect and process it according to their own privacy policy. By using CodX Editor, you consent to Google's data collection and processing as described in this section.
You have control over personalized advertising. You can opt out through the following methods:
For more information about how Google collects and processes data, please review:
CodX Editor collaboration mode is powered by Socket.IO to relay live editor and presence updates between participants.
Collaboration sessions are temporary and are used only to deliver live updates and session presence to connected users. We do not require account registration to collaborate.
CodX Editor itself does not collect:
CodX Editor is a client-side application that runs entirely in your web browser.
All your code, projects, and settings are stored in your browser's local storage (localStorage) by default. This data stays on your device unless you explicitly export, publish, or upload it through another feature. You have complete control over this data and can clear it at any time through your browser settings. The saved-project library keeps up to 24 entries, while an autosaved recovery draft is offered for restoration for up to seven days.
When you write HTML, CSS, or JavaScript in CodX Editor, it is processed and previewed on your device. We do not send your main editor project content to a server for processing, compilation, or storage unless you use a feature such as collaboration or GitHub upload that explicitly sends data to another service.
Add Media reads images, video, and audio selected from your device in the browser and uses that local data to display the media viewer. The viewer does not upload the file by itself. Media leaves the device only when you choose a sharing feature such as collaboration, publishing, or a GitHub upload.
Added media may be stored locally as binary data in your browser's IndexedDB so it can be restored without converting it into a larger base64 string. Temporary object URLs are used for playback and are released when the page closes. Clearing CodX Editor's browser site data removes this locally stored media.
Developer Tools can intentionally expose safe details about that local media in a read-only Media Source View. Large encoded and binary payloads remain hidden to prevent excessive memory use. The view is off by default, is not saved as a preference, and does not upload the media by itself.
ZIP exporting and updating are also handled locally in your browser. If you choose Update ZIP File, CodX Editor reads only the archive you select, updates matching project paths, adds current project files, and preserves unrelated archive entries. A supported browser may ask for permission to write back to that selected file; otherwise the updated archive is downloaded as a new local copy. The selected ZIP is not uploaded to CodX Editor for this process.
ZIP All Projects and Import All Projects are also processed locally in your browser. A bulk export places each locally saved project in its own archive folder and stores restoration metadata in the ZIP. A bulk import reads the ZIP you select and writes supported project files back into the browser project library; projects with matching names are replaced. The archive is not uploaded to CodX Editor.
CodX Editor uses open-source libraries for code editing features (such as syntax highlighting, icons, fonts, and archive support). Once loaded, they run locally in your browser and your code is not sent to them. Some are delivered from public content delivery networks, so your browser requests those files directly and the provider can see standard request details such as your IP address. Enabling the optional Node.js runtime additionally downloads that runtime from its provider.
Google AdSense places cookies on your device to enable personalized advertising. These are third-party cookies managed by Google, not by CodX Editor.
CodX Editor itself does not use cookies for tracking or analytics. We only use browser local storage to save your code projects locally on your device.
Since all your code is stored locally in your browser:
For data collected by Google AdSense, you can:
CodX Editor is intended for a general audience and is not directed at children under 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided personal information through our service, please contact us so we can address it.
Google AdSense may collect non-personal browsing data (such as IP address and device type) from all visitors to serve advertisements. Visitors under 13 should not use this service without parental guidance, and parents or educators supervising younger users should review Google's privacy policies and consider using parental controls or ad-blocking tools.
CodX Editor may contain links to external websites or resources. These third-party sites have their own privacy policies independent of ours. We encourage you to review the privacy policies of any external sites you visit. We are not responsible for the privacy practices of third-party websites.
While your code stays on your device, we still take security seriously:
However, as with any web application, no method of transmission over the internet or electronic storage is 100% secure. While we strive to use commercially acceptable means to protect the integrity of our service, we cannot guarantee absolute security.
We may update this Privacy Policy from time to time to reflect changes in our practices or for other operational, legal, or regulatory reasons. When we make changes, we will revise the "Last Updated" date at the top of this page.
Significant changes will be highlighted on our website or announced through other appropriate channels. We encourage you to review this Privacy Policy periodically to stay informed about how we are protecting your privacy.
Your continued use of CodX Editor after any changes constitutes your acceptance of the updated Privacy Policy.
If you have any questions, concerns, or feedback about this Privacy Policy or our privacy practices, please don't hesitate to reach out to us.
You can contact us via the Contact page on our website.
We value your privacy and are committed to addressing any concerns promptly and transparently.
We built CodX Editor with privacy as a core principle. Your creativity and code belong to you — always. Enjoy coding with peace of mind.