BrickPixel
BRICKPIXEL

Cookie Policy

Cookie Policy

This Cookie Policy is a first-draft framework for the BrickPixel website. It is intended to explain, in general terms, how cookies and similar technologies may be used on this site. It is not legal advice and it should be reviewed and completed with BrickPixel’s actual technical, legal and operational details before publication.

[REVIEW: confirm the legal entity name responsible for this website and insert it consistently throughout this policy.]

1. What this policy covers

This policy should explain:

  • what cookies are;
  • which cookies or similar technologies BrickPixel uses;
  • why they are used;
  • how visitors can manage their preferences; and
  • where to find more information about personal data handling.

This page should be read alongside any related privacy documentation on the website.

[REVIEW: add link or title for BrickPixel’s Privacy Policy if one is available.]

2. What cookies are

Cookies are small text files that may be placed on a user’s device when they visit a website. They are often used to help a website function properly, remember settings, improve performance, understand how visitors use the site, or support embedded third-party services.

Some technologies work in a similar way to cookies, such as local storage, pixels, tags or scripts. If BrickPixel uses any of these, they should also be described clearly in this policy rather than assuming the term “cookies” covers everything.

[REVIEW: confirm whether BrickPixel uses only browser cookies or also local storage, pixels, tags, SDKs or similar technologies.]

3. Types of cookies that may be used

Cookies are often described by how long they remain active and by who sets them.

  • Session cookies may expire when a user closes their browser.
  • Persistent cookies may stay on a device for a set period or until deleted.
  • First-party cookies are set by the website being visited.
  • Third-party cookies are set by external services used by the website.

They are also commonly grouped by purpose, such as strictly necessary, functional, analytics or advertising cookies. The sections below provide a framework for those categories, but they should only be kept if they accurately reflect BrickPixel’s actual setup.

4. Strictly necessary cookies

Strictly necessary cookies are typically used to enable core website functions. For example, they may support page navigation, security features, load balancing, consent settings or access to secure areas of a website.

If BrickPixel uses strictly necessary cookies, this section should describe them in a specific and factual way.

[REVIEW: list each strictly necessary cookie or tool used, its purpose, whether it is first-party or third-party, and how long it remains active.]

[REVIEW: confirm whether BrickPixel relies on consent for any cookies beyond those that are strictly necessary.]

5. Functional cookies

Functional cookies are generally used to remember choices a visitor makes, such as language preferences, region, accessibility settings or other customisations that improve the user experience.

This section should only remain if BrickPixel actually uses cookies for these purposes.

[REVIEW: confirm whether BrickPixel uses functional or preference cookies. If yes, add details of each cookie, its purpose and duration.]

6. Analytics and performance cookies

Analytics or performance cookies are often used to understand how visitors interact with a website, such as which pages are visited, how long users stay, whether errors occur, and how the site can be improved.

If BrickPixel uses analytics tools, this policy should name the provider and explain the categories of information collected at a practical level, without overstating or understating what happens.

[REVIEW: confirm whether BrickPixel uses analytics services such as website traffic measurement, error monitoring or performance monitoring tools.]

[REVIEW: if analytics tools are used, add the provider names, cookie names where possible, retention periods, and whether IP anonymisation or similar settings are enabled.]

7. Advertising, marketing and social media cookies

Some websites use cookies to track browsing activity across pages or websites, measure campaign effectiveness, personalise adverts, or enable social media features. If BrickPixel does not use these technologies, this section should say so clearly rather than leaving generic wording in place.

[REVIEW: confirm whether BrickPixel uses any advertising, remarketing, conversion tracking, affiliate tracking or social media embedding tools that set cookies.]

[REVIEW: if none are used, replace this section with a short statement confirming that BrickPixel does not currently use advertising or marketing cookies.]

8. Third-party services

The website may rely on third-party services that place cookies or use similar technologies as part of embedded content or hosted functionality. Examples might include video players, maps, chat tools, booking tools, form providers or analytics platforms, but no such tools should be listed unless they are actually in use.

Where third-party services are used, this policy should identify them and explain that their cookie practices may be governed by their own policies.

[REVIEW: list any third-party services used on the website that may set cookies or collect related technical information.]

[REVIEW: add links to relevant third-party cookie or privacy information where appropriate.]

9. How users can manage cookies

Visitors should be told how they can control non-essential cookies. This may include a cookie banner, a preference centre, browser settings, or device controls. The explanation should match the website’s actual setup.

[REVIEW: describe BrickPixel’s live cookie control method, for example banner settings, preference centre link, or browser-based controls.]

Users can often also manage cookies through their browser settings. Blocking some cookies may affect how the website functions, especially where certain features rely on saved preferences or embedded services.

10. Changes to this policy

BrickPixel may need to update this Cookie Policy from time to time to reflect changes to the website, the services used, or relevant legal requirements. The published version should include a date showing when it was last updated.

[REVIEW: add “Last updated” date once this policy is completed and approved.]

11. Contact information

If visitors have questions about this Cookie Policy or about the use of cookies on the website, this section should tell them how to get in touch.

[REVIEW: add BrickPixel contact method for cookie-related queries.]

12. Cookie details table

For transparency, BrickPixel should consider adding a clear table or list setting out each cookie or similar technology in use. This should be completed from a real cookie audit rather than copied from a template.

  • Name: [REVIEW: add cookie name]
  • Provider: [REVIEW: add first-party or third-party provider]
  • Purpose: [REVIEW: describe what the cookie does]
  • Category: [REVIEW: necessary, functional, analytics, marketing or other]
  • Duration: [REVIEW: add expiry period]

[REVIEW: repeat the above entries for all cookies and similar technologies actually found on the live website.]

This draft should be checked against BrickPixel’s actual website tools, consent mechanism and legal requirements before it is treated as a finished policy.