Privacy Policy — busy.dev
Effective date: 2026-11-17 Last updated: 2026-11-19
1. Who we are
busy.dev is operated by EFIRITY PTE. LTD., which is the data controller for the personal data described here.
Registered address: 68 Circular Road #02-01, Singapore 049422 Company registration number: UEN 202402844G Website: https://busy.dev/apps/busydev/support
Privacy contact: hi@busy.dev
2. What busy.dev does
busy.dev is a mobile app for Android: Every autopilot app build, live: stages, progress and LIVE badges.
Anyone can create a busy.dev account in the app, with a Google account or with an email address and a password; the app then loads its content from launch.busy.dev over HTTPS. A new account sees one sample project (Nilbite, an app our autopilot built) and no one else's data; accounts we have authorised also see the builds they are allowed to see. On your phone the app keeps: the sign-in session; your settings (filter, live updates, haptics, theme); build pictures; for notifications, a random per-install device ID and the last notification registration ID. The app is excluded from Android backup, so none of this is copied to your Google account backup.
Support chat. Help & support (in Settings, on the sign-in screen and on the sample project's banner) opens our support chat, run for us by Busymate AI. It is optional. We process what you write and, only when you choose the microphone or voice mode, what you say; the app asks for the microphone permission only the first time you tap the microphone. When you are signed in, the app tells the chat who you are (your user ID, email address and app language) so the assistant recognises you, and the assistant can look up your own busy.dev information to answer you: the apps you can follow with their progress and status, and your app ideas with their status. It submits a new app idea for you only after repeating it back to you and getting your yes. Signing out clears the chat from the app. Support chat conversations are kept by our chat provider (Busymate AI) until they are erased. Deleting your account does not erase them automatically: write to hi@busy.dev and we will erase them.
3. What we collect, and why
1. Personal info
What: Email address, user ID, and your name if you sign in with Google
Why: To create your account, sign you in, send the account emails (the sign-up and password-reset codes), decide what the account may see, and, when you use the support chat while signed in, let the assistant recognise you. If you tick "Email me about busy.dev" when you sign up (or turn it on later in Settings), we also email you news about busy.dev; it is off unless you choose it, and every such email has an unsubscribe link.
Purposes declared to the app stores: Account management, App functionality, Developer communications (only if you opt in)
Can you avoid it? Your email address and user ID are needed for the account. Your name is stored only if you sign in with Google (it comes from your Google profile); the email sign-up does not ask for it.
Kept for: While your account exists; deleted when you delete your account.
2. Device or other IDs
What: A random ID for this installation of the app; the device integrity verdict from Google Play Integrity (whether the app and the phone look genuine); and, if you allow notifications, the push registration token of your phone
Why: The integrity verdict protects the service against abuse: it is recorded with your account and never decides whether you can use the app. The push token and installation ID deliver build notifications to this phone.
Purposes declared to the app stores: App functionality, Fraud prevention, security, and compliance
Can you avoid it? The installation ID and the integrity verdict are recorded for every signed-in installation. The push token is optional: without notifications the rest of the app works.
Kept for: While your account exists; deleted when you delete your account. The push token is deleted when you sign out.
3. Messages
What: Support chat: the messages you write in Help & support
Why: To answer your support questions. Busymate AI processes them on our behalf (section 6).
Purpose declared to the app stores: App functionality
Can you avoid it? Optional: the support chat is never required to use the app.
Kept for: Support chat conversations are kept by our chat provider (Busymate AI) until they are erased. Deleting your account does not erase them automatically: write to hi@busy.dev and we will erase them.
4. Audio files
What: Support chat: what you say, only when you tap the microphone or use voice mode
Why: To turn what you say into a support question and answer it. Busymate AI processes it on our behalf (section 6).
Purpose declared to the app stores: App functionality
Can you avoid it? Optional: only when you tap the microphone; the app asks for the microphone permission on that first tap, and you can refuse it and type instead.
Kept for: Support chat conversations are kept by our chat provider (Busymate AI) until they are erased. Deleting your account does not erase them automatically: write to hi@busy.dev and we will erase them.
5. Photos and files
What: Chat: the images and PDF files you choose to attach with the attach (+) button
Why: So the assistant can read what you attached and answer you. Busymate AI processes them on our behalf (section 6).
Purpose declared to the app stores: App functionality
Can you avoid it? Optional: only the files you pick yourself are sent. The app opens your phone's own file or photo picker (or, on iPhone, the camera if you choose Take Photo) and reads nothing else on your phone.
Kept for: Chat conversations, with their attachments, are kept by our chat provider (Busymate AI) until they are erased. Deleting your account does not erase them automatically: write to hi@busy.dev and we will erase them.
6. Crash logs and diagnostics
What: When the app crashes or hits an error: a crash report with the error and where in the app's code it happened, the app version, the Android or iOS version and the phone model. Before a report leaves your phone, the app removes email addresses, phone numbers, sign-in tokens and codes from it. It carries no account ID, no name and no install ID, and the app does not send usage or session data.
Why: To find and fix crashes. Sentry stores the reports on our behalf (section 6).
Purposes declared to the app stores: App functionality (not linked to you)
Can you avoid it? Reports are sent automatically when the app crashes; they are anonymous.
Kept for: Up to 90 days at Sentry, then deleted.
7. App ideas, drafts and notes
What: The app ideas you write or dictate (title, description, notes and saved drafts) and, if you use Build idea with AI, that chat. Ideas are stored in your own workspace on portal.busy.dev; the Build idea chat is run for us by Busymate AI.
Why: To keep your ideas, show you their status, and let us review them and contact you about them.
Purposes declared to the app stores: App functionality
Can you avoid it? Optional: nothing is stored unless you write or submit an idea.
Kept for: Until you delete the idea or your account. The Build idea chat is kept by Busymate AI as described for the support chat.
What we do not collect
- Analytics or advertising identifiers, and no usage or session tracking; there are no ads. The only diagnostics are the anonymous crash reports in section 3.
- Your location, contacts or anything else on your phone. Files and photos only when you attach them in the chat yourself (section 3).
- Settings (filter, live updates, haptics, theme): kept only on your phone.
- Build pictures: kept only on your phone.
- Your voice, unless you tap the microphone in the support chat.
4. Device permissions
The app asks for these permissions. Each one is listed with what it is used for. If a permission is optional, declining it is described here too.
android.permission.INTERNET(Android) — Signing in (bl.efir.is), loading builds (launch.busy.dev) and the support chat: the whole app.android.permission.POST_NOTIFICATIONS(Android) — Build notifications (submitted, live, stalled, owner needed). Asked once after you sign in, with an explanation. Optional — Without it you get no notifications; everything else works.android.permission.ACCESS_NETWORK_STATE(Android) — Added by Firebase Cloud Messaging: checks the connection before it delivers a notification.android.permission.WAKE_LOCK(Android) — Added by Firebase Cloud Messaging: keeps the phone awake while a notification is handed to the app.com.google.android.c2dm.permission.RECEIVE(Android) — Added by Firebase Cloud Messaging: receives notifications from Google Play services.android.permission.RECORD_AUDIO(Android) — The microphone and voice mode of the support chat. Asked only the first time you tap the microphone, never when the chat opens. Optional — Without it you type your questions; the chat works the same.android.permission.MODIFY_AUDIO_SETTINGS(Android) — Lets the support chat route audio while you use the microphone or voice mode. No prompt.
5. Legal bases (GDPR / UK GDPR)
Where the GDPR or UK GDPR applies, we rely on:
- Performance of a contract — Creating and running your account so you can sign in and see the sample project and the builds you are allowed to see, and answering you in the support chat.
- Legitimate interests — Keeping the service secure: recording the device integrity verdict and refusing sign-ups from disposable email services.
6. Who we share data with
We use the following service providers ("processors"). They act on our instructions and may not use your data for their own purposes.
| Provider | What they do for us | What they receive |
|---|---|---|
| OVH (server hosting) | Hosts our own sign-in service (self-hosted Supabase Auth at bl.efir.is) and its database; also hosts Signalbox, our own notification service (api.sb.efir.is) | Your account record: email address, user ID, your name if you sign in with Google, and a salted hash of your password if you use one; the device integrity records; for notifications: your push registration token, a random per-install device id, app version, Android version and phone model |
| Sentry (Functional Software, Inc.) | Stores crash reports so we can fix crashes | Anonymous crash reports: the error, app version, OS version and phone model, with personal data removed on the phone; no account or install ID |
| Mailgun (email delivery) | Sends the sign-up and password-reset codes for email accounts | Your email address and the code email we send you |
| ngrok | Secure tunnel that serves launch.busy.dev, the address the app loads builds from | The app's HTTPS requests in transit, including your access token and your IP address |
| Google Firebase Cloud Messaging | Delivers build notifications to your phone | Your device's push registration token and the notification content (app name, stage, link) |
| Sign in with Google (only if you choose it), and Google Play Integrity, which tells us whether the app and the phone look genuine | If you sign in with Google: the sign-in request (Google already holds your Google account). For Play Integrity: an integrity token from the app, which our server sends to Google to read the verdict | |
| Busymate AI | Our support chat (Help & support in the app). It uses AI, possibly in other countries, to answer you and, when you are signed in, to look up your own busy.dev information for you | What you write in the chat; the images and PDF files you attach; what you say, only when you choose the microphone or voice mode; and, when you are signed in, your user ID, email address and app language, plus the busy.dev information the assistant looks up for you (described in section 3) |
We do not sell personal data, and we do not share it with data brokers or advertising networks.
International transfers
Our servers and service providers may be located outside your country, including in the United States (ngrok, Google, Sentry). Our support chat provider (Busymate AI) may process your messages in other countries. The specific transfer mechanism has not been documented and is one of the items flagged for legal review.
We also disclose data where we are legally required to — for example to comply with a lawful request from a competent authority — and to establish or defend legal claims.
7. How long we keep it
- Your account (email address, user ID, name if you use Google, password hash, device integrity records) — While your account exists. When you delete your account we delete the sign-in account, our record of what it may see, the workspaces only you own, your notification registrations and its device integrity records.
- Support chat conversations — Support chat conversations are kept by our chat provider (Busymate AI) until they are erased. Deleting your account does not erase them automatically: write to hi@busy.dev and we will erase them.
- The sign-in session on your phone — Until you sign out or uninstall the app. Signing out deletes it from the phone, together with the support chat's data in the app.
8. Your rights and how to use them
Depending on where you live you may have the right to access, correct, delete, port, restrict, or object to our processing of your personal data, and to withdraw consent where processing is based on consent. You may also complain to your local data protection authority.
To exercise any of these, email hi@busy.dev.
Deleting your account
You can delete your account and the data attached to it:
- In the app: In busy.dev: Settings > Delete account. You sign in again to confirm (Apple, Google or your password), and the account is deleted at once, in the app. You can also ask on this page or by email to hi@busy.dev from the address your account uses; signing out alone only removes the session from your phone.
- On the web: https://busy.dev/apps/busydev/delete-account
Your sign-in account on bl.efir.is (email address, user ID, your name if you used Google or Apple, password hash), our record of what the account may see, the portal.busy.dev workspaces only you own with their ideas, your notification registrations, and the device integrity records linked to it. If you used Sign in with Apple, we also ask Apple to revoke the app's tokens.
Support chat conversations are kept by our chat provider (Busymate AI) until they are erased. Deleting your account does not erase them automatically: write to hi@busy.dev and we will erase them.
9. Security
All traffic between the app, bl.efir.is and launch.busy.dev runs over HTTPS, and the app accepts only the certificate authorities it pins for those two addresses. The support chat runs over HTTPS too. The sign-in session is stored on your phone encrypted with a key held in the Android Keystore, and it is never included in a backup.
All data busy.dev sends off your device travels over encrypted connections (TLS/HTTPS).
10. Children
busy.dev is not directed to children. The minimum age to use it is 18. We do not knowingly collect personal data from anyone below that age; if you believe a child has given us data, email hi@busy.dev and we will delete it.
11. Cookies and similar technologies
busy.dev does not use cookies or similar tracking technologies.
12. Changes to this policy
We may update this policy. When we do, we will change the date at the top, and — where the change is significant — tell you in the app or by email before it takes effect.
13. Contact
EFIRITY PTE. LTD. 68 Circular Road #02-01, Singapore 049422 hi@busy.dev
Generated by legal/ from a project profile. Not legal advice. Have a lawyer read this before it goes on a store listing.