Customer-operated by default
Climakers tools are designed to run inside customer-controlled environments so documentation data does not need to transit through a mandatory Climakers service.
Climakers designs customer-operated tools to minimize data exposure, reduce dependency risk, and fit regulated documentation workflows.
Security at Climakers starts with architecture: customer-controlled execution, least-privilege behavior, minimal third-party dependencies where practical, and strict controls across the software development life cycle.
Climakers tools are designed to run inside customer-controlled environments so documentation data does not need to transit through a mandatory Climakers service.
Climakers prefers the smallest permission set and the narrowest data handling required for the documented workflow.
Climakers applies a build-your-own bias and keeps third-party library use minimal where practical to reduce supply-chain exposure and simplify review.
Climakers applies security controls across design, implementation, review, release, and maintenance.
Security expectations are considered during product design, code review, and release preparation so risky behavior is identified before publication.
Climakers keeps software and dependencies current, reviews external components carefully, and prefers simpler implementations when they reduce attack surface.
Release processes are intended to preserve integrity, reduce accidental exposure, and maintain a reliable update path for customers.
Security depends on both product design and customer operating practice.
Customers should store tokens, secrets, and exports in their own approved systems. Climakers documentation promotes environment variables, local control, and redaction.
When contacting support, remove secrets, private content, internal URLs, identifiers, and file paths unless disclosure is strictly necessary and approved by your organization.
If you believe you found a vulnerability, report it privately to support@climakers.com with enough detail to reproduce the issue safely.
Climakers products are built for teams that operate under controlled processes and external requirements.
Portable outputs, transparent CLI workflows, least-privilege operation, and limited dependency use help customers integrate Climakers into governed environments.
Climakers aims to support customers working toward or operating within ISO 9001, ISO 27001, ISO 27017, NIS 2, SOC 2, GMP, and similar frameworks. Climakers itself is not currently certified under any of these frameworks; the design and operating principles described on this page are intended to support customer integration into governed environments without implying a certification claim.
The summary above outlines the main commitments. The text below presents the public Security Policy in a more traditional plain-text format.
Climakers security posture begins with the product model: customer-operated tools, customer-controlled storage, and no mandatory relay of documentation content through Climakers infrastructure for normal use.
This architecture is intended to reduce data exposure and give customers direct control over credentials, exports, retention boundaries, and operational governance inside their own environments.
Climakers applies security controls during design, implementation, review, release, and maintenance, including consideration of permissions, behavior, dependency choices, and release integrity.
Climakers keeps software updated and prefers simpler, reviewable implementations where they reduce attack surface, complexity, or supply-chain risk.
Climakers follows least-privilege principles and aims to request or require only the access necessary for the documented product workflow. Access decisions are meant to stay narrow, explicit, and operationally understandable.
Climakers also applies a minimal third-party library approach where practical, with a build-your-own bias for core logic when that choice improves reviewability or lowers dependency exposure.
Customers remain responsible for managing tokens, environment variables, workstation and host security, storage controls, access controls, backups, and the broader security and compliance posture of their own environment.
When requesting support, customers should provide redacted diagnostics and avoid transmitting secrets, regulated content, or unnecessary private information unless disclosure is strictly necessary and approved internally.
Climakers aims to support teams operating under structured frameworks such as ISO 9001, ISO 27001, ISO 27017, NIS 2, SOC 2, GMP, and similar requirements, but customers remain responsible for their own assessments, evidence, controls, and attestations.
Climakers itself is not currently certified under SOC 2, ISO 27001, ISO 27017, or other equivalent third-party attestations. References to these frameworks describe the design intent of Climakers products and are not a representation that Climakers holds a certification or independent audit report under any of them.
Climakers welcomes responsible reporting of security issues. Suspected vulnerabilities should be reported privately to support@climakers.com with sufficient detail to reproduce the issue safely, including the affected product version, environment, and a clear description of the impact. Climakers will acknowledge a good-faith report within a reasonable triage window, will keep the reporter informed of progress, and will work to publish or distribute fixes without unnecessary delay. Climakers does not currently operate a paid bug bounty program.
Researchers acting in good faith under this policy — making reasonable efforts to avoid privacy violations, service disruption, and data destruction; testing only systems within the scope of Climakers-operated infrastructure and Climakers products; and giving Climakers a reasonable opportunity to investigate before public disclosure — will not face legal action from Climakers for that activity. This safe harbor is limited to Climakers-operated systems, does not bind third parties, and does not extend to activities prohibited by applicable law.
The public Climakers site is served over HTTPS with TLS, redirects HTTP traffic to HTTPS, and is configured with HTTP Strict Transport Security so that compliant browsers refuse insecure connections. Standard security-relevant HTTP response headers are applied where supported by the platform. The site is hosted on a managed platform that provides isolated build environments and operational controls for the runtime.
Customer documentation content is never required to flow through the public site. The site operates as a thin marketing and licensing front end; payment and license issuance are handled by the merchant of record under that provider's own security program.
Climakers product releases are produced from controlled build pipelines that pin third-party dependencies, record their versions, and are intended to keep the release artifact stream auditable. Release artifacts are distributed through documented channels referenced in the product documentation. Customers should obtain Climakers tools only from those documented channels.
Climakers reviews dependency advisories and security disclosures for the third-party components listed in the product license-terms documents and aims to publish updates that address known issues in a timely and proportionate manner. Customers should keep installed Climakers tools updated to receive security fixes.
Read how Climakers limits data collection, avoids sharing customer information, and keeps product outputs under customer control.