PRIVACY. TRANSPARENCY. CONTROL.

RAUZ Privacy Policy & Personal Data Protection

This Privacy Policy explains how Rauz Caucasus LLC handles personal data when you visit rauzs.com, contact RAUZ, request services, submit an enquiry or interact with our environmental and engineering monitoring platform.

Privacy Policy

Clear information about how RAUZ handles personal data.

This Privacy Policy applies to the public RAUZ website at rauzs.com and to personal data handled by Rauz Caucasus LLC when people contact RAUZ, request information or quotations, communicate with us, apply for opportunities, or otherwise interact with our public digital services.

Effective: 3 October 2026 Operator: Rauz Caucasus LLC Base: Tbilisi, Georgia Website: rauzs.com
WEBSITE

Public website & enquiries

Applies to visitors, prospective clients, suppliers, partners, applicants and other people who communicate with RAUZ through public channels.

PROJECTS

Project-specific terms may apply

A contracted project, portal, API, software workflow or client dataset may be subject to additional confidentiality, information-security or data-processing terms.

SCOPE

Personal data, not engineering measurements by default

Monitoring measurements about ground, structures, weather or environmental conditions are not personal data unless they are linked to an identified or identifiable person.

Plain-language summary: RAUZ collects only the personal information reasonably connected with operating the website, communicating with people, developing and delivering services, protecting systems, keeping required records and meeting legal obligations. Project data is handled according to the role RAUZ actually performs in the relevant engagement.

Controller

Who is responsible for the personal data covered by this notice?

For normal website use, enquiries, quotation requests, recruitment contacts and RAUZ business communications, Rauz Caucasus LLC acts as the controller to the extent it determines why and how personal data is processed.

Data We Process

The information depends on how you interact with RAUZ.

RAUZ does not need the same information from a website visitor, a prospective client, a supplier contact and a project user. The categories below describe information that may be relevant to those interactions.

YOU PROVIDE

Contact & business information

  • Name, employer, role and professional contact details.
  • Messages, enquiry details and quotation requirements.
  • Information sent by email or through an enabled website form.
  • CV and work-history information if you contact RAUZ about opportunities.
  • Billing, contracting or supplier information when a business relationship develops.
WEBSITE

Technical & usage information

  • IP address and approximate network information.
  • Browser, device and operating-system information.
  • Requested pages, referring page and timestamps.
  • Security, diagnostic and server-log information.
  • Cookie or similar-technology identifiers where those technologies are actually used.
PROJECTS

Project-related personal information

  • Project contact names and professional roles.
  • Correspondence and meeting records.
  • Names contained in reports, drawings or monitoring records.
  • User, author or audit information attached to project files.
  • Other personal data a client is authorised to provide for the agreed work.
Do not send unnecessary sensitive information. Public enquiry routes are not intended for special-category data, identity documents, medical information or large confidential project archives. If a project requires sensitive information, contact RAUZ first so the appropriate scope and transfer route can be agreed.

Purposes & Legal Bases

We process personal data for defined business, security and legal purposes.

The legal basis depends on the activity and the law that applies. Under Georgian law, relevant bases can include consent, steps connected with a contract, legal obligations, review of a person’s request, and legitimate interests where the statutory conditions are met. Where the EU GDPR, UK GDPR or another regime applies, RAUZ uses the basis required for that specific processing rather than treating consent as the basis for everything.

PurposeTypical dataTypical basis, subject to applicable law
Enquiries & RFQsContact details, message content, project contextSteps requested before a contract; review of the person’s request; legitimate interests; or another available statutory basis.
Quotations, contracts & servicesProfessional contacts, commercial, billing and project informationContract performance or pre-contract steps; legal obligation; legitimate interests where permitted.
Website operation & securityIP address, logs, device and request informationLegitimate interests in security, fraud prevention, troubleshooting and service operation; legal obligations where applicable.
Optional analytics / non-essential technologiesOnline identifiers, usage or preference dataConsent where required; otherwise the basis permitted by the law that applies.
Records & legal claimsCorrespondence, contracts, invoices, transaction and dispute recordsLegal obligation; contract; legitimate interests in recordkeeping and establishing or defending legal claims.
Recruitment & collaborationCV, work history, contact and application informationPre-contract steps, consent where appropriate, legal obligation or legitimate interests where available.
Direct marketing under Georgian law: where the Law of Georgia on Personal Data Protection applies to direct marketing, RAUZ will use consent and provide a simple way to withdraw it. Georgian law also requires the fact and date of marketing consent and withdrawal to be recorded for the relevant statutory period.

Cookies & Website Technologies

Cookie disclosures should match the live website, not a generic template.

RAUZ may use cookies, local storage, tags or similar technologies for website operation, security, preferences, performance measurement or embedded functions. The specific technologies disclosed to visitors should be the ones actually active on the production website.

ESSENTIAL

Strictly necessary

Technologies needed for core website functions, security, load balancing, consent preferences or other operation that cannot reasonably be provided without them.

OPTIONAL

Analytics & performance

Where enabled, these may help RAUZ understand aggregate website use and technical performance. Consent is requested where required by applicable law.

THIRD PARTY

Embedded services

Maps, video, forms, social media or other embedded services may process data under their own terms. Where prior consent is legally required, those services should not load before that requirement is met.

RAUZ should not publish the name, retention period or purpose of a cookie, analytics product or advertising technology unless it has been technically verified on the live site.

Sharing & Service Providers

Personal data is shared only where there is an operational, contractual or legal reason.

Recipients depend on the actual service and project. RAUZ should limit disclosures to information reasonably necessary for the relevant purpose and apply appropriate contractual, confidentiality and security controls.

TECHNOLOGY

Digital service providers

Hosting, email, cloud storage, communications, security, backup, collaboration, form-processing or analytics providers may process limited personal data where those services are used.

PROJECT

Professional & project parties

Accountants, legal advisers, consultants, technical partners, subcontractors or other authorised participants may receive data when necessary for the agreed work.

LEGAL

Authorities & legal process

Information may be disclosed where required by applicable law, regulation, court order, lawful governmental request, or where necessary to establish, exercise or defend legal claims.

International Transfers

RAUZ is Tbilisi-based and works across borders, so some data may cross borders.

A website visitor, client, service provider or project team may be in a different country from Rauz Caucasus LLC. International transfer does not remove the need to identify a lawful basis, relevant safeguards and the role of each recipient.

GEORGIA

Transfers under Georgian law

Where Georgian law applies, transfers to another state or international organisation are handled under the Law of Georgia on Personal Data Protection, including the applicable transfer grounds and safeguards.

EU / EEA

GDPR where applicable

Where EU GDPR transfer rules apply, RAUZ will use a legally available mechanism appropriate to the circumstances, such as an applicable adequacy route, contractual safeguards or another permitted basis.

UNITED KINGDOM

UK requirements where applicable

Where UK data-protection law applies, the relevant UK transfer requirements and safeguards are considered for the actual destination, recipient and processing activity.

For project data, the contract or data-processing arrangement should identify any material cross-border processing, the parties’ roles, permitted locations, confidentiality controls and any transfer mechanism required by applicable law.

Retention

We keep personal data for no longer than the purpose, contract or law reasonably requires.

An unanswered enquiry, an active engineering project, an invoice and a security log do not serve the same purpose. RAUZ therefore applies purpose-based retention criteria instead of claiming one universal period for every record.

  • How long the enquiry, project or business relationship remains active.
  • Whether data is needed to deliver or document an agreed service.
  • Accounting, tax, corporate or other recordkeeping obligations.
  • Applicable limitation periods and legal-claim requirements.
  • Security, fraud-prevention, backup and system-integrity needs.
  • Whether consent has been withdrawn where consent is the basis.
  • Whether data can be anonymised instead of retained in identifiable form.
  • Project-specific contractual retention or deletion requirements.
Direct-marketing record: where Georgian direct-marketing rules apply, the law requires the date and fact of consent and withdrawal to be kept for the duration of the direct marketing and for one year after it is discontinued.

Security

Protection depends on both technical controls and disciplined handling.

RAUZ applies organisational and technical measures appropriate to the nature of the information, the processing activity and the risks involved. No internet transmission or storage system can be guaranteed to be completely secure.

ACCESS

Need-to-know access

Access should be limited to people and authorised service providers who need information for a defined business, security or project purpose.

SYSTEMS

Reasonable system protection

Website, account, device, backup, update and security practices should reflect the systems in use and the sensitivity of the information.

MINIMISATION

Collect less where less is enough

RAUZ should avoid collecting, copying or circulating personal data that is not necessary for the agreed website, business or project purpose.

Sensitive project material: ordinary email and public website forms should not be treated as secure archives for identity documents, special-category data, confidential engineering datasets or large project files. Agree an appropriate transfer route before sending sensitive material.

Your Rights

You may have rights over your personal data under the law that applies to you.

Under the current Law of Georgia on Personal Data Protection, data subjects have rights that include information about processing, access and copies, rectification, termination of processing or erasure in relevant circumstances, blocking, transmission of certain data, protection in relation to solely automated decisions, and withdrawal of consent. Statutory exceptions may apply.

01

Information

Ask whether RAUZ processes your personal data and request information about the purpose, basis, source, retention and recipients where the law provides.

02

Access & copy

Request access to personal data concerning you and a copy, subject to the conditions and exceptions in applicable law.

03

Correction

Request correction, updating or completion of inaccurate or incomplete personal data.

04

Deletion / stop processing

Request termination of processing, erasure or destruction where the statutory conditions are met.

05

Blocking

Request temporary blocking in situations recognised by law, for example while accuracy or a deletion request is being examined.

06

Data transmission

For certain automated processing based on consent or contract, request data in a structured, commonly used, machine-readable format where technically feasible.

07

Withdraw consent

Where processing relies on consent, withdraw it using an available and accessible method. Other lawful bases may still permit specific processing.

08

Automated decisions

Exercise applicable rights concerning decisions based solely on automated processing where they produce legal or similarly significant effects.

Georgian response periods: the current Georgian law generally sets 10 working days for several information, access, correction and erasure-related rights, with specific statutory rules and possible extensions in some cases. Blocking decisions have a shorter statutory notification period. Where another privacy regime applies, its own response periods govern.

Project Data

Monitoring intelligence can involve data that is not personal data — and project files that are.

RAUZ works with environmental, geotechnical, agricultural, survey and remote-sensing information. Measurements about ground movement, groundwater, weather, structures or crops are not automatically personal data. Personal-data obligations arise where information identifies or can identify a natural person.

MEASUREMENTS

Technical observations

Instrument readings, InSAR measurements, weather records and similar technical observations are generally handled as project information unless they are linked to identifiable people.

FILES

Personal data inside project records

Reports, drawings, emails, user logs and document metadata can include names, signatures, contact details, authorship or other personal information even when the main purpose of the file is technical.

ROLE

Controller / processor depends on the engagement

For client-provided project data, responsibilities should be defined in the appointment, confidentiality terms and, where needed, a data-processing agreement.

AI-assisted analysis: RAUZ’s monitoring workflows may use automation or AI-assisted tools to organise, screen, compare or report technical information. The public website privacy notice does not treat asset-monitoring analytics as profiling of individuals unless personal data is actually used to evaluate a person. Project-specific use of personal data in automated processing must follow the applicable contract and law.

Official Sources

Privacy rules should be checked against current official sources.

RAUZ operates from Georgia and serves international markets. The links below are official legal or regulatory sources relevant to this public Privacy Policy. They are included for transparency and verification, not as a substitute for project-specific legal advice.

GEORGIA

Law of Georgia on Personal Data Protection

Current consolidated legal framework for personal-data processing, data-subject rights, direct marketing, security and international transfers in Georgia.

Open the official Matsne text ↗
EU

General Data Protection Regulation

The official EUR-Lex text of Regulation (EU) 2016/679, relevant where the GDPR applies to a RAUZ processing activity.

Open EUR-Lex ↗
UNITED KINGDOM

ICO privacy-information guidance

Official guidance from the UK Information Commissioner’s Office on the information organisations should provide when processing personal data.

Open ICO guidance ↗
Privacy, cookie and data-transfer rules can change. RAUZ should review this page when the website introduces new analytics, forms, cloud services, marketing tools, user accounts or material changes to project-data processing.

FAQs

Common questions about privacy at RAUZ.

These answers explain the public website policy in practical terms. A contracted project may include more specific confidentiality, security and data-processing requirements.

Does RAUZ collect project files through the public quote page?
The current RAUZ quote builder prepares an email in the user’s own email application and states that project files are not uploaded through that page. Attachments should be sent only after the appropriate transfer route has been confirmed.
Does every monitoring dataset contain personal data?
No. Ground movement, groundwater, weather, InSAR and other technical measurements are not personal data merely because they are monitoring records. Personal-data rules become relevant when information identifies or can identify a natural person.
Does RAUZ always act as the data controller?
No. Rauz Caucasus LLC is normally the controller for its own website and business communications. For client project data, RAUZ’s role may instead be processor, service provider, joint controller or independent controller depending on the agreed purpose, instructions and applicable law.
Does RAUZ rely on consent for all processing?
No. Depending on the activity and applicable law, processing may rely on contract or pre-contract steps, legal obligations, review of an individual’s request, legitimate interests where permitted, or consent. Direct marketing under Georgian law requires consent.
Can I ask RAUZ to delete my personal data?
You may request deletion or termination of processing where the applicable law provides that right. The request may be refused where a lawful ground requires continued processing, for example certain legal obligations or legal claims. RAUZ should explain any lawful refusal.
Does this policy mean EU GDPR or UK GDPR applies to every RAUZ interaction?
No. Rauz Caucasus LLC is based in Georgia. EU, UK or other privacy rules apply only where their legal scope is engaged by the relevant processing activity. This policy therefore distinguishes the Georgian legal base from additional regimes that may apply in particular circumstances.

Privacy Contact

Ask a privacy question or exercise an applicable right.

Provide enough information to identify the relevant interaction or record, but do not send unnecessary identity documents or sensitive project files in the first email. RAUZ may need to verify identity before disclosing or changing personal data.

ADDRESS

Rauz Caucasus LLC

N20, Apt N70, Vazha Pshavela Avenue
Tbilisi 0160, Georgia

Scroll to Top