Trust / Security
Security and release verification
Understand what signatures, approvals and encrypted records protect—and what they do not.
Updated September 24, 2026. SiliconForge is a native engineering workspace, not a guarantee that a generated design is safe, correct or production-ready.
Check the exact download
Linux AMD64, Linux ARM64 and signed Windows x64 application downloads are published on the download page. Linux artifacts identify their signing scheme in the release record: Minisign for new releases or Sigstore for applicable older releases. Windows uses Authenticode signing. Use the scheme and public key or identity for that exact artifact; Minisign does not imply a certificate, transparency log or trusted timestamp. Compare the selected artifact with its published checksum and signature before installation. The website/API revision and an application artifact can have different source identities.
A valid signature establishes artifact provenance and integrity, not engineering correctness or immunity from malware. Malware scans are point-in-time checks. Signing and installer publication are also not a substitute for headed interactive Windows GUI validation; that separate validation has not been established by this website update.
Use the installation guide, published checksums and rollback instructions. Never bypass an invalid signature just because a download link works. The application signature covers the exact distributed installer or archive, including its recorded payload. Included engineering tools retain their own licenses and source obligations. A signature on the application does not verify an arbitrary external tool archive: use its approved origin, hash and selection checks.
AI proposes; you authorize
- Review the request, disclosed context and execution scope before approval.
- Candidates, validation and apply actions are bound to project state. A stale candidate must be reassessed, not treated as fresh evidence.
- Inspect the actual diff and tool results before applying a change; preserve a revision/checkpoint for recovery.
- Tool access and subprocesses are meaningful authority. Use only projects, tools and integrations you trust.
These controls reduce accidental or unapproved changes; they do not eliminate malicious inputs, incorrect tool configuration, prompt injection or engineering mistakes. Passing lint, simulation, synthesis or a formal check proves only the conditions that particular run actually exercised.
Credentials and service access
Installation-bound rotating credentials are stored in operating-system secure storage: Windows Credential Manager or Linux Secret Service. The service stores token hashes and verifies installation ownership for authenticated operations. Revoke a lost or compromised installation and contact support with a non-secret identifier. Server-side access is blocked on revocation; it cannot instantly disable an already-offline signed desktop lease. That lease ends at its verified paid-term expiry or a definitive online revocation check. Temporary network failure alone does not invalidate a valid lease.
The managed service uses its own provider credentials and does not accept your personal OpenAI or Codex login. Explicit desktop provider settings are separate. Do not paste keys, passwords, refresh tokens or activation claims into prompts, tickets or screenshots.
Desktop entitlement is not a file lock
The service signs the verified paid period using a dedicated entitlement-signing key, separate from payment credentials and installer-signing keys. The app verifies the signature, installation binding and expiry before paid operations. A copied lease is not a transferable license; changing its fields invalidates the signature. Clock anomalies or unknown signing keys require correction or a verified compatible update, not bypassing validation.
After expiry, safe project viewing, export and recovery remain available. Offline activation is not offered, and an offline app cannot independently verify a new renewal. See the billing guide before planned offline work.
Protection has limits
Managed responses, private streamed job content and support email/message bodies are encrypted in the service database. Metadata and restricted managed-runtime files are different stores; this is not end-to-end encryption or a claim that every file is encrypted. Data handling describes these distinctions and the unresolved automatic-retention limits.
Prompt-free chained audit receipts help trace operational events without placing designated prompt or credential fields in the audit payload. They do not replace an external audit. No SOC 2, ISO 27001, penetration-test certification or guaranteed service-level response is asserted here.
Report a vulnerability safely
- Use support with a non-sensitive subject beginning “Security report.”
- Describe the affected version, platform, component and potential impact. Include a minimal, non-destructive reproduction using data you own.
- Do not include live secrets, exploit dumps, another customer’s information or confidential RTL. Keep the returned case identifier.
- If details need a different transfer channel, request arrangements in the initial case before sending them.
The support form is a case queue, not a live incident-response channel or automatic email notification service. Do not attack production, access other users’ data or disrupt service to demonstrate a problem. This page does not create a bug bounty, legal safe harbor or response-time guarantee.
If you suspect exposure
Stop the affected activity, preserve a minimal redacted account of what happened, revoke affected installations and rotate compromised external-provider credentials through that provider. Do not publish the secret in a report or repeat the disclosure to test whether it still works. Consult your organization’s incident process for proprietary designs.
Privacy · Third-party software · Safe diagnostics and recovery