Privacy Policy

1. Basic browsing and accounts

You can browse with OpenBrowser without registering an OpenBrowser account or providing your name, phone number or identity document details. The app does not provide account-based cloud synchronization. Reading or accepting this policy does not automatically grant camera, microphone or location permissions, or constitute consent to additional collection by third-party services.

2. Browsing data on your device

To display and restore your activity, the app stores data needed for its features on your device: browsing history URLs, titles and visit times; bookmarks and groups; home shortcuts; regular-tab URLs, titles and page snapshots; download records and file locations; settings, site permission choices and installed-extension records. The browsing engine also handles cookies, cache and site storage according to website behavior and your settings, for sign-in sessions, page loading and website features. These records are processed on your device. The app does not currently upload your browsing history, bookmarks or tab list to a developer server.

3. Websites and restored tabs

When you open a URL, submit a search, play online media or download a file, the browser communicates with the destination website and its resource providers. They may receive your IP address, requested URL or search terms, browser and system request information, applicable cookies and content you submit. Pages may also load resources or make further requests under their own logic. Restoring saved regular tabs on startup, opening a link from another app, and continuing a background download or playback may generate requests beyond the moment you tap a page.

4. Search suggestions, translation and extensions

Search terms are sent to your selected search engine. Search suggestions are off by default. When Bing is selected and suggestions are enabled, the query you are typing is sent to Bing before you submit it, to obtain suggestions. You can turn this off in settings. When you use webpage translation, the complete current page URL is provided to the Bing translation service. Avoid submitting links containing private tokens or sensitive query parameters.

Extension installation, execution and update requests are made by the relevant services and extensions according to their behavior. Installed extensions may read pages, process data or connect to the network within the permissions you grant. Their providers explain their own rules. You can change their enabled state or uninstall them in extension management.

5. Permissions and system features

Camera: used when you choose to scan a code, or allow a website to take pictures or use video. Scanned images are decoded on your device. Opening a recognized link then makes a normal webpage request.

Microphone: used for recording or audio communication that you permit on a website. The website handles the resulting content for that feature.

Location: used for website location features you permit, which may involve approximate or precise location. System authorization and site permission together determine access.

Files: the app reads images, extensions or other files you provide through the system picker. Saving downloads to public directories on Android 8 and 9 may require storage permission. Newer systems use their system file-access mechanisms.

Notifications and background operation: used for download or media-task status and playback controls. Visibility depends on system settings. Installing downloaded apps, sharing content and creating home-screen shortcuts use the relevant system flows for your confirmation.

Optional permissions are used for their corresponding features. Refusing or revoking one affects that feature and does not prevent general browsing. Manage existing choices in system app-permission settings and the app’s website-permission settings.

6. Google services, analytics, crashes and device information

The Google Play edition offers optional Firebase Analytics usage statistics and Firebase Cloud Messaging (FCM) app messages, using services provided by Google. Analytics and push messaging are each off by default. You can make separate affirmative choices, and withdraw them at any time, in Settings → Analytics and push messaging (统计与推送). Refusing either or both does not affect general browsing. Accepting this policy does not enable either purpose. Enabling analytics does not consent to push messaging, and enabling push messaging does not consent to analytics. A purpose may be unavailable if the installation is not fully configured or the service is unavailable.

If you enable analytics, Firebase Analytics processes an app-instance identifier, app-use and session events, and device and system information. It may infer approximate geographic location from an IP address. This helps us understand app use and improve the app. Firebase notification interactions may also be recorded when analytics is enabled. The SDK sends this information to Google even though the app has no custom browsing-event tracking. The app does not attach URLs, search terms, extension information or private-browsing activity as custom analytics parameters. Automatic screen reporting, Analytics advertising-ID collection and advertising-related consent remain disabled. Turning analytics off stops future analytics and, if it was previously enabled, resets local analytics data and the app-instance identifier. This does not delete previously uploaded cloud history or automatically disable push messaging.

If you enable push messaging, FCM communicates with Google to obtain and maintain a push registration token and Firebase installation identifier, and processes information such as the app version and device or app configuration to deliver app messages to this installation. This purpose is not used for advertising. The system permission to display notifications is managed separately. Refusing that permission does not withdraw push registration you already allowed. The app currently exposes the registration token only in memory and has no developer-server token-binding integration. Withdrawing push consent disables the messaging service, clears the in-memory token and attempts to delete the FCM registration. A failed withdrawal is retried on a later startup or return to the foreground. This is not deletion of all Firebase installation data or cloud history. It cannot recall messages already in transit or notifications already displayed, and does not automatically disable analytics.

Crash-report uploads remain disabled and there is no user entry point to enable them. Neither analytics nor push consent enables crash-report uploads. After Firebase initializes, Crashlytics may store crash stack traces, app version and device environment locally. With the reporting purpose disabled, the app requests deletion of unsent reports. The app does not add browsing URLs, search terms or request headers as custom crash fields. Its existing local crash count remains on your device. Disabling crash uploads does not mean Google stops processing information for analytics or push messaging you have enabled.

When you choose the relevant action on the About page, the app can copy its version, Android version, system API level, device manufacturer and model to your clipboard. You choose any subsequent recipient. This section does not mean websites, extensions or system services will not process device and network information under their own rules.

7. Limits of private browsing

Private tabs are excluded from the persistent regular-tab restoration list and are not restored as regular tabs after closing or a cold start. Private browsing does not hide your IP address or prevent websites, extensions or network services from receiving information you submit. Bookmarks, downloaded files, and content you copy or share in private browsing may still leave records. Manage them separately.

8. System backup and sharing you initiate

The app allows system backup and migration according to device settings and does not exclude all app data. Some local data may therefore enter a system backup service or another device. The scope, location and restoration behavior depend on the operating system, device manufacturer and your settings. This is not OpenBrowser account synchronization. Manage backup and migration using the available system settings.

If you share a page, copy a link, export bookmarks or give a file to another app, that content goes to the clipboard, your selected file location or the recipient you choose. External recipients handle it under their own rules. Remove passwords, cookies, identity information and URLs containing private parameters before making public feedback.

9. Retention and deletion

Browsing data is kept as needed for its features until you delete it, perform an applicable cleanup, it is replaced by capacity or history-count rules, or you clear app storage. Settings and the local crash count are retained for later use. Clearing app storage or uninstalling usually removes app-private data. System restoration may bring backed-up content back. Files downloaded to public directories and copies you exported, shared or that third parties saved are not removed at the same time. Manage them at their respective locations.

Google handles analytics and push-related data it has received according to the applicable service rules and project retention configuration. This policy does not promise an unverified fixed cloud-retention period. Clearing app data, uninstalling, resetting local analytics or deleting a push registration does not delete all data those services previously stored. The current client does not provide automatic deletion of all cloud history.

10. Your choices and data rights

You can view and manage local records in the history, bookmark, download and tab screens. In settings, choose cleanup items under Clear data, adjust the scope under Automatically clear on exit, and withdraw permissions under Website permissions or system settings. You can separately adjust search suggestions, extensions and site settings. Clearing cookies or site data may sign you out of websites. When deleting a download record, check whether the interface will also delete the file.

OpenBrowser has no registered accounts, so there is no account-closure step. To remove all app-private data on your device, use system app-storage management after saving anything you need. For information stored by websites, extensions, backup services or sharing recipients, use their published channels to request access, correction, deletion or withdrawal of consent. Nothing in this policy limits your statutory personal-data rights.

11. Security and younger users

Local data is protected by app storage and operating-system access mechanisms. Firebase services and the app’s search-suggestion and translation entry points use HTTPS/TLS. The network methods of websites and extensions you access depend on their providers and URLs; not all webpages use HTTPS. No device or network system can guarantee absolute security. Keep your device and app updated, use a device lock, and grant website and extension permissions carefully.

The app is intended for ages 13–15, 16–17 and 18+, and is not directed to children aged 12 or younger. Minors should use it with guidance from a parent or guardian, particularly before submitting location, audio, video, identity or other sensitive information. Obtain appropriate consent and review the relevant third-party rules.

12. Policy updates

This policy describes the current features. If we later add cloud synchronization or change the scope of personal-data processing, we will first update the explanation and seek your separate choice where required by applicable law. Your current acceptance does not automatically cover those future changes.

13. Launch pricing and advertising

The initial release is free, displays no ads, and has no membership, product or purchase entry point. Websites and extensions may have their own advertising or paid services, governed by their providers’ rules.

14. Developer and privacy contact

Public developer name: hujay.

Privacy contact email: hujayelax@gmail.com.

Use this email to ask about this policy or make applicable requests for access, correction, deletion or withdrawal of consent. To respond to your email, we use the contact information, description and necessary attachments you choose to provide. Do not send passwords, cookies, private tokens or unrelated sensitive information. Your email service also handles messages under its own rules. Correspondence is retained as needed to handle the request; you may ask about or request deletion of email information within the developer’s control.

What can be done depends on applicable law, the service holding the data and whether the relevant records can be located. The developer cannot remotely read or clear all browsing data on your device; you perform local cleanup in the app or system settings. For data held by Google, websites, extensions, system backups or sharing recipients, we will explain the scope we can handle and applicable service channels. We do not promise automatic cloud deletion that the app has not implemented. Your statutory rights remain unaffected.

Google Privacy Policy: https://policies.google.com/privacy

Firebase privacy and data-processing information: https://firebase.google.com/support/privacy