GptSkin Editorial Policy

Who is responsible

The GptSkin Editorial Team is the organizational author for GptSkin documentation, tutorials, comparisons, safety explanations, pricing references, and use-case guides. It is part of the GptSkin team; we do not invent individual bylines. Product and press questions go to support@gptskin.best.

Evidence standards

We check product claims against the current production service and the public GptSkin Skill source and releases. Comparisons should link to first-party documentation where available. We distinguish verified facts, our interpretation, and recommendations. We do not publish invented benchmarks, testimonials, customers, revenue, or outcomes.

The canonical product facts, limitations, prices, platform support, and independence disclosure are maintained on Brand Facts. Security-sensitive statements are checked against the Security documentation.

Review and updates

Material technical pages show a created or last-verified date. We recheck affected content after a Skill release or a change to Codex integration, authentication, pricing, storage, privacy, or platform support. Historical posts may remain unchanged when their date is necessary context; a correction note is added when an old statement could mislead a current reader.

Corrections

Send a URL, the disputed statement, and supporting evidence through the contact page. We review material corrections, update the page when warranted, and add a visible note when the change alters the meaning of a claim. Typographical and formatting fixes may be made without a correction note.

Independence and commercial disclosure

GptSkin is an independent product and is not affiliated with or endorsed by OpenAI. Our content can describe our own product and link to our pricing or installation pages. Sponsored or paid editorial placement, if ever published, must be labeled. We do not accept payment for undisclosed rankings.

AI assistance and human review

AI tools may assist with outlines, translation, or editing. A GptSkin team member remains responsible for checking product facts, links, safety boundaries, localization, and publication. AI-generated drafts are not treated as evidence.

Privacy in examples

Community theme previews must be derived from the submitted source image. We never publish a screenshot of a user's actual Codex window as a theme preview because it may expose chats, project names, email addresses, or code. Customer stories require explicit permission and may not claim results the participant did not approve.

Last policy review: July 28, 2026.