---
metadata:
  - name: generator
    content: Diplodoc Platform v5.59.0
alternate:
  - https://yandex.com.tr/support2/yandex-app-android/en/privacy/ytp.md
  - https://yandex.com.tr/support2/yandex-app-android/ru/privacy/ytp.md
  - href: https://yandex.com.tr/support2/yandex-app-android/en/privacy/ytp.md
    type: text/markdown
    title: Markdown version
  - href: https://yandex.com.tr/support2/yandex-app-android/en/llms.txt
    rel: describedby
---
> **Documentation Index:** Fetch the complete configuration index at https://yandex.com.tr/support2/yandex-app-android/en/llms.txt

<!-- source: en/_includes/bar-with-links-applications.md -->
#|
||
You're reading Help for the Yandex Start on Android.
[Help for Yandex app on Android →](https://yandex.ru/support2/yandex-app-android-alice/en/)
[Help for Yandex app on iOS →](https://yandex.ru/support2/yandex-app-ios/en/)
||
|#
<!-- endsource: en/_includes/bar-with-links-applications.md -->

# Tracker blocking

{% note info %}

This feature is available only on Android devices.

{% endnote %}

## What are trackers? {#third-party-cookies}

Cookies can be proprietary and third-party (these are called trackers).

_Proprietary cookies_ are small text files that the browser uses to record data about the sites you've visited. Sites use cookies to recognize users. For example, to avoid asking for their username and password every time they visit the site.

_Trackers_ (third-party cookies) are small fragments of website software code. When you open a website, the tracker loads automatically, collects information (such as your location, device type, or IP address), and sends it back to its owner. Trackers can be placed by the site administrator and its partners. For example, the site that you're viewing has an ad banner from `http://www.example.org`. This banner saves a cookie in the app that stores information about your activity on the site. If you visit another site with an ad banner from `http://www.example.org`, the ad network makes a connection between these visits.

There are different ways the tracker owner can use this information:

#### Fair use

- Site owners can use trackers to estimate how many users visit their site, where they're from, and what devices they use. This data may help them optimize the site for their audience's needs.
- Trackers enable you to use the same login or social network widget on multiple sites.

Trackers from sites that you visited yourself (such as social networks) are most likely used fairly.

#### Malicious use

Malicious tracker owners may collect the personal data that you enter on a website, such as your phone number or email address, and sell it to third parties. As a result, you may receive emails with unwanted ads or annoying calls from advertisers you never gave your phone number to.

We believe that malicious use of data by trackers is a violation of your privacy. To protect you, Yandex has developed a special YTP technology that is part of the [Neuroprotect security system](https://browser.yandex.com/).

## What is YTP? {#ytp-what-is}

Your Tracking Protection (YTP) is a technology that restricts third-party cookies. Using it, you can choose which resources to trust with your data.

YTP is based on a simple rule: only sites that you've visited before are allowed to run trackers. Only these sites can send your data from site to site, show you relevant ads, and use other cross-site interaction features. If you haven't visited the site for 45 days, the browser starts blocking its trackers.

Ads mean site owners can afford to keep their sites free, so Yandex aims to find a balance between free services and useful unobtrusive ads.

This way, you can continue using the internet in a way that's convenient for you (for example, use the same login on different sites), while site owners can support themselves financially without using irrelevant ads that annoy their visitors.

Pages where trackers are blocked load much faster.

You can also use the YTP technology to find out what trackers are running on a page, and block the ones that you don't trust.

## Blocking trackers for a site {#blocking}

Once a page loads, you can find out how many trackers are blocked on it. To do this:

1. Tap ![](../_assets/chat-settings.svg) → **About the site**.

2. The **Tracker blocking** option will show the number of trackers blocked.

{% cut "**Block until visiting the site**" %}

1. Tap ![](../_assets/chat-settings.svg) → **About the site** → **Tracker blocking**.

2. To the right of the tracker, tap ![](../_assets/trackers-more-details-icon.svg) → **Block**.

The tracker will be blocked until the next time you visit the site it belongs to.

{% endcut %}

{% cut "**Block permanently**" %}

1. Tap ![](../_assets/chat-settings.svg) → **About the site** → **Tracker blocking**.

2. To the right of the tracker, tap ![](../_assets/trackers-more-details-icon.svg) → **Block permanently**.

The tracker remains blocked until you unblock it.

{% endcut %}

{% cut "**Unblock**" %}

If a tracker is blocked, you can unblock it until visiting the site next time or permanently:

1. Tap ![](../_assets/chat-settings.svg) → **About the site** → **Tracker blocking**.

2. To the right of the tracker, tap ![](../_assets/trackers-more-details-icon.svg) and select **Unblock** or **Unblock permanently**.

If the tracker is unblocked, the **Revoke permission** option will block it until you visit its domain next time.

{% endcut %}

## If a site doesn't work {#unblocking}

Some sites need third-party cookies to work correctly. If a site doesn't work, try disabling tracker blocking completely:

1. While on the site page, tap ![](../_assets/but-menu1.svg) to the right of the SmartBox.

1. Select **Tracker blocking**.

1. Tap **Site not working?**

1. In the window that opens, tap **Allow third-party cookies**.

1. Tap **Refresh** to reload the page.

To re-enable tracking protection:

1. While on the site page, tap ![](../_assets/but-menu1.svg) to the right of the SmartBox.

1. Select **Tracker blocking**.

1. Tap the **Enable blocking** link.

1. Tap **Refresh** to reload the page.

<!-- source: en/_includes/button-content.md -->
<a href="en/content">
  <span class="button">Go to the table of contents</span>
</a>


<!-- endsource: en/_includes/button-content.md -->

<!-- source: en/_includes/button-feedback.md -->
</br>

<a href="en/troubleshooting/callerid-form">
  <span class="button">Contact support</span>
</a>


<!-- endsource: en/_includes/button-feedback.md -->

