COOKIE POLICY
Last updated: 21 September 2026
This Cookie Policy explains what cookies and similar technologies are, how they may be used on websites operated by Rooklyn, which third parties may be involved and how users can accept, reject, configure or withdraw their preferences.
1. Controller
Controller: Geetanjali Dubey. Trading name: Rooklyn. NIF/NIE/CIF: Z0680759X. Email: geet29.dubey@gmail.com. Main website: https://rooklyn.co
This Policy applies, where appropriate, to the following domains and subdomains managed by Rooklyn:
Links to third-party websites are subject to those third parties’ privacy and cookie policies.
2. Regulatory framework and scope
The use of cookies and technologies that store or access information on a user’s device is governed, among other applicable rules, by Article 22.2 of Spanish Law 34/2002 on information society services and electronic commerce (LSSI). Where these technologies involve the processing of personal data, Regulation (EU) 2016/679 (GDPR) and the relevant Spanish data protection legislation also apply.
Cookies that are strictly necessary to transmit a communication or provide a service expressly requested by the user may be exempt from the consent requirement. Non-essential cookies will only be activated where there is a valid legal basis and, where appropriate, after the user has given valid consent.
3. What are cookies and similar technologies?
Cookies are small text files that a website can store in a user’s browser or device. Technologies with similar functions may also be used, such as local storage, pixels, technical identifiers or embedded scripts.
These technologies may enable the technical operation of the site, remember preferences, maintain security, manage sessions, measure page usage or, where appropriate and with consent, personalise content or commercial communications.
4. Types of cookies by purpose
Technical or strictly necessary cookies
These enable basic site operation, browsing, security, load balancing, fraud or bot prevention, session management, retention of cookie choices or the provision of a function expressly requested by the user. Where strictly necessary, they will not be used for incompatible additional purposes.
Preference or functional cookies
These remember user choices, such as language or certain interface preferences. Where the rules require consent for a specific preference, the corresponding technology will remain disabled until consent is obtained.
Analytics or performance cookies
These measure, in aggregate, how a site is used, detect errors, identify visited pages or improve performance. Where consent is required, they will not be installed or activated before the user accepts them.
Advertising or marketing cookies
These may measure campaigns, limit repeated advertisements, create audiences or display interest-based advertising. If used, any required prior consent will be requested.
Cookies or technologies of embedded services
Certain pages may include forms, calendars, CRM, chat, video, maps, captchas or other third-party components. Their purpose and consent requirements will depend on the component and the technologies it actually loads in the browser.
5. First-party and third-party cookies
Depending on the entity managing the technology, the sites may use:
- First-party cookies: managed from domains or components controlled by Rooklyn.
- Third-party cookies: managed by technology providers integrated into the site when the relevant function is active.
The actual presence of a particular cookie may vary according to the domain visited, the page, the loaded component, the technical configuration and the user’s choice in the consent manager.
6. Inventory of cookies and technology services
As of the date of this Policy, Rooklyn uses or may load the following services depending on the page and activated function. Non-essential technologies must remain blocked until consent has been given where required.
| Category | Provider | Purpose | Examples / technology | Indicative duration | Status / activation |
|---|---|---|---|---|---|
| Necessary | Rooklyn / consent manager | Technical operation, retention of cookie choices and, where appropriate, preferences essential to provide the requested function. | Consent cookie or storage; the technical name depends on the manager implemented. | During the session or for the period configured to retain the user’s choice. | Active only as necessary to operate the site or remember the user’s choice. |
| Necessary / security | Cloudflare, Inc. (where required by infrastructure or security functions) | Secure site delivery, traffic filtering, bot protection, security challenges and/or load balancing. | Cloudflare documents technical cookies such as __cf_bm, cf_clearance or _cflb when the corresponding functions are active. | Normally session-based or short-lived, depending on the provider’s function and configuration. | Only when the corresponding technical service or function is active. |
| Functional / CRM / bookings | HighLevel / LeadConnector (when forms, calendars, chat or embedded components are loaded) | Processing forms, requests, bookings, component sessions, preferences and other functions related to the CRM or the interaction requested by the user. | HighLevel uses session and persistent technologies; specific identifiers depend on the loaded component. | From the session to persistent periods defined by the provider; HighLevel publishes durations of up to one year for certain cookies. | Only on pages where the corresponding integration is loaded. Non-essential technologies will be subject to consent where required. |
| Preferences | Rooklyn and/or the component provider | Remembering language or other preferences selected by the user. | Preference cookie or local storage, if implemented. | Until the preference expires, is deleted or the user changes their settings. | Only when the function is implemented and in accordance with the applicable consent requirements. |
| Analytics / performance | Rooklyn and/or an analytics provider activated in the future | Measuring usage, performance and site improvement. | This Policy does not declare any specific cookie-based analytics tool as active by default. If enabled, it will be identified in the manager and in this table. | Depending on the tool activated. | Disabled until configured and, where appropriate, consent is obtained. |
| Marketing / advertising | Rooklyn and/or an advertising platform activated in the future | Campaign measurement, attribution, audiences or personalised advertising. | This Policy does not declare any specific cookie-based marketing platform as active by default. If enabled, it will be identified before use. | Depending on the platform activated. | Disabled until configured and prior consent is obtained where required. |
Important: the exact technical inventory (cookie or identifier name, provider, purpose and expiry) must match the configuration deployed on each domain. Where the consent manager displays a dynamic inventory, that panel must be kept up to date and accessible through “Cookie settings”. If a new analytics, advertising, video, chat, calendar, captcha or other third-party tool is introduced, this section must be reviewed before its activation.
7. Consent and settings
Where cookies or technologies requiring consent are used, users will have clear mechanisms, from the first layer or banner, to:
- Accept non-essential cookies.
- Reject non-essential cookies.
- Configure cookies by purpose and save their selection.
Accept and reject options must be offered at the same time and with equivalent visibility. Pre-selected boxes will not be used, and merely continuing to browse will not be treated as consent. Non-essential cookies requiring consent will remain blocked until the user makes a valid choice.
8. Withdrawing or changing consent
Users may change or withdraw their preferences at any time through the “Cookie settings” link or button permanently available in the footer or in the site’s consent management system.
Withdrawing consent does not affect the lawfulness of processing carried out before withdrawal. When a user rejects a category, technologies in that category will no longer load on subsequent visits, except those that are strictly necessary or must be retained to comply with a legal obligation.
9. Browser settings
In addition to the site’s consent manager, users can allow, block, delete or limit cookies through their browser settings. Blocking certain technical cookies may prevent some requested functions from being provided correctly.
Major browsers include specific privacy and cookie options in their settings menus (for example, Chrome, Edge, Firefox and Safari). The procedure may vary by version and device.
10. Third-party services
Rooklyn may integrate third-party services for hosting and security, CRM, forms, calendars, bookings, messaging, chat, video, maps, analytics or marketing. Where any such service installs non-essential cookies or uses non-essential tracking technologies, the corresponding consent requirements will apply.
- Cloudflare: may be involved in site delivery, security and traffic protection. Cloudflare classifies certain security cookies as strictly necessary when their corresponding functions are activated.
- HighLevel / LeadConnector: may be involved in forms, CRM, calendars, chat, bookings or other embedded components. HighLevel publishes its own Cookie Policy and privacy documentation for its services.
Including a provider in this Policy does not mean that all its cookies are used on every page. Only technologies associated with components actually integrated and activated will be loaded.
11. International transfers
Some technology providers may process data outside the European Economic Area. Where personal data are transferred internationally, Rooklyn will seek to ensure that a mechanism recognised by applicable rules is used, such as an adequacy decision, the EU–US Data Privacy Framework (where the provider is certified and the transfer is covered) or standard contractual clauses, as appropriate.
HighLevel publicly states that HighLevel and LeadConnector participate in the EU–US Data Privacy Framework. To learn about the specific mechanism applicable to a given processing activity, consult the provider’s privacy documentation and Rooklyn’s Privacy Policy.
12. Retention
Session cookies are normally deleted when the browser is closed. Persistent cookies remain for the configured period or until the user deletes them. Rooklyn will apply retention periods proportionate to the purpose and periodically review active technologies to avoid unnecessary retention.
13. Updates to this Policy
This Policy may be updated when the cookies used, technology providers, domains managed by Rooklyn or applicable legal obligations change. The date of the latest update will appear at the beginning of the document. We recommend reviewing this page periodically.
14. Contact
For enquiries relating to this Cookie Policy or the site’s privacy settings, you can contact Rooklyn at: geet29.dubey@gmail.com.
Annex: recommended text for the cookie banner
“We use necessary technical cookies to make the site work. With your consent, we may also use preference, analytics or embedded third-party cookies to improve the experience and measure site usage. You can accept, reject or configure your preferences. More information is available in our Cookie Policy.”
Recommended buttons, displayed at the same visual level:
- REJECT
- CONFIGURE
- ACCEPT