Version: 2026-09-25
Last updated: 25 September 2026

This Policy explains how cookies, local storage and other similar technologies are used on the website realestatescostablanca.com (the Web) and in the REC application (the App).

The Web and the App operate under the REC brand, but use different technologies and have independent preference mechanisms.

A choice made on the Web is not automatically considered valid for the App, and a choice made in the App is not automatically transferred to the Web.

1. Responsible party

The responsible party is:

Pascale Annie Degryse Meuleman
NIF: 48338942A

Avenida L'Albir, 66-68
03581 El Albir / L'Alfàs del Pi
Alicante
España

Email:

support@realestatescostablanca.com

For the purposes of this Policy, REC identifies the brand and the services provided by the responsible party identified above.

2. Scope

This Policy applies to the use of cookies and similar technologies on or in:

• realestatescostablanca.com;
• the REC App;
• associated services and features where they use storage or information from the browser or device.

The Web is primarily an informational environment managed through InmoWeb infrastructure.

The App is the environment in which REC’s main interactive and transactional features operate, including accounts, property listings, REC Tools, credits and paid services.

The technologies used in the two channels are therefore not necessarily the same.

3. What we mean by cookies and similar technologies

A cookie is a small file or identifier that a website may store or read in the user’s browser.

In addition to traditional cookies, a website or an app may use technologies with similar functions, including:

• localStorage;
• IndexedDB;
• technical identifiers;
• tokens;
• SDK-managed storage;
• storage necessary to remember preferences;
• security and session mechanisms.

In this Policy, references collectively to cookies and similar technologies include these mechanisms where applicable.

4. What they may be used for

Depending on the channel and feature, these technologies may be used to:

• enable the technical operation of the service;
• maintain a signed-in session;
• protect the security of the Web or the App;
• prevent fraud, abuse or unauthorised access;
• remember a choice requested by the user;
• temporarily maintain the state of a process;
• remember preferences;
• manage payments or the return from a payment provider;
• enable continuity of a task already started;
• manage notifications;
• personalise the experience where the user authorises it;
• carry out analysis or measurement where the necessary basis exists;
• carry out marketing or advertising personalisation activities where applicable and where consent exists.

Not all these purposes are necessarily active in all channels.

WEB

5. Cookies and technologies on the Web

The Web realestatescostablanca.com uses infrastructure provided by InmoWeb and technical resources necessary to display and operate the site.

The Web has a cookie management system that currently distinguishes between the following categories:

• Strictly necessary;
• Functional;
• Analytics;
• Marketing.

The optional categories must not be understood as a statement that REC continuously uses every possible type of tool within them.

Their actual use will depend on the services genuinely active on the Web.

6. Strictly necessary cookies on the Web

These are cookies necessary for technical operation, security, navigation or provision of a feature expressly requested.

These technologies may be used without consent where the legal requirements for considering them strictly necessary are met.

Depending on the technical configuration used, they may include:

• basic operation of the site;
• security;
• maintenance of technical settings;
• management of the consent mechanism itself;
• functions necessary to deliver requested pages or resources.

These technologies must not be reused for profiling or behavioural advertising without the corresponding legal basis.

7. Functional or preference cookies on the Web

These technologies may remember choices that facilitate or adapt use of the Web.

Where a preference has been expressly chosen by the user and the technology is used exclusively to provide that preference, it may have the legal status applicable to an expressly requested service.

If the same information is reused for additional personalisation, behavioural analysis or advertising, the rules applicable to those purposes will apply.

8. Analytics cookies

Analytics or measurement technologies allow the use of the Web to be studied and information about its operation or use to be obtained.

REC does not assign a specific cookie to this category in this Policy unless its use has been verified.

Where analytics technologies requiring consent are used, they must not be activated until the user has made the corresponding choice.

9. Marketing or advertising personalisation cookies

These technologies may be used to understand user behaviour for commercial, advertising or personalisation purposes.

Where the Web uses technologies of this kind, their activation will be subject to the corresponding consent where legally necessary.

The existence of the Marketing category in the settings panel does not, by itself, mean that REC currently has a specific behavioural advertising system active.

10. Consent on the Web

When the user accesses the Web, the cookie system may offer options to:

• accept optional technologies;
• reject them;
• configure the available categories.

The option to reject must not be hidden or materially more difficult than accepting.

Continuing to browse the Web does not, by itself, constitute acceptance of optional cookies.

Strictly necessary technologies may remain active where they are necessary to provide the requested service or for purposes legally exempt from consent.

11. Configuring and withdrawing consent on the Web

Cookie preferences on the Web are managed through the system provided by InmoWeb.

The user may accept, reject or configure optional categories when the consent panel is displayed.

REC is verifying with InmoWeb the specific technical mechanism used to retain the choice, its duration and the supported method for subsequently reopening the preferences panel.

When InmoWeb provides or changes that mechanism, REC will update this Policy where necessary.

The user may also manage or delete data stored by a website using the functions available in their browser. This action may also affect lawfully stored preferences or sessions.

12. Web cookie inventory

REC does not consider it appropriate to publish as current a list of cookies whose existence has not been verified.

Historical names appearing in previous policies are therefore not reproduced as a current inventory without current technical confirmation.

The inventory must reflect only technologies actually used and, where possible, identify:

• name or identifier;
• provider;
• purpose;
• category;
• duration;
• whether they are first-party or third-party.

When InmoWeb provides the outstanding technical information about its consent and storage mechanism, this section may be completed more precisely without changing the rest of the Policy.

REC APP

13. Technologies used by the App

The App uses browser or device storage for different technical and functional purposes.

Technologies used may include:

• local storage;
• IndexedDB;
• authentication persistence managed by Firebase;
• technical state of REC Tools;
• security tokens and states;
• preferences;
• information necessary for payments and returns from Stripe;
• notification states;
• personalisation information where the user authorises it.

The App does not rely on consent given through the Web banner.

14. Necessary storage in the App

The App uses certain technical mechanisms without which some requested features could not be provided correctly.

These may include information necessary for:

Authentication and session

Maintaining the session and enabling secure access to the account.

Security

Preventing fraud, abuse, improper automation, repetitive requests or unauthorised access.

This may include technologies relating to Firebase, App Check or reCAPTCHA Enterprise.

Payments

Maintaining the state necessary to initiate, verify or correctly recover a payment operation or the return from Stripe.

REC Tools

Maintaining job identifiers, pending requests, retries, idempotency and technical continuity of processes initiated by the user.

Account deletion

Allowing a deletion process that has been initiated to be completed or safely retried.

These technologies do not require acceptance of Personalisation when used solely for the technical functions indicated.

15. Favourites, drafts and requested preferences

The App may save information when the user requests a feature such as:

• retaining favourites;
• recovering a draft;
• remembering certain work states;
• maintaining a chosen preference.

Where such storage is used exclusively to provide the requested feature, it will not, solely for that reason, be used to create personal profiles.

If REC wished to reuse that information for Personalisation, such use would be conditional on the Personalisation preference described in this Policy.

16. Optional Personalisation in the App

The App has an optional category called Personalisation.

If the user accepts it, REC may use information about activity in the App to adapt certain recommendations or suggestions.

This may include information such as:

• properties viewed;
• property types;
• areas or cities of interest;
• price ranges;
• interaction patterns;
• signals used to classify the level of interest;
• certain interactions with REC suggestions or features.

Technical records used by the current implementation may include:

• rec_user_behavior;
• rec_lead_quality;
• certain interaction indicators relating to Personalisation.

This processing remains disabled until the user has expressly accepted Personalisation.

17. Initial choice in the App

When a person accesses the App directly and the relevant scope does not have a valid saved choice, REC presents a simple Privacy and preferences screen.

The user may choose between:

• Accept personalisation;
• Continue without personalisation.

Neither option is selected in advance.

Continuing without Personalisation does not prevent use of the App’s essential features.

Using the App without selecting Personalisation is not interpreted as consent.

18. Changing or withdrawing Personalisation in the App

The choice may subsequently be changed from:

Privacy and preferences

When the user disables Personalisation:

• new writes intended for Personalisation stop;
• Personalisation records safely attributable to the relevant scope are deleted;
• technical storage necessary to provide requested functions remains.

Withdrawal of Personalisation does not affect:

• authentication;
• security;
• payments;
• REC Tools;
• necessary technical functions;
• other valid legal bases distinct from consent.

19. Anonymous and authenticated users

The App may distinguish between an anonymous scope and an authenticated account.

A choice made in an anonymous scope is not automatically considered the choice of an identified account.

If an authenticated account does not have its own preference, REC may request its choice even where there is a previous decision relating to an anonymous scope.

Changing the App’s language does not change the saved decision.

20. Notifications

Notification permissions are managed separately from Personalisation.

Authorising Personalisation does not constitute authorisation to receive notifications.

Where the App needs device or browser permission to send notifications, that permission is requested separately.

21. External services relating to the App

The App may use external technology services, including:

• Firebase Authentication;
• Firebase Cloud Messaging;
• App Check;
• reCAPTCHA Enterprise;
• Stripe;
• Google Fonts;
• OpenStreetMap;
• Nominatim.

Use of an external service does not necessarily mean that the provider installs cookies in the browser.

Where an external technology uses device storage, its processing will depend on its specific purpose and the corresponding legal basis.

Calls to Gemini or OpenAI used for certain REC Tools features are made from the backend in the audited flows and are therefore not described as browser cookies.

Full information about providers and international transfers is set out in the Privacy Policy.

22. Analytics and advertising in the App

The currently audited version of the App has not demonstrated active integrations of:

• Google Analytics 4;
• Google Tag Manager;
• Meta Pixel;
• Hotjar;
• Microsoft Clarity;
• Mixpanel;
• PostHog;
• Firebase Analytics.

REC therefore does not currently present fictitious optional Analytics or Advertising categories within the App’s preferences panel.

If technologies of this kind are introduced in the future, the consent mechanisms and this Policy will be updated before they are used where legally necessary.

23. Storage duration

Duration depends on the specific purpose.

Some states are maintained only during a session or process.

Others may be maintained for as long as necessary to:

• keep an account signed in;
• recover a draft;
• maintain a preference;
• complete a payment process;
• recover a technical job;
• retain a privacy choice.

Certain drafts have expiry periods managed by the application itself.

Personalisation data remain subject to the user’s choice and are deleted for the relevant scope when the user withdraws Personalisation through the implemented mechanism.

Temporary REC Tools files are governed separately by their retention criteria and must not be confused with cookies or preference storage.

24. External providers and third parties

Some technologies may depend on external providers.

Where those providers process personal data, the conditions described in the Privacy Policy will also apply.

REC endeavours to limit the use of third parties and does not attribute a cookie to a provider merely because the provider loads an external resource.

The list of technologies used will be updated when the service’s actual architecture changes.

25. International transfers

Certain technology providers may process information outside the European Economic Area.

Details concerning:

• providers;
• known locations;
• transfer mechanisms;
• applicable safeguards,

are explained in the Privacy Policy.

This Cookies Policy does not replace that information.

26. How to manage technologies through the browser

Major browsers allow users to:

• view data stored by a site;
• block cookies;
• delete cookies;
• delete local storage;
• clear site data;
• configure permissions.

Indiscriminate deletion of data may result in:

• a session being signed out;
• preferences disappearing;
• drafts being lost;
• certain settings needing to be configured again.

Where a specific preference mechanism exists within REC, it is therefore preferable to use it to change only the relevant choice.

27. Relationship with Privacy and Terms

This Policy specifically explains the use of cookies and similar technologies.

The Privacy Policy explains more broadly how REC processes personal data.

The Terms and Conditions govern the use and purchase of REC services.

Acceptance of the Terms does not constitute acceptance of optional technologies.

Reading the Privacy Policy also does not constitute consent to Personalisation.

Choices must remain separate where they have different legal bases.

28. Changes to this Policy

REC may update this Policy when there are changes to:

• the technologies used;
• the InmoWeb configuration;
• the App;
• providers;
• purposes;
• legislation;
• authorities’ guidance.

The applicable version will be identified by a date or version number.

Where a change requires new consent, REC will request the corresponding choice again where legally necessary.

29. Contact

For any matter relating to cookies, device storage, Personalisation or privacy, you may contact REC at support@realestatescostablanca.com.

The responsible party is identified in section 1. Responsible party of this Policy.

Version of this Cookies and Similar Technologies Policy: 2026-09-25