Send a link in one tap, share just part of a tree, add a passcode, or give someone full live access — and take any of it back. Every screen below is the real app.
You choose how much of the tree to send, who can open it, and for how long. Every link you make is listed where you can find and revoke it.
They can pan, zoom, search and export — but not edit. Names are shortened and living people's dates reduced before the page ever reaches them.
Sharing starts inside the tree, in the toolbar. There is no Share button on the dashboard tree cards: two of the three things you can send are defined by what is on your screen, so the tree has to be open.
There are no decisions to make. Simple always creates a read-only view link protected by Google sign-in — so there's nothing extra to hand over.
Paste it straight into WhatsApp. The link is also shown and pre-selected in the box, so if your browser blocks the automatic copy you can still tap Copy.
A welcome screen names the tree they've been invited to. The notice at the bottom explains the privacy rules up front, so nobody thinks the shortened names are a mistake.
This is the part worth understanding. Below is the same tree, at the same moment — on the left as you see it, on the right as your relative sees it through the link.
Full names become a single given name. Ahmad bin Ismail becomes just Ahmad — note that this also removes his father's name. Living people's birth dates disappear from the card, and private notes are never sent at all.
The shared view has its own slim toolbar. They can change how many generations show, search, switch theme, and Export the tree as an image or PDF — but there's no Add Person or edit control anywhere, because the link is read-only.
The same Share button from step 1 also decides how much goes out — and one of the choices is “exactly what is on screen now”. So set the generations window and the Show toggles the way you want them first, then press Share.
Which combination to pick for which relative is its own guide: Choosing how to share.
A Share selector appears at the top of the form with three choices, each showing how many people it covers:
The selector shows in both Simple and Advanced, so you can still create a scoped share in one tap.
Advanced asks "what should this person be able to do?" and then shows only the settings that matter for your answer.
When you've set a passcode, it's shown with the new link — and you can copy it again later from the links list.
Everything else on this page is redacted. Live access is not. The person you name sees the whole tree exactly as you do — full names, living people's dates, private notes — live, on their own dashboard, read-only.
Type their email address and press Grant access. They don't need an account yet — the grant is keyed to the address and starts working the moment they sign up.
The panel lists who currently has live access, and lets you remove any of them. Removing takes effect immediately.
The next three steps take those three buttons in turn. Nothing here is destructive except Revoke, which asks first.
Press Extend and pick how long it should stay active counting from now — not from when you made it. Never expires is there for the link you keep in the family group chat.
The passcode is printed on the row, so if a relative lost it you can just copy it again — you do not need to make them a new link. edit turns the line into a box: type a new code or press Generate, then Save.
Changing it takes effect at once. Anyone still using the old code is locked out until you send them the new one, which is exactly what you want if a link went somewhere it should not have.
Revoke kills the link immediately for everyone holding it — anyone with it open loses access on their next move. You are asked to confirm because it cannot be undone: there is no un-revoke, and a new link is a new URL.
Nothing about your tree changes. Revoking removes the way in, not any data.
A tree that has live links shows a count on its dashboard card. Tapping it opens the share modal straight at the list above — switching to Advanced for you, since that's plainly a manage-what-I-sent intent rather than a make-another-one intent.