Tark

Code signing

Every Tark download is built from the public source and signed, so you can check where it came from.

Who signs Tark

macOS

Signed with the Developer ID of Zynclave Tech Private Limited and notarized by Apple. Updates are also checked against Tark's own signing key before they install.

Windows

Free code signing provided by SignPath.io, certificate by SignPath Foundation (application in progress). Until it is approved, Windows builds are unsigned and say so on the download page.

How a release is made

Built from the public repository

Every release is built by the repository's own build scripts from github.com/ZynclaveTech/tarka-browser: ungoogled-chromium plus Tark's patches, all of them public. Windows builds signed by SignPath are built on GitHub Actions, so the signature ties each file to the commit it came from. Nothing is added by hand between the source and the signed download.

Reviewed before it ships

Changes reach the release branch only through the repository's maintainers, who review every patch.

Approved by Zynclave

Each signing request is approved by a release approver at Zynclave Tech Private Limited, the project's publisher.

Team roles

Committers and reviewers

Members of the ZynclaveTech organization with write access to the repository.

Approvers

Owners of the ZynclaveTech organization.

Privacy

Tark does not send information about you to anyone. The only sites it contacts on its own, and why, are listed on the privacy page; everything else happens only when you ask for it, such as visiting a site or searching.