Cookie Policy
Last updated: 17 July 2026
This Cookie Policy describes how AUDELAB LTD uses cookies and similar technologies on https://audelab.team and related interfaces, in line with PECR and UK GDPR.
1. Introduction
This Cookie Policy explains how AUDELAB LTD ("AUDELAB", "we", "us", or "our") uses cookies and similar technologies on https://audelab.team and, where applicable, on related interfaces that we operate. It should be read together with our Privacy Policy. AUDELAB LTD is located at 11 Wyke Square, Weymouth, DT4 9XP United Kingdom. Contact: +44 161 496 0871 or it.team@audelab.team.
Cookies are small text files placed on your device when you visit a website. Similar technologies include local storage, session storage, pixels, and software development kit identifiers in applications. For simplicity, this Policy refers to all such technologies as "cookies" unless a distinction is required.
Under the Privacy and Electronic Communications Regulations 2003 (PECR) and UK GDPR, we inform you about our use of cookies and, where required, obtain consent before placing non-essential cookies.
2. Who Controls Cookie Data
AUDELAB LTD determines the purposes and means of cookie processing on audelab.team and is the controller of personal data collected through first-party cookies on that site. Where a third-party cookie provider processes data, that provider may also act as an independent controller or as our processor, depending on the tool and configuration. Details of categories are set out below.
Client-operated publishing or learning platforms that we host may implement additional cookies under the client's instructions. In those environments, the client is typically the controller for end-user cookie notices and consent banners, and this Policy does not replace the client's cookie notice.
3. How Cookies Are Used
Cookies help websites function, remember preferences, understand performance, and, where consented, support measurement of marketing effectiveness. Without certain essential cookies, parts of the site or login flows may not work correctly. Non-essential cookies are optional and will not be set until you provide consent, except where a PECR exemption applies.
4. Categories of Cookies We Use
4.1 Strictly necessary cookies
These cookies are essential to provide a service you have requested or to ensure security and network management. Examples include load-balancing identifiers, session authentication cookies for secure areas, cookie consent preference storage so that we can remember your choices, and fraud-prevention tokens. Strictly necessary cookies do not require consent under PECR, but we still describe them here for transparency.
4.2 Preference and functionality cookies
These cookies remember choices you make, such as language preference, interface density, dismissed notices, or accessibility settings. They improve usability but are not strictly required for the core site to load. Where they are not exempt, we will request consent.
4.3 Analytics and performance cookies
Analytics cookies collect information about how visitors use the website, such as pages visited, time spent, approximate geographic region derived from IP address, and technical errors encountered. We use this information in aggregated or pseudonymised form to improve content, navigation, and performance. Analytics cookies are non-essential and require consent on audelab.team unless configured in a genuinely anonymous manner that falls outside PECR cookie consent requirements.
4.4 Marketing and advertising cookies
At present, audelab.team is not operated primarily as an advertising network. If we introduce marketing cookies or pixels that track users across sites for advertising, we will update this Policy and request consent before activation. Any such cookies would be clearly identified in the consent tool.
5. First-Party and Third-Party Cookies
First-party cookies are set by AUDELAB on the audelab.team domain. Third-party cookies are set by another domain, such as an analytics or content delivery provider. Third-party providers may combine data from audelab.team with data from other sites according to their own policies. You should review those policies if you consent to third-party cookies.
Where we embed video, maps, or social content, the embedded provider may set cookies when you interact with the embed. Interaction-based loading and consent gating may be used to reduce unexpected third-party cookies.
6. Cookie Table and Typical Durations
The precise cookie names may change as we update platforms. The following describes typical cookies and retention patterns used on our public website and related portals.
- Cookie consent store (first-party, necessary): remembers whether you accepted or rejected non-essential categories; typically retained for six to twelve months.
- Session identifier (first-party, necessary): maintains a secure session while you navigate authenticated areas; usually expires when the browser session ends or after a short idle timeout.
- Security and CSRF tokens (first-party, necessary): protect forms and authenticated requests; session or short persistent duration.
- Load balancer or CDN edge cookie (first-party or infrastructure, necessary): routes requests consistently; session or short duration.
- Analytics visitor identifier (first-party or third-party, analytics): distinguishes unique visits in aggregate reports; commonly two to twenty-four months if consented.
- Analytics session cookie (analytics): groups page views within a visit; typically thirty minutes of inactivity or similar.
- Preference cookie (functionality): stores interface choices; commonly three to twelve months if consented.
If a specific implementation differs, the on-site cookie banner or preference centre listing will take precedence for operational detail, while this Policy remains the narrative explanation of our practices.
7. Legal Basis for Cookie-Related Processing
Placing strictly necessary cookies and processing related data is based on our legitimate interests in operating a secure and functional website and, where relevant, on steps necessary to provide a requested service. Where cookies are non-essential, we rely on consent under PECR to store or access information on your device, and on consent under UK GDPR for associated personal data processing where consent is the appropriate Article 6 basis.
You may withdraw consent at any time through the cookie preference controls or by clearing cookies in your browser. Withdrawal does not affect the lawfulness of processing before withdrawal.
8. Managing and Controlling Cookies
8.1 Our cookie controls
When you first visit audelab.team, you may be presented with a cookie notice allowing you to accept or reject non-essential cookies, or to choose categories. You can change your mind later by revisiting the preference centre link where available or by clearing stored consent cookies and reloading the page.
8.2 Browser settings
Most browsers allow you to block or delete cookies through settings. Blocking all cookies, including necessary cookies, may cause parts of the site to malfunction, including consent memory and secure login. Browser providers publish guidance for cookie management on their support sites.
8.3 Global privacy signals
Where technically supported and legally appropriate, we may honour recognised browser-based preference signals in addition to our on-site controls. The effectiveness of such signals depends on browser implementation and applicable guidance from the Information Commissioner's Office.
8.4 Do Not Track
Some browsers offer a "Do Not Track" setting. Because there is no uniform industry standard for responding to such signals across all technologies, our primary mechanism remains the cookie preference interface described above.
9. Similar Technologies in Software and Platforms
In SaaS dashboards, CMS admin areas, and e-book platform interfaces, we may use local storage for user interface state, draft autosave, or feature flags. Authentication may use secure HTTP-only cookies or token-based sessions. Mobile or desktop wrappers, if provided, may use device storage comparable to cookies. These technologies are governed by the same privacy principles and, where they are not strictly necessary, by consent or another lawful basis explained in product documentation supplied to the client.
Clients configuring tracking within their own published content remain responsible for PECR compliance toward their end users, including obtaining consent for non-essential trackers injected through tags or scripts.
10. Data Shared via Cookies and Recipients
Cookie identifiers may be associated with IP address, user-agent string, page URLs, timestamps, and approximate location. Analytics providers may process this data to produce reports for AUDELAB. Hosting and security providers may process necessary cookies to deliver content and mitigate attacks. We do not sell cookie data. Sharing occurs under contracts and policies consistent with our Privacy Policy.
11. International Transfers Related to Cookies
Cookie and analytics data may be processed on servers located in the United Kingdom, the European Economic Area, or other countries depending on the provider. Where transfers outside the UK occur, we use appropriate safeguards as described in our Privacy Policy, including adequacy regulations or standard contractual mechanisms recognised under UK law.
12. Retention and Deletion
Cookie lifetimes are set according to purpose, as summarised in the cookie table. When a cookie expires, the browser should delete it automatically. You may delete cookies earlier through browser controls. Server-side logs associated with cookie identifiers are retained according to the retention periods in our Privacy Policy and then deleted or anonymised.
13. Children
Our public website is aimed at professionals and organisations. We do not knowingly use cookies to collect personal data from children for marketing. Client EdTech deployments that serve learners must implement age-appropriate cookie and tracking practices under the client's responsibility as controller.
14. Updates to This Cookie Policy
We may update this Cookie Policy to reflect changes in cookies, law, or operational practice. The last updated date appears at the top of the page. Material changes to non-essential cookie use will be accompanied by renewed consent where required.
15. Relationship to Other Legal Documents
This Cookie Policy supplements our Privacy Policy. Use of our services is also governed by our Terms of Service and Terms and Conditions where applicable. Links to those documents appear in the legal navigation on this page.
16. Detailed Scenarios for Digital Publishing Sites
Publishers often deploy measurement scripts to understand article engagement, scroll depth, and newsletter conversion. If AUDELAB implements such scripts on a client site under instruction, the client's cookie banner must disclose them and collect consent before firing non-essential tags. We can support technical consent mode integrations that prevent tags from loading until consent is recorded.
Paywalled content and entitlement cookies may be strictly necessary to provide a requested digital edition or e-book download. Session cookies that merely remember that a user is logged in for the service requested are typically necessary. Cross-site advertising cookies used to fund open-access content are not necessary and require consent.
Educational platforms may use cookies to keep a learner logged into a course, store progress locally for resilience, or measure feature adoption. Progress storage required to deliver the learning service may be necessary; optional product analytics should be consented or disabled by default depending on the audience and legal assessment.
17. Security Considerations for Cookies
We configure security-sensitive cookies with attributes such as Secure and HttpOnly where appropriate, and SameSite policies designed to reduce cross-site request risks while preserving legitimate functionality. Session fixation and cookie theft risks are mitigated through regeneration of session identifiers on authentication and through transport encryption.
Users should avoid shared devices for authenticated sessions or ensure they log out and clear local data after use. Public computer use increases the risk that persistent cookies remain accessible to subsequent users.
18. How to Contact Us About Cookies
If you have questions about our use of cookies, wish to withdraw consent, or need help with access rights relating to cookie-derived personal data, contact AUDELAB LTD at 11 Wyke Square, Weymouth, DT4 9XP United Kingdom, telephone +44 161 496 0871, or email it.team@audelab.team. Further privacy information is available in our Privacy Policy at privacy-policy.html.
19. Practical Guidance for Browser Vendors
Chrome, Firefox, Safari, Edge, and other browsers each provide menus for viewing and removing cookies on a per-site basis. You may also use private browsing modes, which typically delete session cookies when the window closes. Browser extensions can block trackers, but may interfere with necessary functionality. We recommend allowing necessary cookies for audelab.team if you use authenticated areas or wish your consent preferences to persist.
Enterprise-managed browsers may enforce cookie policies centrally. If you cannot set cookies due to organisational policy, certain features may be unavailable, and you should contact your internal IT administrators.
20. Accountability and Documentation
AUDELAB documents cookie inventories, consent mechanisms, and vendor assessments as part of our accountability under UK GDPR. We review cookies periodically, especially after website redesigns or the introduction of new third-party tools. Redundant cookies are removed. New non-essential cookies are not launched without a consent pathway and an update to this Policy or the preference centre listing.
If you detect a cookie that appears inconsistent with this Policy, please report it to it.team@audelab.team so that we can investigate and remediate if needed.
21. Consent Records and Evidence
Where we rely on consent for non-essential cookies, we retain records of the consent event, including the timestamp, the categories accepted or rejected, and the version of the notice presented where technically available. These records help us demonstrate compliance with PECR and UK GDPR accountability principles. Consent records are retained for as long as necessary to evidence compliance and then deleted or anonymised.
If you withdraw consent, we will stop placing new non-essential cookies of the withdrawn categories and will take reasonable steps to cease processing associated analytics identifiers. Some previously collected aggregate reports may remain in historical datasets that no longer identify you directly.
22. Tag Management and Consent Mode
We may use a tag management system to control when scripts load. Consent mode integrations can adjust the behaviour of analytics tags so that they do not set advertising or analytics cookies until permission is granted. Misconfigured tags are a common source of compliance risk; therefore we review major tag changes as part of release management for audelab.team.
Clients who ask AUDELAB to implement tag managers on publishing sites should supply a complete inventory of tags, vendors, and purposes. We may refuse to implement tags that lack a lawful PECR pathway or that present unacceptable security risk.
23. Local Storage, Session Storage, and IndexedDB
HTML5 local storage and related browser storage mechanisms can hold larger volumes of data than traditional cookies. We may use them for user interface state, caching of non-sensitive preference data, or offline resilience in administrative tools. Where such storage is used for non-essential tracking, we treat it as a similar technology requiring consent under PECR.
Clearing site data in your browser typically removes local storage as well as cookies. Doing so may reset preferences and log you out of authenticated areas.
24. Server Logs Distinguished from Cookies
Even when cookies are refused, our web servers may still process standard request logs containing IP addresses, requested URLs, user-agent strings, and timestamps. Such logging is typically necessary for security, diagnostics, and abuse prevention and is described in our Privacy Policy. Refusal of analytics cookies does not disable all server-side logging.
25. Changes Driven by Browser Privacy Features
Browser vendors increasingly restrict third-party cookies and fingerprinting. AUDELAB monitors these developments and may replace measurement approaches with privacy-preserving alternatives, such as aggregated first-party analytics. When we change technology in a material way, we update this Cookie Policy and refresh consent where required.
26. Contact and Complaints Regarding Cookies
Questions or complaints about cookies may be directed to it.team@audelab.team or by post to AUDELAB LTD, 11 Wyke Square, Weymouth, DT4 9XP United Kingdom, or by telephone on +44 161 496 0871. You may also contact the Information Commissioner's Office regarding PECR and UK GDPR concerns. We encourage you to contact us first so that we can investigate promptly.
27. Examples of Necessary Versus Optional Cookies in Practice
A cookie that stores your decision to reject analytics is itself necessary for compliance, because it records your preference. A cookie that counts page views for an analytics dashboard is optional. A cookie that keeps you logged into a client CMS while you edit articles is typically necessary to deliver the editing service you requested. A cookie that later shows you advertising for unrelated products on other websites is optional and requires consent.
Understanding these distinctions helps visitors make informed choices and helps administrators avoid classifying marketing trackers as essential. AUDELAB will not designate a cookie as strictly necessary merely because it is useful for commercial measurement.