Updated 5 November 2026. Cookies are small files saved by your browser. Local storage can remain after the browser closes; session storage normally lasts for the current tab. This policy explains how Epworth Investment Management uses these technologies and third-party scripts.
Optional analytics, advertising and visitor identification stay off until you choose them. Use Accept all, Reject all, or the separate purpose controls in Cookie preferences. Closing the panel does not give consent. You can reopen Cookie preferences using the persistent control on every page, turn a purpose off, or reject all. Acceptance and refusal are remembered for 90 days.
Withdrawal stops the affected integrations and clears matching browser identifiers that this website can access. The page may reload to stop scripts already running. Withdrawal does not undo information previously sent with consent. Browser settings can also remove site data and data held on other providers’ domains. Forms, PDF links and portal links remain available without optional tracking; linked portals have their own policies.
Civic Cookie Control supplies the preferences panel and checks its licence. Its first-party CookieControl cookie records your choices for 90 days. These choices do not themselves permit analytics or profiling. The panel is supplied by Civic Computing.
Security cookies such as JSESSIONID and Zoho’s LS_CSRF_TOKEN, when present, protect sessions and requests. They are session cookies, separate from Zoho visitor identification. WordPress authentication cookies are used when an authorised user signs in, rather than for visitor advertising.
Elementor uses the elementor key in local and session storage for page functionality. Local storage has no fixed browser expiry and lasts until removed; session storage normally ends with the tab. Pagination can use epw_restore_slug and epw_restore_page session keys to restore navigation. These functions do not authorise visitor profiling.
Google Analytics measures visits and PDF downloads after analytics consent. It uses _ga and _ga_K0N65XPW9C to distinguish browsers and maintain measurement state, normally for up to two years, subject to browser restrictions and renewal on use. Google receives measurement events. This is not a claim that all information is anonymous. We do not send form-field values in our analytics events.
Sentry reports technical errors to help maintain the website. Error reporting does not require optional analytics consent and is configured without browser replay, automatic session tracking or default personal-information collection. Optional performance transactions are sampled only with analytics consent and are discarded if that consent has been withdrawn before transmission. No Sentry cookie or web-storage identifier is required by this configuration.
Google advertising measurement, audience use and personalisation require both the Google advertising choice and analytics consent. Choosing advertising alone does not start Google measurement. Google receives advertising consent only while both choices are on. Advertising identifiers can include _gcl_* and _gac_* cookies where the relevant Google advertising feature is used, generally up to 90 days; they are also covered by withdrawal cleanup. We do not rely on a statistical-purpose exception for advertising or profiling.
Apollo identifies browsers and profiles website visits for sales prospecting. Its apolloAnonId browser identifier and 66abab356a569c03f1dc88b4_eventQueue visit queue use local storage without a fixed browser expiry. Its 66abab356a569c03f1dc88b4_canTrack eligibility cache and liveIntentData recognition cache have a 24-hour application expiry, although stored entries can remain until accessed or cleared. Apollo can load LiveIntent recognition, including hashed email identifiers supplied by that provider. These purposes are off unless you select Apollo; they are not part of essential security or anonymous statistics.
LiveIntent also creates first-party recognition identifiers: _lc2_fpi requests a cookie lifetime of up to two years (browsers can shorten this), while _lc2_fpi_js and the cookie-domain check _li_dcdm_c are session cookies. _li_duid uses local storage without a fixed browser expiry. The current library can also use _li_ss cookie/local storage and lidids.* decision cookies (up to 30 days). Withdrawal clears these accessible first-party identifiers. Apollo’s service may set Cloudflare’s __cf_bm bot-protection cookie on its own domain, expiring after 30 minutes of inactivity; it does not authorise visitor profiling and the Apollo integration remains consent-gated.
Zoho SalesIQ provides chat together with visitor identification and page activity tracking. Its siq_embed data uses local storage, which can persist until removed, and session storage, which normally ends with the tab. The utsdb key also uses session storage. Legacy visitor cookies can include names ending _zldp (up to two years) and _zldt (up to one day). These visitor identifiers are separate from the session security cookie LS_CSRF_TOKEN. Zoho can also set a provider-domain zalb_* cookie; the observed zalb_34e30bb8af cookie lasts for the browser session. It is supplied with the integration and is not used as a reason to start SalesIQ without consent. Keep SalesIQ off to refuse this chat and visitor-tracking integration; site forms and portal links remain available.
Trustpilot supplies the review-collector widget and link. The configured widget fetches its display and records widget impressions without storing a visitor cookie or local/session-storage identifier in the checked configuration. Its split-test storage is not enabled. Loading a remote widget exposes ordinary connection information to its provider; that request alone does not establish a cookie-consent violation. Following the review link opens Trustpilot, where its own notices apply.
Provider information: Civic Cookie Control, Google Analytics cookies, Google cookies, Apollo privacy, Cloudflare cookies, LiveIntent privacy, Zoho cookies, Sentry privacy and Trustpilot cookies. You can refuse or withdraw the optional integrations directly through Cookie preferences without charge.
