COOKIE PROCESSING POLICY
Effective from August 30, 2025
1. INTRODUCTION
1.1. This Cookie Processing Policy (hereinafter referred to as the Policy) of the Owner, as defined in clause 1.8 of the Public Agreement, is developed in compliance with the requirements of the legislation applicable pursuant to clause 1.3 of the Privacy Policy, with the aim of protecting the personal data of Users of the web version of the SENS app (hereinafter referred to as the Service), who are subjects of personal data.
1.2. The Policy explains to Users of the Service for what purposes and how the Owner processes cookies, as well as how Users can control the process of such processing.
1.3. Cookies are small files with text and (or) digital information that are transmitted to the User’s device browser (computer, tablet, smartphone) when visiting the Service. When the User tries to open the Service page, the browser sends the corresponding files to the server in order to authenticate the User, store their personal preferences and settings, track the status of the User’s access session, and so on.
1.4. Cookies do not pose a threat to the User’s device, since they are text, not running programs.
1.5. The information obtained during the use of cookies may include information about the User’s browser and device, data collected during automatic electronic interaction between the User’s device and the Service, including statistical and marketing information.
1.6. The Owner processes cookies for the following purposes:
1.6.1. to ensure the security of Service Users;
1.6.2. to ensure correct operation of the Service and improve its usability;
1.6.3. to create and provide personalized advertising;
1.6.4. to collect aggregated analytical information to evaluate and further improve the Service’s performance.
1.7. The Service does not use cookies to identify Users.
1.8. The legal basis for processing cookies by the Owner is a Public Agreement and (or) the User’s consent as a personal data subject, expressed by performing the corresponding action provided for by the user flow of the Service (user route of the Service): by clicking the «Accept all» or «Save my settings» button on the pop-up banner.
1.9. The Owner uses both its own cookies (set directly by the Service) and third-party cookies (set by third-party services).
2. CLASSIFICATION OF PROCESSED COOKIES
2.1. The Service processes the following types of cookies according to their intended purpose:
2.1.1. strictly necessary:
These cookies are necessary for the operation of our Service and for providing basic functions such as page navigation and access to protected areas of the Service. Without these cookies, the Service will not work properly. This type of cookie cannot be disabled.
2.1.2. functional:
These cookies allow the Service to remember User preferences, such as the interface language or selected region, and provide enhanced and more personalized features. They allow the Service to automatically adapt to the relevant parameters during repeated visits and provide useful functions, such as using map functions, remembering the settings of Service Users, and improving User interaction with Service pages. This file type is necessary for the normal operation of the Service and its functionality and cannot be disabled.
2.1.3. analytical (productive):
These cookies are used to understand how Users and (or) other Service visitors interact with the Service, and help provide information about indicators such as the number of visitors, bounce rate, traffic source, and so on. The main analytical cookies that the Owner uses are Google Analytics and Yandex Metrica, as well as the Amplitude and AppsFlyer cookies. These cookies collect data such as IP address, browser type, platform, language, pages visited, time spent on the site, and other analytical information. This type of file is anonymized (depersonalized) and does not contain personal data of Users.
2.1.4. targeted (advertising):
These cookies are used for marketing purposes and to improve the quality of advertising, creating a profile of Users’ interests and offering them personalized ads that best match their preferences. They can also be used to limit the number of ad impressions and measure the effectiveness of ad campaigns.
2.2. By storage type, cookies can be divided into the following categories:
2.2.1. session:
stored in the User’s browser only for the duration of the session, i.e., until the User closes the browser or logs out. These cookies are used to preserve User state information and ensure session security;
2.2.2. persistent:
stored for a long period in the User’s browser and can be used to store information that will be available on the next visit to the Service. Such cookies are stored for the time specified in the cookie parameters or until deleted by the User and may contain information about User preferences, such as interface language, authorization data, and also enable tracking of user behavior online.
2.3. The Service, using third-party cookies, may transfer aggregated data (information about Users combined into a general array based on their behavioral characteristics), not linked to the identification of a specific User, to third parties whom the Owner has entrusted with the processing of auxiliary cookies, listed in Appendix 1 to this Policy.
2.4. The full list of cookies processed by the Service, a description of their functional purpose and their storage period can be found in Appendix 2 to this Policy, which is an integral thereof.
3. USER CONTROL OVER COOKIE PROCESSING
3.1. When the User logs into the Service for the first time, they are asked to consent to the use of cookies or refuse to use them by clicking the appropriate «Accept all», «Save my settings» or «Reject» buttons on the pop-up information banner.
3.2. By clicking the «Accept all» button, the User agrees to use all types of cookies specified in clause 2.1 of this Policy. When clicking the «Save my settings» button, the User independently selects and marks with the appropriate slider the category of cookies for which they consent to their processing. When the «Reject» button is clicked, the User refuses to use analytical and targeted cookies.
3.3. Since the Owner can ensure the full and correct functioning of the Service, including the security of its use, only by using mandatory and functional cookies, this type of cookie cannot be disabled.
3.4. Disabling analytical and (or) targeted cookies will not allow us to take measures to improve the operation of the Service based on the User’s preferences, as well as to select advertising and other advertising materials for the most relevant, suitable purpose for each specific User.
3.5. The Service stores the User’s choice about cookie settings for the period specified in Appendix 2 to the Policy. At the end of this period, the Service will again request the User’s consent by repeatedly popping up an information banner.
3.6. The User of the Service can change their choice, as well as refuse to use cookies before the expiration of the period specified in clause 3.5 of this Policy, by performing the actions provided for by the user flow (user path) of the Service when clicking on the «Cookie Settings» button as well as by configuring the web browser used in the manner specified in clause 3.7 of this Policy.
3.7. The User can manually clear the device and (or) refuse to use cookies by accessing the browser configuration settings and selecting one of the following options:
- blocking cookies on the User’s device.
- notification from the browser to the User about the consent to install a new cookie on the User’s device;
- accepting or rejecting cookies depending on the sender.
At the same time, some browsers allow you to visit sites in «incognito» mode to automatically delete session cookies.
You can learn more about the cookie management settings by clicking on the external links that lead to the sites of the main browsers listed in Appendix 3 to this Policy.
4. FINAL PROVISIONS
4.1. The Owner has the right, at its sole discretion, to unilaterally change and (or) supplement the terms of this Policy without prior notification to the subjects of personal data by publicly posting it in the information and telecommunications network of the Internet, with the exception of changes and (or) additions regarding the processing of analytical and targeted cookies.
The Owner has the right to make changes and (or) additions to the Policy regarding the processing of analytical and targeted cookies at its sole discretion, unilaterally, with mandatory notification of the User about the change and (or) addition by repeatedly popping up the Service banner with an offer to (i) accept such changes and (or) additions and agree to the processing of analytical and targeted cookies by clicking the «Accept all» button; (ii) refuse the processing analytical and targeted cookies by clicking the «Reject» button; (iii) accept such changes and (or) additions and agree to the processing of analytical and targeted cookies on the terms and in the amounts personalized by the User themselves, by selecting the appropriate items with the slider and then clicking the «Save my settings» button.
If the User does not agree with the changes and (or) additions made to the Policy in whole or in part, as well as if the corresponding settings are changed by the User, the Owner is obliged to stop processing the corresponding User cookies.
4.2. The User has the right to request assistance in exercising their rights, as well as on issues related to the use of Cookie be the Owner by sending an email to the email address secure@sense.dating or by submitting an application in writing in accordance with the procedure specified in clauses 7.3 – 7.4 of the Privacy Policy.
Appendix 1
to the Cookie Processing Policy
List of Third Parties assigned by the Owner to process auxiliary cookies
Name of the Subject |
Address |
Cookie Types |
Privacy Policy |
Yandex LLC |
16 Lva Tolstogo str., Moscow, 119021, Russian Federation |
cookies of the Yandex.Metrica web analytics service and the Yandex online advertising service Yandex.Direct |
|
Google LLC |
1600 Amphitheatre Parkway, Mountain View, California 94043, USA |
cookies of the Google Analytics web analytics service |
|
Google Ireland Ltd. |
Gordon House, Barrow Street, Dublin 4, D04 E5W5, Ireland |
Google AdSense contextual advertising service cookies |
|
Amplitude Inc. |
201 3rd Street, Suite 200, San Francisco, CA 94103, USA |
cookies of the service for product analytics |
|
AppsFlyer Inc. |
100 First Plaza, 100 1st St, San Francisco, USA |
the service’s cookies for web attribution solutions |
|
CookieYes Limited |
3 Warren Yard Warren Park, Wolverton Mill, Milton Keynes, MK12 5NW, United Kingdom |
Service cookies |
Appendix 2
to the Cookie Processing Policy
List of cookies collected by the Owner and (or) Third Parties on behalf of the Owner
Cookie file name |
Provider |
Purpose of cookie processing |
Cookie file type |
Storage period |
The amount of disclosed data |
XSRF-TOKEN |
SENS |
CSRF protection against attacks |
Strictly Necessary |
Session |
Security token |
sens_auth_token |
SENS |
User authentication |
Strictly Necessary |
7 days |
Encrypted authorization token |
sens_refresh_token |
SENS |
Updating the authorization session |
Strictly Necessary |
30 days |
Update token |
sens_device_id |
SENS |
Device identification for security |
Strictly Necessary |
1 year |
Unique device ID |
SESSION |
SENS |
Maintaining a server session |
Strictly Necessary |
Session |
Session ID |
__session |
Google LLC (Firebase) |
Firebase session management |
Strictly Necessary |
2 weeks |
Firebase session token |
firebase-auth-token |
Google LLC (Firebase) |
Firebase authentication token |
Strictly Necessary |
1 hour |
Auth token |
__firebase_request_key |
Google LLC (Firebase) |
Firebase request key |
Strictly Necessary |
Session |
Request key |
firebase-idToken |
Google LLC (Firebase) |
Firebase User ID token |
Strictly Necessary |
1 hour |
User ID token |
firebase-refreshToken |
Google LLC (Firebase) |
Updating the Firebase token |
Strictly Necessary |
Constant |
Refresh token |
sens_user_id |
SENS |
User identification in the system |
Functional |
1 year |
SENS user ID |
sens_session |
SENS |
User's session in the app |
Functional |
30 days |
App session ID |
sens_preferences |
SENS |
Saving Partner search settings |
Functional |
1 year |
Preference settings |
sens_location |
SENS |
Defining the region to search for |
Functional |
7 days |
Geolocation hash |
sens_filters |
SENS |
Saving search filters |
Functional |
30 days |
Filter parameters |
sens_theme |
SENS |
Interface design theme |
Functional |
1 year |
Setting up a theme |
sens_lang |
SENS |
Interface language |
Functional |
1 year |
Language code |
sens_onboarding |
SENS |
Tracking the registration stage |
Functional |
90 days |
Onboarding status |
sens_last_seen |
SENS |
Last User activity |
Functional |
7 days |
Timestamp |
sens_notifications |
SENS |
Notification settings |
Functional |
1 year |
Notification settings |
cookieyes-consent |
CookieYes Limited |
Cookie consent management |
Functional |
12 months |
Consent status |
cky-consent |
CookieYes Limited |
Detailed consent by category |
Functional |
12 months |
Consent categories |
cky-action |
CookieYes Limited |
Last action with the banner |
Functional |
12 months |
Type of action |
cky-active-check |
CookieYes Limited |
Checking the banner activity |
Functional |
1 day |
Verification status |
firebase_feature_flag* |
Google LLC (Firebase) |
Feature flags for A/B tests |
Functional |
30 days |
Function flags |
firebase-messaging-token |
Google LLC (Firebase) |
Token for push notifications |
Functional |
30 days |
FCM token |
_ga |
Google LLC |
Distinguishing between unique site visitors, view statistics |
Analytical |
2 years |
Anonymous user ID, aggregated session data |
ga<container-id> |
Google LLC |
Maintaining session status |
Analytical |
2 years |
Session ID |
_gid |
Google LLC |
Distinguishing between visitors during the day |
Analytical |
24 hours |
Anonymous session ID |
_gat (_gat_UA-#) |
Google LLC |
Limiting the frequency of requests |
Analytical |
1 minute |
Anonymous query frequency data |
ga<stream-id> |
Google LLC |
GA4 data stream identifier |
Analytical |
2 years |
Stream ID GA4 |
gac_gb<container-id> |
Google LLC |
Information about the advertising campaign |
Analytical |
90 days |
Campaign information |
__utma |
Google LLC |
Difference between sessions and users |
Analytical |
2 years |
User and session IDs |
__utmb |
Google LLC |
Defining new sessions |
Analytical |
30 minutes |
Session timestamp |
__utmc |
Google LLC |
Determining the end of the session |
Analytical |
Session |
Session status |
__utmz |
Google LLC |
Sources of traffic and campaigns |
Analytical |
6 months |
Traffic source |
_ym_uid |
ООО «Яндекс» |
Unique user ID for behavior analysis |
Analytical |
1 year |
Unique identifier, aggregated statistics |
_ym_d |
ООО «Яндекс» |
Date of the first session (for repeat session metrics) |
Analytical |
1 year |
Date of the first session |
_ym_isad |
ООО «Яндекс» |
Checking for an ad-block, сounter's correct operation |
Analytical |
24 hours |
Flag for the presence of a blocker |
_ym_visorc |
ООО «Яндекс» |
Webvisor – recording User actions |
Analytical |
30 minutes |
Actions data |
_ym_mp2_substs |
ООО «Яндекс» |
Number substitution CallTracking |
Analytical |
30 days |
Substitution data |
_ym_metrika_enabled |
ООО «Яндекс» |
Metrica’s operating status |
Analytical |
1 day |
Activation status |
amplitude_id_<API_KEY> |
Amplitude Inc. |
Identification of the device and/or user, formation of sessions and events |
Analytical |
1 year |
Device ID, session ID, event counters (anonymized) |
amplitude_cookie_test |
Amplitude Inc. |
Checking cookie support |
Analytical |
Deleted immediately |
Technical status only |
AMP_<hash> |
Amplitude Inc. |
Alternative identifier |
Analytical |
1 year |
Hash ID |
AMP_MKTG_<hash> |
Amplitude Inc. |
Tracking marketing campaigns |
Analytical |
1 year |
Campaign information |
amplitude_session_<API_KEY> |
Amplitude Inc. |
Session identifier |
Analytical |
30 minutes |
Session ID |
af_id |
AppsFlyer Inc. |
Statistics on attribution and effectiveness of advertising campaigns |
Analytical |
2 years |
Unique identifier of the installation and/or client, aggregated attribution |
afUserId |
AppsFlyer Inc. |
AppsFlyer User ID |
Analytical |
2 years |
User ID |
AF_SYNC |
AppsFlyer Inc. |
Data synchronization between platforms |
Analytical |
7 days |
Synchronization data |
af_session_id |
AppsFlyer Inc. |
AppsFlyer session ID |
Analytical |
Session |
Session ID |
af_click_id |
AppsFlyer Inc. |
Attribution of clicks |
Analytical |
30 days |
Click ID |
_gcl_au |
Google Ireland Ltd. |
Google Ads Conversions |
Targeted |
90 days |
Conversion ID |
_gcl_aw |
Google Ireland Ltd. |
Click ID for tracking conversions |
Targeted |
90 days |
Click ID |
_gcl_dc |
Google Ireland Ltd. |
DoubleClick activity floodlight |
Targeted |
90 days |
Activity ID |
IDE |
Google Ireland Ltd. |
Ad targeting and personalization |
Targeted |
1 year |
ID for targeting |
NID |
Google Ireland Ltd. |
Ad settings and preferences |
Targeted |
6 months |
User preferences |
1P_JAR |
Google Ireland Ltd. |
Collecting statistics for optimization |
Targeted |
30 days |
Statistical data |
CONSENT |
Google Ireland Ltd. |
GDPR consent status |
Targeted |
20 years |
Consent status |
test_cookie |
Google Ireland Ltd. |
Checking cookie support |
Targeted |
15 minutes |
Technical status |
yandexuid |
ООО «Яндекс» |
The identifier for ad targeting |
Targeted |
10 years |
User ID |
yuidss |
ООО «Яндекс» |
ID for a specific domain |
Targeted |
1 year |
Domain ID |
i |
ООО «Яндекс» |
User identifier |
Targeted |
10 years |
User ID |
yabs-sid |
ООО «Яндекс» |
Advertising system session |
Targeted |
Session |
Session ID |
_yasc |
ООО «Яндекс» |
Scroll tracking for ads |
Targeted |
10 years |
Scroll data |
yashr |
ООО «Яндекс» |
Data on ad traffic |
Targeted |
1 year |
Traffic history |
_ym_fa |
ООО «Яндекс» |
First attribution of the source |
Targeted |
1 year |
Traffic source |
_fbp |
Meta Platforms, Inc. |
Facebook Browser ID for retargeting |
Targeted |
90 days |
Browser ID |
_fbc |
Meta Platforms, Inc. |
Facebook Click ID |
Targeted |
90 days |
Click ID |
fr |
Meta Platforms, Inc. |
Encrypted ID for retargeting |
Targeted |
90 days |
Encrypted ID |
xs |
Meta Platforms, Inc. |
Facebook User session |
Targeted |
90 days |
Session ID |
c_user |
Meta Platforms, Inc. |
User ID Facebook |
Targeted |
90 days |
User ID |
datr |
Meta Platforms, Inc. |
Browser identification |
Targeted |
2 years |
Browser ID |
sb |
Meta Platforms, Inc. |
Browser security |
Targeted |
2 years |
Security token |
wd |
Meta Platforms, Inc. |
Browser window size |
Targeted |
7 days |
Window size |
remixlang |
ООО «ВКонтакте» |
VK interface language |
Targeted |
1 year |
Language code |
remixstid |
ООО «ВКонтакте» |
VK session ID |
Targeted |
Session |
Session ID |
remixdt |
ООО «ВКонтакте» |
Device parameters |
Targeted |
1 year |
Device data |
vk_ads_retargeting_id |
ООО «ВКонтакте» |
ID for retargeting VK Ads |
Targeted |
90 days |
Retargeting ID |
remixsid |
ООО «ВКонтакте» |
Secure session ID |
Targeted |
90 days |
Secure ID |
mrcu |
ООО «Мэйл.Ру» |
User ID Mail.ru |
Targeted |
1 year |
User ID |
tmr_lvid |
ООО «Мэйл.Ру» |
Visitor ID Top.Mail.Ru |
Targeted |
1 year |
Visitor ID |
tmr_lvidTS |
ООО «Мэйл.Ру» |
Session timestamp |
Targeted |
1 year |
Timestamp |
mt_click_id |
ООО «Мэйл.Ру» |
myTarget Click ID |
Targeted |
30 days |
Click ID |
mt_sub |
ООО «Мэйл.Ру» |
myTarget subaccount |
Targeted |
30 days |
Subaccount ID |
_ttp |
TikTok Pte. Ltd. |
TikTok Pixel ID |
Targeted |
13 months |
Pixel ID |
_tt_enable_cookie |
TikTok Pte. Ltd. |
Cookie consent status |
Targeted |
13 months |
Cookie status |
tt_chain_token |
TikTok Pte. Ltd. |
Attribution chain |
Targeted |
13 months |
Attribution chain |
ttwid |
TikTok Pte. Ltd. |
Web visitor ID |
Targeted |
13 months |
Visitor ID |
ttclid |
TikTok Pte. Ltd. |
TikTok Click ID |
Targeted |
90 days |
Click ID |
Appendix 3
to the Cookie Processing Policy
List of browsers and external links to their sites
Name of the browser |
Link to the site |
Firefox |
|
Google Chrome |
|
Safari |
|
Opera |
|
Microsoft Edge |
|
Internet Explorer |