Clear
People should understand when Buddy is listening, connected or processing a request.

Buddy is being designed around understandable privacy controls, family-aware personal spaces and clear choices about what the companion can hear, remember and share.
Currently in development
A companion can only become meaningful when people feel comfortable around it. Buddy’s privacy experience should be visible and understandable—not hidden behind complicated settings.
People should understand when Buddy is listening, connected or processing a request.
People should decide what Buddy can remember and remove saved information when needed.
Different family members should have separate profiles, preferences and private histories.
These principles guide planned controls. The hardware, software and security systems still require development and testing.
The planned approach is to make listening and voice processing understandable. Physical or software microphone control is a design goal under consideration; a physical switch is not a confirmed hardware feature.
The intended controls would let people choose what is retained and distinguish a passing conversation from information they want saved.
Buddy should not treat every conversation as something that must be remembered.
These planned product behaviours aim to give family members their own experiences and protect against one person casually accessing another person’s information.
The companion app is part of the product vision and has not been released. These controls are planned ways to manage the device and personal information.
Buddy may eventually communicate with its owner through the internet and companion app. The following safeguards are design goals that require implementation, review and testing.
Buddy’s intended audience includes people of different ages. For younger users, the design should provide additional guidance, controls and boundaries.
Final child-safety features will require specialist review, testing and compliance work before release.
Some features may require online AI services, while selected basic functions may eventually work locally. The final architecture has not been decided. The intended approach is to make these choices understandable.
The security programme is planned work, not a completed architecture or certification. The following areas will need development, validation and ongoing review.
Specific security measures, providers and certifications will be confirmed as Buddy’s hardware and software architecture develops.
This checklist describes the controls we intend to develop, rather than functionality that is available today.
As Buddy moves through prototyping, Ankorforge intends to document important changes to privacy, connectivity and data handling in clear language.
This page describes current design principles and planned controls. It is not a final legal Privacy Policy or a guarantee of completed functionality.
Get occasional updates about Buddy’s development, prototype progress and early-access opportunities.
For investment, technical partnerships, manufacturing, media or general enquiries, contact Ankorforge.
iamsoundharraj@gmail.com