Privacy Policy

Effective date: October 15, 2026

1. Personal Information We Collect

The app does not require sign-up and does not transmit to or store on its own servers any directly identifiable personal information such as your name, phone number, or email address.

The app does not collect the addresses of websites the user visits, search terms, web page content, or the content of forms the user fills in.

However, the following information may be stored on the device to provide browser features.

• Recent visit history
• Home screen shortcuts and favorites
• App settings such as text size, dark screen, and bottom navigation
• List of downloaded files and download status

To build a better app and fix errors quickly, the app may use Analytics and Crashlytics provided by Google Firebase. In this process, the following may be processed: whether the app was launched, app language, text scale range, light/dark screen setting, bottom navigation setting, anti-phishing and pop-up blocking settings, whether buttons and features are used, whether the app is set as the default browser, error type, a general category or a short non-identifying host hash of the site where an error occurred, device and app version information, and crash logs.

If the app was installed through Google Play, campaign identifiers provided by Google Play Install Referrer (e.g., utm_source, utm_medium, utm_campaign) may be processed to understand how users came to the app. In this case, the full original referrer is not stored or transmitted; only the necessary identifiers are used, on a limited basis.

To respond quickly to web page connection errors or site compatibility issues, the app may receive compatibility settings that are already built into the app through Firebase Remote Config. These settings are used only to turn features on or off and to set exceptions based on non-identifying host hashes, and do not include full visited addresses, search terms, web page content, entered content, or download file names.

The usage flows recorded with Firebase do not include the full addresses of websites the user visits, search terms, web page titles, web page content, the content of forms the user fills in, or download file names.

Notifications are off at first. Notifications are divided into two types, and consent is obtained separately for each.

• Notices: updates, important notices, and feature information
• Offers & ads: Big Text Browser's own offers and advertising information. From 9 p.m. to 8 a.m., they are sent only if you have separately consented. Advertising notifications show “(Ad)” in the title and state the sender (By My Side Labs, mark@bymysidelabs.com) together with a free way to opt out. When you consent or withdraw consent, the app shows you the date and the result on screen.

If either one is turned on, the following information is stored on the notification server (Cloudflare) operated by the developer (By My Side Labs) in order to send notifications: a randomly generated identifier for each app installation, the Google Firebase Cloud Messaging push token, app language, app version, and the consent status of each notification type with the time of consent or withdrawal. This information is used only to send notifications and to match them to the recipient's language. Your name, phone number, email address, and browsing history are not sent to the server.

You can view past notices again under Big Text Browser Settings > Notifications > Notification inbox in the app. The Notification inbox list is stored on the device, and the identifier above and the app language are sent along when new notices are fetched. Ads for unrelated third-party apps or services are not sent as system notifications.

To check notification delivery quality, the following may be processed: non-identifying campaign identifiers, notification type, whether the notification was received, displayed, opened, or dismissed on the device, notification permission or channel blocking status, and approximate response time ranges. Notification titles, body text, full destination addresses, push tokens, and message identifiers are not recorded in Analytics.

The app may display Google AdMob ads below Recent visits on the home screen and below the tab list on the open tabs screen. To deliver ads, measure ad performance, and prevent fraudulent use, the Google Mobile Ads SDK and the Google User Messaging Platform SDK may process ad-related information. The app does not collect, for advertising purposes, the full addresses the user visits, search terms, web page content, entered content, or download file names, and does not include them in ad requests.

Prioritizing privacy, the app keeps the Android Advertising ID permission removed from the app manifest. However, the Google Mobile Ads SDK or Android/Google Play services may process limited device- and app-related information to display ads and manage consent, and depending on the region, an ad privacy choice screen may be shown through the Google User Messaging Platform.

2. Purposes of Permission Use

• Internet permission: used to access the websites the user enters.
• Location permission: used only to pass location permission to a website when the user has allowed that website to use location.
• Storage-related permissions: used so that the user can download and open files.
• Speech recognition: used to invoke Android speech recognition when the user taps the voice search button.
• Notification permission: when the user has consented to Notices (updates, important notices, feature information) or Offers & ads and has allowed Android notification permission, used to display the types of notifications consented to on the phone.

3. Purposes of Using Personal Information

Information stored in the app is used only to provide browser features such as showing recent history, managing shortcuts, checking downloads, and keeping user settings.

Information processed through Firebase is used, to the extent that it does not directly identify individuals, to review usage flows in order to build a better app, to find the causes of errors, and to deliver notices (updates, important notices, feature information) to users who have consented to notifications and, where separately consented, offers and Big Text Browser's own promotions.

Information processed through AdMob is used to display ads in the app and to check ad quality and stability.

4. Disclosure to Third Parties and External Websites

The app does not itself sell or provide personal information to third parties.

Data processing related to Firebase is handled in accordance with Google's Privacy Policy and the Firebase terms.

Websites the user visits are subject to each site's own privacy policy and cookie policy. Information entered or permitted on those sites may be processed according to that website's policies.

5. Retention and Deletion

Recent visit history and settings are stored on the user's device. The user can delete recent visit history in the app settings, and deleting the app also deletes the app data stored on the device. Operational data processed through Firebase is handled in accordance with Google Firebase policies and retention periods.

You can turn off Notices and Offers & ads separately at any time, free of charge, under Big Text Browser Settings > Notifications in the app. If you turn off both, or use Big Text Browser Settings > Clear and reset > Reset app settings in the app, that device's information and Notification inbox are deleted from the notification server and use of the push token stops. Notification server information that has not been updated for 180 days and notices older than 180 days are deleted automatically. If you turn off the app's notifications in Android system settings, notifications will not appear on your phone.

6. Children's Privacy

The app does not knowingly collect personal information from children.

7. Changes to This Policy

From 8/14/2026, the integrated notification description above replaces the previous notification description stating that “no advertising information is sent.” Existing users' notification settings are not automatically converted into consent to receive advertising information; notifications are enabled only if the user consents again to the revised integrated notification notice.

From 10/15/2026, notifications are divided into Notices and Offers & ads, with separate consent for each, and the information above is stored on the notification server operated by the developer in order to send notifications. For those who turned on notifications in a previous version, Notices remain as they are, and Offers & ads are received only after consenting again.

If this privacy policy changes, the changes will be announced through the app or the distribution page.

8. Contact

How to delete data: bigtextbrowser.bymysidelabs.com/data-deletion

Privacy inquiries can be submitted through the developer contact information shown on the app's distribution page.