Family CRM
The plumber’s number, a cousin’s new address. Never shown to a crowd.
Kinshire keeps one record of the people in your life. On top of it sit your contacts, your photos, the family calendar, and whatever you’ve worked out about where everyone came from.
The whole platform runs from one Docker Compose file on a home server. Self-hosting is the default, not a paid tier.
Kinshire keeps details about people together with who added them and who may see them. A family tree is one view over that shared record, not a separate database.
The plumber’s number, a cousin’s new address. Never shown to a crowd.
Your photos, tagged with who is in them. A face tag is as private as a phone number, and the person pictured controls who can see their name.
Chores, meals, shopping lists, the calendar. Plus a living-room display that shows the day without being asked.
Research on the dead, backed by evidence and open to review by other researchers. Seeded from public-domain records, never scraped.
Private family data stays on your family’s own server. When you publish something, Kinshire makes that change explicit and applies the same choice everywhere.
How Kinshire treats family-held and published information.
| Kept with your family | Shared publicly | |
|---|---|---|
| Who can read it | You, and the people you name | Whoever you published it to |
| Where it is stored | Your family’s own server. Not copied to Kinshire. | May join Kinshire’s shared research collection |
| Face matching | On your device. We never receive it. | Only for people who opted in |
| If you erase it | Removed completely. It never left your box. | We erase ours and request erasure elsewhere; external copies may remain. |
And whoever you write about is protected whatever you choose: a living person who never signed up shows as a name and nothing else outside your own circle.