Skip to content
Skip to content

Code signing

Code signing policy

How the Windows installers are built, who can release them, and when they are signed. Translations are provided for convenience; the English version is the binding one.

Section 1

Status

Windows releases will be signed through SignPath.io with a certificate from SignPath Foundation once the project is approved. Until then the installers are unsigned.

Until signing starts, Windows may show a SmartScreen warning for the installers. The one-line PowerShell install on the download page does not trigger it. This policy applies to every signed release from the first one.

Section 2

What gets signed

Only the Windows installers of a zcrypt release:

  • The .exe and .msi installers attached to each GitHub release.
  • They are built by the GitHub Actions release workflow from the public source code, on GitHub-hosted runners.
  • The program files inside the installers are not signed separately.
  • Not covered: the macOS, Linux and Android builds, the website and the server.

Section 3

When signing happens

  • Only for releases built by CI from a tagged version commit. Nothing built on a personal computer is ever submitted for signing.
  • Every signing request is approved by hand by the approver before the certificate is used.
  • Signed files carry the product name zcrypt and the release version.
  • The signing key is held by SignPath. The project never has a copy of it.
  • A signed release can be matched to its exact source commit in the public repository.

Section 4

Team and roles

zcrypt is maintained by one person, who holds every role below. The roles follow the SignPath Foundation terms.

  • Authors (can change the source code without a second review): Muhammad Wasif Malik, GitHub account Wosmos.
  • Reviewers (review changes from people who cannot commit): Muhammad Wasif Malik, GitHub account Wosmos.
  • Approvers (approve each signing request): Muhammad Wasif Malik, GitHub account Wosmos.

Changes from other contributors are reviewed by the maintainer before they are merged. Multi-factor authentication is required on the GitHub and SignPath accounts of everyone on the signing team.

Section 5

Privacy

zcrypt does not transfer your information to other networked systems unless you ask it to, or it is needed to do what you asked. What it sends:

  • Encrypted file chunks, to the storage accounts you connected, or to zcrypt-operated storage if you did not. We cannot read them.
  • Account details and file metadata (sizes, timestamps, sealed names, wrapped keys), to zcrypt's server.
  • The desktop app asks GitHub whether a newer version exists. That request carries no account or file information. Installs from the Microsoft Store do not do this.

The full details, including the services involved and what each one sees, are in the privacy policy.

Section 6

Installing and removing

The installer adds zcrypt and a handler for zcrypt:// links, which the browser uses to hand sign-in back to the app. Nothing else on your system is changed. Launch at login stays off until you turn it on in the app's settings. You can uninstall zcrypt at any time from Windows Settings, Apps.

Section 7

Contact

Questions about code signing? Email m.wasifmalik17@gmail.com.

See also: Privacy Policy

Get started today

The drive you actually own.

Connect your own account. Encrypted on your device. No artificial limits, no vendor lock-in.