Global cookie and tracking governance
Cookie Policy
Effective date: 21 August 2026 | Last updated: 21 August 2026 | Version 1.0
Cookie choices at a glance
This Cookie Policy explains how Percepta Growth uses cookies and related storage or access technologies on perceptagrowth.com. It is designed to give visitors meaningful control, identify the purposes for which technologies are used, and connect those choices with our wider Privacy Policy.
| Item | Details |
|---|---|
| Brand | Percepta Growth |
| Legal operator | Percepta Advisory & Strategy Ltd |
| Website | https://perceptagrowth.com |
| Consent standard | Non-essential technologies remain disabled until a valid choice is recorded where consent is required. |
| Control | Visitors can accept, reject or customise optional categories and later change that choice. |
| Contact | hello@perceptagrowth.com |
The short version: technologies needed to deliver, secure and remember choices on the website may operate automatically. Analytics, advertising, personalisation and comparable optional technologies operate only after the required consent or another lawful exception applies. Rejecting optional technologies will not prevent access to the core website.
1. Purpose and scope
This Policy applies when you visit or interact with perceptagrowth.com and any page on which it is linked. It covers cookies, pixels, tags, scripts, browser storage and comparable technologies that store information on, or access information from, a browser, device or application.
It should be read with the Percepta Growth Privacy Policy, which explains the personal data we collect, our legal bases, disclosures, international transfers, retention, security and privacy rights. If a client engagement uses tracking technology on a client-owned property, the client's notice and agreement govern unless Percepta Growth is separately identified as responsible.
2. What these technologies are
A cookie is a small text file placed on a browser or device. Some cookies last only for the browsing session; others remain for a defined period. Related technologies may include local or session storage, tracking pixels, software tags, embedded scripts, device or browser identifiers, link decoration and server-side event signals.
In this Policy, cookie or technology refers to all of these methods unless the context requires a narrower meaning. A technology may be set directly by Percepta Growth or by an approved provider whose service appears on the website.
3. Who is responsible
Percepta Growth is the brand responsible for the website. Percepta Growth is operated by Percepta Advisory & Strategy Ltd. For technologies deployed for our own website purposes, the legal operator determines the relevant purposes and controls, subject to the roles of third-party providers.
Some providers process information on our instructions. Others may act as independent or joint controllers for defined activities, such as platform advertising measurement. Their own notices may therefore apply in addition to this Policy.
4. Categories and consent model
| Category | Purpose | Default position |
|---|---|---|
| Strictly necessary | Deliver pages, route traffic, maintain security, prevent abuse, submit forms and remember privacy choices. | Always active where genuinely necessary; no advertising or behavioural profiling. |
| Preferences and functionality | Remember optional settings or enable a feature requested by the visitor, including a scheduling or embedded service. | Off until selected where consent is required; a feature-led choice may apply when lawful and sufficiently clear. |
| Analytics and performance | Understand aggregate use, diagnose faults, measure content performance and improve the website. | Off until consent where required. Any applicable narrow statistical exception must be documented before use. |
| Advertising and measurement | Measure campaigns, attribute conversions, limit repetition, build audiences or support targeted advertising. | Off until consent. Never treated as strictly necessary. |
No consent by silence. Continuing to browse, closing a banner or using a pre-ticked setting is not treated as consent where a positive action is required. Optional categories are off by default, and rejecting them is as straightforward as accepting them.
5. Approved technology register
The register below describes services that may be approved for the website. Listing a service does not mean it is currently active. The live preference centre identifies the technologies actually enabled, their provider, purpose, category and current duration.
| Service or function | Approved use | Category and activation |
|---|---|---|
| Website hosting and delivery | Routing, availability, load management and delivery of requested pages. | Strictly necessary where required for operation. |
| Security and abuse prevention | Rate limiting, bot detection, form integrity, fraud prevention and protection of the service. | Strictly necessary only to the extent proportionate and security-related. |
| Consent preference storage | Remember whether optional categories were accepted, rejected or customised. | Strictly necessary for the consent mechanism; retained only for a reasonable refresh period. |
| Cloud application platform | Host approved website functions, receive qualification-form submissions or support secure service operations. | Necessary for requested functions; optional browser storage must be separately classified. |
| Scheduling service | Show availability and permit a visitor to request a meeting. | Preferences and functionality; loaded only after the required choice or opened as a separate third-party page. |
| Website analytics | Measure visits, navigation, campaigns, errors and aggregate content performance. | Analytics; off until consent where required. |
| Google Ads conversion technology | Measure advertising outcomes, attribution and campaign effectiveness. | Advertising and measurement; off until consent. |
| Meta Pixel or Conversions API | Measure Meta campaigns, conversions and approved audience activity. | Advertising and measurement; off until consent and configured to respect applicable choices. |
| LinkedIn Insight Tag | Measure LinkedIn campaigns, conversions and approved professional audience activity. | Advertising and measurement; off until consent. |
6. Information generated
Depending on the technologies enabled and the choices made, information may include:
- IP address, approximate location derived from it, device and browser characteristics, operating system and language;
- pages viewed, links selected, referring and exit pages, timestamps, session activity and interaction events;
- campaign, source and medium parameters, ad interactions, conversion events and attribution data;
- consent category, preference state, time of choice and technical evidence needed to demonstrate that choice;
- security signals, request logs, error data, bot indicators and rate-limiting information; and
- identifiers assigned by us or an approved provider, subject to the provider, configuration and applicable law.
We do not intentionally use website cookies to collect passwords, payment card numbers, precise geolocation, government identifiers, health information or other highly sensitive information. Qualification forms and business communications are governed by the Privacy Policy and should not be used to send unnecessary sensitive data.
7. Purposes and legal bases
Strictly necessary technologies support a service requested by the visitor, communications transmission, security, form integrity and the operation of privacy controls. Where personal data is involved, the corresponding processing may rely on performance of a requested service, legitimate interests, legal obligations or another available basis.
Optional analytics, preferences and advertising technologies rely on consent where required by applicable storage-and-access or privacy rules. In jurisdictions that permit another basis, Percepta Growth may still apply consent as a global baseline. A later use that is materially incompatible with the original purpose requires a new assessment and, where applicable, fresh consent.
8. Consent design standard
Where consent is required, the website should:
- provide clear, layered information before optional technologies activate;
- identify purposes and material third parties with sufficient specificity;
- present Accept, Reject and Customise choices without manipulative design;
- use separate controls for preferences, analytics and advertising where appropriate;
- record the choice and a relevant policy or configuration version;
- allow easy withdrawal and stop future optional activity; and
- request a refreshed choice when purposes or providers materially change.
9. How to manage your choices
9.1 Cookie preference centre. Use the Cookie Settings link displayed in the website footer or consent interface to accept, reject or customise optional categories. Changes apply to future use on that browser or device. A choice made on one browser or device may not automatically carry to another.
9.2 Browser and device controls. Most browsers allow you to delete, block or restrict cookies and site data. Blocking all storage may affect security, form submission, saved preferences or embedded functionality. Browser controls are additional to, and do not replace, the website preference centre where a consent choice is required.
9.3 Advertising and platform controls. Advertising platforms may provide their own controls for ad personalisation, account activity or audience use. Using those controls may reduce activity on that platform but may not communicate your choice to every other provider or to the Percepta Growth website.
9.4 Global Privacy Control and similar signals. Where legally required and technically supported, recognised opt-out preference signals may be treated as a request to opt out of sale, sharing or targeted advertising for the browser sending the signal. Because signals and legal effects differ, use Cookie Settings or contact us if you need confirmation.
9.5 Do Not Track. There is no universally accepted response standard for the legacy Do Not Track signal. We do not promise a particular response to it unless required by law. This does not affect controls available through Cookie Settings or a recognised legally binding preference signal.
10. What happens if you reject optional technologies
You should still be able to access the core website, review services and submit an enquiry. Certain optional features, embedded media or scheduling interfaces may not load. Where practical, we will provide a direct link or another way to access the feature without requiring unrelated tracking.
11. Third parties
Approved providers may receive device, usage, consent or campaign information when their technology is enabled. We select providers for a defined purpose, configure available privacy controls, limit data where practicable and use appropriate contractual safeguards. Third parties may nevertheless determine some processing purposes independently under their own policies.
We do not authorise a provider to activate an optional technology merely because its software is present in source code. Tags, pixels and embedded services are technically blocked until the applicable category is enabled.
12. International processing
Some providers operate globally, so cookie-related information may be processed outside the country where it was collected. Where personal data is transferred across borders, we use safeguards described in the Privacy Policy, which may include adequacy decisions, standard contractual clauses, contractual addenda and supplementary security measures.
13. Retention
Session technologies expire when the relevant session ends. Persistent technologies remain only for the period stated in the live register or until deleted. Duration is selected according to purpose, sensitivity, user expectations, provider configuration and legal requirements.
Consent and rejection records may be retained long enough to honour and demonstrate the choice, manage refresh cycles and resolve complaints. Event data received from a provider may have a different retention period under the Privacy Policy or the provider's controls.
14. Security and governance
We apply risk-based controls to cookie deployment, including role-based tag access, change approval, provider review, environment separation where feasible, consent-mode testing, periodic scans and removal of obsolete technology. No browser or network technology is completely secure, but we seek to minimise unnecessary identifiers and access.
15. Children
The website is directed to organisations and business professionals and is not intended for children under 16. We do not knowingly use optional advertising technology to profile children through the website. If a child is likely to access a new service, we will reassess notices, consent and design controls before deployment.
16. Changes to this Policy
We may update this Policy when technologies, providers, purposes, services or legal requirements change. The effective and last-updated dates will be revised. Material changes to optional purposes or third parties may require a new consent choice before the affected technology is enabled.
17. Contact
Questions, complaints and requests concerning cookies or tracking choices may be sent to our privacy and cookie contact, using the subject line: Cookie or Tracking Request.
Percepta Growth, operated by Percepta Advisory & Strategy Ltd
hello@perceptagrowth.com
https://perceptagrowth.com
Appendix A — Deployment and audit standard
This control schedule is intended for the website owner and development team. It is not a substitute for testing the live deployment.
| Control | Required operating standard |
|---|---|
| Pre-launch inventory | Scan production pages and record each cookie, pixel, tag, storage key, provider, host, purpose, category and duration. |
| Default state | Block every non-essential technology before a valid choice. Confirm behaviour on first visit, rejection and withdrawal. |
| Banner equality | Make Accept and Reject comparably visible. Do not use pre-ticked toggles, consent by scrolling or misleading colour hierarchy. |
| Granularity | Separate preferences, analytics and advertising where their purposes differ. Keep necessary technologies non-toggleable and narrowly defined. |
| Provider disclosure | Identify material third parties before consent and link to current provider information in the live preference centre. |
| Evidence | Record the choice, time, region or rule set where relevant, consent text or version, and category state without collecting excessive data. |
| Withdrawal | Provide a persistent Cookie Settings link and verify that withdrawing is no harder than accepting. |
| Change control | Re-scan after releases, tag-manager changes, new embeds or campaign tracking. Obtain fresh consent for materially new purposes. |
| Review cycle | Review the inventory at least quarterly during active campaigns and whenever a provider or website architecture changes. |
| Incident handling | Disable unexplained or misclassified technology, preserve evidence, assess affected users and follow the Privacy Policy incident process. |