Privacy
Privacy Policy
ADBKit is a local-first browser workspace for Android developers and QA engineers. Your device data is handled in your browser and is never sent to us.
Data that stays on your machine
When you connect a device, over USB or over your network, the following travels only between your browser, your own computer (through the ADBKit agent, for network connections) and your Android device:
- Screen frames and input events
- Screenshots and screen recordings
- Device logs
- Files you browse, upload, or download
- APK files you install
- Device serial numbers and other device identifiers
ADBKit has no server that receives this data, and we cannot see it.
The ADBKit agent
A web page cannot open network connections to a phone by itself, so for TCP/IP and Wireless debugging you run the small ADBKit agent on your own computer. It listens only on your computer (127.0.0.1), answers only pages you allow, connects only to your phone on your own local network, and sends nothing to ADBKit or anyone else. It saves one file, its own key, in a folder in your home directory. You can read its source code and verify the download at adbkit.com/agent/source.
What we collect
The workspace needs no account. The website pages (home, blog and legal pages, not the workspace) load Google AdSense, which may show ads there. Ad personalization is off, and ads never use your device content.
We use Google Analytics 4 to count visits and see which pages and tools are used, so we can improve ADBKit. It receives the pages you open, which feature you used (for example “opened Logcat” or “took a screenshot”), whether it worked, and standard technical details such as browser, language and approximate location. It never receives device content or identifiers: no screen frames, screenshots, files, APKs, logs, serial numbers, device model, package names, file names, or anything you type.
- In the European Economic Area, the United Kingdom and Switzerland, analytics is off until you choose “Allow” on the notice. Until then Google receives only cookieless signals that do not identify you or your browser.
- Everywhere else, analytics is on by default. You can turn it off at any time with “Analytics settings” at the bottom of every page.
Either way, the workspace works the same whether analytics is on or off.
Accounts and purchases
You can sign in with Google on “My account” and on the checkout, to see or buy ADB Kit Pro for the ADB Kit apps. Signing in uses Google Firebase Authentication, which keeps your account ID, email address and name. Your purchases and Pro status are kept by RevenueCat under that account ID, so Pro follows you to the ADB Kit apps signed in with the same account. Payments on the web are handled by Paddle, the reseller of record, which receives your payment details and email to process the order and send your receipt. ADBKit never sees your card details. None of this is linked to your device data, which still never leaves your browser.
Like any website, the host serving ADBKit may keep standard server logs (such as IP address, user agent, and requested URL) for security and reliability. These logs do not contain device data.
Browser and device permissions
Connecting a device needs two separate approvals, both under your control:
- Browser permission — your browser asks you to choose a USB device through WebUSB.
- Local network access — newer versions of Chrome and Edge ask whether this site may connect to apps on your computer. This is needed only to reach the ADBKit agent.
- Android authorization — your device asks you to allow USB debugging from this computer.
You can revoke either at any time: remove the site permission in your browser, or revoke USB debugging authorizations in Android developer options. Disconnecting in ADBKit closes the connection and stops all streams.
Files placed on your device
To mirror and control the screen, ADBKit pushes an open-source scrcpy server helper to a temporary location on your device. This file is served from ADBKit's own origin, not a third party.
Cookies and local storage
ADBKit itself sets no advertising cookies. Google AdSense, which the website pages load, may set its own cookies according to Google's policies. Google signals and ad personalization are turned off on our side. When analytics is on, Google Analytics stores cookies with a random identifier to tell visits apart. We remember your analytics choice in your browser's local storage, and you can change it with “Analytics settings”. If you sign in, Firebase keeps your sign-in session in your browser's storage until you sign out. Your browser may store the USB permission you grant and, for the ADB connection, a key used to identify this browser to your device. The key stays in your browser and is never uploaded. Clearing site data removes it, and your device will ask for authorization again next time.
Retention
We hold no device data, so there is nothing to retain or delete on our side. Account and purchase records are kept while your account exists, and as long as tax and accounting rules require for purchases. Screenshots and screen recordings open in an editor that runs entirely in your browser. They are kept in that tab’s memory only, and are cleared when you disconnect or close the tab. Screenshots, recordings, logs and downloaded files are saved only where you choose on your own computer, and you manage them yourself. Server logs are kept only as long as needed for security and reliability.
Security
Because device data never leaves your browser, it is not exposed to our servers. The site is served over HTTPS. Use ADBKit only on computers you trust, and only connect devices you are allowed to debug. Anyone with access to your unlocked browser session can use the device connection while it is open.
Your rights
Depending on where you live, you may have rights to access, correct or delete personal data, or to object to its processing. Without an account we hold no personal data about you beyond standard server logs. If you have an account, email us to get a copy of it or to delete it, and we will respond.
Third parties
ADBKit does not sell personal data. These services process data described above on our behalf, under their own terms and privacy policies: Google LLC (Analytics, AdSense and Firebase Authentication), RevenueCat (purchase records) and Paddle (payments, as reseller of record). Links to other sites, such as GitHub, are governed by those sites' own policies.
Children
ADBKit is a developer tool and is not directed at children under 13.
Changes
If this policy changes, we will update the date above and describe what changed before it takes effect.
Contact
Questions or requests about your privacy? Email us at cellhubsapp@gmail.com.