Privacy Policy — Mobile Dev Browser

Effective date: 2 June 2026 Last updated: 2 June 2026

Mobile Dev Browser (“the App”) is published by Grainbox Limited (“we”, “us”, “our”). This policy explains what data the App handles, what leaves your device, and who processes it. For more about us, visit grainbox.com. Questions: privacy@grainbox.com.

This policy covers the Mobile Dev Browser Android application only. Websites you visit through the App have their own privacy policies, which we do not control.


The short version

Mobile Dev Browser is a developer tool, and it is built to keep your data on your device:


1. Data that stays on your device

The following is stored locally on your device only and is never transmitted to us:

DataWhere it livesPurpose
Browsing data — history, cookies, cache, site storageAndroid System WebViewSo pages load and the browser works
Captured console logsLocal app database (Room)So you can inspect console.* output
App settings — default search engine, view preferences, log-retention modeLocal preferences (DataStore)To remember your choices

You can clear this data at any time from within the App (“Clear site data”, “Clear log history”) or by uninstalling the App.

Export / Share is user-initiated. When you tap Share or Export on your console logs, the App hands the content to Android’s standard share sheet so you can send it to an app or destination you choose. We do not receive a copy and we do not control where you send it.

2. Data collected and processed by third parties

To keep the App reliable and improve it, we use two third-party processors. All such data is transmitted over encrypted (HTTPS) connections.

a. Crash and performance diagnostics — Sentry

We use Sentry (Functional Software, Inc.) to receive crash and “app not responding” (ANR) reports so we can fix stability problems. A report may include:

We have deliberately configured Sentry to exclude:

b. Product analytics — PostHog

We use PostHog, Inc. to understand which features are used, at the level of simple counts. All automatic capture is turned off — no screen views, no taps, no deep links, no browsing data. The App sends only these five explicit events, plus an anonymous device identifier and standard technical metadata (device model, OS version, App version) that PostHog attaches automatically:

EventExtra information sentMeaning
app_openednoneThe App was opened
share_button_tappedis_paying_user (true/false)The Share button was tapped
iap_purchase_attemptednoneA purchase was started
iap_purchase_completednoneA purchase succeeded
iap_purchase_failederror_code (a numeric Google Play code)A purchase failed

No console-log content, browsed URLs, or personal information is ever sent to PostHog.

c. Purchases — Google Play Billing

The App offers a one-time in-app purchase to unlock copying/exporting your console logs. Payment is processed entirely by Google Play Billing; we never see your card or payment details. The App receives only a purchase confirmation token from Google so it can unlock the feature and restore it on your devices. Google’s handling of your payment data is governed by Google’s Privacy Policy.

3. What we do not collect

4. Sub-processors

ProcessorRolePrivacy policy
Functional Software, Inc. (Sentry)Crash / error diagnosticshttps://sentry.io/privacy/
PostHog, Inc.Product analyticshttps://posthog.com/privacy
Google LLC (Google Play Billing)In-app purchase processinghttps://policies.google.com/privacy

These providers may process data on servers located in the United States.

5. Data retention

6. Children

The App is a developer utility and is not directed to children under 13 (or under the equivalent minimum age in your country, such as 16 in parts of the EEA). We do not knowingly collect data from children.

7. Your rights and choices

Because the diagnostic and analytics data we collect is anonymous and not linked to your identity, we generally cannot single out or return data about a specific person. You can still:

8. International transfers

Our processors are based in the United States, so data described in Section 2 may be transferred to and processed there. Where required, these providers rely on appropriate safeguards (such as Standard Contractual Clauses) for international transfers.

9. Security

Data sent to our processors is encrypted in transit (HTTPS/TLS). On-device data is protected by Android’s app sandbox. No method of transmission or storage is completely secure, but we configure the App to minimise what is collected in the first place.

10. Changes to this policy

We may update this policy as the App evolves. We will revise the “Last updated” date above and, for material changes, provide a more prominent notice. Continued use of the App after an update means you accept the revised policy.

11. Contact

Grainbox Limited Email: privacy@grainbox.com Web: grainbox.com