How Privacy Actually Works
"Private" can mean different things on different platforms. Here's what to look for.
Architectural privacy vs. opt-in privacy
Some platforms allow privacy as a setting — you can toggle off public discovery, hide from search engines, or password-protect a campaign. The request still technically exists in the public-facing system; you've just turned off the visibility flags.
Architectural privacy is different. The request is built private from the start. There's no public profile to disable, no directory listing to hide, no SEO index to remove. Instead, the request reaches people only through a unique link the requester hands out directly. Platforms like A Better Gift use this approach.
The practical difference: opt-in privacy can be reversed (intentionally or accidentally — by a settings change, a platform update, or a UI mistake). Architectural privacy can't, because there's nothing to reverse.
What "not indexed by search engines" means
When a webpage is "indexed," Google's automated crawlers have read it and added it to their database, where it can appear in search results. When a page is not indexed, it doesn't appear in Google searches even if someone types the exact text from the page.
Properly-built private fundraising platforms send signals to search engines (via robots.txt directives and meta tags) telling crawlers not to index private requests. Combined with no-public-listing architecture, this means a private fundraising request can't be found through search.
What contributors see
When a contributor receives a private fundraising link, they see the request page just like they would on any platform — story, goal, contribution form. What they don't see is a community feed, related campaigns, "discover other causes" sidebars, or any path to other private requests. The page exists in isolation.
This matters for the requester's privacy. Contributors can't browse their friend's "fundraising history" or see what else they've created.