The moment new parents hesitate
Building a gift list is the easy part. Typing your street address into it is where people stop and stare at the screen.
The worry is specific, and it is reasonable. That is a newborn's home address, sitting on a page, findable. Not for a week, but for as long as the page exists. Shared with everyone who ever got the link, including the people two forwards removed from anyone you actually know.
So parents invent workarounds, and the workarounds are usually worse than the problem. Ship everything to a relative's house and re-sort a pile of boxes later. Skip the address entirely and then answer the same question forty separate times.
Here is the thing nobody tells you. "Show my address" does not have to be one switch for your entire account.
On Belovity it is not. It is a decision you make one gift list at a time.
The question people are actually asking
It sounds like one question. It's four.
Is it on the page? Sitting out in the open where any visitor reads it, or tucked inside a step that only a buyer reaches?
Who is standing there when it appears? A stranger who found the link, or someone you already let in?
Does it apply to everything? One address for your whole account, or a separate call for each list?
Can you take it back? Is turning it off a real removal, or just a hidden field still sitting in a database somewhere?
Most people ask one question and get one answer. These four can have four different answers, and the difference between them is the whole story.
The two designs that get it wrong
There are two ways to build this that leave you without a real choice.
The first is the address as a profile field. You enter it once when you sign up. Every list you ever make inherits it. There is no per-list answer available to you, because the product never asked a per-list question in the first place.
The second is the address as page content. It is printed on the list itself, right next to your name, for whoever opens the page. No purchase required, no account required, no relationship required.
How Belovity approaches it
The address belongs to the list, not to you
Every gift list carries its own answer to DISPLAY DELIVERY ADDRESS. It is a plain Yes or No, and you answer it while you are building the list.
Two lists in the same family can answer it differently. Yes on the baby shower list. No on the birthday wish list. Changing one list's answer changes nothing at all about the other.
There is no account-level address setting quietly overriding your choice, because there is no account-level address setting.
Answer No, and the list still works completely
Guests browse every published item, sorted by price, exactly as they would otherwise.
They still click through to the store and buy. They still come back and mark items as purchased, set a quantity, sign their name, and leave you a note.
Nothing about the gifting flow depends on the address being there. The address block is simply absent.
What guests never learn is what street you live on, what city, or what postal code.
Answer No later, and the address is actually gone
The address fields disappear from the form the moment you switch the answer to No.
Save the list, and the stored street address, unit, city, region, postal code, country, and recipient name are cleared. Not hidden. Cleared.
That matters for a sequence that happens to almost everyone. The shower happens, the gifts arrive, and now you would rather your address stopped existing on the internet.
Turning it back on later means typing it again. That is the tradeoff, and it is the right one.
Answer Yes, and it shows up in one place only
The address is not printed on the gift list page. It never appears next to your family name, your items, or your cover image.
It appears inside the purchase step, in the panel that opens when someone has picked an item and is on their way to the store.
Two things have to be true before that panel can even open. The person has to be signed in. And the person has to already be an owner, an admin, or an approved follower of your family.
A signed-out visitor on a shareable list gets a plain link to the store. No panel, no address. A signed-in person who is not a follower yet gets a request-to-follow prompt instead, and that request comes to you for approval before they see anything more.
The net effect is simple. The only people who ever see your address are people you already said yes to, at the moment they are buying you something.
Built to be copied, not to be read
The address renders as labeled, read-only fields with a copy button on each one: street address, unit, city, region, postal code, country.
Read-only means a guest can copy a line straight into a checkout form and cannot accidentally edit your list while they are at it.
The section is titled with the first names of your family's owner and admins, so the buyer knows whose doorstep this is.
And if no street address is saved, the section does not render at all. There is no empty "address" heading sitting there advertising a blank.
A separate line for who the box is addressed to
The setup form asks for a RECIPIENT FIRST NAME and LAST NAME as their own fields, apart from the street address.
This is the "address it to Sammy, not to me" line. It is useful when the list is for a baby who does not have a mailbox yet, or when the household name and the shipping name are simply not the same.
Both are required once you have turned the address on for a list that is live. They are stored with the list, and they are cleared alongside everything else when you turn the address off.
The form speaks your country's language
Country is a full country picker, searchable, not a US-only dropdown.
Pick the United States and the field is labeled STATE, chosen from a real state list, with ZIP CODE beside it. Pick Canada and it becomes PROVINCE OR TERRITORY, from a real province list, with POSTAL CODE. Anywhere else and it is a free-text REGION with POSTAL CODE.
The same labels follow through to the buyer's copy panel. Someone shipping to Ontario sees "PROVINCE/TERRITORY," not a confusing "state" box.
Your profile's city, region, and country pre-fill a new list to save you some typing. Your street address is never guessed for you. You type it, deliberately, or you do not type it at all.
Lists made by the browser add-on start closed
Items saved from the Belovity browser add-on can create a new gift list on the fly.
Lists created that way start with the address turned off and switched off from public view. They are drafts.
You decide about the address when you open the list and finish it, not as a side effect of saving a stroller you liked.
What never touches the address
Notification emails and web push about your list never contain it.
Your private "Gifts Received" view, the one showing who bought what along with their name and note, never contains it either.
Usage analytics record only whether an address line was filled in, never what it says.
And changes to your gift lists are recorded in an audit trail, so you can see what changed and when.
The layers behind it
The address setting does not stand alone.
A gift list that is switched off is invisible to followers regardless of the address setting. A list with no published items is invisible to followers too, so drafts do not leak.
A private family page turns strangers away entirely, which means the address question never even arises for them. Search visibility is a separate setting again: a private or hidden page tells search engines not to list it and not to follow it.
Every one of these is checked when the page loads, not just when a button is drawn.
Three setups that actually happen
The baby shower list
Address: Yes. The gifts need somewhere to go.
The page is followers only, with each request approved by you. The recipient line carries the baby's name, so boxes arrive addressed correctly.
After the shower, switch the address to No and save. It is cleared.
The birthday wish list
Address: No.
Family already knows where you live, or they are handing gifts over in person anyway.
Guests still browse, still buy, and still mark items purchased so you do not end up with three of the same blender. Nothing on the page tells a distant relative's forwarded-link recipient where you are.
The two-list household
Baby shower list: address Yes, visible to approved followers. Birthday wish list: address No, same family page, same followers.
Same account, two different answers, and no setting anywhere that forces them to match.
Running more than one gift list at a time requires a plan that allows it, so this is the one setup here that depends on your plan.
Audit your current registry in five minutes
Open your registry in a private window while signed out. Is your street address on the page?
If it is, count the clicks it took to get there.
Look for the address setting. Is it attached to the list, or to your account?
Make a second list. Does it inherit the address whether you wanted it to or not?
Turn the address off. Then check whether the site says it removed the address or just hid it.
Ask who has to be signed in to see it. If the answer is "nobody," the answer is "everybody."
Close
Your address is not a profile field. It is a decision you make once per list, for one occasion, for one set of people.
Hidden, your list still does its whole job. People browse, buy, and mark things purchased.
Shown, it reaches a signed-in person you already approved, at the moment they are checking out, in fields built to be copied and then forgotten.
Either way, it is never a standing public notice of where a newborn sleeps.
Create your family page, build your first gift list, and answer the address question yourself. One list at a time.
