Terms of Use
Use boundaries for browser-local tools, Enhanced theme artifacts, third-party Engine workflows, file rights, integrity values, and exact-record runtime evidence.
Scope
These terms apply to use of CodexSkin Tools, its local browser tools, documentation, and downloadable theme artifacts. The True MVP is provided without accounts, payment, subscription, cloud sync, or hosted user-content storage. A future capability is not promised by its mention in internal plans or conditional contracts.
Independent project
CodexSkin Tools is an independent project and is not affiliated with, endorsed by, or sponsored by OpenAI. OpenAI and Codex names and marks remain with their respective rights holders. Referential use does not imply permission, partnership, sponsorship, endorsement, or official status.
Third-party local Engine
Enhanced themes require the independent Codex Dream Skin local Engine. The Engine is third-party software with its own source, license, instructions, local files, logs, runtime behavior, and risks. The website creates, previews, and structurally validates files; it does not directly operate the user’s Codex installation.
User responsibilities
Use only files and images you have the right to use and, where applicable, redistribute. Do not use the service to create or distribute infringing, deceptive, malicious, unlawful, or privacy-invasive material. Review platform and build status, source, license, hashes, Apply steps, and Restore steps before use. Keep backups and save work before local Engine operations.
Validation and compatibility limits
Structural PASS is not runtime compatibility, absolute safety, malware certification, official support, or a guarantee for every Codex version. Runtime status is limited to the exact OS and architecture, Codex build, Engine version, Runtime SHA, artifact hash, and evidence shown. Updates to Codex or the Engine may require re-verification.
Artifacts, hashes, and source licenses
SHA-256 values support integrity comparison; they are not digital signatures or safety certificates. MIT-licensed upstream source remains subject to its copyright and permission notice. MIT does not grant rights to OpenAI or Codex marks, people or likenesses, artwork, screenshots, user images, or other third-party content.
Availability and changes
Do not rely on uninterrupted availability, permanent compatibility, permanent free access, or unannounced future features. Features may be changed or removed when evidence, security, rights, or platform behavior requires it. Theme publication and downloads may be withheld when source, rights, artifacts, hashes, runtime evidence, QA, or release approval is incomplete.
Contact and removal
Technical, removal, intellectual-property, privacy, and security requests may go through the Contact route only after a real channel is configured. No acknowledgement or resolution time is promised while Owner operations cannot support it. The inactive Contact page does not accept a submission.
Product data boundary
Selected Builder and Validator files are processed locally in the browser under the current True MVP contract. The current product has no enabled analytics, billing, account, cloud-sync, or active Contact workflow. Any material change requires the implementation, Privacy notice, and these terms to be reviewed together before release.
Terms that are not supplied here
This contract does not add a governing law, venue, arbitration provision, company registration, postal address, limitation amount, age threshold, warranty formula, DMCA-agent designation, response time, refund policy, or legal-entity name. Those details require Owner input and qualified review before they can be published.
Status and evidence vocabulary
Structural status uses PASS, WARN, FAIL, or CANNOT_VERIFY. Runtime status by platform uses VERIFIED_BY_US, REFERENCE_ONLY, NOT_VERIFIED, or REVERIFY_REQUIRED. These fields must remain separate. Formal verification requires the complete exact-build evidence record; reference material does not authorize redistribution.
Before using an artifact
Review the record, source rights, redistribution decision, integrity values, structural report, exact platform evidence, and Restore path. Do not proceed with a FAIL result, unresolved rights, a hash mismatch, unexpected scripts or executables, nested archives, traversal paths, extra files, or a guide that does not match your machine.
How to read a published theme record
A published record describes only the approved artifact and evidence displayed on that page. Its Structural status, Runtime status, hashes, source, license, rights status, and redistribution decision are separate fields. Users must not treat an available preview as permission to redistribute, a matching hash as a signature, a PASS result as runtime evidence, or REFERENCE_ONLY material as formal verification. Missing fields remain unresolved until the responsible evidence or rights review supplies them.
Creating and sharing local themes
Users may create a local theme from an image they are entitled to use, but local creation does not itself grant permission to publish or redistribute that image or a package containing it. Before sharing an artifact, review the image rights, source terms, marks, screenshots, people or likenesses, and any other third-party material separately from the Engine source-code license. Do not remove attribution or permission notices required by an applicable source license, and do not describe referential naming as a partnership or approval.
Evidence changes and re-verification
Runtime evidence is tied to a specific tuple, not permanently attached to a theme name. A changed Codex build, Engine version, Runtime SHA, operating system, architecture, artifact, or recovery method may invalidate the prior result and require REVERIFY_REQUIRED. Users should compare the current record before each local Engine workflow and retain the Apply and Restore instructions that match it. An older observation may remain REFERENCE_ONLY when useful for context, but it must not be promoted to the current formal result.
Blocking and removal decisions
CodexSkin Tools may withhold or remove a preview, artifact, route, or action when rights, redistribution permission, structural checks, integrity data, runtime evidence, security review, or release approval is incomplete or changes. A blocked download does not decide ownership or resolve a legal dispute; it preserves the project boundary while the relevant record is reviewed. Once a real Contact channel is active, the applicable request category and configured process may be used without sending local files, credentials, or other forbidden inputs.
States
Errors
Frequently asked questions
Do these terms cover the independent local Engine?
They cover use of this website and its artifacts. The independent Engine is third-party software with its own source, license, instructions, files, logs, runtime behavior, and risks.
Does Structural PASS guarantee runtime compatibility?
No. Structural PASS reports known file checks only. Runtime status requires evidence for the exact platform, Codex build, Engine version, Runtime SHA, artifact hash, date, and recovery record.
What rights do I need for a theme image?
Use only files and images you have the right to use and, when distributing them, the right to redistribute. An upstream source-code license does not automatically grant rights to marks, artwork, screenshots, likenesses, or user images.