Glyvo Browser Privacy Policy

Effective date: November 9, 2026.

Developer and service provider: ARABIA. Privacy contact: arabia.hu@gmail.com.

1. About this policy

This policy describes how Glyvo Browser accesses, stores, uses and sends information when you use its browser, content and device tools. “We” and “our” refer to ARABIA. It covers information handled by the app and its integrated services and SDKs. Websites, advertisers, speech recognition services and external apps may also process information under their own policies.

This policy describes the app’s features and integrations. Which services operate for you depends on the app version, device, permissions, available configuration and service availability. An integration does not mean that it receives information from every user.

2. Browsing, searches, bookmarks and private tabs

The app stores browsing history, search history, bookmarks, tab URLs, tab state, page previews and preferences on your device to support browsing and returning to pages. Websites loaded in Android WebView can use cookies, cache and website storage. When you visit a website or submit a search, the destination receives the URL or search terms and connection information such as your IP address and browser information. Text searches are directed to Google Search. Information you enter into a website is handled by that website.

Local storage does not mean every related action stays on the device. For pages opened from search, the app records the visited site’s domain in usage events. News events can contain the article URL, content identifier, category, entry point and time spent viewing it. These events are sent through the app’s analytics services described below. The search-submit event records the action, rather than the search text; the search text is nevertheless sent to the search provider.

Private tabs suppress the app’s ordinary browsing-history and search-history writes. They do not provide complete anonymity. Private tab records, URLs and page previews can still be stored locally, and private and normal tabs currently share the WebView cookie and website-storage profile. Private mode does not switch off analytics or the other integrated SDKs. Websites, network operators and service providers may still observe requests. Close private tabs and use the relevant clearing controls when you want to remove local records; closing a tab does not itself erase all cookies or information already received by a service. Bookmarks and downloads you choose to save may remain.

Downloads use Android’s download service after confirmation. The requested file URL and, when available, browser user-agent information are passed to that service and sent to the download destination. Files are saved in the app’s external-files download directory in the app.

3. Installation identity and service registration

The app creates or reuses a random installation identifier and automatically registers the installation with the configured service. The registration can include that identifier, app package and version, device model and manufacturer, Android version, distribution channel, time, timezone, advertising ID when available and permitted by the device settings, and a previously assigned service user ID. A positive user ID returned by the service is saved locally and reused.

This is a technical service identity. This installation registration is not a username/password account, Firebase Authentication sign-in or a cross-device account recovery service. The identifiers can link activity from an installation and must not be understood as anonymous or unidentifiable data. Clearing local app data does not request removal of an existing server record.

4. News, video and weather

News requests send the selected category and pagination cursor to the content service. Article images and original articles are loaded from their respective hosts. News card views, taps and reading activity can also generate the URL-bearing events described above, including when content is presented in a notification or popup.

Video feed requests include the installation identifier. When playback starts, the app reports the installation identifier and video identifier to the content service. Separate usage events can contain the video identifier, the content’s supplied keyword/category, playback activity and viewing durations. Playback progress and local choices such as liked or uninterested items may be stored on the device. Media and image hosts receive requests needed to deliver their files. Media network calls are also instrumented for Firebase Performance Monitoring.

The default weather request does not send latitude or longitude, and Glyvo does not request Android location permission for this feature. Weather responses are cached locally. The weather detail page loads a hosted web page that can use JavaScript and website storage. The service receives connection information, including IP address. A displayed location does not mean Glyvo has obtained GPS coordinates; the service’s location-selection method and upstream provider are not specified in this policy.

5. Voice search and QR scanning

Voice search uses the microphone with Android permission and passes speech recognition to the device’s configured Android speech recognition service. That service may send audio to remote servers. The app receives recognized text and uses it to open a browser search. Glyvo does not keep an audio-recording archive or provide its own audio-upload service for voice search. The speech recognition provider’s own storage practices still apply. Typed search remains available without using voice search.

QR scanning uses the camera with permission, or an image you select through the system picker. CameraX and bundled Google ML Kit process the selected image or camera frames on the device. Google documents separate ML Kit performance and usage metrics; on-device image processing does not mean the SDK never communicates with Google. If you choose to open or search a scan result, its URL or text is sent through the normal browser/search flow. A selected image is used for the scan, not automatically uploaded by the scan feature.

6. Files, cleanup, battery and applications

File management and cleanup inspect accessible local storage, including file names, paths or content URIs, types, sizes, modification times and available space. They use this information to list and classify files and carry out the selected opening or deletion operation. Cleanup may compare directory names with visible application packages to identify possible residual files. All-files access is required for the broad file-scanning flow; Android still limits what can be accessed.

Opening a file in another app grants the selected handler access to that file’s content URI. That app then handles the file under its own practices. Deleting a file can be irreversible and does not remove copies held elsewhere.

The process tool reads visible launchable application packages, labels and icons and device memory information. It directs you to Android application settings for available management actions; it is not a complete inventory of running processes and does not promise to stop every app. This tool does not request Android Usage Access or read other apps’ usage history.

Battery tools read battery status and related device settings locally. With separate permission to modify system settings, selected actions can change brightness, screen timeout and rotation. The battery report is produced using local rules, rather than remote AI analysis.

These app features do not upload file contents, captured notification text, or the process tool’s application list to its business API. Tool usage, permission outcomes and feature interactions are recorded separately in analytics. This statement applies to these features; it is not a claim that integrated SDKs collect no device information.

7. Notification access, popups and background activity

Permission to post Glyvo notifications and permission to read other apps’ notifications are different controls. If you enable notification access, the notification cleanup service can read qualifying notifications from other apps, store the source package, app name, notification message text and capture time locally, and cancel those system notifications. Message text may contain private communications or other sensitive information. Global and per-app cleanup settings determine which qualifying notifications are captured; in the app they default to enabled once access is granted. The local record list is trimmed to the newest 200 records after insertion and can be cleared in the notification tool.

If you allow display over other apps, Glyvo can show content and tool reminder popups over other screens. This permission is not a grant to read the contents of those screens. Background components can refresh content, deliver push messages and evaluate local conditions such as battery state, storage usage, available cleanup candidates, presence of browsing history and notification-record counts to choose tool or content prompts. This can occur while you are not actively using a Glyvo screen, subject to Android restrictions and the feature settings. Popup impressions, taps, entry sources and related content identifiers are recorded in usage events.

Firebase Cloud Messaging uses installation identifiers and delivery tokens to deliver messages. The app subscribes to a general messaging topic. The new-token callback does not upload the token to a custom business registration endpoint; Firebase still processes messaging identifiers. Turning off notification display does not by itself disable all SDK initialization, installation registration or analytics.

8. Analytics, diagnostics, advertising and attribution

Usage events are queued on the device and sent to the configured analytics endpoint and, for supported events and properties, Google Analytics for Firebase. They include event names and times, installation and service identifiers, device/app information, screen dimensions, network type and connectivity status, locale-derived country, first-install-day information and the event-specific details described in this policy. Permission events can include permission type, result and entry point. Advertising ID is included in the business device snapshot when available and not limited by the device’s advertising setting.

Firebase Remote Config retrieves settings controlling features, ads, cache freshness and notifications. Firebase Analytics, Crashlytics, Sessions and Performance Monitoring are integrated for usage measurement, crash/session diagnostics and performance. These services can process installation or app-instance identifiers, device/app information, crash traces and network-performance information. Network-performance information may include requested resource URLs, timings, response status and sizes according to the SDK’s processing. The information processed depends on the enabled service settings; not every service receives data from every user.

The app integrates Google Mobile Ads with mediation adapters for Meta Audience Network, Mintegral, Pangle, Unity Ads, Vungle/Liftoff and Bigo Ads. Depending on the adapter, configuration and availability, advertising services can process advertising and other SDK identifiers, IP address and approximate location derived from it, device/app information, ad requests, impressions, taps, diagnostics and fraud-prevention signals. These services use information to deliver and measure ads and prevent abuse; personalization depends on the applicable settings and consent requirements. We do not represent every listed network as serving every user, or describe the current ads as necessarily non-personalized. Available advertising choices depend on the device, the advertising service and the settings that apply to you. See Section 10 for the controls available through Android.

The app includes an Adjust integration for installation attribution and advertising-revenue measurement. When configured and initialized, the app supplies the installation identifier as an external device ID, receives attribution details, can register the attribution source with the service, and submits paid-ad callback details such as revenue, currency, network, ad unit and placement. Adjust’s Google install-referrer, licensing and signature components are also included. Adjust operates only when configured and initialized; an unconfigured integration is skipped. The integration does not forward all business events to Adjust.

9. Recipients and reasons for processing

Information is processed to provide browsing and selected tools, obtain and display content, maintain the installation’s service state, deliver messages, measure usage and ad performance, diagnose problems and help prevent abuse. Depending on the feature, recipients include the configured business/content and analytics services, Google/Firebase, the advertising providers listed above, Adjust when enabled, visited websites and their embedded services, media/image hosts, the device’s speech recognition provider, and external apps you open files with.

Content and weather requests go to the configured services, which may use other providers to deliver content. The fact that a service is accessible through Glyvo does not mean that ARABIA owns its underlying website or content. Contact us if you need information about a service receiving your information or about advertising-related sharing and your applicable rights.

10. Permissions and choices

You can decline optional camera or microphone permission and continue using typed browsing. Declining all-files access limits file management and cleanup. Declining notification access prevents the notification cleanup listener from accessing other apps’ notifications. Declining notification posting or display-over-other-apps access limits the corresponding notifications or popups. Declining system-setting modification prevents direct battery-setting changes. Making Glyvo your default browser is optional.

Use Android app permissions, special app access, notification settings and default-app settings to review or revoke these choices; menu labels vary by device. Use the app’s available notification and tool controls for their respective features. Android advertising controls can limit, reset or delete the advertising ID where supported. Those controls do not erase the app’s separate installation identifier or disable every measurement method.

Several services can initialize during app startup, before the startup acceptance screen is completed. The startup screen is not a control that switches off all collection. This policy and acceptance of the Terms do not replace permission or consent required for particular processing. Glyvo does not provide a single in-app switch that disables all analytics and advertising services. Use the available Android and feature controls, and contact us about other privacy choices or concerns.

11. Retention, clearing and deletion requests

On-device history, search history and bookmarks can be removed using their management or privacy-clearing controls. Tabs and their previews are managed through the tab controls; private tabs can retain local records until removed. Cookie and cache controls address selected WebView data, but the active page can remain open and create further data. Clearing browser data does not clear all installation, analytics, notification or SDK state.

Notification records can be cleared separately. The local analytics queue is pruned when maintenance runs, including removal of queued events older than seven days and trimming above 10,000 events. Sent events can be removed from that queue after acknowledgement; this is not a deletion request to the recipient and not a seven-day server-retention promise. Deduplication markers and other settings have different lifetimes.

Android’s clear-storage or uninstall controls generally remove app-owned local data. Shared files and copies held by other apps or services may remain. The app disables its Android backup and device-transfer data inclusion through its manifest and backup rules; this is not a guarantee about every device or external copy.

The local limits above do not set retention periods for records held by remote services, SDK providers, logs, backups or support correspondence. This policy does not specify a fixed retention period for those records or promise automatic server deletion. Contact us for information about the retention and deletion options applicable to your information.

For a privacy inquiry or a request to access or delete information, contact arabia.hu@gmail.com and describe the request. Avoid sending passwords, sensitive notification content or unnecessary identity documents. A request may require proportionate verification to locate the relevant installation and protect other users. Sending a request does not itself erase records. We do not promise a particular completion time or that the app’s local clearing controls can delete records held by other services. Your mandatory rights remain unaffected. Uninstalling the app is not a substitute for requesting remote deletion.

The technical installation registration described in Section 3 is separate from a user-facing account. You may still contact us about information associated with your installation; lack of a password account does not remove applicable privacy rights.

12. Security, location of processing and rights

The business clients use HTTPS with normal certificate and hostname checks. Login and business analytics also use an encrypted payload format. App-owned storage and Android permission boundaries help restrict access. These measures do not make information unidentifiable, establish end-to-end encryption against the receiving service, or guarantee perfect security. Third-party websites may have different protections; check the destination before submitting sensitive information.

Service providers may process information outside the place where you use the app. This policy does not designate a processing country or promise a particular transfer safeguard. Contact us if you need information about processing locations and protections relevant to your information.

Depending on applicable law, you may have rights to access, correct or delete information, restrict or object to certain processing, receive a copy, withdraw consent where processing relies on it, or complain to a competent authority. Contact arabia.hu@gmail.com to raise a request or concern. Availability and handling depend on the applicable requirements and the data involved. This policy does not reduce mandatory rights.

13. Children and policy changes

Children’s information may be subject to additional protections under applicable law. This policy does not establish a minimum age or represent that parental-verification or child-specific advertising controls are provided. If you are a parent or guardian with a question about a child’s use or believe a child’s information has been handled improperly, contact arabia.hu@gmail.com.

We will identify the effective date of policy updates and provide any notice required by applicable law for material changes.

Website · Privacy Policy · Terms of Service · Contact ARABIA