This Cookie Policy explains how Eppigo (the "Platform"), operated by Epicare Insurance Corp ("Epicare," "we," "us," or "our"), uses cookies and similar technologies. It should be read together with our Privacy Policy, which describes our broader privacy practices, and with the Your Privacy Choices controls described in Section 7.
In short: cookies strictly necessary for the Platform to work load automatically, and so do the technologies we use to measure traffic and our advertising — you can turn those off at any time. Session recording stays off unless you switch it on. Two things override those defaults: a Global Privacy Control signal from your browser, and being in Washington State — in either case nothing beyond the strictly necessary loads until you tell us otherwise. We never place health questionnaire responses, policy numbers, or payment details into any of these technologies, and we keep the features that could send hashed customer data turned off.
What cookies and similar technologies are
Cookies are small text files placed on your device by a website. Similar technologies include local storage, session storage, software development kits (SDKs) in mobile apps, pixels, and tags.
- First-party vs. third-party.A cookie is "first-party" when it is set on the eppigo.com domain, and "third-party" when it is set by, or shared with, another company. Some of the cookies described below are first-party cookies that nonetheless send information to Google or Meta.
- Mostly client-side. The technologies described below run in your browser and send data directly from your device to their providers. The one exception is Meta's Conversions API Gateway(Section 2), which receives a copy of the Meta pixel's events and sends it to Meta from a server. We send no conversion events from our own servers.
The technologies we use, and how each one is controlled
We name every third-party technology we use, and we do not treat them all the same — because they do not all do the same thing to your privacy.
On by default. You can turn these off.
- Google Tag Manager (Google LLC) — the tag-orchestration layer that loads and fires our advertising tags. It sets no tracking cookies of its own, other than temporary cookies used by an administrator previewing the configuration.
- The Meta advertising pixel (Meta Platforms, Inc.), delivered through that container — measures how our advertising performs. It does so across other websites, which under California law counts as "sharing" your personal information (Section 7). It is configured with Meta's Conversions API Gateway: the pixel also sends a copy of the same events to a gateway server (hosted on Google Cloud, with a backup on Amazon Web Services), which passes them to Meta server-side without adding customer data. It switches off with the pixel.
- Vercel Analytics (Vercel Inc.) — aggregate counts of traffic to our own pages.
Off unless you switch it on.
- Contentsquare — records how you move through a page: which areas you see, click, and scroll. We keep this off by default, and it runs only if you turn it on.
Two situations override those defaults, and then nothing beyond the strictly necessary loads at all:
- Your browser sends a recognized opt-out preference signal, such as the Global Privacy Control.
- You are in Washington State, or we cannot determine where you are, and we ask for your choice before loading anything (Section 6). Washington also has its own standalone policy for this data: see our Consumer Health Data Privacy Policy.
We measure advertising results from visits and steps on the Platform — for example, viewing plans, starting an application, creating an account, and app downloads. Conversion triggers read the structure of the page — destination URLs and the identifiers of visible page elements — and do not read the name, gender, health answers, or any other content you type into a form.
What the container loads. Through Google Tag Manager we also load Google Analytics 4 and Google Ads conversion tracking and remarketing (Google LLC): Google Ads uses visits to the Platform to build audiences so our ads can be shown to those visitors on other sites, which is also "sharing" (Section 7). They belong to advertising measurement: turning that category off, or sending a Global Privacy Control signal, stops them with the container. There is no TikTok integration: the TikTok Events API was named as a recipient in earlier versions and has been removed, because it does not exist.
Cookies and identifiers
The following first-party cookies and identifiers may be set. Advertising and traffic-measurement identifiers are set unless you turn those categories off; session-recording identifiers are set only if you turn session recording on (see Section 6). The values below are pseudonymous random identifiers, not your name or email.
Read the "Verified" column before relying on this table. Rows marked code are verifiable from the application's source. Rows marked container are set by tags confirmed in the live Google Tag Manager container on 2026-09-23. Rows marked live need to be confirmed against the live cookie inventory. Confirming the whole table against production is a pre-publication verification, not a drafting question.
| Cookie / identifier | Set by | Party | Lifespan* | Purpose / stored value | Nature | Verified |
|---|---|---|---|---|---|---|
| _fbp | Meta advertising pixel | First-party | 90 days | Randomly generated browser identifier (format fb.1.<timestamp>.<random>) | Pseudonymous | container |
| _fbc | Meta advertising pixel | First-party | 90 days | Stores the Meta click identifier (fbclid); set only when you arrive from a Meta ad | Pseudonymous | container |
| FBCLID | Meta (URL → stored in _fbc) | First-party | With _fbc | Meta ad-click identifier | Pseudonymous | container |
| _ga, _ga_<id>, _gid | Google Analytics 4, through the container | First-party | 2 years / 24 hours | Random client ID and session state | Pseudonymous | container |
| _gcl_au, _gcl_aw, _gcl_dc, GCLID | Google Conversion Linker / Google Ads, through the container | First-party | 90 days | Ad-click information for conversion attribution | Pseudonymous | container |
| Contentsquare identifiers | Contentsquare | First-party | Live inventory | Session-recording identifiers; set only if you turn session recording on | Pseudonymous | live |
| Vercel Analytics | Vercel | — | — | Aggregate page-traffic counts; designed to operate without setting cookies | Pseudonymous | live |
| Strictly-necessary cookies | Eppigo | First-party | Session / short-lived | Session management, authentication, security, fraud prevention | Operational | code |
| Functional cookies | Eppigo | First-party | Persistent | Remember preferences such as language and market | Operational | code |
| Consent record | Eppigo | First-party | Persistent | Your category choices and the date you made them, so we can evidence your decision | Operational | code (PR #384) |
| Anonymous session storage (web only) | Eppigo | First-party | Session | An opaque identifier so activity can continue within a session before you create an account | Pseudonymous | code |
* Browser caps shorten these in practice.The two-year figure is a Google default. Chrome caps any cookie at 400 days. Apple's Safari further caps script-set cookies to 7 days, and to 24 hours when you arrive from an ad with a click parameter in the URL. Because iPhone browsers use Safari's engine, many visitors hold these cookies for days, not years. Exact lifespans depend on the live configuration and your browser.
Google Tag Manager does not set tracking cookies of its own. Google Analytics 4 does not store IP addresses; it uses the IP in memory to derive coarse location and then discards it.
Where these technologies run, and what never enters them
They run across the Platform.The technologies in Section 2 are loaded from the application's root layout, which means they are present on public pages and on signed-in pages alike — including the insurance application and enrollment flow, the medical questionnaire, identity verification, payment, and your Wallet.
What never enters them. We never place health questionnaire responses, policy numbers, or payment details into any analytics or advertising technology. Conversion measurement reads only the structure of a page — its URL and the identifiers of visible elements — and does not read what you type. We do not use browser-fingerprinting technologies.
A withdrawn claim, stated plainly. Version 2.0 of this Policy said these technologies ran only on public, non-authenticated marketing pages, and never on the surfaces listed above. It named a content-security policy and a route allowlist as the controls enforcing that boundary. Neither control exists in the codebase, and the claim has been withdrawn. A control that was never implemented cannot be relied on, even if it turns out that no sensitive data left. What we rely on instead is the payload limit above, and keeping session recording off by default.
HIPAA. We do not have a HIPAA business associate agreement with Google, Meta, Contentsquare, or Vercel, and they are not our business associates: they receive page and event information, not protected health information, because we do not place health questionnaire responses into them. That rests on the payload limit, not on those technologies being absent from health-related pages — which is the reason version 2.0 gave, and it was not accurate. See our Compliance framework and the subprocessors registry.
Analytics and session recording
We measure aggregate use of the Platform to understand which parts work and which do not. Some of that measurement is first-party and server-side, and stays within our systems. The rest goes through Vercel Analytics and — if you have switched it on — Contentsquare. Both are third-party providers bound by contract to process this data only on our instructions. We do not build advertising profiles about you.
We do use a session-recording technology. Contentsquare records how you move through a page. Version 2.0 of this Policy stated that we used no session-replay, heatmap, or fingerprinting tool on any surface; the session-recording half of that statement was false from 2026-08-19, when Contentsquare became a production dependency, and it is corrected here. Contentsquare is off unless you switch it on, and we treat it as the most intrusive of the four technologies for the reasons given in Section 6.
On fingerprinting specifically: we do not use browser-fingerprinting technologies, and no dedicated fingerprinting library is part of the Platform.
Your choice, and how it is recorded
The first time you visit, a notice tells you what we use and lets you decide. You can accept everything, keep only the essentials, or choose category by category: strictly necessary (always on), traffic analytics, advertising measurement, and session recording. Strictly necessary cookies are not part of that choice, because the Platform cannot operate without them.
You can change your decision at any time — including long after that first visit — from the Your Privacy Choices link in the footer of every page, which carries the official California opt-out icon. We record your choice together with the date on which you made it, so that we can evidence it.
Why the four categories are not treated alike. Traffic analytics and advertising measurement are on by default, because that is the signal the business needs and, under United States law, opt-out is the applicable model. Session recording is off by default because it is the most intrusive of the four: recording a visitor's session before showing a privacy notice is the fact pattern of Javier v. Assurance IQ (9th Cir. 2022) — in which the defendant was itself an insurance agency — and is the subject of a large and growing body of litigation under the California Invasion of Privacy Act and its state analogues.
Washington State. If you are in Washington — or if we cannot determine where you are — that notice appears beforewe load anything beyond the strictly necessary, and we wait for your answer. Washington's My Health My Data Act requires affirmative consent before consumer health data is collected, its definition reaches people who are looking for health coverage, and it carries a private right of action.
This replaces both our pre-2026-06 practice of presenting no notice at all, and the version 2.0 description of a consent-first Consent Management Platform with Google Consent Mode v2 in "basic" mode. Neither of those was ever the deployed behavior.
Your choices and opt-outs
You have several ways to control tracking and advertising:
- Your Privacy Choices. The link in the footer of every page opens the category controls described in Section 6. Change your choice at any time.
- We do not sell. We do "share", and this is how you stop it. Using the Meta advertising pixel (and its Conversions API Gateway) for advertising measurement that works across other websites, and Google Ads remarketing, is "sharing" of personal information under the California Consumer Privacy Act as amended (CCPA/CPRA). Some state laws use broader definitions; turning off advertising measurement in Your Privacy Choices opts you out of all of it. It is on by default. Turning off advertising measurement in Your Privacy Choices opts you out; we stop loading those technologies.
- Global Privacy Control (GPC). We honor recognized browser opt-out preference signals, including the Global Privacy Control, as an opt-out of sharing for the browser that sends it. A GPC signal suppresses every technology in Section 2, not only the advertising ones.
- Account marketing preferences. You can manage marketing communications in your account settings; this governs the messages we send you, not the technologies in Section 2.
- Industry and platform opt-outs. You can also use industry opt-out tools at the Digital Advertising Alliance (optout.aboutads.info) and the Network Advertising Initiative (optout.networkadvertising.org), and the advertising controls offered by Google (adssettings.google.com) and Meta (in your Meta account settings).
- Browser controls. You can block or delete cookies in your browser settings. If you block strictly-necessary cookies, parts of the Platform may not function, including signing in.
Advertising measurement and hashed-data features
All advertising measurement happens in your browser, through the technologies in Section 2. We send no conversion events from our own servers and there is no Google Ads server-side integration. The one server-side path is Meta's Conversions API Gateway, which forwards a copy of the pixel's browser events to Meta (Section 2); it does not add customer data.
Certain platform features are capable of sending hashed customer data (for example an email address or phone number that has been transformed with SHA-256) to Google or Meta to improve match quality. Eppigo keeps all of them off. They are:
- Google Enhanced Conversions (hashed email, and optionally phone, name, and address);
- Meta Advanced Matching (hashed email, phone, name, city, state, ZIP, and an external identifier).
These features are OFF, and Eppigo does not enable them. Google Enhanced Conversions and Meta Advanced Matching are the only features that could send hashed customer data (a hashed email, phone, or name) to Google or Meta, and we keep them turned off. We share only pseudonymous identifiers and the page and event information described in Section 2 with Google and Meta. No hashed email, phone, or name — and no health questionnaire response, policy number, or payment detail — is ever transmitted to Google, Meta, Contentsquare, Vercel, or any other provider. Both are settings in the Google Tag Manager container and the Meta console rather than in our code; both were confirmed off in the live container on 2026-09-23. Hashed data is not anonymous (the receiving platform can re-identify it), which is one reason we keep these features off; Meta additionally restricts such matching for regulated verticals like insurance.
What each recipient receives, and IP addresses
- Google receives, through the Google Tag Manager container, the events and page information the container forwards. Through Google Analytics 4 it receives events, page URLs, referrer, device/browser information, and coarse location; your IP address is transmitted and processed only momentarily to derive coarse location and then discarded. Through Google Ads conversion tracking it receives the conversion event and stored ad-click information (GCLID / _gcl_*), and visits used to build remarketing audiences.
- Meta receives, through the advertising pixel, events, page URLs, device/browser information, IP address, and user agent, plus the _fbp / _fbc values, directly from your browser and as a copy through the Conversions API Gateway. Advanced Matching is off, so no hashed customer data is sent.
- Contentsquare receives, only if you have switched session recording on, a recording of how you moved through the page: which areas you saw, clicked, and scrolled.
- Vercel receives aggregate counts of traffic to our own pages.
Across every channel, we share only pseudonymous identifiers and page and event information. No hashed email, phone, or name, and no health questionnaire response, policy number, or payment detail, is ever transmitted to any of them.
These recipients process data in the United States and on their own multi-region infrastructure. We name Google, Meta, Contentsquare, and Vercel here because transparency about who receives your data requires it. TikTok was named in earlier versions and has been removed: no such integration exists.
The mobile app
The mobile app does not use cookies in the traditional web sense. It uses device storage to keep you signed in securely and to support security features, and a push-notification token to deliver notifications you have enabled. Third-party advertising and analytics technologies are kept off the app's sensitive surfaces (application, medical questionnaire, identity verification, payment, and Wallet).
On Apple devices, apps must ask permission before accessing the device advertising identifier (IDFA) under App Tracking Transparency; you are opted out by default unless you grant permission. On Android, the advertising identifier (GAID) can be reset or deleted in your device settings. Our disclosures here are consistent with the privacy information we publish on the app stores (Apple Privacy "Nutrition" Labels and the Google Play Data Safety form).
App install and app-store measurement
A website tag cannot see an app-store download; the download happens inside Apple's App Store or Google Play. Advertising-driven installs of the Eppigo apps are measured by software inside the apps together with the stores' privacy-preserving attribution frameworks:
- iOS: Apple SKAdNetwork and AdAttributionKit, which send cryptographically signed, delayed, and aggregated postbacks that contain no per-user identifier;
- Android: the Google Play Install Referrer, and the resettable Google advertising identifier (GAID);
- Meta and Google app measurement: Aggregated Event Measurement (iOS) and install-referrer methods (Android).
These frameworks are aggregated and privacy-preserving by design; they measure campaign performance, not the individual who downloaded the app, and they do not use the website's Pixel or Google tag.
Retention
Cookie and identifier lifespans are shown in Section 3 (subject to the browser caps noted there, and to the verification caveats in that section). Google Analytics 4 detailed event data is retained for no longer than 14 months. Conversion events and related identifiers are retained as described in our Data Retention Policy. Consent records are retained as required by law.
Changes to this Cookie Policy
We may update this Cookie Policy from time to time. When we make changes, we will update the "Last Updated" date above and, where the change is material, provide notice through the Platform and set a new Effective Date.
Contact us
For questions about this Cookie Policy or our privacy practices:
Epicare Insurance Corp
Attn: Privacy Officer
6970 Bird Rd APT 308, Miami, FL 33155
Email: privacy@eppigo.com
Member Support: support@eppigo.com, or the chat in the Eppigo mobile app
For more about how we handle your information and the service providers we use, see our Privacy Policy.
| Version | Effective Date | Summary |
|---|---|---|
| 1.0 | June 2, 2026 | Initial Cookie Policy for the Eppigo platform. |
| 2.0 | July 7, 2026 | Major rewrite reflecting a material change of practice: adoption of third-party analytics and advertising technologies (Google Tag Manager, Google Analytics 4, Google Ads conversion tracking, and the Meta Pixel + Conversions API) on public marketing pages, with a cookie banner / Consent Management Platform and Google Consent Mode v2. Retired the prior no-third-party-trackers and no-banner posture. Added the cookie/identifier table, the surface-segmentation control (no ad-tech on PHI/sensitive surfaces), CCPA/CPRA sharing opt-out and GPC honoring, disclosure of Google and Meta as recipients, the hashed-data features, and app-store measurement. Set the hashed-data features (Google Enhanced Conversions, Meta Advanced Matching, and Meta Conversions API user data) to OFF as a final decision — reversing the earlier draft position that had documented Google Enhanced Conversions and Meta Conversions API user data as "planned to be enabled with consent." The founder reverted that position to simplify the legal framework and reduce risk; no hashed customer data (email, phone, or name) and no medical, health, or financial information is transmitted to Google, Meta, or TikTok. Any future activation would require a fresh legal evaluation and, for Meta, written confirmation that the feature is permitted for a regulated vertical (insurance). Confirmed TikTok (TikTok Events API) as an active server-side conversion recipient carrying only pseudonymous identifiers plus the two conversion events — no hashed customer data, no client-side pixel, and no cookies — subject to the same consent and PHI red-line as Google and Meta. |
| 3.0 | September 1, 2026 | Rewrite following the September 1–2 audit. The v2.0 consent architecture — a Consent Management Platform, a cookie banner, Google Consent Mode v2 in "basic" mode, and Global Privacy Control handling — was never built, and the surface boundary it described was enforced by a content-security policy and a route allowlist that do not exist; both claims are withdrawn in §§4, 5 and 6 rather than restated. Contentsquare (session recording, a production dependency since 2026-08-19) and Vercel Analytics are disclosed for the first time; the v2.0 statement that no session-replay tool ran on any surface was false and is corrected. The consent model is the hybrid one decided by the founder on 2026-09-01: strictly necessary always on, advertising measurement and traffic analytics on by default and switchable off, session recording opt-in, and nothing beyond the strictly necessary under a Global Privacy Control signal or in Washington State, which is gated under the My Health My Data Act. "Sharing" is now affirmed rather than denied, and the footer control is named Your Privacy Choices with the official California opt-out icon. TikTok and the third-party CMP provider are removed as recipients because neither exists; Google Analytics 4 and Google Ads are described as container-side and explicitly not verifiable from the codebase, and the Section 3 table gained a Verified column recording which rows are code, console, or live-inventory facts. Publication is gated on PR #384 and PR #389; counsel review was waived by the founder on 2026-09-02. |
| 3.1 | September 21, 2026 | Aligned with the published text of the same date. Server-side conversion events removed from §§1, 7, 8 and 9: we send none, and no Meta Conversions API or Google Ads server-side integration exists. Google Analytics 4 and Google Ads conversion tracking are named as loaded through the Google Tag Manager container, verified against the live container on 2026-09-23, instead of "not verifiable". §6 follows banner copy 2.1 ("keep only the essentials"), and the Washington gate also applies when the visitor's location cannot be determined. |
| 3.2 | October 2, 2026 | Corrected against the live site (2026-10-01/02). Meta's Conversions API Gateway is active on our pixel and is now disclosed (§§1, 2, 8, 9): the statement that no server-side conversion events exist is withdrawn. Google Ads remarketing is disclosed and counted as "sharing" (§§2, 7, 9). The "only two conversions" statement is replaced by what is measured. §10 no longer says "as on the web", which contradicted §4. Contact: support@eppigo.com or the mobile-app chat — there is no chat on the website. The explanation of broader state-law definitions in §7 is simplified. |
A complete change log is available on request.