Acceptable Use Policy
Zapbird is a tool for building apps on your own devices. This policy says what that does and does not include. It is part of our Terms of Service.
1. The idea
Use Zapbird to build, test and show your own apps, on devices and networks that you own or are allowed to use. Most people never need to read the rest of this page. It exists so that the rules are clear, and so that we can act when someone abuses the services or other people.
2. What you must not do
Harm other people, devices or networks
- Connect the CLI or the runner app to a phone, computer or network you do not own and have no permission to use.
- Scan, probe or test other people’s systems, or try to reach a Zapbird server that is not yours, without the owner’s written permission.
- Use pairing links or QR codes that you did not generate for yourself, or share your own to give strangers access to your computer.
- Build or run software meant to damage, disrupt or gain unauthorised access to a device, an account or a network.
Deceive or abuse
- Create malware, spyware, stalkerware, ransomware, credential stealers or apps that hide what they really do from the person using them.
- Use the services to commit fraud, to phish, to impersonate a person or an organisation, or to mislead people about who you are.
- Break the law that applies to you or to us, or use the services to help someone else do so.
- Infringe other people’s copyright, trademarks, trade secrets, privacy or other rights.
Misuse the software and the downloads
- Get around, disable or tamper with the security checks in the software, including the signature and checksum checks on downloads and the protections on the connection to your phone.
- Overload, scrape or attack our website, our download address or our status page, or use automated tools in a way that harms them. Reasonable use of the install script, such as in your build pipeline, is fine.
- Resell, rent out or offer the services to other people as a hosted service, as set out in the Terms of Service.
- Remove or hide our notices, or use our name or logo in a way that suggests we back your product.
3. What is fine
Building apps for clients or for your employer. Using Zapbird in a company, a school or a bootcamp. Writing about Zapbird, comparing it with other tools, and making tutorials. Looking for security problems in the software in good faith and reporting them to us (see section 5). Using it on a private network you control, including a lab with several test phones.
4. What happens if the policy is broken
Where we can, we start with a conversation. Depending on how serious the problem is, we may ask you to stop, block access to the downloads or the website from the addresses involved, end your licence under the Terms of Service, remove content, or report the matter to the authorities. We may act without warning where there is a risk to people, to the services or to our legal position. If you think we got it wrong, write to support@zapbird.dev and we will look again.
5. Reporting abuse and security problems
If you see a breach of this policy, tell us at support@zapbird.dev. If you think you have found a weakness in the software, please follow the steps on the security page and write to security@zapbird.dev. Good-faith research that follows those steps is welcome and is not a breach of this policy.
6. Changes
We may update this policy as the services change. The date at the top shows the latest version, and material changes are announced as described in the Terms of Service.