Cookie policy and consent settings
This Cookie Policy explains what cookies are, which ones the lorcabase.com site uses, for what purpose and how you can manage them. It forms part of the Privacy Policy and the Legal Notice of LORCABASE - FZCO.
1. What cookies are
A cookie is a small text file that a website installs on the user's browser to store information about the visit (preferences, session, statistics, etc.). They may be session cookies (deleted when the browser is closed) or persistent (kept for a defined period). Some are placed directly by the site visited (first-party cookies) and others by external services integrated into it (third-party cookies).
Other technologies similar to cookies used on this site include local storage (browser local storage) and verification tokens for anti-bot protection.
2. Types of cookies according to their purpose
- Technical or necessary: essential for the operation of the site (navigation, security, load balancing, anti-bot protection). They do not require consent.
- Preferences: allow user choices to be remembered (language, region). They require consent.
- Analytics / statistics: measure the use of the site in aggregate to improve it. They require consent.
- Marketing / advertising: allow relevant advertising to be displayed or campaigns to be measured. They require consent. LorcaBase currently does NOT use cookies of this type.
3. Cookies and technologies used by this site
The following table describes all the cookies and storage technologies currently used on lorcabase.com:
3.1 Technical cookies (necessary, no consent required)
- __cf_bm · Cloudflare, Inc. · Third-party · Duration: 30 minutes · Purpose: identifies automated traffic (bots) to protect the security of the site. Essential for the operation of the CDN and the anti-bot system.
- cf_clearance · Cloudflare, Inc. · Third-party · Duration: 30 days · Purpose: remembers that the visitor has passed a security verification challenge, avoiding the need to repeat it on subsequent visits.
- cf_chl_* · Cloudflare, Inc. · Third-party · Duration: session · Purpose: associated with the Cloudflare Turnstile system that protects the contact form against automated submissions (spam and bots). It is installed only when interacting with the form.
- lb_consent_v1 · LorcaBase · Browser local storage · Duration: until the user clears the site's stored data · Purpose: remembers whether the user accepted or rejected optional cookies and content so the notice is not shown on every visit.
3.2 Analytics cookies (consent required)
If the user selects “Accept all”, the site loads Google Analytics 4 (GA4), using measurement ID G-H190H15VHV, to understand in aggregate how the website is used and improve its content and navigation. If the user rejects cookies, the Google Analytics library is not loaded.
- _ga · Google Analytics · Third-party · Typical duration: up to 2 years · Purpose: distinguish visitors pseudonymously and calculate usage statistics.
- _ga_* · Google Analytics · Third-party · Typical duration: up to 2 years · Purpose: maintain session state and collect aggregate navigation metrics.
Google may process technical data such as online identifiers, pages visited, device, browser, approximate time and general location data derived from the connection. More information: Google Privacy Policy and privacy and data in Google Analytics.
Selected client reviews are served directly from lorcabase.com as first-party content. Displaying them does not connect to Google or an external widget platform; Google only receives data if the user voluntarily opens the link to the original review.
3.3 Third-party integrations
- Google Maps (google.com) · Google · Third-party · Purpose: display the embedded office map. The map is loaded only after the user selects “Accept all”; it is then downloaded automatically when its section approaches the visible area. It may involve processing technical data. More information: policies.google.com/technologies/cookies
3.4 What we do NOT use
For transparency, we hereby state that lorcabase.com does NOT currently use:
- Meta (Facebook/Instagram), TikTok, LinkedIn or other social network pixels.
- Advertising or retargeting cookies.
- Google reCAPTCHA (we use Cloudflare Turnstile, which is more privacy-respecting).
If additional tools requiring consent are incorporated in the future, this Policy will be updated before they are activated and the corresponding consent will be requested.
4. Legal basis for the use of cookies
- Technical and necessary cookies: the controller's legitimate interest in ensuring the security and operation of the site. They do not require consent (Art. 22(2) of Directive 2002/58/EC and equivalent regulations).
- Google Analytics cookies: the user's consent, requested through the cookie notice before the tool is loaded.
- Google Maps: user consent given by selecting “Accept all”.
5. How to manage cookies from the browser
On your first visit, you can accept or reject optional cookies and content —analytics and maps— through the notice displayed on screen. The choice is stored under the key lb_consent_v1. To change it later, clear the data stored for lorcabase.com in your browser's privacy settings and reload the page.
You can also accept, block or delete cookies through your browser settings (Google Chrome, Mozilla Firefox, Apple Safari, Microsoft Edge, Opera or others). Please refer to your browser's official help documentation for specific instructions.
You can also use extensions or private/incognito browsing modes to limit the use of cookies. Please note that, if you reject the necessary technical cookies, some site functions (form, anti-bot protection) may not work correctly.
6. Controller and contact
- Name: LORCABASE - FZCO
- Trade licence: 62952 · Dubai Integrated Economic Zones Authority (DIEZ)
- Address: DSO-IFZA, IFZA Properties, Dubai Silicon Oasis, Dubai, United Arab Emirates
- Email: accounting@lorcabase.com
- Phone: +971 55 633 8871
- Website: https://lorcabase.com
7. Modifications
LorcaBase may update this Cookie Policy to reflect changes in the tools used, applicable regulations or industry best practice. The current version will always be published on this site with its last updated date. When new types of cookies that require consent are introduced, consent will be requested before they are activated.