2.5 KiB
Code Signing Policy
NotAlterra uses automated, auditable pipelines to ensure every release artifact is traceable to its source.
Build & Signing Process
All release binaries are built from this repository by GitHub Actions on
tag push. The CI workflow runs on ubuntu-latest, installs the
required toolchain via dtolnay/rust-toolchain@stable, and produces
deterministic artifacts using a locked Cargo.lock and pinned
dependency versions.
AI Usage Disclosure
This project uses agentic AI coding tools (e.g., DeepSeek TUI, GitHub Copilot) as assistive aides for code generation and review. AI tools operate under human supervision only:
- Every code change is reviewed and committed by a human maintainer.
- AI-generated code is identified in commit history — no attempt is made to obscure or anonymize the source.
- All contributions pass the same lint and verification gates as any human-authored change.
Integrity
AI tools do not have direct write access to the release pipeline or the repository's tag namespace. Builds are triggered exclusively by signed Git tags, which can only be created by a human maintainer with access to the project's GPG key.
Privacy
NotAlterra does not collect or transmit any personal user data — it has no network access, no telemetry, and no analytics. The application runs entirely offline:
- No telemetry, no analytics, no crash reporters.
- No network requests — the binary never opens a socket.
- Configuration is stored locally in
app.iniunder the platform config directory (e.g.%LOCALAPPDATA%\NotAlterra\config\app.ini).
The app.ini file stores your save-folder path and backup root — the
minimum needed to avoid re-entering them each session. These paths may
include the current system username (e.g. C:\Users\jane\...). This
information never leaves the local machine. The file is plain text and
can be inspected or deleted at any time.
Because no data is transmitted, there is nothing to share, sell, or expose. This section serves as a safe-harbor statement: NotAlterra is designed to respect user privacy by never sending data anywhere.
Signing
Status: pending certification. No binaries have been signed by SignPath yet. This policy exists for transparency and privacy documentation while the project prepares for certification.
Only binaries produced by the official CI runner from the main
branch will be submitted to SignPath for signing. Manual or off-CI
builds are never shipped as signed releases.