Enterprise trust
If you are reviewing Zapbird for a team, these are the answers to the questions that usually come up. We keep them short and we do not stretch the truth.
What data does Zapbird process?
None of your content. Your source code, assets and app data go from your computer to your phone over your own network and do not pass through us. There is no Zapbird account, so we hold no user profiles, no usage records and no project data. What we do have is described in the Privacy Policy: ordinary server logs at our hosting providers, and the messages people send us.
Do we need a data processing agreement?
Usually not, because we do not process your company’s personal data on your behalf. If your review decides one is needed, write to privacy@zapbird.dev and we will talk it through.
Who are the subprocessors?
We have none for customer content, because we do not receive it. We use hosting and content delivery providers for the website and the download files, and an email provider for our mailboxes. They handle the ordinary logs and messages described in the Privacy Policy. We can give you the current list of these providers on request.
Is there single sign-on, user management or an audit log?
No, because there is nothing to sign in to. Zapbird runs on each developer’s own computer and phone. Access is controlled by the pairing step between those two devices, which uses a short-lived secret and a one-time certificate, as the security page explains.
How is the software delivered, and how do we know it is genuine?
The command and the SDK files are downloaded from our download address. The list of SDK versions is signed, and every download is checked against its checksum and the hashes of the files inside it before anything is installed. A team that wants more control can fetch the files itself and have them reviewed before they are used.
Which certifications do you hold?
None at this time. We do not hold a SOC 2 report or an ISO/IEC 27001 certificate, and we have not published a third-party penetration test. We would rather say that than imply otherwise. Because we do not process customer content, the question is often about the developer’s environment rather than about us, and we can help your team document how Zapbird behaves on a developer machine and a network.
Can we use it for commercial work?
Yes. The licence in the Terms of Service covers developing, testing and demonstrating your own apps, including for an employer or a client. It does not allow offering Zapbird to others as a hosted service.
What happens if there is a vulnerability or an incident?
Researchers can report problems to security@zapbird.dev. We acknowledge reports within five working days, fix confirmed issues, and publish what happened and what to do. If an incident affects personal data, we notify the people and the authorities concerned as the law requires.
What about support and availability?
Support is by email and the community channels on the support page, without a guaranteed response time. There is no service-level agreement at this time. Zapbird works on your own network and does not need our servers to run, apart from the downloads, so an outage on our side does not stop a team that has already installed it. The status page shows the state of the downloads and the website.
Who is the contracting party?
JAGO INTELLIGENCE. For a vendor questionnaire, a custom agreement or a question this page does not answer, write to support@zapbird.dev. Tell us what your reviewers need, and we will answer in writing.