Kaito AI founder Yu Hu said the Pulse browser extension’s verification feature uses zkTLS (zero-knowledge transport-layer security) and creates encrypted proofs only when users actively start verification. Kaito receives the final proof, not users’ complete account data or browsing history. Pulse’s interactive data collection on X, including content exposure, time spent and interactions, is authorized during installation and does not transmit activity from other websites to Kaito. Yu Hu acknowledged that Chrome’s permission prompt, "can read and write all website data," describes a broader scope than Pulse’s actual use and said it will be changed in the next version to "can read and write X website data," a point recognized by critics including Ultra. Kaito plans to open-source Pulse this week for community review. Yu Hu said device fingerprinting is used only to prevent abuse such as click fraud and witch attacks, not for analysis or other purposes. The open-source code is expected to provide the specific confirmation of Pulse’s features.