COOKIE POLICY
Effective from: August 18, 2026
Current status of services
Google Analytics, Google Ads, Google Signals, and Microsoft Clarity are prepared for future integration but are not currently active. The description of these services and their cookies provided below refers to their planned use following activation and the granting of the appropriate consent. We currently use necessary technologies and an optional external Google Maps service.
1. WHO USES COOKIES
The operator of the Bytové domy Jižní svahy project website is:
PERSEMPRE, s.r.o.
registered office at Olomoucká 704/174, Černovice, 627 00 Brno
Company ID: 08508054
VAT ID: CZ08508054
Contact phone: +420 775 000 510
Contact email: grasser@bdjiznisvahy.cz
2. WHAT ARE COOKIES
Cookies are small text files stored on your device when you visit websites. They allow us, for example, to maintain your selected settings, ensure the website functions correctly, measure traffic, and personalize advertising.
Other technologies, such as local browser storage, pixels, device identifiers, and tracking tags, may function in a similar way. In this document, we refer to them collectively as cookies.
3. LEGAL BASIS
We use necessary cookies without consent because they are required for the transmission of communications, website security, saving user preferences, or providing a service explicitly requested by the user.
We use analytical and marketing cookies only with the user's prior consent, in accordance with Act No. 127/2005 Coll., on Electronic Communications. If personal data is processed via cookies, the legal basis is consent pursuant to Article 6(1)(a) of the GDPR.
Upon your first visit, all optional categories are disabled by default. If the user closes the cookie banner, makes no selection, or declines optional cookies, they will remain disabled.
4. COOKIE CATEGORIES
Necessary cookies
These cookies ensure basic functions, security, protection against misuse, and the storage of your choice in the cookie banner. They cannot be turned off via the cookie banner. Their use must not be extended to analytical or advertising purposes.
Functional services — Google Maps
We load the external Google Maps map only after separate consent to functional services. Google Ireland Limited receives, in particular, the IP address and technical browser data and may use its own cookies; processing may also take place outside the EEA. Without consent, the location description remains available without the interactive map. Details: Google policies.
Analytical cookies
These cookies help us understand how visitors use the website, where they come from, which pages they visit, and whether a form has been submitted. We use Google Analytics and Microsoft Clarity.
Microsoft Clarity can create heatmaps, measure clicks, movement, and page scrolling, and record pseudonymized session recordings. The content of form input fields must be masked in Clarity and must not be transmitted as analytical data.
Marketing cookies
We use these cookies via Google Ads, Google Signals, and Google Analytics advertising features. They are used for ad measurement, creating remarketing audiences, ad personalization, and potentially linking activity across devices for logged-in Google users who have ad personalization enabled.
Marketing cookies are only activated after marketing consent has been granted. Analytical consent in itself does not constitute consent to ad personalization.
5. TOOLS AND COOKIES USED
The overview below describes common cookies used by the selected tools. The specific set may vary depending on the browser, device, service settings, and how you arrived at the website. Current cookies can always be viewed in your browser settings and in the detailed settings of the cookie banner.
A. NECESSARY COOKIES
Cookie preferences / cookie banner used
Purpose: storing information about which categories the user has permitted or declined.
Provider: PERSEMPRE, s.r.o., or the provider of the cookie banner used.
Name: js_cookie_consent.
Duration: 365 days for both consent and refusal, unless there is a significant change in processing or the user deletes the choice.
Unit selection — jizni-svahy-selection
SessionStorage stores the selected apartment, parking space, and storage unit during the browser tab session. The provider is PERSEMPRE, s.r.o.
Webflow and security infrastructure
Purpose: technical operation of the website, request routing, protection against misuse, and security.
Provider: Webflow, Inc. and its technical infrastructure.
Duration: for the duration of the session or for another period strictly necessary for the technical purpose.
B. ANALYTICAL COOKIES – GOOGLE ANALYTICS
_ga
Purpose: Distinguishing individual visitors using a pseudonymous identifier.
Provider: Google / first party.
Typical duration: Up to 2 years.
_ga_<ID>
Purpose: Maintaining session state and measuring website usage for the specific Google Analytics service.
Provider: Google / first party.
Typical duration: Up to 2 years.
Google Analytics primarily processes data regarding visits, sessions, approximate location, device, browser, traffic source, visited pages, and events. Form submissions are measured only as an event without transmitting the values of individual fields.
C. ANALYTICAL COOKIES – MICROSOFT CLARITY
_clck
Purpose: Storing a pseudonymous visitor identifier and Clarity settings for the specific website.
Provider: Microsoft / first party.
Typical duration: Up to 1 year.
_clsk
Purpose: Linking multiple page views into a single Clarity session.
Provider: Microsoft / first party.
Typical duration: Approximately 1 day.
CLID
Purpose: Recognizing that the Clarity service has already recorded the given browser.
Provider: Microsoft / third party.
Typical duration: Up to 1 year.
ANONCHK
Purpose: Information on whether the MUID identifier is being passed to the advertising identifier. For Clarity, the value is set so that the ANID advertising identifier is not used.
Provider: Microsoft / third party.
Typical duration: Approximately 10 minutes.
MR
Purpose: Information on whether the MUID identifier needs to be refreshed.
Provider: Microsoft / third party.
Typical duration: Approximately 7 days.
MUID
Purpose: Distinguishing unique web browsers visiting Microsoft services.
Provider: Microsoft / third party.
Typical duration: Up to 13 months.
SM
Purpose: Synchronizing the MUID identifier across Microsoft domains.
Provider: Microsoft / third party.
Typical duration: Session duration.
We do not use Clarity on this website for Microsoft Advertising. The ad_storage signal must be set to "denied" for Clarity, regardless of the user's choice. Without analytical consent, Clarity must not set analytical cookies or create a continuous session recording.
D. MARKETING COOKIES – GOOGLE ADS, GOOGLE SIGNALS, AND REMARKETING
_gcl_au
Purpose: measuring ad effectiveness and storing conversion information.
Provider: Google / first party.
Typical duration: up to 3 months.
_gcl_aw and other cookies with the _gcl_ prefix
Purpose: linking ad clicks to subsequent activity or conversions on the website.
Provider: Google / first party.
Typical duration: usually up to 90 days.
IDE
Purpose: displaying, measuring, and personalizing ads, and limiting their frequency.
Provider: Google / third party.
Typical duration: up to 13 months in the European Economic Area.
test_cookie
Purpose: verifying whether the browser supports cookies.
Provider: Google / third party.
Typical duration: approximately 15 minutes.
NID, AEC, SOCS, and any other Google domain cookies
Purpose: security, setting storage, measurement, and, depending on user settings, content and ad personalization.
Provider: Google / third party.
Duration: depends on the specific cookie and current Google service settings, typically from session duration up to 13 months.
Google may use first-party and third-party cookies, pseudonymous advertising identifiers, and information about user activity together. For users signed in to their Google account with ad personalization enabled, Google Signals can associate activity across different browsers and devices. Individual identities of these users are not made available to administrators; outputs are provided primarily in aggregate form and as advertising audiences.
Further information about how Google uses data is available at:
https://policies.google.com/technologies/partner-sites?hl=en
https://policies.google.com/privacy?hl=en
https://myadcenter.google.com/
Further information about Microsoft Clarity is available at:
https://learn.microsoft.com/clarity/
https://privacy.microsoft.com/en-us/privacystatement
6. GOOGLE CONSENT MODE AND MICROSOFT CLARITY SETTINGS
For visitors from the European Economic Area, the default state for all of the following signals must be "denied" until they make a choice:
- analytics_storage,
- ad_storage,
- ad_user_data,
- ad_personalization.
Analytical consent can only change analytics_storage to "granted."
Marketing consent can change ad_storage, ad_user_data, and ad_personalization to "granted." If a user does not grant or withdraws marketing consent, these signals must remain or revert to "denied."
The website must use basic consent mode: until appropriate consent is granted, optional tags will not load, and Google Analytics, Google Ads, and Microsoft Clarity will not send measurement or advertising requests. Simply closing the banner does not constitute consent.
Clarity must receive an appropriate consent signal. Since we do not use Microsoft Advertising, advertising consent for Clarity is not granted, and its advertising storage remains disabled.
7. HOW TO GRANT, REJECT, OR WITHDRAW CONSENT
In the cookie banner, you can:
- accept all optional cookies,
- reject all optional cookies,
- independently configure functional services and, once tracking is enabled, analytical and marketing cookies.
Buttons for accepting and rejecting must be available in the same layer of the cookie banner, be equally easy to use, and have a comparable visual design. Analytical or marketing options must not be pre-checked.
Consent can be changed or withdrawn at any time via the permanently available "Cookie settings" link in the website footer. Withdrawing consent must be as easy as granting it. Once withdrawn, the relevant cookies will no longer be used, and cookies that can be technically removed will be deleted.
We store your choice for 365 days, both for acceptance and rejection. If a user rejects optional cookies, we will not ask for consent again for at least 6 months, unless there is a significant change in the tools or purposes used, or the user deletes their stored choice.
Cookies can also be managed in your browser settings. Disabling all cookies in your browser may affect some website features.
8. RECIPIENTS AND TRANSFERS OUTSIDE THE EEA
Data obtained through cookies may be made accessible to Google and Microsoft and their processors, depending on the consent granted. Technical data related to website operation may also be made accessible to Webflow and its infrastructure providers.
Some providers may process data outside the European Economic Area, particularly in the United States. Transfers are based on valid safeguards, primarily the EU–U.S. Data Privacy Framework, standard contractual clauses approved by the European Commission, or another mechanism under Chapter V of the GDPR.
Details regarding the processing of personal data and user rights are provided in the Privacy Policy.
9. CHANGES TO THIS POLICY
We continuously review our cookie overview and update this document, particularly when the services, purposes, or storage periods used change.