Update README.md

README.md

@@ -125,13 +125,20 @@ In order to keep IOCs and whitelist updated constantly, TinyCheck integrates som
 
 If you have seen something very suspicious and/or needs to be investigated/integrated in one of these two lists, don't hesitate to ping us. You can also do you own watcher. Remember, sharing is caring. 
 
+### Q&A with the developper
+
+**Your project seem very cool, does it send data to Kaspersky or any telemetry server?**<br />
+No, at all. You can look to the sources, the only data sent by TinyCheck is an HTTP GET request to a website that you can specify in the config, as well as the watchers URLs. Kaspersky don't - and will not - receive any telemetry from your TinyCheck device.<br /><br />
+**I'm not very confortable with the concept of "watchers" as the IOCs downloaded are public. Do you plan to develop a server to centralize AMBER/RED IOCs?**<br />
+Yes, if the demand is felt by NGOs (contact us!). Is it possible to develop this kind of thing, allowing you to centralize your IOCs and managing your fleet of TinyCheck instances. The server can also embed better detection rules thanks to the telemetry that it will receive.<br /><br /><br />
+
 ### Possible updates for next releases
 
 - Centralized server for IOC/whitelist management (aka. Remote Analysis).
 - Possibility to add watchers from the backend interface.
 - Encryption of ZIPed reports.
 - Better frontend GUI/JS (use of websockets / better animations).
-- More OpSec (TOR integration, IP randomization etc.)
+- More OpSec (TOR integration, Local IP randomization etc.)
 - 3d template for kiosks ?
 
 ### Special thanks