This page documents the policies, practices, and standards that govern code-with-me. Each section is written to accurately reflect current system behavior. Areas marked with [TO BE DECIDED] are known gaps to be resolved before monetized launch.
Last updated:
Data Collection. This site uses basic page-view analytics to understand general traffic patterns. As of the current version, this analytics system is a no-op placeholder — no data is actively collected, transmitted, or stored. If you use the contact form, the email address you provide is used solely to respond to your message and is not used for any other purpose.
Cookies. This site does not set any cookies at this time. If essential cookies are added in the future (for example, to support authentication or user preferences), this policy will be updated to describe their purpose and duration.
Third-Party Services. [TO BE DECIDED: hosting provider, analytics provider if any, and any embedded third-party services]
Data Retention. [TO BE DECIDED: retention period for any collected data, including contact form submissions]
User Rights. [TO BE DECIDED: user rights regarding access, correction, deletion, and data portability]
Last updated:
This site may contain affiliate links and sponsored content. When an article includes an affiliate link or has been sponsored, a disclosure is displayed near the relevant claim or recommendation — not hidden in the footer or terms of service.
Affiliate Links. Some product or service links on this site are affiliate links. If you click an affiliate link and make a purchase, the site may earn a commission at no additional cost to you. Affiliate links are visually marked with a disclosure badge adjacent to the link or within the same content section, following the pattern established in the SponsorDisclosure component (S4.1).
Sponsored Content. Content that has been sponsored, paid for, or otherwise financially supported is clearly labeled as such. Sponsored content carries a distinct visual treatment — a highlighted notice at the top and bottom of the article — so it is unmistakable from editorial content.
[TO BE DECIDED: affiliate program provider(s) and specific commission disclosure language]
[TO BE DECIDED: criteria for accepting sponsored content and editorial independence safeguards]
Last updated:
Trust Standard. Every technical claim published on this site should make its basis inspectable: personally tested, project-derived, source-reviewed, or explicitly uncertain (S1.5). Tutorials and recipes surface versions, dates, source links, repository or artifact links where supplied, and last-verified or updated status when content can age.
AI Assistance Stance. AI tools may assist with research, drafting, translation, SEO, or organizational tasks outside of runtime. Any material AI assistance — meaning assistance that shapes the substance or presentation of content beyond trivial copy-editing — is disclosed in the article's trust signals section (S2.4) and is human-reviewed and tested before publication. AI does not make unsupervised technical claims or author articles autonomously.
AI Disclosure Labeling. Articles that use AI assistance include a visible disclosure in the Trust & Provenance section at the bottom of the article. This disclosure describes the nature and extent of AI involvement.
Content Type Trust Requirements. Tutorials and recipes include version information, source links, test status, and last-verified dates. Commentary and opinion pieces are clearly identified as such.
[TO BE DECIDED: specific AI tooling or models used in the editorial workflow]
Last updated:
Article Content. Unless otherwise noted, article text and accompanying media are licensed under a [TO BE DECIDED: Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License (CC BY-NC-SA 4.0)] — or an equivalent open license determined at launch. This means you may share and adapt the content for non-commercial purposes, provided you give appropriate credit and distribute any adaptations under the same license.
Code Examples. Code snippets, configuration files, and technical examples published on this site are licensed under [TO BE DECIDED: MIT License] unless otherwise noted in the source repository. You may use, modify, and distribute the code for any purpose, subject to the terms of that license.
Permission Requests. For uses not covered by the above licenses — such as commercial reproduction, translation for commercial distribution, or use of media assets — please [TO BE DECIDED: contact via the permissions process described on the contact form or a dedicated permissions page].
Copyright Owner. All content is copyright Hiddengem unless otherwise attributed.
Last updated:
Reporting Errors. If you spot an error, outdated information, or have a suggestion for improvement, please reach out via the contact page (S4.3). Every reasonable correction report is reviewed and, if confirmed, addressed promptly.
Correction Handling. When a substantive error is corrected, a visible update notice is added to the article explaining what changed and when. Minor edits (typographical fixes, link updates) proceed without an individual notice but are noted in the article's revision history.
Outdated Content. Articles that contain time-sensitive information carry a last-verified date. When content is known to be stale or superseded, a prominent notice is displayed at the top of the article directing readers to newer or more accurate material.
Update and Verification Practice. Technical content is reviewed periodically. High-traffic articles and time-sensitive tutorials receive priority in the review queue. Readers can see the last-verified date for each article.
[TO BE DECIDED: formal review cadence and scheduled audit process]
Last updated:
Target Level. This site aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. We are committed to making the content and functionality accessible to all users, including those using assistive technologies.
Known Limitations. [TO BE DECIDED: specific known accessibility limitations after an audit is conducted]
Reporting Accessibility Issues. If you encounter any accessibility barriers or have suggestions for improvement, please report them via the contact page. We take accessibility feedback seriously and will work to address reported issues.
Ongoing Effort. Accessibility is an ongoing commitment. As the site evolves, we will continue to test and improve the experience for all users. Periodic accessibility reviews will be conducted as part of the development process.
[TO BE DECIDED: dedicated accessibility contact or reporting channel]