Cookie Policy

Effective: April 23, 2025
Updated: April 23, 2025
Version 1.0

Effective Date: April 23, 2025

1.1

Our SaaS platform uses cookies to ensure secure, efficient access to Medicare claims data. In the United States there is no comprehensive federal cookie law, but various state privacy laws regulate cookies and tracking as part of personal data protection.

1.2

Generally, U.S. privacy laws such as California’s CCPA/CPRA and similar laws in Virginia and Colorado follow an opt-out model. Prior consent for cookies is not strictly required, but users must be given transparency and the ability to opt out of certain data uses.

1.3

California law requires companies to provide a clear Notice at Collection of personal information and a Do Not Sell My Personal Information link if cookies or other means are used to sell or share data, even though an explicit cookie banner is not mandated.

1.4

In line with U.S. best practices and emerging regulations, we provide this Cookie Policy to explain what cookies we use and why. We focus on transparency about cookie use (as required by laws like GDPR in Europe and state laws in the U.S.). Even though U.S. laws do not yet demand a banner for cookies, many organizations apply the strictest standards to all users as a precaution. We are committed to clarity and will inform you of how cookies function on our site. We do not use any cookies for advertising, telemarketing, or selling personal data. Our cookies are used only for the purposes described in this policy, in support of our service to licensed insurance agents and Medicare beneficiaries.

1.5

Note: “Cookies” in this policy also covers similar technologies like local storage or pixels, which we currently do not use beyond the stated purposes.

2. What Are Cookies and Why We Use Them

2.1

Cookies are small text files stored on your device when you visit websites. They help enable essential site features, enhance your experience, and collect analytics to improve our services.

2.2

Because our platform handles sensitive Medicare claims information, we design our cookie usage with privacy and security in mind. We do not store any Protected Health Information (PHI) or Medicare claims data in cookies.

2.3

Cookies generally contain anonymous unique identifiers or small pieces of data, not your personal details. A cookie might store a random session ID or remember that you prefer to stay logged in, but it will not contain your name, claim details, or health information.

2.4

There are two types of cookies by lifespan. Session cookies are temporary and last only while your web browser is open, for example to manage your login session. Persistent cookies remain on your device for a set period after your session unless you delete them and can remember preferences or credentials for future visits.

2.5

Our platform uses three categories of cookies: Essential, Functional, and Analytics.

3.1 Essential Cookies

Purpose: necessary for core functionality such as login, secure navigation, and basic features. These are required for the service to work properly and do not collect personal information beyond what is needed to operate the site. Examples: a session ID cookie to keep you logged in and security cookies used for fraud prevention or access controls.

3.2 Functional Cookies

Purpose: improve your experience by remembering choices and preferences. These are not strictly necessary but provide convenience, such as remembering your login on return visits or other settings. They may save limited personal data if you choose to use those features, for example a persistent login token when you select “remember me.” Current use is minimal and primarily limited to login preferences.

3.3 Analytics Cookies

Purpose: collect information about how users interact with our site—pages visited, frequency, and errors encountered—to help us improve performance. Cookies such as Google Analytics assign a random ID to your browser to distinguish users, but do not identify you personally. Data is aggregated and used anonymously. We configure analytics in line with privacy best practices, including IP anonymization.

4. Essential Cookies (Strictly Necessary)

4.1

These cookies are critical for the operation of our platform. They enable authentication, session management, and security. Without them, services such as logging into your account, navigating secure areas, or submitting claims data would not be possible.

4.2 Authentication

Essential cookies remember your login state during your session so only authorized users can access Medicare claims data and you stay logged in securely.

4.3 Session continuity

Essential cookies preserve context as you navigate so your connection to our server remains active and associated with your account.

4.4 Security

Essential cookies help protect against unauthorized access and may support load balancing or CSRF protection. These cookies contain no sensitive personal details and are not used for marketing.

4.5

Because essential cookies are necessary for the site to function, they are set without requiring prior consent. Privacy laws recognize that strictly necessary cookies can be used so long as users are informed about them. Blocking them in your browser will likely prevent secure login and core functionality from working.

4.6 Examples

A session cookie that stores a unique random identifier for your session and expires when you log out or close your browser, a security cookie such as a CSRF token to confirm actions are initiated by you, and a load balancer cookie to direct requests to the same server for stability.

4.7 Changes

Cookie names and technical details may change as we update security practices, but the purposes described here define the essential category.

5. Functional Cookies (Preferences and Convenience)

5.1

Functional cookies enhance usability by remembering preferences and choices. If a licensed agent opts to “Remember Me” at login, a functional cookie can store a secure token so that on the next visit the agent can log in more quickly.

The primary functional cookie in use is a persistent login cookie that stores a hashed identifier allowing us to recognize your device on your next visit. It may reference your user ID in encrypted form, may have a longer expiration to facilitate periodic visits, and should not be used on public computers. If you do not use “remember me,” this cookie will not be set.

5.3

Most functional cookies do not individually identify you and often store generic settings or random IDs. Where an identifier exists, it is used solely for the feature you requested and is not shared for other purposes. The platform will still work if you disable functional cookies, but you may need to log in manually or reset preferences.

6. Analytics Cookies (Tracking and Performance)

6.1

We use a limited set of analytics cookies to understand how our platform is used and to improve it. Google Analytics helps us gather aggregate information such as the number of users who log in, frequently used pages or features, session duration, and error rates.

6.2

Data collected may include device type, browser type, anonymized IP information, pages visited, time on page, and interactions such as link clicks or downloads. We do not feed account-specific information or Medicare claim content into Google Analytics, and we receive only aggregated or statistical reports.

6.3

Google acts as our service provider for analytics. We enable privacy-enhancing features such as IP masking and disable data-sharing features we do not need. Google Analytics cookies do not allow Google to personally identify you in this context.

6.4 Examples

Examples of analytics cookies include \_ga which distinguishes unique users and typically persists for two years, \_gid which distinguishes users on a shorter timescale and typically lasts twenty-four hours, and \_gat which may throttle request rates and typically lasts about one minute.

6.5

We use analytics to improve content and performance, not to make decisions about individual users and not for marketing.

6.6 Controls

You may block or delete analytics cookies without affecting core functionality. We plan to implement an on-site consent tool to allow formal opt-out of analytics. Browser-level Do Not Track signals and Google’s opt-out add-on can also reduce or stop analytics tracking.

7. No Advertising or Marketing Cookies

7.1

We do not use advertising cookies or tracking for commercial marketing. We do not run ads on our platform, and we do not include ad-network pixels or social media trackers.

7.2

If our practices change in the future, for example by embedding third-party media that sets tracking cookies, we will update this policy and obtain consent where required.

8. Your Choices and Control Over Cookies

8.1

Browser settings allow you to block or delete cookies, refuse new cookies, or receive notifications when cookies are set. Disabling all cookies will prevent essential functions such as secure login from working.

8.2 Do Not Track

Do Not Track signals are honored for analytics on our platform. When detected, we do not load analytics cookies for that session.

A future cookie consent tool will provide on-site controls to accept or decline non-essential cookies and to change preferences at any time.

8.4 Google Analytics opt-out

Google provides a global opt-out browser add-on for Google Analytics that prevents data collection across sites that use it.

8.5

Our site functions best with essential and functional cookies enabled, but we respect your preferences and design for privacy-maximized settings where possible.

9. Contact Information

9.1

If you have questions or concerns about our use of cookies or need assistance managing them, contact us at [email protected].

9.2 Address

1034 N. Madison Ave., Pasadena, CA 91104.

10. Additional Reference

10.1

We also recommend reviewing our Privacy Policy for a broader understanding of how we protect user data.


Last Updated: April 23, 2025