We are providing the source, and people can rebuild it from scratch and ensure that their device is running the open-source code. In theory, it is each user who should deploy his device. If an industrial partners want to ship our software to many devices, indeed it will be needed for them to prove he hasn't modified the software and we are happy to learn about best practices to help them do so, so we will look at this
This might be a good starting point:
Yea, as a privacy conscious user this would be the attack vector that I’d be most nervous about. “Partners” taking the open source engine and loading it up with surveillance. Being able to re-compile and deploy a vanilla version from source is critical. There are a lot of “smart” devices out there that I would buy if only I had root and/or could decide what software ran on it.
edit: I thought you were also doing something similar to Mycroft and their 'mark 1' thing. I was wrong.
It will be open-source and free for all users to use and create assistants.
If an industrial device maker wants to use the open-source version and add to it proprietary components, it will be his decision and he should inform his customers.
The best we can do when building and open-sourcing our assistant platform is to make it possible for commercial vendors to create state-of-the-art private-by-design voice assistants if they want
Put some of the information of your posts here on your page and things would be much clearer.
Is this monitoring built into your product? If not, wouldn't a user of any AI assistant have this same ability?
Excellent! How will you guarantee that your devices will not leak data?