Last updated: July 16, 2026
This Cookie Policy explains how eFind uses Cookies and similar technologies across our websites, advertising platform, and other Services. It describes what these technologies are, the categories we set, why we set them, how long they last, and the choices you have to accept, manage, or refuse them.
The purpose of this Cookie Policy is to give a clear and honest account of the small files and similar technologies that eFind reads from and writes to browsers and Devices when people use our Services. Cookies and related technologies are a normal part of how modern websites and advertising work, but they can also be confusing, and they touch on real questions about privacy and choice. This document is written so that a business owner, a User, or a regulator can understand what we do, why we do it, and how to change it, without having to be a technologist or a lawyer.
This policy also serves a legal function. It supports the disclosures we are required to make about tracking technologies, and it explains how we obtain Consent where the law requires it and how we honor the choices you make. It is meant to be read alongside our broader privacy documents, which describe in more detail what Personal Information we collect through these technologies and what we do with it.
This Cookie Policy applies to the eFind Ads advertising platform, the eFind websites at ads.efind.com and related domains, the dashboards and consoles we provide to Advertisers and Publishers, and any other Services that link to this policy. It covers Cookies and similar technologies that eFind sets directly, as well as those set by third parties through our Services when we permit them, to the extent we have visibility and control over them.
This policy does not govern the Cookies and technologies used by a Publisher on its own Publisher Property beyond the Advertisements and measurement code that eFind delivers, and it does not govern the practices of third-party websites, Landing Pages, or services that you reach through a link or an Advertisement. Those properties have their own cookie and privacy notices, and we encourage you to read them. Where an Advertiser or Publisher embeds eFind measurement code on its own property, the Advertiser or Publisher is responsible for providing its own notice and obtaining any Consent that applies to its site.
This Cookie Policy applies to Users who visit our websites or interact with Advertisements delivered through the Services, to Advertisers and Publishers who use our dashboards and tools, and to Authorized Users acting on their behalf. It is relevant to anyone whose browser or Device may store or transmit a Cookie or similar identifier in connection with the Services, regardless of where that person is located.
Capitalized terms used in this document, such as Advertiser, Publisher, User, Device, Consent, Personal Information, Conversion, and Conversion Tracking, have the meanings given in the Master Definitions. In this document, the word Cookie is used broadly to mean not only classic browser cookies but also the related technologies described below, unless the context clearly limits it to browser cookies. Where we mean a specific technology, we name it.
A Cookie, in the classic sense, is a small text file that a website asks your browser to store on your Device. The file holds a short piece of information, such as an identifier or a setting, that the browser sends back to the website on later visits. This lets a site remember things between page loads and between sessions, which is what makes it possible to stay signed in, keep items in a cart, or remember a language choice. Cookies cannot run programs, and they are not Malware, but the information they carry can be used to recognize a browser over time, which is why they matter for privacy.
The Services also use several technologies that work like Cookies or alongside them. Together we refer to all of these as Cookies in this policy unless we say otherwise. The main types are described below.
These are the classic text files described above. A session Cookie is deleted when you close your browser. A persistent Cookie remains on your Device until it expires or you delete it, and it lets us recognize your browser across separate visits.
A pixel, tag, or web beacon is a tiny piece of code or a small transparent image embedded in a web page, an Advertisement, or an email. When the page or message loads, the pixel sends a request to a server, which allows that server to record that the content was viewed and to read or set a Cookie. Pixels are central to how we measure Impressions, record Clicks, and attribute Conversions, and they often work together with Cookies to connect an action on one page to an event on another.
A software development kit, or SDK, is code that a developer includes in a mobile or connected-device application. When the application runs, the SDK can collect information about the Device and the app, support the delivery and measurement of Advertisements, and record events such as installs or in-app Conversions. SDKs perform in apps a role similar to the one Cookies and pixels perform on the web, because many apps do not use browser Cookies.
Local storage, including the browser feature known as local storage and similar on-Device storage, lets a site or application store larger or longer-lived data directly on your Device. We may use local storage to keep settings, cache content for speed, or hold information that supports features and measurement. Local storage is not automatically sent with every request the way a Cookie is, but it can still be read by the site or application that wrote it.
A Device identifier is a value assigned to a Device or provided by an operating system, such as a mobile advertising identifier, that can be used to recognize a Device across apps and sessions. We may use these identifiers, where they are available and permitted, to deliver and measure Advertisements in environments where Cookies are not present. Operating systems typically give people controls to reset or limit these identifiers, and we honor those signals as described later in this policy.
Throughout this policy, when we say we set or read a Cookie, we mean any of the technologies above that apply to your Device and environment. The choices we describe for managing Cookies are meant to reach all of these technologies together, not browser cookies alone.
Cookies are often described as first-party or third-party. The distinction is about who sets the Cookie, not about who benefits from it.
A first-party Cookie is set by the website you are visiting or by eFind on our own domains. First-party Cookies support core functions such as keeping you signed in to a dashboard, remembering your preferences, protecting against Fraud and Invalid Traffic, and measuring how our own pages perform. Because they are tied to the site you chose to visit, first-party Cookies are generally more limited in what they can see.
A third-party Cookie is set by a domain other than the one shown in your address bar, typically because the page or Advertisement includes content, measurement, or advertising code from another provider. In the advertising context, third-party Cookies and identifiers have historically been used to recognize a browser or Device across different sites in order to build audiences, cap how often an Advertisement is shown, and attribute Conversions. Browsers and operating systems are increasingly restricting third-party Cookies, and we are adapting our measurement and advertising to rely more on first-party data, consented signals, and privacy-preserving techniques. Where third parties set Cookies through our Services, we identify the categories they fall into below and we describe how you can control them.
We organize the Cookies and similar technologies we use into four categories, based on what they do. The table below summarizes each category with an example purpose and a typical duration. Durations are approximate and describe the longest we would normally keep a Cookie in that category; many expire sooner, and session technologies expire when you close your browser or app. Actual names, providers, and lifetimes are listed in the preference center described later, which is the authoritative and up-to-date inventory.
| Category | What it does | Example purpose | Typical duration |
|---|---|---|---|
| Strictly Necessary | Required for the Services to work and to be secure. These cannot be switched off through our controls because the Services would not function without them. | Keeping you signed in to a dashboard, balancing traffic across servers, remembering items in a session, and detecting Fraud, Invalid Traffic, and security threats. | Session to 12 months |
| Functional and Preferences | Remember choices you make so the Services feel personal and consistent, without which some features are less convenient. | Remembering your language, region, time zone, currency, accessibility settings, and whether you have already seen a message. | Session to 12 months |
| Analytics and Performance | Help us understand how people use the Services so we can measure performance, find errors, and improve. Data is used in aggregate wherever possible. | Counting visits, measuring page speed and reliability, understanding which features are used, and diagnosing technical problems. | Session to 24 months |
| Advertising and Targeting | Support the delivery, measurement, and relevance of Advertisements, including Conversion Tracking and cross-context behavioral advertising where permitted. | Attributing Conversions to Campaigns, limiting how often an Advertisement is shown, measuring reach, and tailoring Advertisements to likely interests. | Session to 13 months |
Strictly Necessary Cookies are the ones the Services genuinely cannot do without. They let us authenticate you when you sign in, keep your session secure, route requests to the right servers, remember what you are doing during a visit, and protect the Services and other people from Fraud, Invalid Traffic, and abuse. Because these Cookies are essential, we treat them as necessary under the law, which generally means we may set them without asking for Consent first. You can still block them using your browser, but if you do, parts of the Services, including signing in and completing secure actions, may stop working.
Functional and Preferences Cookies remember the choices you make and the state of the interface, so you do not have to set them again every time. Examples include your chosen language and region, your currency for Billing displays, accessibility options, and whether you have dismissed a particular notice. These Cookies make the Services more usable, but the Services will still work if you refuse them; you will simply see default settings and may need to re-enter certain choices.
Analytics and Performance Cookies help us understand how the Services are actually used, so we can make them faster, more reliable, and more useful. They let us count visits, see which pages and features are popular, measure load times and error rates, and understand the paths people take through a dashboard. We use analytics data primarily in aggregate to spot trends and problems rather than to learn about any one person. Some analytics providers may set their own Cookies through the Services; where they do, we categorize those Cookies here and disclose the providers in the preference center.
Advertising and Targeting Cookies support the part of our business that most people think of when they think of Cookies. They fall into a few related uses.
Advertising and Targeting Cookies are the category most affected by your choices. In regions where Consent is required, we do not set these Cookies for advertising purposes until you agree, and everywhere you have tools to opt out of them, which we describe in the sections on Consent and on managing Cookies.
The Advertising Services depend on being able to connect events that happen at different times and in different places. An Advertisement is requested for an Ad Unit, it is served as an Impression, a User may Click it, the User arrives at a Landing Page, and later the User may complete a Conversion. Cookies, pixels, SDKs, and identifiers are the threads that let us stitch these events together into a coherent measurement, so that an Advertiser can see that a Campaign produced results and pay only for what it agreed to pay for.
These technologies also support the integrity of the marketplace. By recognizing browsers and Devices, we can detect and filter Invalid Traffic, identify Fraud, and enforce our Policies, which protects Advertisers from paying for fake activity and protects Publishers and Users from abuse. Measurement built on these technologies is therefore not only about performance reporting; it is part of how we keep the ecosystem fair.
We are committed to doing this in a way that respects privacy. Wherever we can, we prefer aggregated and de-identified measurement, first-party and consented signals, and privacy-preserving techniques over broad cross-site tracking. As browsers and platforms retire third-party Cookies, we continue to move measurement toward methods that achieve the same accountability with less exposure of individual data.
Whether we need your Consent before setting a Cookie depends on the Cookie and on where you are. In many regions, the law requires Consent before non-essential Cookies are set, particularly Analytics and Advertising Cookies. In others, the law instead gives you the right to opt out of certain uses. We design our Consent experience to meet the higher standard where it applies and to offer meaningful choices everywhere.
For Users in the EEA, the United Kingdom, and other places with similar rules, we ask for Consent before we set Cookies that are not strictly necessary. This means that Functional, Analytics, and Advertising Cookies are not placed for those purposes until you agree. For Users in California and other United States jurisdictions with comparable laws, we may set certain Cookies by default but we give you the right to opt out of the sale or sharing of Personal Information and of cross-context behavioral or targeted advertising, and we honor recognized opt-out preference signals.
When Consent is required, we present a consent banner the first time you visit, before non-essential Cookies are set. The banner explains in plain language that we use Cookies, tells you the categories involved, and gives you clear options to accept all, reject all non-essential Cookies, or open the preference center to choose category by category. Rejecting is as easy as accepting. We do not treat continued browsing, scrolling, or closing the banner as Consent, and we do not use pre-ticked boxes. If you do not make a choice, we set only Strictly Necessary Cookies.
The preference center is the control panel for your Cookie choices. From it you can turn each non-essential category on or off, see the specific Cookies and third-party providers in each category with their purposes and durations, and change your mind at any time. Strictly Necessary Cookies are shown for transparency but cannot be switched off, because the Services would not function without them. You can reopen the preference center at any time using the link we provide in our footer or settings, and your choices are remembered for future visits on that browser until they expire or you clear them.
You can revisit and change your Cookie choices whenever you like through the preference center. Withdrawing Consent is as simple as giving it, and it will not affect any Processing that already took place while your Consent was valid.
Where we rely on your Consent, you can withdraw it at any time through the preference center or the equivalent controls we provide. When you withdraw Consent for a category, we stop setting new Cookies in that category for those purposes and we act to disable the related technologies going forward. Withdrawing Consent does not undo Processing that already happened lawfully while your Consent was in effect, and it may reduce the personalization or convenience of the Services.
You have several ways to control Cookies, and you can use as many of them as you like. The preference center described above is the most direct way to control the Cookies eFind sets, but the following tools give you broader control.
Most browsers let you see the Cookies you have, delete them, and block or limit new ones, including blocking third-party Cookies specifically. You can usually set the browser to warn you before accepting a Cookie or to reject all Cookies, and you can clear Cookies and local storage at any time. Because these settings live in the browser, changing them affects all sites, not just eFind, and clearing Cookies will also clear the choices you made in our preference center on that browser, so you may be asked again. If you use several browsers or Devices, you will need to set your preferences on each one.
Mobile operating systems and connected Devices provide their own advertising controls. You can typically reset or delete your Device advertising identifier and turn on a setting that limits or opts you out of interest-based advertising. When you enable these settings, we and our providers treat them as a signal to stop using that identifier for cross-context behavioral advertising. In apps, these Device controls, rather than browser Cookie settings, are the primary way to manage advertising.
Some browsers and extensions can send an automated opt-out preference signal, most commonly the Global Privacy Control, or GPC. Where the law requires us to honor such a signal, we treat a valid GPC signal received from your browser as a request to opt out of the sale or sharing of Personal Information and of cross-context behavioral or targeted advertising for that browser or Device. This lets you exercise your choice automatically across sites without having to opt out on each one. Because the signal is tied to a specific browser or Device, you should enable it on each browser and Device you use.
Various industry programs and advertising platforms offer their own tools to opt out of interest-based advertising from participating companies. These tools generally work by setting an opt-out Cookie in your browser, which means that if you clear your Cookies or use a different browser or Device, you may need to opt out again. We participate in and honor recognized opt-out mechanisms to the extent they apply to the Advertising Services, and the preference center lists the third-party providers whose own opt-out tools you may also wish to use.
Opting out of advertising Cookies does not mean you will stop seeing Advertisements. It means the Advertisements you see will be less tailored to you. Blocking Strictly Necessary Cookies, by contrast, may prevent parts of the Services, including signing in, from working at all.
Do Not Track is a setting some browsers offer that sends a request asking websites not to track a User. There is no common industry or legal standard that defines what a website must do when it receives a Do Not Track signal, and browsers do not send it consistently. For that reason, our Services do not currently respond to Do Not Track signals in a uniform way. We do, however, honor the Global Privacy Control and other legally recognized opt-out preference signals as described above, and we encourage you to use those mechanisms together with our preference center to control cross-context behavioral advertising.
How long a Cookie lasts depends on its type and purpose. Session Cookies and equivalent session technologies expire when you close your browser or app. Persistent Cookies remain until they reach the expiry date set when they were created or until you delete them. The typical durations shown in the category table above describe the longest we would normally use for each category; in practice many Cookies expire sooner, and we set expiry to no longer than is reasonably needed for the purpose.
We periodically review the Cookies we set and their lifetimes, and we remove Cookies that are no longer needed. The preference center shows the current, specific durations for individual Cookies, which take precedence over the general ranges in this policy. When a Cookie expires or you delete it, the information it held is no longer available to be sent back to us, although information already collected while it was active may be retained separately as described in the Privacy Policy.
Some Cookies and similar technologies used in connection with the Services are set by third parties we work with, such as analytics providers, advertising and measurement partners, content delivery and security providers, and, on Publisher Properties, the demand and supply partners that participate in the advertising ecosystem. These third parties may use the technologies they set to perform the services they provide to us, and, subject to our agreements and Applicable Law, for their own purposes as described in their own policies.
We require the third parties we engage to Process Personal Information on our behalf to do so under appropriate contractual protections, including a Data Processing Addendum where applicable, and to respect the choices you make. We do not, however, control the independent practices of third parties, and we are not responsible for the content of their policies. The preference center identifies the third-party providers that may set Cookies through the Services, along with links to their own notices and opt-out tools where available, and it is the authoritative source for that list because providers change over time.
This Cookie Policy focuses on the technologies themselves. It works together with our broader privacy documents, which explain what Personal Information we collect, why, and what rights you have.
If there is any conflict between this Cookie Policy and one of those notices about a specific right or obligation, the more specific privacy notice governs for the matter it addresses, and this Cookie Policy governs the details of how the technologies work.
We may update this Cookie Policy from time to time to reflect changes in the technologies we use, in the Services, in our providers, or in the law. When we make a material change, we will post the updated policy and, where required or appropriate, we will give additional notice, such as through the consent banner or a notice in the Services, and we will ask for renewed Consent where the law requires it. The list of specific Cookies and providers in the preference center is kept current continuously and may change more often than the text of this policy. We encourage you to review this policy and your preferences periodically so that you understand how we use Cookies and can keep your choices up to date.
If you have questions about this Cookie Policy or about how we use Cookies and similar technologies, you can contact the eFind Office of Trust and Legal at support@efind.com or by phone at 1-214-444-8126. You can also write to us at eFind LLC, 2451 West Grapevine Mills Circle, Suite 324, Grapevine, TX 76051, United States. To change your Cookie choices, the fastest route is the preference center, which you can open at any time from the footer of our Services.
Building Technology People Can Trust.
© 2026 eFind. All rights reserved.