Privacy Policy

The Secure ID Coalition does not sell, rent, exchange or otherwise disclose our mailing lists or information about our site visitors, except when compelled by law (we discuss this exception in greater detail here).

This Privacy Policy covers the Secure ID Coalition’s main Web site at, as well as other Secure ID Coalition -created or Secure ID Coalition -maintained sites that link directly to this Policy. Such other sites may also provide supplemental information in a site-specific policy.

When you visit any Web page hosted at our Web site, we will record the following information about you in our log files:

  • Internet Protocol (IP) address - The address of your computer on the Internet. Your IP address gets transmitted whenever you communicate online or surf the Web so that the content you are looking at and the people you are talking to can find your computer on the network.
  • Browser type, version, and operating system –Knowing the browsers (for example, Internet Explorer 7 or Firefox 3.5.3) and operating systems (for example Windows 7, Windows Vista, Windows XP or Mac OS X) used by our visitors helps us optimize the display and delivery of our site for visitors accessing it from differing software platforms.
  • Screen size - Knowing the screen sizes used by our visitors helps us optimize the display and delivery of our site for visitors.
  • Technologies supported by your browser for Java, Adobe Flash, Adobe Director, and Adobe PDF, and the audio formats supported by your browser for RealPlayer, QuickTime, and Windows Media Player – Knowing the formats supported by visitors’ browsers helps us optimize the content on our site for visitors accessing it with different browser configurations.
  • URL of the page that directed you to our site – If you arrive at our Web site through a link on another Web site - a blog, newspaper article, or search engine, for example - our Web server will record the address of the Web page that referred you to our site. If you arrive at our Web site by clicking on a search result returned by a search engine, our server will record the search terms that you used.
  • Whether you have bookmarked our Web site on your Web browser – This information is only reported for Internet Explorer users.
  • The Web pages within our site that you visit, the Web page you visit first on our site (the entry page), and the Web page you visit last on our site (the exit page).
  • Bandwidth used – The total number of bytes downloaded when you browse our site.
  • Amount of time you spend during a visit to our site.
  • Time and date of your site visit.
Learn How

Secure ID News to Know

  • Making Medicare Smart

    Today the House of Representatives took a significant step forward to protect seniors and ensure the solvency of the Medicare program by unanimously passing the bipartisan Fighting Fraud to Protect Senior Care Act – HR.6690. The bill calls for a pilot program to test modernizing the Medicare card by incorporating smart card technology to prevent waste, fraud and abuse.

    This landmark program will enable front-end authentication of Medicare beneficiaries and providers at point of care and support back-end data analytics to ensure transactions are legitimate. The Government Accountability Office estimates that such a program can positively impact over 22% of all Medicare improper payment and fraud cases. With Medicare waste, fraud, and abuse costing US taxpayers an approximated $60 billion every year, the Fighting Fraud to Protect Senior Care Act will help prevent over $13.2 billion from being lost on a yearly basis.

    We thank Congressman Peter Roskam and Congressman Earl Blumenauer for their heroic effort to protect Medicare for all Americans: beneficiaries, providers, and taxpayers alike.

  • The Five Things IoT Manufacturers Can Do To Future-Proof the Industry

    If there’s one thing that we’ve learned over the past few days since the Internet of Things (IoT) distributed-denial-of-service attack (DDoS) attack gave the Internet brain freeze last Friday is that (1) IoT devices are insecure, (2) we have a really good idea what needs to be done to make them more secure, yet (3) it’s hard to get everyone on the same page in dedicating the resources to actually make them more secure.

    While that might seem like a stark truth, it only makes sense given how our economy and legal system works. Since no one company or device was responsible for allowing the attack, there’s no specific organization to shame or blame. Plus, it’s way too easy to point fingers at everyone else in the room and say there was nothing that could’ve been done, as everyone is responsible. Further, security costs money, and at the moment, companies want to pour their resources into grabbing IoT market share, not plugging holes that may or may not cause problems downstream. Unfortunately, this kind of thinking invites regulators and legislators to step in and attempt to dictate technology standards and best practices to address harms, both real and imagined.

  • Patient Identity: Getting Back to Basics for National Health IT Week

    Monday kicked off National Health IT week! While the United States has made progress in moving towards a more modern healthcare system, significant work remains. There’s no disputing that our medical device and health technology companies are the most advanced on the planet, developing the solutions that are diagnosing diseases earlier, expanding treatment options, and improving quality of life. However, when it comes to healthcare and identity—making sure that the correct data is associated with the right patient, and ensuring that that information is able to be shared, analyzed, and acted upon in a timely fashion—the United States lags woefully behind many other developed nations.