Included with every paid KnytX plan — Shield, Vigil, Scam Shield, Score, and the deepfake/voiceprint tools in one audited app.

Open source · launching soon

Privacy shouldn't require an app you can't audit.

Read the code. Verify the build yourself.
KnytX Mobile is an open-source (GPLv3) privacy app with no default telemetry — App Store, Google Play, and F-Droid at launch. Free with every paid plan.
Launching soon

iOS and Google Play depend on Apple's and Google's own distribution infrastructure — we can't make them behave like F-Droid. Here's exactly where each store diverges. Read the full picture ↓

GPLv3
License
0
Default telemetry endpoints
3
Distribution channels
Reproducible
Build artefacts

Open source isn't a marketing badge. It's the architecture.

GPLv3 licensed

The mobile codebase is GPLv3 — copyleft, so it can’t be quietly relicensed or closed. Any fork or modification stays open, deliberately.

No default telemetry

Out of the box, the app sends nothing to us: no crash analytics, no usage pings, no anonymous identifiers. Diagnostics are opt-in, not opt-out.

Reproducible builds

Every published binary on the App Store, Google Play, and F-Droid can be rebuilt from the tagged commit. F-Droid’s own check publishes with each release.

On-device vs server, documented

Scam Shield’s call verdict, link checks, and SMS filtering run on-device against signed feeds. Broker scans and dark-web lookups run server-side. We document which is which, per feature.

F-Droid distribution

F-Droid is the main open-source Android store. Shipping there is hard: no proprietary dependencies, F-Droid-built binaries, anti-feature labels. We do the work anyway.

Independent security audit

An external security audit is planned before public launch, on an annual cadence after. We’ll publish findings, severity, and remediation status to the trust ledger.

Three stores, one source of truth.

1
Source
At launch, the mobile codebase lives on GitHub with public issues, pull requests, and security advisories. CONTRIBUTING will explain how to file a bug or propose a feature.
GitHub · GPLv3
2
Build
F-Droid builds Android releases from source on their own infrastructure and publishes a reproducible-build verification. App Store and Play releases share the same tagged commit.
Reproducible from tag
3
Distribute
Three channels: App Store for iOS, Google Play for Android-with-Play, F-Droid for Android-without-Play. All three carry the same feature set.
iOS · Play · F-Droid

Why open source

A privacy app you can’t audit is one you have to trust — KnytX Mobile ships public source, GPLv3, and no default telemetry instead.

Privacy is the wrong category to ship a closed-source mobile app in. Across the US mainstream privacy industry, closed-source, telemetry-on-by-default apps are the rule, not the exception. Several of the biggest have been caught quietly shipping usage data — we’ve written up the documented cases.

KnytX Mobile starts at the opposite default: public source, GPLv3, no default telemetry. We ship to F-Droid alongside the App Store and Google Play, because the open-source audience is exactly who this app should reach.

What “open source” buys you

You don’t have to trust our claims — you can read the code, run a network monitor, and check F-Droid’s reproducible-build result yourself.

A privacy app you can read end to end is a different product from one you have to trust. You don’t have to trust our claim that Scam Shield’s call verdict runs on-device — you can read the code. You don’t have to trust our claim about default telemetry — run a network monitor on a fresh install and check. And you don’t have to trust that the F-Droid build matches the Google Play build. F-Droid runs its own reproducible-build verification and publishes the result.

This is the difference between “we promise” and “you can check”.

What we are honest about

On iOS, the app depends on Apple’s stores; iOS doesn’t allow alternative app stores in every country. The Google Play build depends on Google’s store and runs Play Services on devices that have them. F-Droid is the cleanest channel: fully open-source, reproducible-build checks, no proprietary dependencies. It’s the home for users on de-Googled Android. We can’t make iOS or Google Play behave like F-Droid. What we can do is ship to all three and document where each one diverges.

We’ll also commission an external security audit and publish the report — findings, severity, remediation status — to the trust ledger. The first audit is planned before public launch, with an annual cadence after. Audit-driven security is more honest than self-attestation.

See the full Mobile App Permissions page for a per-permission breakdown of every Android and iOS permission the app requests.

Downloads

The app isn’t published yet. At public launch it ships to all three stores; join the waitlist to hear when.

  • iOS — App Store (launching soon)
  • Android with Play — Google Play (launching soon)
  • Android without Play — F-Droid (launching soon)
  • Source and audit reports — open-source page

See also

Distribution details
License GPLv3
Source GitHub · publishing at launch
iOS App Store · launching soon
Android (Play) Google Play · launching soon
Android (FOSS) F-Droid · launching soon
Default telemetry None
Status Waitlist · launching soon

Choose your tier

Open Source
GPLv3. No telemetry. Reproducible builds. Three official distribution channels.
$0/forever
  • Source code (publishing at public launch)
  • No default telemetry — verifiable at launch
  • Reproducible builds across App Store, Play, and F-Droid
  • Independent security audits (planned pre-launch, annual after)
  • Community contributions welcome (post-launch)
View launch plan →
Included
Every Basic, Pro, Family, Team, and Executive plan includes the mobile app at no extra cost.
$0/with any paid tier
  • Scam Shield call and link defence on-device
  • Broker-removal status dashboard
  • Voiceprint enrolment consent surface
  • Same feature set across all channels
  • Same security guarantees as web tier
See pricing →

Who it's for

Privacy-native users who don't trust proprietary mobile apps

If you’ve already left the major US privacy-app vendors over telemetry concerns, this is for you: no default telemetry, opt-in diagnostics, public source, GPLv3.

F-Droid users on de-Googled Android

GrapheneOS, CalyxOS, /e/OS users — the canonical open-source mobile audience. F-Droid is a hard requirement here. Same feature set, no Play Services.

Security professionals who audit their own toolchain

If your job is reading code for a living, this is the app you can actually read. Issues, advisories, and the on-device split are public.

Anyone on a paid KnytX tier

If you’re on any paid tier, the mobile app is included: Scam Shield verdicts, broker-removal dashboard, and voiceprint consent flow. Free to download either way.

Frequently asked questions

Is the source actually public, or is this 'source available' marketing? #
It will be actually public, not ‘source available’. The GPLv3 repo — public issues, pull requests, and security advisories — publishes at public launch; timeline on the open-source page. GPLv3 is copyleft: anyone who ships a fork ships their changes back, so this app can’t quietly become proprietary in a fork that strips the privacy guarantees.
What does 'no default telemetry' actually mean? #
Out of the box, a fresh install sends no usage metrics, crash analytics, anonymous identifiers, or ‘service quality’ pings to KnytX servers. The only outbound traffic is the calls you explicitly make: logging in, syncing your dashboard, downloading Scam Shield feeds. Opt-in diagnostics exist in settings and default to off.
What runs on-device and what runs server-side? #
Call verdicts, SMS link classification, and the reputation-feed lookups for Scam Shield run on-device against signed feeds delivered over HTTPS. Broker scans, dark-web monitoring, deepfake verification, and voiceprint enrolment run server-side because that’s where the underlying data and models live. The on-device versus server split is documented per feature in the source repository and in the app’s settings.
Are the App Store and Play Store builds the same as the F-Droid build? #
Feature parity, yes. Binary identity, no — the App Store build is signed by our Apple Developer account, the Play build by our Play Developer account, the F-Droid build by F-Droid’s own infrastructure. All three are built from the same tagged commit, and F-Droid publishes a reproducible-build verification you can compare against.
Why GPLv3 instead of MIT or Apache? #
Permissive licenses (MIT, Apache 2.0) let a downstream vendor strip the privacy posture out of a fork, ship it as a proprietary product, and keep the changes. Copyleft prevents that. The trade-off is that some commercial third parties won’t link against GPLv3 code — an audience whose practices we want nothing to do with anyway.
Where do I download it? #
iOS: App Store (link in the downloads section below). Android with Play Services: Google Play. Android without Play Services (GrapheneOS, CalyxOS, /e/OS, vanilla AOSP): F-Droid. The downloads section has the direct links and the trust-ledger page covers the signing keys for each channel.

The mobile app the privacy industry should have shipped years ago.

Three stores. One codebase. Reviewable from the first commit. Source repos publish at launch — see the open-source roadmap for the timeline.

Your data stays in the EU Cancel anytime, no lock-in Delete your account and data in 30 days
Get Mobile with Shield