Search documentation

Security and compliance

Zapbird keeps your project on your own computer and network. This page describes how it protects that connection, what we do not claim, and how to tell us about a problem.

Last updated 16 November 2026

1. Our approach

The safest data is data we never receive. Zapbird has no accounts and no cloud service that stores projects, and it sends no analytics, so most of the usual risks of a hosted developer tool do not apply. The risks that remain are on your local network and in the files you download. Those are where we spend our effort.

2. The connection between your computer and your phone

  • Encryption. The command creates a fresh TLS certificate every time it starts. The QR code carries that certificate, and the runner app trusts only that one. Another computer on the same Wi-Fi therefore cannot pose as yours.
  • Local only. The server accepts only local network addresses.
  • Pairing. The QR code and the link hold a secret. By default it works for 24 hours (you can set it from 1 to 24 hours with --qr-hours), and it stops when you stop the server. Asking for a new QR code ends the old one, and --single-use-qr makes a code work once.
  • Pairing by address. If you type an address instead of scanning, the phone shows a six-digit code. You type it in the terminal to allow the phone, or refuse it.

3. Your code and secrets

  • The phone receives compiled bytecode and your assets, such as images and fonts. It does not receive your source files unless you turn on phone editing.
  • A project that holds server-side keys, such as a payment secret key, cloud provider keys or a database service key, is refused before it is sent. You can override that with --allow-secrets, and we do not advise it.
  • Values you pass with --dart-define are compiled into the app. Pass only keys that are safe to ship inside an app.
  • Phone editing is off unless you start with --allow-phone-edit, and it reaches only the Dart files in lib/.
  • Output and errors that your project prints go to your terminal with keys, tokens and passwords hidden.

4. Downloads and the supply chain

The published list of SDK versions is signed by the publisher, and a list whose signature does not check is not used. Every download is checked against its checksum, and each file inside it against its own hash, before anything is installed. The status page shows whether the download address is reachable. The full technical description is in the documentation.

5. The website

The website is a static site. It has no accounts, no database and no login, and it has no payment forms. That removes most of the ways a website gets attacked. It is served over HTTPS by our hosting provider.

6. What we do not claim

We prefer to be plain about this. Zapbird does not currently hold a SOC 2 report, an ISO/IEC 27001 certificate or any other formal security certification, and we have not commissioned a public third-party penetration test. We do not process customer content, so many of the controls those frameworks check do not apply to us in the same way. If an organisation needs evidence for a review, the enterprise trust page says what we can provide. We will update this page if that changes, and we will not describe ourselves as compliant with a standard we have not met.

7. Reporting a vulnerability

If you think you have found a weakness in Zapbird, please write to security@zapbird.dev. It helps if you include what you found, the steps to reproduce it, the version of the command and the runner app, and what an attacker could do with it.

What you can expect from us:

  • We will acknowledge your report within five working days.
  • We will tell you what we find, and keep you updated while we work on a fix.
  • We will credit you in the release notes if you want us to, and say nothing if you prefer.

What we ask of you: give us a reasonable time to fix the problem before you make it public, do not access or change other people’s data, do not degrade the services for others, and test only against your own devices and projects. If you follow that, we will not take legal action against you for good-faith research, and we will say so if anyone asks. This is not a bug bounty, and we do not offer payment for reports at this time.

8. If something goes wrong

If we learn of a security incident that affects people’s data or the integrity of the downloads, we will investigate, fix it, and publish what happened and what to do, on this website and in the documentation. Where the law requires it, we will notify the people and the authorities concerned within the time limit that applies.