Google chrome download paused android

Debugging tools. Recording and Playback. Instant Placement. Lighting Estimation. Augmented Images. Cloud Anchors. Augmented Faces. Android NDK C. Unity AR Foundation. Getting started. Additional WebXR resources. Google is committed to advancing racial equity for Black communities. See how.

Your browser does not support the video tag. Capabilities ARCore can track up to 20 images simultaneously. If no physical size is provided, ARCore estimates the size and refines this estimate over time. ARCore can respond to and track images that are: Images that are fixed in place, such as a print hanging on a wall or a magazine on a table Moving images, such as an advertisement on a passing bus or an image on a flat object held by the user as they move their hands around.

Be flat for example, not wrinkled or wrapped around a bottle. Best practices Tips for selecting reference images The image's resolution should be at least x pixels. Using images with high resolution does not improve performance.

Color information is not used. Both color and equivalent grayscale images can be used as reference images or by users at runtime. If the resume fails due to a payment issue, the user enters the account hold state, as shown in figure A user can also choose to manually resume a subscription at any time during the pause period, as shown in figure 2.

When a user resumes manually, the billing date changes to the manual resume date. When a user's subscription is paused, the subscription is not returned by queryPurchasesAsync.

If the subscription is resumed, the subscription is then returned by queryPurchasesAsync. If your app synchronizes subscription state with a secure backend server, you should listen to Real-time Developer Notifications to maintain state. These notifications also allow you to notify your users in your app that they have paused their subscription and don't have access to it. You should also provide a way for the user to manually resume the subscription by using a deep link to Google Play.

This should be handled as described in renewals. This should be handled as described in the account hold section. A cancelled subscription remains visible in the Play Store app until its expiration date.

A user can restore a cancelled subscription before it expires by clicking Resubscribe previously Restore in the Subscriptions section in the Google Play Store app. If your app relies solely on queryPurchasesAsync to determine whether a user is entitled to a subscription, then your app should automatically handle restorations, as queryPurchasesAsync continues to return cancelled purchases before their expiration dates.

A restored subscription continues to renew as if it was not cancelled. Once received, your app can respond to the notification, record that the subscription is now set to renew, and stop displaying restoration messaging in your app. When a user upgrades , downgrades , or resignup from your app before the subscription expires , the old subscription is invalidated, and a new subscription is created with a new purchase token.

In addition, the subscription resource returned from the Google Play Developer API will contain a linkedPurchaseToken that indicates the old purchase from which the user upgraded, downgraded, or resubscribed.

You can use the linkedPurchaseToken to look up the old subscription and identify the existing user account so that you can associate the new purchase with the same account.

As a developer, you must make it easy for your customers to manage their subscription. Your app should include a link on a settings or preferences screen that allows users to manage their subscriptions. An example of this link is shown in figure 4. In this link's click handler, add logic to determine whether the user has any non-expired subscriptions for your app, where expiryTimeMillis is in the future or autoRenewing is set to true. To programmatically determine the SKU for an existing subscription, query your app's backend for a list of subscriptions associated with a particular user.

If the user has a non-expired subscription, you can direct them to a URL similar to the following, replacing "your-sub-product-id" and "your-app-package" with the subscription ID and app package info:. If a user doesn't have any non-expired subscriptions within your app, use the following URL to direct them to the page that shows all of their other subscriptions, as shown in figures 5 and You can find example code for subscription link logic in the Classy Taxi sample app.

You can offer users different subscription tiers, such as a base tier and a premium tier. Figure 7 shows a screen that offers two subscription tiers:. Users should be able to access a screen similar to figure 7 to upgrade or downgrade a subscription.

When upgrading or downgrading a subscription, you can set the proration mode , or how the change affects your subscribers. The following table lists available proration modes:. Samwise has a subscription to online content from the Country Gardener app. He currently has a monthly subscription to the Tier 1 version of the content, which is text-only. When upgrading the subscription, the developer selects a proration mode.

The following list describes how each proration mode affects Samwise's subscription:. When choosing a proration mode, be sure to review our proration recommendations. Your app can offer users an upgrade or downgrade using the same steps as with launching a purchase flow. However, when upgrading or downgrading, you need to provide details for the current subscription, the future upgraded or downgraded subscription, and the proration mode to use, as shown in the following example:.

For the immediate replacement proration modes, your app receives the new purchase in your PurchasesUpdatedListener. The purchase is also available in BillingClient. When you receive the purchase token, follow the same verification process as with verifying a new purchase token. Make sure to acknowledge these purchases with BillingClient. Be sure to invalidate the token provided in the linkedPurchaseToken to ensure that the old token is not used to gain access to your services.

See Upgrades, downgrades, and resignups for information on handling upgrade and downgrade purchases. For the deferred replacement mode, your app receives a call to your PurchasesUpdatedListener with an empty list of purchases and a status of whether the upgrade or downgrade was successful.

Until the replacement takes effect, BillingClient. For deferred replacements, it is strongly recommended to listen to this notification and to acknowledge the purchase using Purchases. The linkedPurchaseToken in the subscription resource can be used to determine which user in your subscription backend, if applicable, should be updated with the new entitlement.

Your app should not rely on the user opening the app and acknowledging via BillingClient. Free trial eligibility settings apply when a user is upgrading or downgrading. You can adjust the free trial eligibility settings in the Google Play Console.

The following table describes the behavior of each proration mode if both the new and old plans have a free trial, and the user is upgrading during a free trial:. The user loses the free trial immediately. The price difference for the remaining period is then charged to the user. The next billing date remains unchanged.

Note: This option is available only for a subscription upgrade, where the price per unit of time increases. To understand how free trial transitions work in the default case of one free trial per app, consider the following scenario:. Maria has a subscription to online content from the Country Gardener app. She currently has a monthly subscription to the Tier 1 version of the content, which is text-only. She is enjoying a day free trial as a first-time subscriber, which means her first payment is due on May 1.

This second subscription has a day trial as well. The following list describes the transition behavior if the developer instead allows one free trial per subscription:. The following table shows diferrent proration scenarios along with what we recommend for each scenario:. After a user has cancelled their subscription, you can try to win them back either in your app, or through the Play store. The following table describes various subscription scenarios along with associated winback actions and app requirements.

For subscriptions that have been canceled but have not yet expired, you can allow subscribers to restore their subscription within your app by applying the same in-app product purchase flow as for new subscribers.

Ensure your UI reflects that the user has an existing subscription. For example, you might want to display the user's current expiration date and recurring price with a Reactivate button.

Most of the time, you will want to offer the user the same price and SKU they were already subscribed to, as follows:. If you would like to offer a different price—for example a new free trial or a winback discount—you can instead offer a different SKU to the user:.

When you receive the purchase token, process the purchase just as you would with a new subscription. While the subscription is canceled but still active, users can restore the subscription in the Google Play subscriptions center by clicking Resubscribe previously Restore. This keeps the same subscription and purchase token. You can allow expired subscribers to resubscribe within your app by applying the same in-app product purchase flow as for new subscribers.

Note the following:. You will not receive a linkedPurchaseToken in the subscription resource. If enabled, users can resubscribe to the same SKU for up to one year after expiration by clicking Resubscribe in the Google Play subscriptions center. This generates a new subscription and purchase token. Resubscribing is considered an out-of-app purchase, so be sure to follow best practices for handling purchases made from outside your app.

Using Real-time Developer Notifications, you can detect in real time when a user decides to cancel. When a user cancels, but before their subscription has expired, you can send them push notifications or in-app messages to ask them to resubscribe. For more information, see Winback after churn. You can let your users try out a subscription before making a payment. Free trials run for a period of time that you specify and convert to full subscriptions automatically once the free trial period ends.

These converted subscriptions use the same time period and price as ordinary subscriptions. You can set up a free trial for any type of subscription. To start a free trial, a user completes the standard process for purchasing a subscription on Google Play.

If a user is eligible for a free trial, they aren't charged for the duration of the free trial, and they're notified by email that the subscription includes a free trial period. Google Play verifies that the user has a valid payment method before starting the free trial. Some users may see this verification as a hold or charge on their payment method.

This hold or charge is temporary and is later reversed or refunded. After the trial period ends, the user's payment method is charged for the full subscription amount. Information is not shared with the merchant until you agree. Google Chrome supports the Geolocation API , which provides access to fine-grained user location information with your consent.

By default, Chrome will request your permission when a web page asks for your location information, and does not send any location information to the web page unless you explicitly consent. Furthermore, whenever you are on a web page which is using your location information, Chrome will display a location icon on the right side of the omnibox. You can click on this icon in order to find out more information or manage location settings.

You can also configure exceptions for specific web sites. In the Android version of Chrome, your default search engine automatically receives your location when you conduct a search. On the iOS version of Chrome, by default your location is sent to Google if you conduct a search from the omnibox.

Read more about how your default search engine handles geolocation and how to manage your settings in the Omnibox section of the whitepaper. If you do choose to share your location with a web site, Chrome will send local network information to Google also used by other browsers such as Mozilla Firefox in order to estimate your location.

The requests are logged, and aggregated and anonymized before being used to operate, support, and improve the overall quality of Google Chrome and Google Location Services. It uses Google's servers to perform the conversion.

Using the feature sends an audio recording to Google audio data is not sent directly to the page itself , along with the domain of the website using the API, your default browser language and the language settings of the website. If you opt in to the feature, Chrome OS listens for you to say "Ok Google" and sends the audio of the next thing you say, plus a few seconds before, to Google. Detection of the phrase "Ok Google" is performed locally on your computer, and the audio is only sent to Google after it detects "Ok Google".

You can enable or disable this feature in Google Assistant Settings. Enabling this feature in Chrome Settings will cause Chrome to listen whenever the screen is unlocked.

On Chrome OS devices with a local audio processor, the device also listens when the device is asleep. Once the audio has been converted to text, a search with that text is submitted to Google. You can quickly complete tasks on the web using the Google Assistant in Chrome on certain Android devices. If you opt-in to this feature, you can speak to the Google Assistant and ask it to search websites.

It also can fill out forms on your behalf, or speed up the checkout experience. For example, if you issue a command to the Google Assistant e. As another example, if you ask the Google Assistant to help you purchase tickets for an upcoming movie, then the address of the website you are viewing, your credit card information, and your email address will be shared with Google to complete the transaction and make it possible for you to receive the purchase receipt and movie ticket. If you opt-in to this feature, the Google Assistant in Chrome will send data to Google in order to complete the command you issued.

At the time the command you issued is executed, additional information can be shared. Depending on the command you issued, the information shared with Google can include the address of the website you are viewing, your email address, your name, your delivery and billing address, your credit card information, and possibly the username you use to log into the website. This information is not stored by Google — rather, this information is passed on to the third party website to complete the command you issued to the Google Assistant.

Additionally, information about your system is collected in order to improve the product and to debug issues. To personalize future actions Google Assistant in Chrome will save configuration information about the command you issued to improve your future experiences for example: seat selections, number and types of movie tickets, etc.

This information is saved to your Google Account. Some Google Assistant features are not available on Incognito tabs. The Google Cloud Print feature allows you to print documents from your browser over the Internet. You do not need a direct connection between the machine that executes Chrome and your printer.

You can manage your printers and print jobs on the Google Cloud Print website. Chrome stores locally a list of expected SSL certificate information for a variety of high-value websites, in an effort to prevent man-in-the-middle attacks. For Google websites and other websites that choose to opt in, Chrome will report a possible attack or misconfiguration.

Chrome sends these reports only for certificate chains that use a public root of trust. You can enable this feature by opting in to report data relevant to security, as described in the Safe Browsing section.

Each time you see an SSL error page, a report will be sent containsing the SSL certificate chain, the server's hostname, the local time, and relevant details about the validation error and SSL error page type. Additionally, each time a mismatch between different certificate verifiers is detected, a report will be sent containing the certificate chain and the verification result.

Because Chrome sends these reports for all certificate chains, even those that chain to a private root of trust, these chains can contain personally identifiable information.

Users can install external apps and extensions for the desktop versions of Chrome to add features to or customize their Chrome browsers.

Installing an application or extension from the Chrome Web Store directly or via an inline installation flow on a third-party site involves a request to the Chrome Web Store for details about the application. The store uses this information to recommend applications to you in the future, and in aggregate to evaluate application popularity and usage.

As noted above, applications and extensions are updated via Google Update. As they're more deeply integrated into Chrome, applications and extensions that you choose to install can request access to additional capabilities, enabling functionality that doesn't make sense on the web at large: background notifications or raw socket access, for instance.

These additional permissions may change the way your data is collected and shared, as extensions and applications might have access to data regarding the websites you visit, and might be capable of monitoring or modifying your interactions with the web.

When installing an application or extension, Chrome may first warn you about certain capabilities. Please do take the time to read and evaluate this warning before proceeding with the installation.

Note also that interactions with and data collected by these third-party applications and extensions are governed by their own privacy policies, not Google's privacy policy.

The developer may end-to-end encrypt the message data, or may send it in a form such that Google servers process it as plain text. Websites you visit in Incognito mode are not allowed to send you push messages and therefore cannot get a registration token. When you uninstall an app or extension, revoke the notification permission for a website, or clear cookies for a permitted website, its registration token is revoked and will not be reused, even if the same app or extension is re-installed or the same website is re-visited.

Registration tokens used by Chrome components such as Sync are revoked once they are no longer in use for example, when the user disables Sync.

The registration tokens that are passed to entities contain an encrypted device ID, which is used for routing the messages. Google can decrypt the device ID, but other entities cannot, and the encryption is designed so that two registration tokens for the same device ID cannot be correlated. On desktop versions of Chrome, the device ID is reset when the Chrome profile is removed, or when neither Chrome Sync nor any of the entities requires it for push messaging.

On Android, the lifetime of the device ID is governed by the operating system and is independent of Chrome. Any messages routed to registration tokens containing a revoked device ID will not be delivered. A Custom Tab may look different from a regular Chrome tab, for example it may have app-specified visual style, and the absence of an editable URL bar. Despite the different visual style a Custom Tab may have, the data sent and received in the Custom Tab, such as cookies, saved passwords and browsing history function the same way they do in a normal Chrome tab.

The Custom Tab is an app-customized view using the same underlying user profile. If you tap on such a button, the address of the current website is shared with the application.

An application can request Chrome to pre-render a given URL in the background. This allows Chrome to show you a pre-loaded site instantly when you open it from the app. At the same time it allows an application to set cookies in your browser in the background. Trusted Web Activities are a form of Chrome Custom Tab where the top bar is not present, allowing web browsing with no browser UI but with access to the cookie jar.

They can only be used to view web content on an origin that the client app can prove that it owns using Digital Asset Links. If the user navigates off this origin the the top bar reappears. When the client app is uninstalled or has its data cleared through Android Settings, Chrome will allow the user to clear data for the linked origin. Chrome reloads the tabs you had open and persists session information to get you up and running as quickly as possible.

This feature effectively extends a browsing session across restarts. In this mode, session cookies are no longer deleted when the browser closes; instead, they remain available on restart to keep you logged into your favorite sites. On desktop versions of Chrome, this feature can be enabled or disabled in Chrome settings. On Chrome OS, it is enabled by default. On OS X, when you restart your device, a checkbox in the OS confirmation dialog asks you whether you want to re-open applications and windows after restart.

If you check this box, Chrome restores tabs and windows, as well as the session cookies, even if you have disabled "Continue where you left off" on Chrome. Chrome is constantly evolving to better meet the needs of users and the web. To ensure new features are providing the best experience and working correctly, they may be enabled for a subset of users before they are fully launched.

This is done through a system called "Chrome Variations" - also known as "field trials". A given Chrome installation may be participating in a number of different variations for different features at the same time. These fall into two categories:. Other factors may additionally inform the variations assigned to a Chrome installation, such as country determined by your IP address , operating system, Chrome version and other parameters.

Usage statistics and crash reports are tagged with all variations a client participates in, including both low entropy and high entropy variations. These reports, which also contain a pseudonymous client identifier, can be disabled in Chrome settings.

Additionally, a subset of low entropy variations are included in network requests sent to Google. The combined state of these variations is non-identifying, since it is based on a bit low entropy value see above. On Android, this header may include a limited set of external server-side experiments, which may affect the Chrome installation. This header is used to evaluate the effect on Google servers - for example, a networking change may affect YouTube video load speed or an Omnibox ranking update may result in more helpful Google Search results.

On Android Chrome, in certain cases these low entropy variations may also be sent to Google apps when cross-app communication occurs to support a Chrome feature; for example, when searching with Google Lens. This information is used to better understand how Chrome experiments affect that Google feature: for example, Chrome memory usage change could affect how long it takes an action in the Google app to complete.

The header will not be sent with system traffic such as the geolocation, metrics or device management services. The effect of Do Not Track depends on whether a website responds to the request, and how the request is interpreted.

For example, some websites may respond to this request by showing you ads that aren't based on other websites you've visited. Many websites will still collect and use your browsing data - for example, to improve security; to provide content, services, ads and recommendations on their websites; and to generate reporting statistics.

If you grant this permission, the plugin is granted unsandboxed access. This allows content providers to offer you access to DRM protected content like videos or music but may have security and privacy implications, so consider carefully whether you trust a plugin or website with this privilege. Some websites encrypt media to protect against unauthorized access and copying. When users play media from these sites, they typically log into the site, which authenticates the user, and then digital rights management negotiates a key exchange for the decryption and playback of the media.

The implementation of that API is tightly coupled with the browser to protect user privacy and security, through Content Decryption Modules CDM , which are provided by digital rights management solutions such as Google Widevine or Microsoft PlayReady. When a user asks Chrome to play encrypted HTML5 media for example, watching a movie on Google Play Movies , Chrome will generate a request for a license to decrypt that media.

This license request contains an automatically generated request ID, which is created by the Content Decryption Module, as well as proof that the CDM is legitimate. After generation, the license request is typically sent to a license server managed by either the content website or Google. Neither the license request, the proof, nor the request ID include any personally identifying information. As part of the license request, Chrome also generates a unique session ID which does not contain personally identifying information.

This session ID is sent to the license server, and when the server returns a license the session ID is used to decrypt the media. The session ID may be stored locally even after the site has been closed. The license may also be stored locally for offline consumption of protected content. When returning a license, the site license server may include a client ID, generated by the site.

This client ID is unique to the user and the site, it is not shared between sites. If provided, the client ID is stored locally and included by Chrome in subsequent license requests to that site. On some platforms, the website may additionally request verification that the device is eligible to play specific types of protected content. In this case, Google creates a certificate using a unique hardware identifier for the device.

This hardware ID identifies the device, but does not identify the user. If the user agrees, Google receives the hardware ID and generates a certificate verifying the device for the requested site. The certificate does not include the hardware ID or any other information that could permanently identify the device.

On Android, this is called Provisioning. In order to give you access to licensed music, the Google Play Music app can retrieve a device identifier that is derived from your hard drive partitions or, on a Chrome OS or Linux installation, from a unique file on your disk.

This identifier can be reset by reinstalling your operating system. Chrome on Android uses Android MediaDrm to play protected content. As on ChromeOS, the website may request verification that the device is eligible to do so.

This is achieved by MediaDrm provisioning. A provisioning request is sent to Google, which generates a certificate that will be stored on the device and sent to the site whenever you play protected content. The information in the provisioning request and in the certificate vary depending on the Android version.

In all cases, the information can be used to identify the device, but never the user. On Android K and L, the device only needs to be provisioned once and the certificate is shared by all applications running on the device. The request contains a hardware ID, and the certificate contains a stable device ID, both of which could be used to permanently identify the device.

On Android M or later, MediaDrm supports per-origin provisioning. Chrome randomly generates an origin ID for each website to be provisioned. Even though the request still contains a hardware ID, the certificate is different for each website, so that different websites cannot cross-reference the same device.

On Android O or later on some devices, provisioning can be scoped to a single application. The request will contain a hardware ID, but the certificate will be different for each application, in addition to each site, so different applications cannot cross-reference the same device.

On Android versions K and L, Chrome will always ask you to grant this permission before provisioning starts. On later versions of Android, this permission is granted by default. Chrome also performs MediaDrm pre-provisioning to support playback of protected content in cases where the provisioning server is not accessible, such as in-flight entertainment.

Chrome randomly generates a list of origin IDs and provision them in advance for future use. On Android versions with per-device provisioning, where provisioning requires a permission, Chrome does not support pre-provisioning. Playback might still work because the device could have already been provisioned by other applications. On Android versions with per-origin provisioning, Chrome pre-provisions itself once the user attempts to play protected content.

As the provisioning for the first playback already involved sending a stable hardware ID to Google, the subsequent pre-provisioning of additional origin IDs introduces no new privacy implications.

If provisioning fails and there is no pre-provisioned origin ID, Chrome may ask for permission to further fallback to per-device provisioning. On devices with per-application provisioning, Chrome pre-provisions itself automatically on startup.

When you sign into a Chrome OS device, Chrome on Android, or a desktop Chrome profile with an account associated with a Google Apps domain, or if your desktop browser is enrolled in Chrome Browser Cloud Management, Chrome checks whether the domain has configured enterprise policies.

Any configured policies are applied. To revoke the registration, remove the Chrome OS user, sign out of Chrome on Android, remove the desktop profile, or remove the enrollment token and device token for Chrome Browser Cloud Management. This will enforce enterprise policies for the entire device, such as providing shared network configurations and restricting access to developer mode.

When a Chrome OS device is enrolled to a domain, then a unique device ID is registered to the device. In order to revoke the registration, the admin will need to wipe the entire Chrome OS device. Registered profiles and devices check for policy changes periodically every 3 hours by default.

In some cases, the server pushes policy changes to the client without waiting for Chrome's periodic check. Unregistered profiles check whether a policy has been turned on for their domain each time Chrome starts up. The policy list contains details about the types of configurations that are available via Cloud Policy. Chrome will share the URLs you visit with Google, as well as usage and performance statistics for those sites so Chrome can better optimize them.

Cookies for sites you visit are not shared with Google. Logs are not associated with your Google Account, and all log entries are removed within 14 days. Pages loaded in Incognito will not use the optimizing servers and usage and performance statistics will not be reported.

To save Lite Mode users data, image requests may be sent to a Google image optimization server which will fetch the image from the origin and return a compressed version to Chrome. To avoid optimizing private images, Chrome first asks Google for a list of image URLs known to be on the page according to a crawl of the site from a Google data center. Only images on that list will be sent to the optimization server. Chrome for Android offers features to be used when signed in with a kid's Google Account and automatically signs in a kid's account if they've signed into the Android device.

You can read about how Sync data is used in the Sign in section of this Whitepaper. Browsing history can still be removed in the Chrome section of the Google Dashboard. Parents can go to chrome. Incognito mode in Chrome is a temporary browsing mode.

The browsing history and cookies are deleted only once you have closed the last incognito window. Incognito mode cannot make you invisible on the internet. Websites that you navigate to may record your visits. Browsing as a Guest in Chrome allows you to use somebody else's computer without modifying their profile. For example, no bookmarks or passwords get stored on their computer. Note that Guest mode does not protect you for example, if the computer you are using is infected by a keylogger that records what you type.

While browsing in a standard i. This information is only sent to Apple devices that are paired with your iOS device, and the data is encrypted in transit. Chrome support for this feature can be disabled in Chrome settings. This mitigates the risk of various kinds of man-in-the-middle attacks in which websites try to steal your password and use it later.

To prevent abuse, a website is required to be delivered over a secure connection HTTPS , and to register the security key before it can be used for identification. Once a website is registered with a specific security key, that security key will provide a persistent identifier, regardless of which computer it is plugged into, or whether you're in incognito or guest mode, but you must physically interact with the security key to give a website access to an identifier by, for example, touching it, or plugging it in.

The Physical Web lets you see a list of URLs being broadcast by objects in the environment around you. For each URL, the PWS obtains the title of the web page, filters out unsafe results, and returns a ranking based on non-personalized signals about the quality and relevance of the web page.

Users will need to turn on Bluetooth to use the feature. If Android users have location settings enabled on both their device and in Chrome, they will receive a notification the first time they are near a beacon that will give them the option to turn on the Physical Web feature.

Users can also enable or disable the feature in the Privacy settings. Once a user enables the feature, Chrome scans for nearby devices for a few seconds each time the user unlocks the mobile device in use and sends them to the PWS in order to obtain more information about the beacon. The user receives a silent notification when Chrome finds a nearby URL. On iOS devices, users can enable or disable the feature in the Privacy settings or by adding the Chrome widget to their Today view in the notification center.

Additionally, the feature is automatically enabled for users who have location enabled on their device, granted Chrome the location permission, and have granted Google the geolocation permission.

Chrome scans for nearby devices whenever it is open in the foreground. When Chrome finds nearby URLs, users will see them as omnibox suggestions. Additionally, Chrome scans for nearby devices for a few seconds when the Today widget is displayed in the notification center. Chrome does not let any page communicate with a device unless you explicitly consent. When a web page asks to pair with a device, Chrome will ask you to choose which device the web page should access, if any.

Selecting a device for one page does not give other pages access to the device you have chosen, and does not allow that page to access other devices. Currently, permission for a page to communicate with a device is usually revoked when the page is reloaded, and is always revoked when Chrome is restarted. The data collection and usage described in this section is handled by Android and governed by the Google Privacy Policy.

If the Android Backup Service is enabled on your device, some of your Chrome preferences will be saved and stored on Google servers. For other Android devices, you may be able to find help by looking up your device on this page. When setting up a new Android device, you may request that it copies the preferences from a previously set up device.