Cookies and similar storage technologies help modern websites deliver faster journeys, more relevant experiences, and measurable growth. On this page, cookies are used to personalise content and ads, enable social media features, and support traffic analysis. Information about site usage may also be shared with social, advertising, and analytics partners, who can combine it with information you have provided to them or they have collected through your use of their services.
This guide explains the cookie categories in use, what they enable, and how consent is stored and applied across domains. It also highlights site-specific storage entries such as emailFinderAttempts and emailVerifierAttempts, which signal helpful on-site capabilities related to CRM data enrichment and email verification.
Why websites use cookies (and what you get out of it)
When cookies and related technologies are implemented responsibly, they create tangible benefits for both visitors and teams operating the site:
- Smoother experiences: essential functions like navigation and secure access work reliably.
- More relevant content: preferences and embedded components can remember settings and reduce friction.
- Performance measurement: marketing and embedded-media technologies make it possible to understand what is working, then improve it.
- More targeted outreach: marketing cookies help show ads that are more relevant to users, improving efficiency for campaigns.
- On-site productivity signals: persistent entries such as emailFinderAttempts and emailVerifierAttempts indicate active enrichment and verification workflows that support cleaner CRM data.
These benefits rely on clear consent choices and transparent categorisation, which is where a cookie banner and a cookie declaration come in.
Cookie categories used on this site
Cookies are grouped into clear categories so you can understand what each group does and decide what to allow. The categories referenced are:
- Necessary
- Preferences
- Statistics
- Marketing
- Unclassified
In addition to traditional cookies, the declaration includes other storage mechanisms (for example HTML Local Storage and IndexedDB) that can store data such as session state, embedded content settings, or feature-related counters.
At-a-glance: categories, providers, and common technologies
The table below summarises the categories, example providers, and the typical storage technology types referenced in the declaration.
| Category | Purpose | Examples of providers and entries | Common technology types |
|---|---|---|---|
| Necessary | Make the site usable, including core functions like navigation and secure access. | Cookiebot (CookieConsent), LinkedIn (bcookie, li_gc), (FORM_SESSION_#, RESPONDENT) | HTTP Cookie, HTML Local Storage |
| Preferences | Remember information that changes how the site behaves or looks. | LinkedIn (lidc) | HTTP Cookie |
| Statistics | Understand how visitors interact with the site via anonymous reporting. | None listed for this category (as declared). | N/A |
| Marketing | Track visitors across websites to show relevant ads and measure performance. | Meta (_fbp, lastExternalReferrer, lastExternalReferrerTime), YouTube embedded content identifiers and preferences | HTTP Cookie, HTML Local Storage, IndexedDB |
| Unclassified | Items being classified together with the provider of individual cookies. | (EXP_POWERED_BY_2601), (sj_v_id), site entries (emailFinderAttempts, emailVerifierAttempts, lastReset, lastResetVerifyEmail) | HTML Local Storage |
Necessary cookies: the foundation for a reliable experience
Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. Without them, core functionality may not work as intended.
Cookiebot: consent state storage
Consent tooling typically needs a reliable way to remember your choices. Here, Cookiebot is referenced with a cookie named CookieConsent, which stores the user’s cookie consent state for the current domain. The declaration indicates a maximum storage duration of 1 year for this entry (HTTP Cookie).
LinkedIn: security and consent-related entries
- bcookie: used to detect spam and improve the website’s security (HTTP Cookie, up to 1 year).
- li_gc: stores the user’s cookie consent state for the current domain (HTTP Cookie, up to 180 days).
embedded form session support
Forms need session continuity to work smoothly, especially when embedded. The declaration lists entries tied to :
- FORM_SESSION_#: used to implement forms on the website (Persistent, HTML Local Storage).
- RESPONDENT: used to implement forms on the website (Persistent, HTML Local Storage).
In practice, this helps ensure form experiences remain consistent and functional throughout your visit.
Preferences cookies: optimising delivery and user experience
Preferences cookies support convenience by remembering information that changes how the website behaves or looks.
The declaration includes LinkedInlidc, which registers which server-cluster is serving the visitor. This supports load balancing and helps optimise user experience (HTTP Cookie, up to 1 day).
Statistics cookies: what the declaration says
Statistics cookies are used to understand how visitors interact with websites by collecting and reporting information anonymously. In the declaration provided, the site states: “We do not use cookies of this type.”
That means, as declared here, no cookies are currently listed under the Statistics category.
Marketing cookies: performance measurement and targeted outreach
Marketing cookies are used to track visitors across websites. The intent is to display ads that are relevant and engaging, while also enabling campaign measurement. This is especially valuable for growth teams because it allows a feedback loop: measure what drives qualified traffic and iterate with confidence.
Meta (Facebook): attribution signals and ad delivery
The declaration references Meta Platforms, Inc. entries, including:
- lastExternalReferrer: detects how the user reached the website by registering their last URL-address (Persistent, HTML Local Storage).
- lastExternalReferrerTime: stores the time associated with how the user reached the website (Persistent, HTML Local Storage).
- _fbp: used by Facebook to deliver a series of advertisement products, such as real-time bidding from third-party advertisers (HTTP Cookie, up to 3 months).
These entries support understanding where visitors came from and help power more effective ad delivery and measurement.
YouTube: embedded content interaction and player preferences
Embedded video is a high-impact way to explain products and workflows quickly. YouTube-related entries in the declaration help support embedded playback, remember settings, and track interaction with embedded content.
Examples referenced include:
- __Secure-ROLLOUT_TOKEN, __Secure-YNID: interaction tracking with embedded content (HTTP Cookie, up to 180 days).
- __Secure-YEC, YSC, LAST_RESULT_ENTRY_KEY: session-related interaction or playback behaviour (Session, HTTP Cookie).
- VISITOR_INFO1_LIVE: estimates bandwidth on pages with integrated videos (HTTP Cookie, up to 180 days).
- remote_sid: necessary for implementation and functionality of YouTube video content (Session, HTTP Cookie).
The declaration also references storage beyond standard cookies, including IndexedDB entries such as LogsDatabaseV2:V#||LogsRequestsStore, ServiceWorkerLogsDatabase#SWHealthLog, and YtIdbMeta#databases (Persistent, IndexedDB). In addition, multiple yt-remote-* items in HTML Local Storage store video player preferences and device-related settings across sessions (some Session-based, some Persistent).
Net effect: embedded YouTube content can load and behave consistently, while providing interaction signals that support content optimisation and marketing performance measurement.
Unclassified items: what “pending classification” means
Unclassified cookies and storage entries are those the site is in the process of categorising, together with the providers of individual cookies. This category commonly includes newer features, recently added tools, or entries awaiting final documentation.
Examples of unclassified providers and entries
- : EXP_POWERED_BY_2601 (Persistent, HTML Local Storage).
- : sj_v_id (Persistent, HTML Local Storage).
Site-specific persistent entries tied to enrichment and verification workflows
Alongside third-party items, the declaration lists site entries stored in HTML Local Storage with a Persistent duration:
- emailFinderAttempts
- emailVerifierAttempts
- lastReset
- lastResetVerifyEmail
These names strongly suggest on-site functionality for email finding and email verification. In a CRM enrichment context, that is a practical advantage: enrichment and verification workflows support data cleaning and higher-quality contact records, which can improve deliverability, reduce bounce risk, and help sales and marketing teams focus outreach on more reliable data.
How consent is stored: domain-level and cross-domain consent
A consent banner is only useful if your choices persist. The declaration indicates that consent state is stored (for example via a consent cookie such as CookieConsent for the current domain), and it also references cross-domain consent functionality.
Cross-domain consent means your selections can apply across a defined list of domains. The declaration includes a section indicating: “List of domains your consent applies to”, reflecting that the consent framework can store and apply choices beyond a single domain where configured.
This approach can deliver a smoother experience because it reduces repeated prompts and keeps your preferences consistent across related properties.
Personalisation and ads: what “sharing with partners” enables
The cookie notice explains that information about your use of the site may be shared with social media, advertising, and analytics partners. Those partners may combine it with other information you have provided to them or they have collected from your use of their services.
From a benefits perspective, this setup can:
- Improve relevance: ads and messages can better match user interests.
- Boost efficiency: teams can reduce wasted spend by learning which channels drive engaged visitors.
- Support smarter content strategy: embedded media interaction signals help refine what users find useful.
Technologies referenced: cookies, Local Storage, and IndexedDB
The declaration references multiple storage types, each suited to different needs:
- HTTP Cookies: classic browser cookies that can be session-based or have defined lifetimes (for example 1 day, 180 days, 1 year).
- HTML Local Storage: key-value storage in the browser, often used for persistent settings or feature state (for example form session support, referrer timestamps, counters like emailFinderAttempts).
- IndexedDB: a browser database used for structured storage, often by complex embedded applications (for example certain YouTube logs and metadata).
You may also see durations such as Session (cleared when the session ends) and Persistent (stored until it expires or is cleared), which helps explain why some settings “stick” longer than others.
Keeping control: updating or withdrawing consent
The notice states you can change or withdraw your consent at any time from the cookie declaration on the website. Consent interfaces commonly offer options such as Allow all, Deny, or Allow selection, plus a Customize view where you can manage categories like Necessary, Preferences, Statistics, and Marketing.
If you contact the site regarding consent, the notice also asks you to provide your consent ID and the date, which helps support accurate troubleshooting or support requests.
Cookie declaration freshness
Staying current is a key part of transparency. The cookie declaration is stated as last updated on 3/2/26 by Cookiebot.
What this means for CRM enrichment outcomes
On a CRM enrichment page (for example www.findymail.com), it’s especially valuable to understand the connection between on-site functionality and measurement:
- On-site enrichment and verification signals (for example emailFinderAttempts and emailVerifierAttempts) point to workflows that help enrich records and clean data.
- Embedded forms (for example via ) can streamline lead capture and reduce friction during sign-up or requests.
- Marketing and embedded-media technologies (for example Meta and YouTube) support measurement and targeted outreach, enabling teams to learn what drives engagement and optimise campaigns accordingly.
Together, these elements support a practical growth loop: acquire interest, capture intent, enrich and verify data quality, and measure outcomes to continually improve performance.
Summary: cookies and related storage technologies are used here to support essential site function, remember certain preferences, enable marketing and embedded-media experiences, and store consent state (including cross-domain consent). Persistent site-specific entries also signal on-site email finding and verification capabilities that align with CRM enrichment and data cleaning goals.
