Daol Browser Privacy Policy

1. Browsing information Daolsoft does not collect itself

Daol Browser has no Daolsoft-operated account, sync server, analytics SDK, or remote configuration. Daolsoft does not collect visited addresses, search terms, cookies, form input, bookmarks, browsing history, location, camera data, or microphone data on its own servers through the app. Google advertising SDK processing is described separately below.

2. Google advertising and consent

The Android app uses the Google Mobile Ads Next-Gen SDK to display app-open ads. The app does not directly provide current page URLs, search terms, form input, bookmarks, or browsing history to the advertising SDK. According to Google’s disclosure, the SDK may automatically collect and share the following information for advertising, analytics, and fraud prevention.

• IP addresses that may estimate a device’s approximate location
• App interactions such as launches, taps, and ad views
• Diagnostics such as app and SDK launch time, hang rate, and energy usage
• Android advertising ID, app set ID, and applicable device-account identifiers
• This information is encrypted in transit with TLS. Where consent is required, Google’s User Messaging Platform (UMP) presents choices before an ad request. When required, choices can be managed again from Ad privacy options in app Settings.

3. Information sent directly to websites and search providers

The browser uses Android System WebView to communicate directly with sites opened by the user. The following may be sent to the relevant website or service provider.

• URLs and web requests entered or opened by the user
• Search terms when the user searches (Google is currently the default provider)
• Ordinary network and browser information such as IP address, User-Agent, and language
• Form input and files explicitly selected with the system picker
• Camera, microphone, or selected-precision location after both website and Android permission approval
• The URL, User-Agent, and relevant site cookie needed for a download
• Websites and search providers process information under their own privacy policies. Explicit HTTP connections may be unencrypted. Android DownloadManager handles downloads; this is not a transfer to a Daolsoft server.

4. On-device blocking and reader processing

• Ad and tracker blocking compares request URLs and the current page URL with the on-device adblock-rust engine and bundled EasyList/EasyPrivacy rules. Request URLs and blocking events are not sent to a Daolsoft server or kept in a persistent log.
• Domains where blocking is disabled are saved in app preferences. Blocked counts are held only in memory for the current app session.
• Reader mode analyzes the current document with Readability on the device, sanitizes extracted HTML with DOMPurify, and displays it with JavaScript disabled. Extracted content is not sent to Daolsoft or stored persistently.
• Read aloud uses the selected speech engine. Offline Android voices and optional Supertonic 3 process text on the device. A network system voice may process text under its provider’s policy.
• When Reader images are enabled, remaining HTTPS image URLs may communicate directly with their image servers.

5. Information stored on the device

• Open-tab URLs, titles, order, and last-used state
• Bookmarks, browsing history, and visit counts
• Past search terms and icons supplied by visited sites
• Preferences such as search provider, tab restore, and history settings
• Launch count and last ad display time used to limit app-open ad frequency
• Domains where content blocking is disabled
• Cookies, cache, DOM storage, and site data maintained by Android System WebView
• Downloaded files and system download records managed by Android DownloadManager
• Tab, bookmark, history, search, and preference data use Room and DataStore. Up to 200 site icons use app-private files. This local data is excluded from Android cloud backup and device-to-device transfer.

6. Permissions

File upload uses the Android system picker. Phone, SMS, email, map, and market links open a compatible app only after confirmation; the browser does not place calls or send messages automatically.

7. Retention and deletion

• Tabs, bookmarks, browsing history, past search terms, and settings may remain until deleted in the app, app storage is cleared in Android settings, or the app is uninstalled.
• Clear browsing data removes history, past search terms, and saved site icons. One control for all cookies, cache, and site data is not yet available.
• Site blocking exceptions are removed when app storage is cleared or the app is uninstalled. Blocked counts and Reader content are not stored persistently.
• Files in Downloads and Android system download records may remain after clearing app storage or uninstalling and must be deleted separately.
• Daolsoft stores no remote browser account or browsing dataset, so there is no remote Daolsoft account data to delete.

8. Security and third parties

The app does not bypass invalid SSL certificates, blocks mixed content and third-party cookies by default, and disables WebView debugging in release builds. Reader mode accepts sanitized HTML and restricts JavaScript, forms, frames, and network connections. Web-content blocking cannot guarantee every ad or tracker is blocked. Google Mobile Ads, websites, search providers, Android System WebView, and the device operating system have their own terms and policies.

9. Changes and contact

We will update this policy before shipping remote collection, an account or sync service, a new SDK, or materially different data processing. Contact devsky@daolsoft.net with privacy questions.