Legal
Cookie Notice
Information about the cookies and similar technologies used on this website, their purposes and how to manage preferences.
Last updated: 22 July 2026
About this notice
This Cookie Notice explains how ASP Partners Limited (“ASP”, “we”, “us” or “our”) uses cookies and similar technologies on asp-partners.com. It should be read together with ASP’s Privacy Notice.
Cookies and similar technologies may process information that identifies or can be linked to a device or individual. Where that information is personal data, ASP handles it in accordance with applicable data-protection law.
What cookies are
A cookie is a small text file placed on a computer, mobile telephone or other device when a website is visited. Cookies can help a website operate, remember choices, protect against misuse and understand how visitors use the site. Similar technologies include pixels, tags, local storage, software development kits and other device-storage or identification mechanisms.
Cookies may be set by ASP’s website (“first-party cookies”) or by an external service whose functionality is used on the website (“third-party cookies”). They may last only for the browsing session or remain for a stated period after the browser is closed.
Categories of cookies and similar technologies
| Category | Purpose | Consent position |
|---|---|---|
| Strictly necessary | Required for core operation, security, form delivery and storage of cookie choices. | Always active; required for requested website functions. |
| Functional or preference | Remember optional settings or enable enhanced features. | Off by default; enabled only after consent unless strictly necessary for a feature requested by the user. |
| Analytics or performance | Measure visits, interactions and errors to improve website performance and content. | Off by default; enabled only after consent. |
| Marketing or advertising | Track activity, build profiles or measure advertising campaigns. | Not planned at launch; blocked unless approved by ASP and consented to by the visitor. |
Cookies and technologies currently used
The website’s cookie-preference centre must display a current list of the cookies and similar technologies detected on the live site. For each item, it should identify the category, provider, cookie or technology name, purpose and duration. The developer must populate or dynamically generate the following table from the production environment before launch:
| Category | Provider / cookie or technology name | Purpose | Duration |
|---|---|---|---|
| Strictly necessary | [insert exact live names] | [insert exact operational or security purpose] | [session or exact duration] |
| Functional / preference | [insert only if used] | [insert exact purpose] | [exact duration] |
| Analytics / performance | [insert only if enabled after consent] | [insert exact measurement purpose] | [exact duration] |
| Marketing / advertising | None intended at launch | Not applicable | Not applicable |
| Embedded third-party content | [insert only if maps, video, booking or similar tools are used] | [insert exact purpose] | [provider duration] |
Do not publish the bracketed rows. They are implementation fields. Delete unused categories and replace every remaining bracketed field with the result of the live cookie and script audit. The cookie-preference centre should remain the authoritative current inventory if the platform supports automatic scanning and updating.
Consent and managing preferences
When you first visit the website, you should be given a clear choice to:
- accept all cookies;
- reject non-essential cookies; or
- manage individual categories.
Strictly necessary cookies will remain active. All other categories must remain disabled until you make an affirmative choice.
Consent choices must not use pre-selected boxes or assume consent from continued browsing.
The “Accept all” and “Reject non-essential” choices should be equally easy to find and use.
The website must record the categories consented to, the date and the version of the notice or settings presented.
Withdrawing or changing consent must be as easy as giving it. A persistent “Cookie settings” link should appear in the footer on every page.
Where the categories, purposes or providers change materially, the website should request a fresh choice before the new non-essential technology is activated.
You can change your choice at any time by selecting “Cookie settings” in the website footer. Withdrawal of consent does not affect processing that occurred before withdrawal.
Browser and device controls
Most browsers allow you to view, block or delete cookies through their settings. Blocking all cookies may affect core website functions and may require you to reset preferences on each visit. Browser controls are separate from ASP’s cookie-preference centre, and their location and operation depend on the browser or device provider.
Third-party services and embedded content
If the website uses third-party analytics, maps, videos, appointment-booking tools, social-media content or other embedded functionality, those providers may set or access cookies or similar technologies. Such functionality must be blocked until the appropriate consent is obtained, unless it is strictly necessary for a service specifically requested by the visitor. Third-party providers process data under their own terms and privacy notices, which visitors should review.
Information collected through cookies
Depending on the technology used and the visitor’s choices, cookies may collect or generate:
- internet protocol address;
- device and browser information;
- operating system;
- approximate location derived from the network;
- referring page;
- pages viewed;
- clicks;
- visit date and time;
- session duration;
- error information;
- consent choices; and
- unique identifiers.
ASP uses this information only for the stated purposes and in accordance with the Privacy Notice.
How long cookies remain
Session cookies expire when the browser is closed. Persistent cookies remain until their stated expiry date, until they are deleted through browser settings, or until consent is withdrawn and the relevant technology is disabled. The exact duration of each live cookie must be shown in the cookie-preference centre or the table above.
Changes to this Cookie Notice
ASP may update this Cookie Notice when the website, providers, cookie categories, purposes, applicable law or guidance change. The updated version will be published on this page with a revised date. Where a material change affects consent, non-essential technologies should remain blocked until a fresh choice is obtained.
Contact
Questions about cookies or ASP’s use of personal data may be sent to [email protected]. Further information about personal-data rights and complaints is available in ASP’s Privacy Notice.
Developer consent configuration requirements
The following requirements apply to the implementation of this notice:
- Default state: strictly necessary only. Analytics, functional third-party and marketing categories must be denied until consent.
- Prevent tags from firing through page code, tag managers, embedded iframes or plug-ins before consent. Merely hiding a banner is not sufficient.
- Use a consent-management platform that can store and retrieve consent records, allow granular category choices and provide a permanent footer link to reopen settings.
- Ensure forms required to contact ASP work without consenting to analytics or marketing cookies.
- Do not bundle newsletter consent with acceptance of the Privacy Notice or with submission of the general contact form.
- Re-run a cookie and script scan after each material website update and reconcile the live results to this notice and the preference centre.
