Privacy Policy
Zapbird runs on your own computer and your own network. It has no accounts and no analytics, so there is very little for us to collect. This page explains exactly what there is.
1. Who we are
Zapbird is run by JAGO INTELLIGENCE. For the personal data described in this policy we are the “controller”, which means we decide why and how it is used. You can reach us about privacy at privacy@zapbird.dev. We have not appointed a data protection officer, because our processing is small and does not call for one, and the address above goes to the person who handles these requests.
This policy covers the zapbird command, the SDK downloads, the runner app, this website and the documentation, and the messages you send us. It does not cover the apps you build, which are yours, or other sites we link to.
2. The short version
- There is no Zapbird account and no cloud service that stores your projects.
- The command and the runner app send no analytics, tracking or crash reports to us.
- Your code travels from your computer to your phone over your own network and nowhere else.
- The website has no advertising, no trackers and no cookies. It keeps a few settings in your browser, and those stay on your device.
- We do not sell personal data, and we do not share it for advertising.
- The data we do have comes from three places: ordinary hosting logs, messages you send us, and what your browser sends to a service you choose to use from our pages (for example, playing a video).
3. What we collect, and why
The runner app
The runner app connects your phone to the zapbird command on your computer. While it does that, it handles:
- Pairing details. The address and the one-time secret from the QR code or link are held in memory while the app is running. They are not written to storage and are not sent to us.
- Recent project names. The app can list the projects you opened in the current session. The list is cleared when the session ends.
- Your app and its data. The compiled app is sent from your computer to your phone. It stays between those two devices.
- The camera. If you scan a QR code to pair, the camera reads the code on the phone. The pictures are not saved or sent anywhere.
The apps you run may ask for phone permissions of their own, such as location or the microphone. That is your app talking to your phone. Zapbird does not collect the result.
The command
The command runs on your computer and serves your project to your phone on your local network. It does not upload your source code and does not report your usage to us. When you install it, or an SDK, it downloads files from our download address. That request reaches our storage and delivery provider, which sees what any web server sees (see “Hosting and logs” below).
Hosting and logs
The website and the download files are served by hosting and content delivery providers. When your device asks for a page or a file, those servers receive and may log your IP address, the time and the address of the file, the type of browser or tool you used, and how much was sent. We use this information to keep the services working, to protect them from abuse, and to understand in broad terms whether they are being used. We do not use it to identify you, and we do not combine it with anything else. Retention is set by the provider, and is usually a matter of days or weeks.
Messages you send us
If you write to us, for example to support@zapbird.dev or privacy@zapbird.dev, we receive your name (if you give it), your email address, and whatever you tell us. We use it to answer you, to look into a problem, and to improve Zapbird. We keep an email thread for as long as we need it to deal with your request and any follow-up, and normally delete it within two years after the last message. If you report a security problem, we keep the report for as long as the issue needs.
Things your browser does on our pages
A few features of the website make your browser contact other services. We do not control what those services do with the information, so here is what happens:
- GitHub star count. The page asks GitHub’s public programming interface for the number of stars on our repository. GitHub receives your IP address and the usual browser details, as it would if you visited github.com.
- Videos. A video from YouTube loads only after you open it. We use YouTube’s privacy-enhanced address (youtube-nocookie.com), which avoids setting tracking cookies until you play it. YouTube, which is operated by Google, then handles your data under its own policy.
- The status page. The page at zapbird.dev/status asks our own download address whether it is responding. This sends a request like any file download.
- Links. The website links to GitHub, Discord, social networks and the app stores. Once you follow a link, that service’s own policy applies.
What stays on your device
The website stores a few settings in your browser’s local storage: your light or dark theme, the operating system tab you picked in the documentation, and whether you marked a documentation page as helpful. These settings never leave your device and we do not read them. You can remove them by clearing the site data in your browser. The Cookie Policy has the details.
Things we do not collect
We do not run analytics, advertising pixels, session recording, fingerprinting or A/B testing tools. We do not collect your name, your location, your contacts, your device identifiers or your project contents through the services. We do not use your data to train machine learning models.
4. Our legal bases
If the law of your country (for example the GDPR in the European Union and the UK GDPR) requires a legal basis for our use of your data, ours are:
- Legitimate interests, for hosting logs and security. We need to keep the services running and safe, and the impact on you is small. You can object (see section 8).
- Performing a contract or taking steps before one, and legitimate interests, when we answer your messages and support requests.
- Consent, where we ask for it, for example when you choose to play an embedded video. You can withdraw it at any time by closing the video and clearing your browser’s site data.
- Legal obligation, where we must keep or share information to follow the law.
5. Who we share data with
We do not sell personal data, and we do not share it for cross-context behavioural advertising. We share it only with:
- Service providers that host the website and the download files, deliver them, and handle our email. They may process data only on our instructions and to provide their service to us.
- Professional advisers, such as lawyers and accountants, when we need their advice, under a duty of confidence.
- Authorities and others, where the law requires it, to enforce our terms, or to protect people’s safety or our rights. We ask for a proper legal basis first.
- A buyer or partner, if the business is merged, sold or reorganised. The new owner would have to keep to this policy or tell you before changing it.
The blog’s text and pictures are written in a hosted publishing tool. It stores our posts. It does not receive data about the people who read them.
6. International transfers
Our providers may run servers in several countries, so your data may be processed outside the country where you live, including in countries whose data protection rules differ from yours. When we transfer personal data out of the European Economic Area, the UK or another place that restricts transfers, we rely on an adequacy decision, the standard contractual clauses approved by the relevant authority, or another lawful mechanism. You can ask us for details by writing to privacy@zapbird.dev.
7. How long we keep data
- Hosting logs: for the period the provider sets, usually days or weeks.
- Support and privacy emails: for as long as we need to deal with the request, and normally no longer than two years after the last message.
- Security reports: for as long as the issue and any fix need.
- Records we must keep by law: for the period the law sets.
When the time is up, we delete the data or make it anonymous.
8. Your rights
Depending on where you live, you may have the right to:
- ask whether we hold personal data about you, and get a copy;
- have wrong data corrected, and incomplete data completed;
- have your data deleted;
- restrict how we use it, or object to a particular use, including use based on our legitimate interests;
- receive the data you gave us in a portable format;
- withdraw consent where we rely on it, without affecting what we did before; and
- complain to the data protection authority where you live, work, or think the problem happened. In the UK that is the Information Commissioner’s Office, and in the EU you can find your authority on the website of the European Data Protection Board.
To use any of these rights, write to privacy@zapbird.dev. We may need to check who you are before we act, and we do not want to be tricked into handing your data to someone else. We answer within one month (or the shorter period your law sets), and we may take longer for complex requests, in which case we will tell you. There is no charge unless a request is clearly unfounded or excessive. Because we hold so little, the honest answer is often that we do not have any data about you, and we will say so.
California and other US states
If you live in California, Colorado, Virginia or another US state with a consumer privacy law, you may have the right to know what personal information we collect, to ask for it to be deleted or corrected, and to opt out of the sale or sharing of your personal information. We do not sell personal information and we do not share it for cross-context behavioural advertising, so there is nothing to opt out of. We will not treat you differently for using your rights. You can make a request, or have an authorised agent make one for you, at the address above.
9. Children
Zapbird is a developer tool and is not directed at children. We do not knowingly collect personal data from anyone under 16 (or the lower age that applies in your country for consent to online services, where that is less than 16). If you think a child has sent us personal data, tell us at privacy@zapbird.dev and we will delete it.
10. How we protect data
We keep what we hold to a minimum, which is the best protection there is. The command and the runner app protect the connection between your computer and your phone with TLS, and the security page describes the measures in detail. We use access controls on our systems and restrict our email and hosting accounts to the people who need them. No system is perfectly secure. If a breach affects your personal data in a way that creates a risk to you, we will tell you and the relevant authority as the law requires.
11. Automated decisions
We do not make decisions about people by purely automated means that have legal or similarly significant effects.
12. Do Not Track
We do not track you across websites, so there is nothing to change when your browser sends a Do Not Track or Global Privacy Control signal. We respect it anyway.
13. Changes to this policy
We will update this page when what we do changes, and change the date at the top. If Zapbird ever starts collecting data it does not collect today, we will say so here before it starts, and where the law requires it, we will ask for your consent first.
14. Contact
Questions, requests and complaints about privacy are welcome at privacy@zapbird.dev. The controller is JAGO INTELLIGENCE. If you are not happy with our answer, you can contact your local data protection authority.