First I want to say that it’s totally my fault for not preparing proper documentation for the Spark and VivoKey service platform before the Spark was released. We had several units shipped to various people early to prep them for launch and they ended up being implanted into people and then questions started flying so we went ahead and released the Spark and MVP version of the VivoKey service platform ahead of any documentation.
The chip in the Spark is an ICODE ISO15693 NFC Type 5 compliant chip.
The NDEF data of the Spark is pre-programmed with a unique Spark URL that directs to the VivoKey service platform. This URL is central to the function of the VivoKey profile service, is locked, and cannot be changed or written to. The AES function performs encryption in the chip. We pre-program AES keys into the Spark and these are used to authenticate the Spark to the VivoKey service platform. When you create a VivoKey profile, your Spark is linked to it cryptographically using those keys. The only way to access your profile or any services tied to it will be by scanning a chip that is associated with your profile. It is not possible at this time for customers to access or use those keys.
That’s great! The point of the Spark and VivoKey service platform is to keep expanding the utility of your implant! The APIs, bug fixes, and more platform features are due out in the next release of the app. I really can’t wait to see what developers create!