Why Kinavela has no public feed

As of 15 August 2026, Kinavela has no public feed. Such a feed would be easy to explain. Open the app, see pictures and posts, react to them, and come back later. We decided against that pattern for Kinavela.

The reason appears in one line on our home page: “Families need trust, not reach.” Someone mentioning their child, cultural roots, or a possible meeting place should not first have to wonder which unknown audience is reading.

Kinavela is built around relationships, not attention.

Discover first, then consent

Family discovery shows enough information for a useful first impression. Shared roots, compatible age groups, and an approximate distance can help. An exact address or a public child profile cannot. Those details only add risk.

Nor can someone simply message every family they see. A private conversation starts only after mutual consent. Until then, contact details and precise locations remain hidden. A family that does not want further contact never has to extract itself from a chat that was already opened for them.

This reduces the number of possible conversations. It gives the conversations that do begin a clearer foundation.

A Village is not an audience

Villages are intended to be small local communities. Kinavela may recognise that several compatible families live within the same radius, but that signal does not create a group by itself. A family must deliberately start a Village, invite others, and give it a purpose.

Inside a Village, families can talk, share culture, and plan activities. The precise address of an event is handled separately and shown only to the people allowed to see it. A Village post is a conversation among members, not material for a public timeline.

Private does not mean unaccountable. Messages and Villages can be reported, families can end or block connections, and child-safety concerns have a clear route for review. Trust needs boundaries and tools for the moments when something goes wrong.

Four questions before signing up

Before joining a family network, people should be able to get clear answers to four questions:

• Are exact addresses or child profiles publicly visible?
• Can a stranger send a message without prior consent?
• Who can see the precise address of a family activity?
• How can a family block contact and report a safety problem?

Those answers belong in the platform itself, not only in a long privacy policy. Families should be able to understand which information becomes visible, at what point, and to whom.

Less display, more meeting

A feed rewards whatever gets viewed often. Kinavela should reward a different outcome: two families feeling safe enough to start talking, and that conversation eventually becoming an afternoon spent together.

We do not judge the idea by how much can be shared publicly. What matters is how little a family has to reveal before choosing who may be trusted with more. For Kinavela, that is not a missing feature. It is the shape that holds the product together.