CLEAR. GRANULAR. REVERSIBLE.
Manage Cookies & Privacy Preferences
Review how rauzs.com uses cookies and similar technologies, understand which functions may require consent, change optional privacy choices, and find browser controls for deleting or blocking stored website data.
Cookie & Privacy Preferences
Control optional website technologies without losing sight of what is essential.
This page explains how cookies and similar storage or access technologies may be used on rauzs.com, how optional technologies should be controlled, how to revisit a previous choice and how to remove website data from your browser.
A cookie is a small piece of data stored by a website through your browser. Websites may use cookies to provide requested functions, remember preferences, understand site use or support third-party services. Similar rules can also apply to local storage, pixels, scripts, tags and other technologies that store information on or access information from a device.
Know the purpose.
Optional technologies should be described clearly enough for a visitor to understand why they are used and what choosing them means.
Control optional use.
Where consent is required, the choice should be specific and affirmative rather than inferred from silence, inactivity or simply continuing to browse.
Change your mind.
Where a technology relies on consent, visitors should be able to withdraw that consent through an accessible preference mechanism.
RAUZ does not guess its live cookie inventory on this page. The authoritative list of cookie names, providers, purposes and durations should come from the current production-site audit or consent management platform. This avoids publishing a legal notice that becomes inaccurate when website tools change.
Preference Centre
Open the live cookie settings for this website.
The button below does not create, delete or override consent by itself. It looks for the cookie-preference control already provided by the production website and opens that existing control. If no compatible preference control is available in the current browser session, a fallback message is shown.
Cookie preferences
Implementation note for the website owner: this helper only opens an existing consent-management control. It never treats this page as proof of consent and does not attempt to delete HttpOnly, server-side or third-party cookies.
Cookie Categories
Purpose matters more than the label.
Cookie categories are a practical way to explain choices, but legal treatment depends on what a technology actually does. The live RAUZ cookie inventory should classify each technology by its real purpose and whether an applicable consent exception exists.
Strictly necessary
Technologies required to deliver a service or function specifically requested by the visitor, or otherwise falling within a lawful technical exception. They should not be repurposed for unrelated analytics or advertising.
Analytics & performance
Technologies used to understand visits, navigation, performance or aggregate site use. Whether consent is required depends on the applicable law, purpose, implementation and any available exception.
Functionality & preferences
Technologies that remember choices or provide enhanced features. Some may fall within a narrow exception when genuinely necessary for a user-requested feature; others may require consent.
Advertising & profiling
Technologies used to build profiles, track behaviour across services or support targeted advertising generally require a clear choice before use under EU and UK cookie rules.
| Category | Typical purpose | RAUZ publication rule |
|---|---|---|
| Strictly necessary | Security, requested session functions, load balancing, consent-preference storage or another essential function. | List only technologies actually present on the live site and explain why each one is necessary. |
| Analytics / performance | Audience measurement, site performance or understanding use of pages and features. | Do not name an analytics provider unless it is actually installed and reflected in the live consent configuration. |
| Functionality | Remembered preferences, embedded features or enhanced user experience. | Explain whether the feature is user-requested, whether storage persists and whether consent is required. |
| Marketing / targeting | Advertising, behavioural tracking, cross-site profiling or campaign attribution. | Do not activate before valid consent where consent is required; disclose relevant third parties and purposes. |
Beyond Cookies
Privacy controls can apply to more than small text files.
Modern websites can store or access information through several technologies. The UK ICO’s 2026 guidance expressly covers cookies, tracking pixels, link decoration, web storage, fingerprinting, scripts and tags. The relevant question is what the technology does, not what it is called.
Local & session storage
Web storage can hold information in the browser without using a traditional cookie. It may be temporary or persistent depending on the implementation.
Pixels, scripts & tags
Embedded code can record events, load third-party services or communicate information about a page view or interaction.
Fingerprinting & navigational tracking
Some technologies can derive or transmit identifiers from device, browser or navigation characteristics even when a conventional cookie is not used.
RAUZ publication rule: if the production website introduces a new storage or access technology for a new purpose, the cookie/privacy documentation and consent settings should be reviewed before the technology is enabled for visitors who must consent.
Third-Party Services
Embedded services can bring their own privacy consequences.
A website may load content, analytics, maps, video, forms, security features or other tools supplied by external organisations. If those services store or access information on a visitor’s device, the relevant third party, purpose and control should be reflected in the live consent configuration.
Know what the service does.
RAUZ should verify whether an embedded service sets cookies, uses local storage, loads tags or sends device and usage information to a third party.
Block optional technology where required.
Where consent is the legal basis for storage or access, optional technology should not be activated before the required positive choice has been made.
Keep the inventory current.
Third-party providers, purposes and retention periods can change. RAUZ should review the live inventory when website tools, plugins or embedded services change.
No speculative vendor list: this page intentionally does not claim that RAUZ uses Google Analytics, Meta Pixel, LinkedIn Insight Tag or any other named tracker unless that technology is verified on the production site.
Consent & Withdrawal
A choice should be informed, specific and easy to revisit.
For visitors covered by consent-based cookie rules, a compliant preference mechanism should distinguish optional purposes, avoid treating silence as agreement and make withdrawal no harder than giving consent.
No silent opt-in.
Under EU guidance and UK rules, consent is not created merely because a person continues to browse. Optional technologies that require consent should remain off until the necessary action occurs.
Granular purposes.
Where different technologies serve different purposes, visitors should be given meaningful choices rather than being forced into one bundled “accept everything” decision.
Withdrawal remains available.
If consent is withdrawn, technologies relying on that consent should stop future optional storage or access. Previously stored data may still need to be removed through the browser or the relevant provider’s controls.
Changing the website may require fresh consent. The ICO’s final 2026 guidance says that a new technology or a new purpose can require a fresh consent decision. The live RAUZ preference mechanism should therefore be reviewed whenever tracking, analytics, embedded media or advertising tools change.
Browser Controls
Delete or block stored website data directly in your browser.
A website preference centre controls the technologies that the site chooses to use. Browser settings provide a separate layer of control and can be used to remove cookies or site data already stored on your device.
Google Chrome
Google’s official guidance explains how to delete existing cookies, block or allow third-party cookies and change site-specific settings.
Google Chrome Help ↗Apple Safari
Apple provides controls for website data, cross-site tracking and cookies in Safari on Apple devices.
Apple Support ↗Mozilla Firefox
Mozilla explains how to clear cookies and site data for the current website, a specific website or all websites.
Mozilla Support ↗Microsoft Edge
Microsoft provides controls to view, allow, block and delete cookies and site data, including site-specific controls.
Microsoft Support ↗Deleting cookies can also remove stored preferences or session information. If the cookie that remembers your consent choice is deleted, the website may ask for your preference again on a later visit.
Privacy Rights
Cookie choices are part of a wider data-protection framework.
RAUZ is operated by Rauz Caucasus LLC in Tbilisi, Georgia. The website is intended for international use, so the applicable privacy and cookie rules can depend on the visitor, the technology, the purpose and the jurisdiction involved.
Personal data protection
Georgia’s Law on Personal Data Protection governs processing of personal data within its scope, including automated processing and electronic communication identifiers.
GDPR & ePrivacy rules
The EDPB states that cookies involving personal data can engage the GDPR, while storage or access on a user’s device is also governed by the more specific ePrivacy rules.
PECR & UK GDPR
The ICO’s final 2026 guidance covers cookies and other storage/access technologies under PECR and, where personal data is processed, the UK GDPR.
This page is operational information, not jurisdiction-specific legal advice. Where a law grants a visitor additional rights or requires a different consent mechanism, the mandatory rule applies.
Official Sources
Primary regulatory and platform guidance.
The sources below are official publications used to frame this page. They should be checked again when RAUZ materially changes its website technologies or when the relevant law or regulator guidance changes.
European Data Protection Board
The EDPB’s small-business guidance explains the relationship between cookies, personal data, the GDPR and ePrivacy consent, including the exception for technically necessary cookies.
Official EDPB guidance ↗European Commission
The Commission’s cookie policy explains first-party and third-party cookies, session and persistent cookies, preference storage, operational cookies and browser controls.
European Commission cookie policy ↗UK Information Commissioner’s Office
The ICO’s final April 2026 guidance covers cookies, pixels, web storage, fingerprinting, scripts, tags, consent, exceptions, third parties and withdrawal mechanisms.
ICO storage & access guidance ↗Georgia — Legislative Herald of Georgia
The official consolidated Law of Georgia on Personal Data Protection provides the national legal framework for personal-data processing within its scope.
Official Georgian law ↗Frequently Asked Questions
Common questions about cookie and privacy preferences.
Can I use rauzs.com without accepting optional cookies?
Why are strictly necessary cookies not always switchable?
How do I change a previous cookie choice?
Does withdrawing consent delete cookies already stored on my device?
Does RAUZ use Google Analytics or advertising pixels?
Are cookies the only technology covered by these controls?
Why might the cookie banner appear again?
Can my browser block cookies independently of RAUZ?
Privacy Contact
Questions about website privacy or cookie controls?
If the preference control does not behave as expected, if you believe an optional technology is loading before the required choice, or if you need clarification about RAUZ website privacy, contact RAUZ and identify the browser, device and page involved.
RAUZ
rauzs.com is operated for RAUZ by Rauz Caucasus LLC, Tbilisi, Georgia.
Contact RAUZ →What to include
Browser and version, device type, page URL, approximate time of the issue, the choice you attempted to make and a screenshot if it helps explain the problem.